Pay by Milestones
Stage 0 is free. Then the project is divided into 4 paid stages: each next one starts only after acceptance of the previous one and prepayment for the new stage. If the result doesn't fit — we refine it within the agreed scope.
Process
How we work on a project
A transparent process from the first call to launch and support. Clear stages, specific results after each, and a predictable payment scheme: we launch a new stage after acceptance of the previous one and prepayment of the next.
Straight to business
What's important to know right away
There's no upfront payment for the entire project, no floating estimates, and no lock-in to our infrastructure. We fix basic conditions in advance.
Fixed Estimate
The price and scope of work are fixed in the contract after the audit. Additional tasks are only with your consent and separate estimation. No hidden bills.
Source Code is Yours
Upon project completion, all source code is transferred to you. You are the sole owner of the development. No lock-in to our infrastructure.
5 Stages
Working Stages
From the first conversation to post-launch support. For each stage, the timeframe, result format, and acceptance criteria are known in advance.
Stage 0
Intro and Discussion
Duration: 1 meeting 30-60 minutes
Cost: Free
First call without obligations. We get to know each other, listen to your challenge, discuss preliminary solution ideas, and see if we're a good fit. If the task is interesting and clear, we move to the next stage.
At the end of this stage, we decide if it makes sense to go into deep audit and design.
What you get
- 1Understanding if we can be useful.
- 1If yes — a rough project estimate and action plan.
Stage 1
Audit and Design
Duration: 1-3 weeks
Cost: Fixed prepayment before the stage starts
We dive deep into the task: interviews with process owners, audit of current systems, data study. We design the solution architecture, collect technical requirements, and fix the scope of work and deadlines.
At the end of this stage, you decide whether to proceed or not. If not, you take all materials and can use them with any other contractor.
What you get
- 2Technical document describing the solution (PDF).
- 2Architectural diagram.
- 2Roadmap with stages and milestones.
- 2Fixed estimate for development.
- 2List of risks and assumptions.
Stage 2
Development
Duration: From 1 to 6 months
Cost: Prepayment before the agreed development stage starts
We implement the agreed scope of work iteratively. Every 1-2 weeks — a working increment with a demo. You see progress in real-time, provide feedback, and we adjust direction.
At the end of this stage, we conduct acceptance testing. If accepted, we move to launch. If not, we refine it to the agreed state.
What you get
- 3Working product on a test environment.
- 3Access to the code in the repository from day one.
- 3API documentation and deployment instructions.
- 3Regular demos of the results.
- 3Weekly progress reports.
Stage 3
Production Launch
Duration: 1-3 weeks
Cost: Prepayment before the launch stage starts
We prepare the solution for production: data migration from old systems, load testing, setting up monitoring, backups, and logging. We launch the solution gradually, with a quick rollback capability.
After launch, we ensure stable operation, rollback procedures, and a list of operational actions for your team.
What you get
- 4Solution deployed to production.
- 4Configured monitoring and automatic backups.
- 4Operations documentation (runbook).
- 4Transfer of access and infrastructure.
Stage 4
Training and Support
Duration: 1-2 weeks + optional support
Cost: Prepayment before training starts
We train your team to work with the solution. We conduct sessions for users and administrators. We support the first weeks of operation so the team enters the new process confidently.
Afterward, you can either complete the project with a full set of artifacts or transition to regular support and development.
What you get
- 5Training sessions for users and admins.
- 5Written instructions and regulations.
- 5Answers to team questions in the first weeks.
- 5Optional SLA contract for further support.
Finance
How payment is structured
We split the project cost into stages and link payment to clear milestones. Stage 0 is free, and each subsequent one is paid in advance before starting. We start a new stage only after you accept the result of the previous one.
1
Stage 0: Introduction → free
2
Stage 1: Audit and Design → 100% prepayment before stage starts
3
Stage 2: Development → prepayment before the agreed development stage starts
4
Stage 3: Launch → 100% prepayment before release work starts
5
Stage 4: Training → 100% prepayment before training sessions start
6
Support → separate SLA contract per month, quarter, or year
What is fixed in the contract
The exact distribution and amounts are fixed in the contract after the audit. All payments are under an official contract, bills are issued before the start of the relevant stage.
If new tasks appear, we don't quietly include them in the bill. First, we provide an estimate of the impact on deadlines and budget, then formalize a separate agreement.
Communication
Communication and Transparency
We don't disappear and don't work in a black box. You see progress in real-time and can contact the team at any moment.
Project Telegram/Bitrix Chat
A shared chat with you and the team. Quick questions, statuses, operational communication. We respond during business hours within 5-10 minutes.
Weekly Demos
Every Friday for 30 minutes — we show the week's result, discuss priorities for the next one, and answer questions.
Dedicated Project Space
All artifacts in one place: requirements, architecture, design, roadmap, task statuses. Full access for your team.
Access to Code and Tasks
From day one — access to the repository on GitHub/GitLab and the task board. You see every commit and every closed task.
Roles
What's needed from you for project success
A good project is always a joint effort. We're not developers you just 'throw a spec at and forget' — we need your involvement. Here's what we ask from your side.
One person from the business side — your product owner. They make product decisions, answer team questions, and approve stage results. Without a dedicated person, projects stall.
Readiness for 1-2 meetings a week — short syncs, demos, priority discussions. Usually 1-2 hours a week from your side.
Access to the right people and systems — sometimes we need to talk to the sales head, see how the existing system works, or get test data. Help the team with this.
Quick feedback — after a demo or document approval, it's best to provide comments within 2-3 days. If waiting for weeks, the project will stall.
Readiness to make decisions — sometimes you need to choose between two options. Readiness to say 'let's do it this way' instead of 'let's think more' is critical for speed.
After Launch
Post-Launch Support and Development
Launch is not the end, but the beginning of operation. We offer several collaboration formats after the main project is completed.
Warranty Period
Included in the project cost
The first month after launch — free bug fixes related to the agreed functionality. Response within 30 minutes during business hours.
SLA Support
Separate contract
Ongoing support with a fixed response time for incidents, planned dependency updates, monitoring, and redundancy. Suitable for projects where downtime is critical.
Product Development
Separate projects or retainer
We refine the product as the business grows. New features, integrations, process restructuring. We can work in sprints or by the hour depending on the volume.
Need support after launch
If the project is business-critical, it's better to discuss the SLA format and incident escalation scheme in advance.
Complex Cases
How we handle problems
In real-world development, something always goes not according to plan. Requirements change, unexpected complexities appear, business changes priorities. Here's how we handle it.
What if during the audit it turns out the task is bigger than it seemed initially?
We speak openly about it right away, provide justification, and offer options: reduce the scope of the first version, increase the budget, or split into several projects. The decision is always yours.
What if we want to change requirements in the middle of development?
This is normal and we're ready for it. Small changes are added to the current sprint, large ones — we discuss the impact on deadlines and budget, and formalize it with a contract addendum.
What if we can't meet the agreed deadline?
If the delay is our fault, we finish at our expense. If it's due to scope changes or waiting for decisions from your side, deadlines are shifted with notification.
What if the stage result doesn't fit?
We refine it to the agreed state within the stage budget. If the task turns out to be fundamentally unsolvable in the chosen architecture, we discuss options up to refunding for the stage and terminating the contract.
Tell us about your project
A quick intro and initial ideas. Free, no strings attached.
1
Inquiry
2
Conversation
3
Estimate
Book a conversation
or email us directly: hello@digitalkitty.studio