01
How many roles act in the first release.
SaaS development for the first working release
A web product with accounts, roles and a first workflow. A full SaaS is estimated separately from a focused MVP.
A SaaS is a web product people log into. The starting MVP price, from A$15,000 + GST, covers one core journey. Accounts for several roles, billing and a large admin area are a wider product and get their own estimate.
We build the first usable slice of a SaaS: sign-in, the core job, and an admin view. The rest of the catalogue waits.
The useful first release is the job a customer must be able to finish, plus the smallest admin view you need to operate it. Extra plans, teams and integrations are easier to add after that path is real. We use a TypeScript web stack and hand over the repository.
What changes the estimate
02
Whether billing is in this version or the next.
03
Which external services must connect on day one.
What the first SaaS release costs
A focused MVP from A$15,000 + GST is one journey. A SaaS with several roles, billing and a large admin area is a wider product and gets its own estimate.
What changes the price
The estimate follows who logs in, what they must finish, and which services connect on day one. We do not hide a full catalogue inside the starting price.
- Roles in the first release
- Billing and plans
- Admin screens you need to operate
- External APIs and data migration
What ships first
The first release is the workflow that proves the product. Extra modules stay on a list you can see.
- One workflow is named before development
- You use a working build every week
- Later modules are estimated on their own
How we shape the first release
- 01
One job
We name the workflow the product must prove.
- 02
Roles
Only the roles in that workflow enter the estimate.
- 03
Weekly demos
You use a working build while the rest is still a list.
- 04
Handover
The code and the admin access pass to you.
Who this is for
- A product people will log into
- A team that should not build every module first
- A business that needs an admin view early
- A founder who wants to own the codebase
What the first slice includes
- Sign-in and the roles the first release needs
- One core workflow, not every future screen
- A small admin view for early operations
- The source code on your side
What you receive
- A working first workflow
- Accounts for the agreed roles
- A small admin area
- The repository and a note of what waits
Questions about a first SaaS release
Scope, billing and ownership.
Is A$15,000 a full SaaS?
No. That price is a focused MVP with one core journey and no heavy integrations. Several roles, billing and a large admin area are estimated separately.
Do you build billing in the first release?
Only if the first workflow needs it. Otherwise billing waits, and the estimate says so.
Who owns the product?
You do. The repository, documentation and access are handed over. The product is not locked to a closed Inu-apps platform.
Can this start from a web app you already have?
Yes. We read the code first and propose what the next release should change.
Describe the first workflow
Tell us who logs in and what they must finish. We will separate that path from the later SaaS roadmap.
Contact page
