Multi-tenant apps, hand-coded.
Web applications with real auth, real billing, real admin, real integrations. Built so the second hire on your team can actually read the codebase.
- Starting at
- $60k
- Structure
- Phase-by-phase quote, fixed bid
What you get for the work.
- 01
Real auth, day one
Multi-tenant from the start. Roles, invites, audit trail. NextAuth or Clerk, with the seams in your codebase rather than a black box.
- 02
Billing that holds up
Stripe subscriptions, metered usage, proration, dunning. Tested against a real failure-case suite so you don't lose revenue to an edge case.
- 03
Admin from sprint one
An internal admin gets built alongside the app, not bolted on after support tickets start. You can see and edit every record in your data.
- 04
Owned by you
Schema, migrations, deploy keys, observability. All in your accounts. We work for you, the code does too.
What we build it on.
- Nuxt 3 or Next.js
- SSR-first. Choice depends on your stack and your team.
- TypeScript strict
- Types derived from schema, no any escapes.
- Drizzle or Prisma + Postgres
- Migrations checked in, no manual schema drift.
- NextAuth / Clerk / Better Auth
- Multi-tenant patterns from day one.
- Stripe Billing
- Subscriptions, metered usage, customer portal.
- Sentry, Datadog, Better Stack
- Errors, traces, uptime. All set up at launch.
$60k buys this. Bigger scope scales it.
Included at the floor
- Multi-tenant data model with org + user + roles
- Auth (email + OAuth) and team invites
- Stripe Billing with one to two plan tiers
- Internal admin scaffolding for support and ops
- Errors, traces, uptime monitoring at launch
- One core feature loop (the thing the app actually does) end-to-end
What scales the number
- Multiple feature loops with cross-team workflows
- Real-time collaboration (presence, cursors, shared state)
- Public API and webhook system for customer integrations
- SSO, SCIM, audit logging for enterprise plans
- Mobile companion app (see Mobile)
What a starter SaaS build looks like
The $60k floor covers a multi-tenant data model, auth with invites, Stripe billing, an internal admin scaffold, and one core feature loop fully built. Eight to twelve weeks. The point is to land at a working app one user could actually pay for, with the seams in place to grow from there.
Where the build scales
Multiple feature loops is the most common scaler. Each new loop usually touches the data model, the UI, billing, and admin, so the cost is not linear. Real-time collaboration is a step change in complexity. Public APIs and webhooks add their own contracts to maintain. Enterprise plans (SSO, SCIM, audit) are usually deferred to a separate phase.
What we will not build
SaaS that bets the company on a feature no user has asked for. SaaS without billing. Apps where the founder cannot describe the first paying user. Anything where the build is the cheap part and the distribution is unsolved.
Common questions.
- What stage of company is this for?
- Founders going from spec to first paying customer, or teams whose v1 was built fast and now needs to actually work. We are not the right shop if you already have ten engineers shipping daily.
- How do you split the build from the design?
- Discovery and design phases come first. We do not write code against unsolved problems. Once the screens are signed off the build is mostly mechanical.
- Can we hand off mid-build?
- Yes. Every milestone is a working app. You can stop after design, after the first feature loop, or after launch and we hand off the codebase as-is.
- Why Nuxt or Next instead of Rails or Django?
- We are faster in TypeScript and the audience usually has TypeScript people on hand for the next hire. We will write Python or Rails for the right project but it is not our default.
- How does enterprise stuff fit in?
- SSO, SCIM, and audit logs are a real chapter, not a checkbox. We sequence them after product-market fit. Building enterprise-features-first is a common reason for SaaS projects to die.
- What about AI in the app?
- See AI integrations. Adding LLM features to an existing SaaS is its own scope. We will tell you when AI is the right shape and when it is not.
Pair this build with.
Build this with us.
Twenty minutes through the intake. A real reply within a work day.