Skip to content
TRDThe Research Desk, home

02 · Software

SaaS development with the architecture decided up front

Decisions made in the first weeks of a SaaS build (tenancy, permissions, billing, data model) are the expensive ones to undo later. We make them deliberately, write them down, and build an MVP that can become the product rather than be thrown away.
Discuss your software requirements (opens WhatsApp in a new tab)Send a written brief

Free first conversation · No obligation · You own the code

§ 01Is this you?

You're likely in the right place if…

  • 01You have validated demand and need a product, not a prototype.
  • 02An internal tool you built works well and other businesses want it.
  • 03Your current MVP can't support multiple customers safely.

Sound familiar? Tell us which one on WhatsApp (opens in a new tab) and we'll suggest where to start.

§ 02Deliverables

What we build

  1. 01

    MVP builds

    The smallest version that real customers can pay for, built on a foundation that scales.

  2. 02

    Multi-tenant architecture

    Tenant isolation enforced in the database with row-level security, not just in the interface.

  3. 03

    Auth and roles

    Sign-up, invites, organisations and role-based permissions, including an internal admin console.

  4. 04

    Billing

    Stripe subscriptions, trials, usage limits and invoices, with webhooks handled idempotently.

  5. 05

    APIs

    Documented APIs for your frontend, mobile apps and partners.

§ 03Approach

How we build it

  1. Architecture document first

    Data model, tenancy, permissions and integrations are specified and agreed before sprint one.

  2. Typical timelines

    MVPs usually take 4–10 weeks; a full production platform 3–6 months. Your written scope gives the real estimate.

  3. Production from day one

    Environments, migrations, backups and error monitoring are set up at the start, not added before launch.

Typical stack

  • Next.js
  • TypeScript
  • PostgreSQL
  • Supabase
  • Stripe
  • Vercel
  • Tailwind CSS
§ 04FAQ

Questions about saas development

01Do we own the code and the infrastructure?

Yes. Repositories, hosting and third-party accounts are created in your name or transferred to you at handover.

02Can you take over an existing SaaS codebase?

Yes, after a paid code and architecture review so we can quote the work honestly.

03Can you build our MVP quickly and improve it later?

Yes, and we build it so it can grow: the data model, permissions and billing are designed properly from the start so later features don't require a rewrite.

04How do you keep customers' data separate?

Each record belongs to a tenant, and separation is enforced by row-level security in the database, not only in the interface. We test that one customer can't read another's data.

05Can you handle subscriptions and payments?

Yes. We integrate Stripe for plans, trials, upgrades, invoices and failed-payment handling, with webhooks processed safely so no payment is counted twice.

06What happens after launch?

We can continue with ongoing development and support, or hand everything to your own team with documentation. Either way the code, hosting and accounts are yours.

07How is the price decided?

After a short study of your process we send a written scope with fixed deliverables, timeline and price. Nothing is charged before you approve it; payment is typically 50% to start and 50% on delivery.

08Who owns the work when it's finished?

You do. Code, accounts and documentation are handed over in your name once the project is paid.

Often combined with

Next step

Ready to talk about saas development?

Describe the system you need, or the spreadsheet you've outgrown. We'll ask the right questions and reply with a sensible first version.

Free first conversation · No obligation · NDA on request

Discuss your software requirements (opens WhatsApp in a new tab)Send a written brief