Four phases, a fixed price on each, and working software on a URL from the first sprint. This page is the whole method — so you know what you are buying before the first call.
The short version
Each phase ends with something you can hold — a document, a prototype, a release. If a phase does not produce that, it has not finished.
2–5 days
A working session — not a sales call — to map the problem, the users, the constraints and the things that must not break. We come back with what it takes to build, in writing.
What we need from you — Two hours from whoever knows how the process really works today.
1–2 weeks
Data model, API contract and clickable screens for the journeys that matter. Expensive decisions get made on cheap artefacts, while changing them still costs an afternoon.
What we need from you — One review session and a decision on anything we flag as a fork in the road.
4–12 weeks
Two-week sprints, a demo at the end of every one, and a staging URL that is always current. The board is open to you — there is no weekly status theatre to sit through.
What we need from you — One decision-maker who can answer a question within a day, and an hour a week for the demo.
Ongoing
Production hardening, monitoring and a handover built for people who were not in the room. Then we tune what real usage teaches us — because the first week of real traffic teaches more than the whole build.
What we need from you — A go-live date, and the people who will operate it for a two-hour walkthrough.
Delivery goes wrong quietly, in the weeks nobody reports on. This is the rhythm that keeps it visible.
Monday
We agree what lands in the next two weeks and what is deliberately not in it. You get the list before work starts.
Every day
What moved, what is blocked, what needs a decision from you — in the shared channel, not in a meeting.
Any day
Every merged change deploys to staging automatically. You can open the product whenever you want proof.
Friday, week two
Thirty minutes of working software, recorded if you cannot attend, followed by the plan for the next sprint.
Pick the shape that matches the problem. Most clients start with one and move to another once the first release is live.
A defined product, MVP or module with a deadline
A written scope and a fixed price per phase. If the scope does not move, the number does not move.
Typically 4–12 weeks
An ongoing roadmap, or extending an in-house team
One or more senior engineers reserved for you each month, working inside your board, repository and rituals.
Monthly, 30 days' notice
A product that is slow, fragile or unowned
A paid audit first: architecture, data model, security and delivery risk in a written report you keep whatever you decide next.
1–2 weeks to the report
We do not publish a price list, because a number without a scope is a guess. We do publish how we arrive at one.
You never wait for a milestone to see the product. Whatever is merged is live on staging within minutes.
Every change runs the suite and gets a preview environment. Deploys are reversible, so releases stop being events.
Core Web Vitals and WCAG checks sit in the sprint definition of done, not in a clean-up phase nobody funds.
Repositories, cloud accounts, domains and model keys are created in your name. There is nothing to hand over because nothing was ever ours.
The first 30-minute call and the written estimate that follows are free. A full discovery — the working session, the architecture sketch and the phased scope — is a small fixed fee that is credited against the build if you continue with us. The document is yours either way.
Anything not yet started can be reordered at a sprint boundary at no cost. Genuinely new work is priced as a change note before it is started, so you approve the number first. Nothing is added silently and billed later.
Fixed-scope work pauses at a sprint boundary with everything delivered to date deployed and documented. Dedicated-squad engagements run monthly with 30 days' notice. In both cases you keep the code, the accounts and the documentation.
Fixed price per phase against a written scope for project work, and a flat monthly rate for dedicated squads. We do not bill open-ended hours, because it puts the risk of our estimating mistakes on you.
The senior engineers who scoped it. There is no hand-off to a junior bench once the contract is signed, and you meet the people on the discovery call — the same faces stay through launch and support.
You hear it in the sprint it happens, not at the end of the project. We say what slipped, why, and what we are cutting or re-sequencing to protect the date — before you have to ask.
Thirty minutes, the engineer who would build it, and a written scope in your inbox within two working days.
Mon–Sat, 9:00–19:00 PKT (overlaps GST, AST and CET business hours)