SaaS development

SaaS development by a team that runs its own SaaS products

Plenty of agencies can build a SaaS. Far fewer have to run one afterwards. We build and operate three of our own, so we design for what matters after launch: billing that's always right, onboarding that converts and code that stays easy to change.

  • Subscriptions, usage-based credits and Stripe Tax, built and running
  • Teams, roles and separated customer data from day one
  • Multilingual from the start, with SEO and analytics wired in
Twelve Lumens app: a property with its rooms sorted automatically, each photo staged in the Modern style, with plan usage in the sidebar
What we can build

Everything a SaaS needs, not just the screens

The features users see are half the work. The other half is what turns a SaaS into a business: billing, accounts, limits, emails, analytics and operations. We build both halves.

Subscriptions and usage billing

Stripe Checkout and the customer portal, monthly and annual plans, usage allowances or credit packs, Stripe Tax and VAT IDs, trials, discounts and properly handled webhooks.

Accounts, teams and roles

Sign-up with email or Google, organisations with owner, admin, editor and viewer roles, invites, and every query scoped to the right workspace.

Plan limits and fair use

Entitlements per plan, live usage meters, automatic refunds when a job fails, and protection against trial abuse and traffic spikes.

Onboarding and lifecycle email

Transactional mail plus flows that react to what users do: a nudge when they stall, a trial offer when they run out, a check-in after their first result.

Multilingual product and marketing

Native copy per language, translated URLs, hreflang and prices in euros or dollars, so you can sell in more than one market from day one.

Hosting, monitoring and backups

Zero-downtime container deploys, error tracking, product analytics, encrypted off-site database backups and a firewall that only admits Cloudflare.

Proof, not promises

Three SaaS products, built and run by us

Postcrest is an AI content and scheduling platform we've been building since 2023, with subscriptions, metered credits and automated handling of trials and payment disputes. Twelve Lumens (AI virtual staging) and Salestreak (multichannel selling) launched in 2026 on the same foundation.

Because we run them ourselves, the patterns on this page are proven in production: real payments, real webhooks, real traffic. Not a demo environment.

  • Between 1,400 and 1,900 automated tests per product, plus security and dependency checks in CI
  • Container deploys with Kamal on European servers (Hetzner) behind Cloudflare
  • Continuous, encrypted database backups to two storage providers, checked every week
  • Usage-based billing where users see the cost before they start, and failed jobs are never charged
  • Product analytics, error tracking and server-side ad conversion tracking built in
Postcrest pricing breakdown before generating a video: 225 credits for a five-second 1080p clip
Usage-based billing in Postcrest: the cost of every run is shown before you click.
Twelve Lumens export dialog with file format, watermark options and a built-in AI disclosure template
Plan features in practice: export formats, watermarks and disclosure templates in Twelve Lumens.
SaaS products we run ourselves
3
commits on our oldest product
1,700+
languages in our newest products
5
automated tests per product
1,400+
Who it's for

Who we build SaaS for

Founders launching a first product

You know the market and maybe have a waiting list. We turn it into a focused first version with billing in place, so you learn from paying users early.

SMEs turning know-how into software

Your team has a process, calculation or service customers would pay to use themselves. We package it as a subscription product.

Teams replacing a fragile first version

The no-code MVP or a freelancer's prototype got you here, but it won't carry you further. We rebuild what matters and move your users over without drama.

Companies adding AI to their offer

You want an AI feature customers pay for, with usage limits and costs under control. We've built exactly that, three times.

How it works

How we build your SaaS

In small, visible steps, with the commercial basics in place before the nice-to-haves.

  1. 1

    Scope the smallest sellable version

    Who pays, for what, and what the first version must do to earn that. Everything else goes on a list for later.

  2. 2

    Foundations first

    Accounts, teams, billing, plan limits and analytics go in early. Retrofitting them later costs far more.

  3. 3

    Build the core in short increments

    You see working software early and often, and steer as we go. No months of silence.

  4. 4

    Launch with measurement

    Product analytics, error tracking and conversion tracking from the first user, so decisions rest on data.

  5. 5

    Operate and harden

    Backups, monitoring, security updates and performance work, so the product keeps running while you sell it.

  6. 6

    Grow the product

    New plans, languages, integrations and AI features, prioritised by what users actually do.

A stack that lasts and is easy to hand over

We usually build with Ruby on Rails and Hotwire on PostgreSQL: one codebase, quick to change, cheap to host and easy for another team to take over later.

  • Ruby on Rails
  • Hotwire
  • PostgreSQL
  • Solid Queue
  • Tailwind CSS
  • Stripe
  • PostHog
  • Sentry
  • Kamal
  • Docker
  • Hetzner
  • Cloudflare
Cost & timeline

What does SaaS development cost?

There's no honest price without a scope, but what drives the price is predictable. These five factors weigh most:

Scope of the first version
The number of core workflows a paying user needs on day one. Cutting here is the fastest way to launch sooner and spend less.
Billing model
A single subscription is simple. Usage-based credits, seats, add-ons or payouts to third parties need more logic and more testing.
Integrations
Every external system (payments, CRMs, APIs, AI providers) adds authentication, error handling and maintenance.
Languages and markets
A second language is more than translation: URLs, pricing, tax, emails and support all change with it.
Existing users and data
Moving off an old system or prototype without losing customers needs a careful plan. We include it upfront.
FAQ

Questions about SaaS development

How much does it cost to build a SaaS?

It depends mostly on the scope of the first version, the billing model and the number of integrations. After a free intro call you get a written scope and estimate, split into phases, so you know what the first launchable version costs before we start.

How long does it take to build a SaaS MVP?

That depends on how much the first version needs to do. We aim for the smallest version people will pay for, ship it in visible steps and plan the rest in phases. The estimate after the intro call includes a timeline per phase.

Which tech stack do you use for SaaS?

Usually Ruby on Rails with Hotwire and PostgreSQL, background jobs with Solid Queue, Stripe for billing and Cloudflare in front. It's the stack behind our own products: fast to build on, cheap to run and easy to hand over.

Can you build usage-based billing or credits?

Yes. We've built monthly and annual plans, usage allowances, credit packs that expire, live cost previews and automatic refunds when a job fails, all on Stripe.

Can you take over an existing SaaS or MVP?

Yes. We start with a review of the code, hosting and data, then propose what to keep, what to fix and what to rebuild. Migrations are planned so existing customers can keep working.

Do you also host and maintain the SaaS after launch?

We can. Our own products run on the same setup: container deploys, monitoring, error tracking and encrypted off-site backups. Or we hand everything over to your team, with documentation.

Do you work with startups outside the Netherlands?

Yes. We're based in the Netherlands and work with clients in English or Dutch, wherever they are.

Have a SaaS idea or an MVP to grow?

Tell us who it's for and what it should do. You'll get an honest view on scope, risks and the fastest route to paying users.

martin@balk.dev

Typically a reply within one business day.

Useful to mention

  • What you want to build, in a few sentences
  • Who is going to use it
  • Any deadline or launch date
  • Tools and systems it should connect to