Custom Build Sprint
Fixed scope, fixed price, 2–4 weeks. Owned software instead of an open-ended retainer.
Useful when replacing: the retainer that never ends
Pricing · USD
Service
from $990 fixed
Repository, deployment assets, and the licence agreed in scope are handed over.
What you get
per week · you own it
The people, cadence, and deliverables stated in the offer.
Pilot Week $990; sprints $1.9k–$9.9k over 2–4+ weeks. Built on our own proven components, so you launch faster. Ongoing hosting and maintenance is an optional flat add-on from $49/mo — never a default retainer, cancellable any month, and the software keeps running because you own it. India-registered startups pay INR parity. Scoped and disclosed before you commit.
Inside Custom Build Sprint
The problem
Custom software usually means an hourly engagement with a drifting scope and an invoice that grows to fill the quarter. You need a feature, an integration, or an internal tool — not a standing meeting.
How Custom Build Sprint solves it
Scoped and priced before work starts
A one-page scope with a number on it. Changes are re-quoted explicitly — never absorbed into a drifting invoice.
Code in your repo from week one
MIT-licensed deliverables in your GitHub org from the first commit. If we disappear, you lose a vendor, not your product.
Ends on purpose
A sprint has a last day. Ongoing help is an optional flat-priced add-on, never a default retainer.
Delivery terms — stated precisely
How Custom Build Sprint is delivered, what you control, and where the boundaries sit.
Customer-owned deliverables
Repository, deployment assets, and the licence agreed in scope are handed over.
Data and hosting
Deploy in your cloud or use the stated optional managed-hosting plan. Data location and operator access are agreed before production use.
Compliance boundary
Residency, controls, and regulatory requirements are implementation decisions documented in the selected plan or delivery scope.
Built on
Custom Build Sprint — the questions buyers ask
Who owns the code and IP?
For a Build Sprint, the repository, deployment assets, and work-product IP described in the SOW are handed over to you. Pre-existing products retain the licence shown on their product page; hosted services remain services. We state that boundary before work starts.
What happens if a sprint misses its scope?
We finish it. Fixed price means the risk of estimation is ours, not yours — a missed scope item is completed without a new invoice. Changes you request are re-scoped explicitly, so the line between 'our miss' and 'new ask' stays honest.
How do time zones work with a pod in India?
Every engagement includes 4+ hours of overlap with US or EU working hours. Async by default — written updates, weekly clickable demos — and meetings only when they earn the slot. You'll never chase a status report.
How is our data and code kept secure?
Work happens in your repos and your infrastructure wherever possible — we hold the minimum access needed, revoked at handover. NDAs are standard on request, and everything we self-host for you runs behind your keys, not ours.
How fast can you actually start?
Scoping takes a day; most sprints start within a week of sign-off. Pods are deliberately small and senior, so your start date is confirmed in the sprint plan — not left floating.
Do we need a retainer afterwards?
No — that's the point. A sprint ends with handover docs and training. If you want us to keep maintaining what we built, that's an optional flat monthly add-on you can cancel any month, because the software keeps working without us.
Put a number on what you need.
See the price, deploy on your infrastructure, keep the code. Or scope a sprint and we'll customise it and hand it over.