Loading page…
Web apps & MVPs
If your idea needs people to sign in, keep their own data, pay you, or check a dashboard, a brochure website won't do it — you need a web app. We build MVPs and internal tools for Australian founders and business owners, and the written scope you sign off on is the same document the quote is priced against. This page covers how we keep a first version small enough to launch, and what happens once it's live.
A website tells people about your business. A web app does work for them: it remembers who they are, holds their records, takes their money, and shows them where things stand. The moment your idea involves user accounts, a database, payments, or a dashboard, you've crossed from one to the other. Everything on this page is about that second kind of build.
The usual reason a web app project blows out is that the feature list keeps getting longer after the price is set. We prevent that by deciding, before work starts, exactly what version one does and what it deliberately doesn't. That written scope is what the fixed quote covers, and it's what you sign off on. Anything outside it isn't refused — it's quoted separately, so the original budget and launch date stay intact.
Launch isn't the day the last feature is finished; it's the day real people can use the app without you sitting beside them. We work backwards from that. Early on you get a clickable mock-up to react to, and well before the end you get login details for the real build so you can try each feature as it lands. The final stretch is testing, deployment, and making sure whoever runs the app day to day knows where everything is.
A v1 that launches is the start, not the end, and we plan for that during the build. The parked feature list from discovery becomes the natural roadmap for a second phase. Whether we do that work or someone else does is entirely your call, because nothing — code, data, hosting, or domain — is registered to us.
We build web apps in Next.js and TypeScript on top of Postgres, usually through Supabase, and use .NET where a heavier back end is warranted. None of that needs to mean anything to you, and that's the point: these are common, well-documented tools that any experienced developer can pick up. It means you're never locked into us, and it means your app is built with the same tools we use for our own products — Reckonly, Near Space, Inferly, and Scentena.
Start a project
Tell us what you need and get a proper plan back — usually within one business day.
Three short steps in your own words. No specs, no jargon, no forms that assume you already know what you need.
Every submission is screened for safety and legitimacy before it reaches our team — so real clients get a fast answer and nobody else gets through.
Scope, user stories, acceptance criteria, risks, and the questions worth asking — prepared for you, so we both start from the same understanding.
A clear quote with milestones you can accept or counter, then a plain-English contract you sign online. No surprises, no lock-in.
You'll create a free account first — it's how we keep your project details private and your contract tied to you.
A first version starts from A$2,500; builds with several user types, payment flows, or third-party integrations tend to land as a Custom Engagement from A$4,500. Either way, the figure you get after the free 30-minute consultation is a fixed quote tied to a written scope, not an estimate. If what you actually need is a marketing site with a contact form, a Starter Website from A$900 will serve you better.
Small enough that one type of user can complete one valuable task from start to finish — sign up, do the thing, pay or see the result. If a feature isn't required for that loop, it goes on the after-launch list. Scentena, for example, runs with no user accounts at all, because the formula builder is the whole point.
Yes, and it's often the better first project: the users are your own staff, the requirements are clearer, and the return shows up as hours saved every week. Typical examples are approval queues, job trackers, and admin screens that replace a shared spreadsheet. The same scope, quote, and handoff process applies.
For content, prices, and settings, yes — the admin area is built so you don't need a developer for everyday changes. New features or changes to how the app works are development work, which we quote as a second phase or handle under a maintenance plan when they're small.
No. Once the final invoice is paid there are no ongoing fees to us unless you choose a maintenance plan. Hosting and payment-provider fees are billed to you directly, because those accounts were opened in your name.