I build the product layer a subscription business runs on.
The parts every SaaS needs and nobody enjoys rebuilding — accounts, authentication, billing, an admin panel and a dashboard people can actually use.
Accounts and authentication, including social and passwordless sign-in
Subscription billing and plan management
A dashboard designed around the job, not around the database
An admin panel so you can run the product without a developer
A database and API layer built to grow with the product
Model
What the product stores and who is allowed to see it. Getting this wrong is expensive later.
Foundations
Accounts, authentication and permissions first — everything else assumes they exist.
Build
The features that make the product worth paying for, on top of foundations that already work.
Operate
An admin panel, sensible logging, and a handover that leaves you able to run it.
- Supabase
- Convex
- Clerk
- JavaScript
- Git & GitHub
Have you built a SaaS product?
Not a subscription product, no — I would rather be straight about that than imply otherwise. What I have built repeatedly are the pieces one is made of: authentication and databases with Supabase, Convex and Clerk, and admin dashboards that let an owner manage their own content without touching code.
What do you use to build it?
Supabase or Convex for the database, authentication and file storage, with Clerk where a richer sign-in flow is needed. All three are services I use in production rather than have only read about.
Can you take over an existing SaaS?
Depending on the stack, yes. The honest first step is a look at what exists — some codebases are cheaper to continue than to rewrite, and some are the opposite.
How is this priced?
Scope first, then a written quote, same as everything else. A SaaS build is usually staged so you get something working early rather than everything at once.