Stage 01
Product & UX design
Discovery, user flows, a clickable prototype and the written specification that everything downstream is priced against.
→ DetailSaaS build service · Fixed scope, fixed price
Ship the product,
not the estimate.
Akontec designs, builds and launches SaaS products on a fixed-scope engagement. A short validation sprint produces the specification, the specification fixes the price, and anything outside it is quoted openly rather than absorbed into an overrun you find out about later.
Free scoping call · NDA on request · Code and IP yours from the first commit
Section 01 · The case
Most software projects
Most software projects
fail at the scope, not the code.
Engineering is rarely the reason a build goes wrong. The reason is that nobody wrote down precisely what was being built, so every week becomes a negotiation and every estimate becomes a rough guess defended after the fact.
The usual build
- Estimated in hours, billed in months
- Scope discovered during development
- “Small change” requests absorbed silently, then charged
- Timeline slips are reported at the demo
- Repository sits with the agency until final payment
- Handover is a ZIP file and a good-luck email
- Nobody can price the next phase either
The Akontec engagement
- Validation sprint first — specification before price
- Fixed scope, fixed price, fixed dates in a signed SOW
- Change requests quoted in writing before any work starts
- Weekly written build note, whether the week went well or not
- Your repository, your cloud account, from the first commit
- Documented handover plus 60 days of warranty
- Phase two priced from a spec, not from a feeling
30/30/30/10payment across signature, design, UAT and go-live
2–3 wksvalidation sprint before anything is quoted
60 daysdefect warranty after go-live
100%of code, IP and accounts owned by you
Section 02 · What we build
Four stages.
Four stages.
One accountable team.
You can buy any one of these on its own. Most products need the first two, and the ones that succeed commercially usually buy the third as well.
Stage 02
Engineering
Web app, mobile app, APIs, admin, billing and the cloud infrastructure underneath, built in your accounts and your repository.
→ DetailStage 03
Launch & go-to-market
Marketing site, pricing page, onboarding, analytics, billing configuration and the first ninety days of acquisition support.
→ DetailStage 04
Support & iteration
Monitoring, defect fixes, security patching and a monthly build allowance for the features your first real users ask for.
→ DetailTechnology choices you can hire for
We build on mainstream, well-documented stacks so your next developer is easy to find and not dependent on us. The stack →
Ownership settled before the first commit
Repository, cloud account, domains and IP in your name from day one, with assignment written into the contract. Ownership →
A specification you could hand to anyone
The validation sprint output is yours to keep even if you never build with us. The process →
Section 03 · Planning aid
Size your build
Size your build
before you call anyone.
Tick the modules your product needs. The output is an indicative range built from typical builds — not a quotation. The validation sprint is what turns it into a fixed number.
Every engagement includes the validation sprint, cloud setup, CI/CD, a test pass, documentation and a 60-day warranty. Those are not separate line items.
INDICATIVE ESTIMATE0 modules
Build window
—
Indicative fee range
—
Payment schedule
30/30/30/10
Warranty
60 days
Turn this into a fixed price →
Illustration only, not a quotation. Ranges exclude GST, third-party licences and cloud running costs, which are billed to your own accounts.
Section 04 · Process
Seven phases,
Seven phases,
and a gate at each one.
Every phase ends with something you sign. Nothing moves forward on a verbal “looks good”, because that is the sentence every disputed invoice starts with.
Phase 00 · Free
Scoping call
Forty-five minutes on the product, the users, the money model and the deadline. You get an honest read on whether it should be built at all, and whether we are the right people.
Phase 01 · 2–3 weeks
Validation sprint
Discovery workshops, user flows, a clickable prototype and a written functional specification. Gate: you sign off the spec. It is yours to keep either way.
Phase 02 · 3–5 days
Fixed-price SOW
Scope, deliverables, architecture, milestones, dates, acceptance criteria and one number. Gate: countersignature and the 30% mobilisation instalment.
Phase 03 · 1–2 weeks
Design & architecture
Full UI design, data model, API contract and infrastructure plan, in your accounts. Gate: design sign-off and the second instalment.
Phase 04 · Bulk of the build
Engineering sprints
Two-week sprints with a demo and a written build note at the end of each. Anything outside scope is raised as a priced change request before it is built.
Phase 05 · 1–2 weeks
UAT & hardening
You test against the acceptance criteria in the SOW. Defects are fixed at our cost; new ideas become phase two. Gate: UAT sign-off and the third instalment.
Phase 06 · Go-live
Launch & handover
Production deployment, monitoring, documentation, a walkthrough for your team and the 60-day warranty clock starts. Gate: final 10%.
Full process, change-control rules and acceptance criteria →
Section 05 · Pricing
Four shapes of
Four shapes of
engagement.
Indicative bands so you can size a business case. The binding number comes out of the validation sprint and is written into the Statement of Work.
01
Validation sprint
Spec, prototype and a fixed price for the build. Standalone — you can walk away with it.
₹1,25,000
02
MVP build
A real product in front of real users, with the modules that prove the idea and nothing that does not.
from ₹6,50,000
03
V1 platform
Billing, admin, integrations, mobile and the operational depth a paying customer base needs.
from ₹14,50,000
04
Support & iteration
Monitoring, fixes, patching and a monthly build allowance once you are live.
from ₹35,000 /mo
Section 06 · Deliverables
What you own
What you own
at the end.
Not a demo and an invoice. A working product plus everything needed to run, extend or hand it to another team without asking our permission.
- The full source repository, in your organisation account
- Cloud infrastructure in your own provider account
- Written functional specification and acceptance criteria
- UI design files with components and a style guide
- API documentation and a data model diagram
- Deployment and environment runbook
- CI/CD pipeline configuration
- Admin and operations manual for your team
- Test cases and the UAT results record
- Third-party account inventory with credentials handover
- A recorded walkthrough for whoever maintains it next
- Signed IP assignment covering everything built
Section 07 · Straight talk
What we will not promise.
Every Akontec proposal carries this section. Ask the same questions of whoever else is quoting you.
- We will not quote a fixed price before the validation sprint. A number given before the spec exists is a guess dressed as a commitment.
- We will not promise that your product will find customers. We can build it well and launch it properly; the market decides the rest.
- We will not absorb genuine scope changes silently and then argue about them at the end. They are quoted in writing, before the work.
- We will not hold your code, accounts or domains as leverage. They are yours throughout.
- We will not build something we think should not be built — we will tell you in the scoping call rather than take the money.
How can the price be fixed before you know what you are building?
It cannot, which is why the validation sprint comes first. Two to three weeks of discovery, prototyping and specification produce a document precise enough to price against. Only then do we issue a fixed-price Statement of Work. Anyone quoting a full build price off a one-hour call is guessing and will recover the difference later.
Who owns the code and the accounts?
You do, from the first commit. The repository is created in your organisation, the cloud infrastructure runs in your provider account, domains are registered in your name, and IP assignment is written into the contract rather than promised at handover.
What happens when we want a change mid-build?
You raise it, we assess it, and you get a written change request with the cost and the timeline impact before anything is built. You approve or decline. Nothing is absorbed quietly and nothing is invoiced as a surprise.
What if the build takes longer than you said?
If the overrun is ours, it is ours — the fixed price does not change. If it is caused by something on your side, such as a delayed sign-off or a third party we are waiting on, the timeline moves and we flag it in the week it happens rather than at the end.
Can you work with our existing codebase or team?
Yes. We take over existing products, build alongside an internal team, or deliver a defined module inside a larger system. Inherited code gets a short technical audit first, and we will tell you plainly if a rewrite is cheaper than a rescue.
What happens after launch?
Sixty days of defect warranty at no cost, then an optional support plan covering monitoring, patching, fixes and a monthly build allowance. Or you take it in-house entirely — the documentation and handover exist for exactly that.
Next step
Bring us the idea. We’ll bring back a scope you can hold us to.
A scoping call costs nothing and takes forty-five minutes. If the product does not need building yet, or needs building by someone else, we would rather say so in that call than three months into a contract.