Service / Independent specialist
SaaS development that ships and scales, not just demos
- Product scoping and architecture that won't need a rewrite in six months
- Accounts, roles, subscriptions and billing with Stripe
- Dashboards, admin panels, client portals and internal tools
- Fixed scope and price in writing, weekly demos, and you own all the code
/ Fit
Who this is for
Founders with a product idea
You need a real application users can sign up for and pay for — not another pitch deck or clickable prototype.
Small businesses
Operations running on spreadsheets, email threads and duct tape — you need one system that actually fits how you work.
SaaS teams
Senior hands to build a new module, untangle an existing codebase or ship a version two.
Agencies and consultancies
A client portal or internal tool — without hiring an in-house team.
If you're not sure whether what you need is "a SaaS" or "just a web app" — don't worry about the label. The question that matters is what the product has to do, and that's what the first call is for.
/ Scope
What I build
Accounts, roles and multi-tenancy
Sign-up, login, permissions — the plumbing every product needs and no user should notice. If your customers are companies, the app is multi-tenant from the start: each customer gets its own workspace with its own users, roles and strictly separated data. Cheap on day one, painfully expensive to retrofit — so it's settled during scoping.
Subscriptions and billing with Stripe
A SaaS that can't charge money is a hobby. Stripe wired end to end: plans, monthly and annual subscriptions, trials, upgrades, cancellations, failed-payment recovery and invoices. Card data never touches your servers; payments go straight to your Stripe account.
Dashboards and user-facing screens
Lists, filters, search, charts, exports — designed around the jobs users actually do rather than the database structure. The difference between a product people tolerate and one they recommend.
Admin panels and internal tools
See what's happening inside your product: who signed up, who's paying, where users get stuck. An admin panel built alongside the product, so your team runs the business without asking a developer for database queries.
Integrations
Payments, transactional email, CRM, analytics, accounting, third-party APIs — connected into one system. Where an integration can save you from building a whole feature, I'll say so.
Client portals
Often the highest-value application is a portal where your existing clients see their orders, documents, bookings or project status — replacing a hundred weekly emails. Same architecture, different business model.
/ Phasing
How a SaaS build is scoped
The most expensive mistake in custom software is building too much before anyone uses it. So I scope every SaaS in phases.
Phase one is an MVP — the smallest version that real users can log into and get value from. MVPs are a service of their own: from €5,000 fixed, delivered in 2–4 weeks. The crucial part: the MVP is built on the data model and architecture of the full product, so nothing gets thrown away when you grow.
Then we iterate. Each following phase — billing, more roles, integrations, the admin panel v2 — gets its own written scope, fixed price and timeline before it starts. You decide what to build next based on what real users are telling you, not on a roadmap invented before launch. Larger applications are always scoped this way: as a sequence of phases you approve one at a time, never as one intimidating quote for a year of work.
/ Stack
Architecture choices, explained for non-engineers
You don't need to know how the stack works, but you deserve to know why it was chosen. My default for SaaS is deliberately boring:
Next.js — the application
The framework behind many products you already use. Fast pages, good SEO for the public parts, and a huge hiring pool if you ever grow a team beyond me.
Laravel (PHP) — heavy backend work
Mature, extremely well documented, and famously good at exactly what a SaaS needs: queues, scheduled jobs, notifications, billing.
PostgreSQL — the database
The reliable open-source workhorse that banks and startups alike run on. Your data sits in a format any developer in the world can work with.
Stripe — the money
Building your own billing is how products die. Stripe is the industry answer to subscriptions, invoices and card compliance.
Why boring-but-proven instead of whatever is trending this quarter? Because your product will live for years, and every exotic technology choice is a tax you pay forever: harder hiring, thinner documentation, riskier upgrades. Proven tools are cheaper to run, easier to hand over, and just as capable of scaling. If your project genuinely needs something different, I'll recommend it and explain why in plain language — the stack serves the business, never the other way around.
/ Deliverables
What you get
A working application
Real users can sign up, use it and pay for it.
All the code, owned by you
Repository, accounts and infrastructure in your name — no lock-in.
A documented architecture
Good enough that any competent developer could take over.
Tested critical flows
Type-safe code and automated tests on what matters: sign-up, payment, the core action of your product.
A partner who speaks both languages
Code and business — and answers within 24 hours.
/ Process
How it works
Free 20-minute call
You describe what the product needs to do; I ask the questions that shape the scope. No preparation needed, no obligation.
Fixed scope and price, in writing
The first version, the architecture, the timeline and the cost. You know exactly what you're buying before anything starts.
Build with weekly demos
Every week you see the actual product running and steer what happens next. No months of silence followed by a big reveal.
Launch and support
Deployment, analytics, and further phases scoped one at a time as real usage tells us what's worth building next.
10+
years in web development
120+
launched projects
24h
reply, EU-based
/ Honest check
When you don't need custom SaaS
Sometimes the honest answer to "can you build this?" is "you shouldn't pay for it." A few cases where I'll tell you so on the first call:
Off-the-shelf does 90% of it
If Airtable, a Shopify app or an existing SaaS covers your workflow for a modest monthly fee, custom software is the expensive way to get the same result. Buy it, and spend your budget on customers instead.
Demand isn't validated yet
If nobody has agreed to pay even in principle, a landing page and twenty conversations cost almost nothing and teach you more than any codebase. Come back when someone wants to pay you.
No-code gets you to ten users
For simple internal workflows, no-code tools can be genuinely enough. Custom development starts paying off when you hit their walls — pricing, performance, permissions, integrations — and by then you'll know precisely what to build.
If one of these is your situation, the free call still stands — I'd rather point you at the right cheap option now and build your product later, when it's actually the right move.
/ Proof
SaaS I've built
Two products of my own show what this looks like in practice: wMenu, a SaaS for restaurants with QR menus, online ordering and an owner dashboard, and dr100, a platform for a dental clinic covering bookings and patient flows. Both run in production with real businesses depending on them daily — the same accounts-billing-dashboard architecture I'd build for you, tested on my own money first.
Book a scoping call
Tell me what your product needs to do. I'll reply within 24 hours with the smallest sensible first version and how I'd build it — no obligation.
Frequently asked questions
Should I start with an MVP or build the full SaaS right away?
Almost always the MVP. A first launchable version costs from €5,000 fixed and takes 2–4 weeks, which means you learn from real users before committing a larger budget. The difference with how I build MVPs is that the data model and architecture are designed for the full product from day one — so the MVP is phase one of your SaaS, not a throwaway prototype you pay for twice.
Can you build a multi-tenant application, where each customer has their own workspace?
Yes — most SaaS products I build are multi-tenant: one application, many customer accounts, each with its own users, roles and data kept strictly separate. Multi-tenancy is a day-one architecture decision, not a feature you bolt on later, which is exactly why it's part of the scoping conversation before any code is written.
How do subscriptions and billing work? Do I need to handle payments myself?
I wire in Stripe end to end: plans, monthly or annual subscriptions, trials, upgrades and downgrades, failed-payment handling and invoices. Stripe holds the card data and handles compliance, your customers manage their own billing through a portal, and the money goes directly to your Stripe account — I never touch it. You get a product that can charge customers from launch day.
What are the ongoing costs after launch?
Two kinds. Infrastructure — hosting, database, email and Stripe's per-transaction fees — which you pay directly to the providers from your own accounts, so there's no markup and no lock-in to me. And development — new features and maintenance, which we scope the same way as the initial build: a written scope and fixed price per phase, only when you actually want something built. There is no mandatory retainer.
Can you take over a SaaS another developer started?
Yes, this is common. I start with a paid code review: I read the codebase, check security basics, and give you an honest written assessment of what's solid, what's risky and what it would take to move forward. Sometimes the verdict is 'this is fine, let's continue'; sometimes it's cheaper to rebuild a part than to patch it. Either way you decide with real information instead of guesses.
Related / Services
Related services
Web Application Security
Practical security audits and remediation for websites, SaaS products and web applications: authentication, access control, exposed secrets, dependencies, forms and production configuration.
Web Application Security →02Web App QA & Testing
Independent QA and testing for websites and web applications: critical user flows, responsive and cross-browser checks, integrations, accessibility basics and automated end-to-end coverage.
Web App QA & Testing →03API Integrations & Business Automation
API integrations and business automation connecting your website, CRM, CMS, email, analytics, payments and documents through reliable data sync and workflows.
API Integrations & Business Automation →