Custom SaaS development
Subscription platforms with multi-user access and billing, built end to end. We have done it three times for ourselves before doing it for anyone else, and all three can be opened without asking us for permission.
- Who it is for
- Companies selling a service that today runs on spreadsheets, email and one tool that has reached its limit.
- Deliverable
- Deployed application · code and repository yours · deployment manual
What it includes
- Authentication, organisations, roles and permissions: who gets in, what they see and what they can touch, with invitations, from day one.
- Subscriptions and billing with Stripe: plans, per-plan limits, proration, and the portal where your customer changes their card without emailing you.
- Background jobs: what publishes at 3 a.m., what gets retried and what expires, outside the process that serves your users.
- A real admin panel, the one you will use: usage per customer, errors, and the ability to see what they see when they call.
- Reproducible deployment on your server or your cloud, with error logging and a runbook that does not depend on us still being around.
Where it gets hard
A new platform always works. What decides the cost is how it ages: migrating data with customers inside, raising a plan's price without touching those already paying, deleting an account so that it is really deleted. That is designed at the start or paid for twice.
Taking a payment is two afternoons with Stripe. The time goes into what surrounds it: what happens when a card fails, when access is cut off and when the customer is warned, what is kept from the customer who left, and how every plan limit is counted on every screen.
One account with three people and different permissions changes the whole data model. Adding it later means rewriting every query, so the question gets asked before the first table exists, even when the first customer is a single person.
The proof
PlanVortex is exactly this: a subscription with several plans, organisations with roles, per-plan limits and background jobs publishing around the clock. QaGamers is the same skeleton in another sector. Both are deployed and can be opened.
- Check it at
- planvortex.com · qagamers.com
How we work
Half an hour of conversation, a closed proposal with scope, price and date, a deployed increment every two weeks in an environment you can log into, and handover. The four steps are on the home page.
Frequently asked questions
- Is the code mine?
- Yes, from day one. The repository is created in your account or handed over at the end, with the deployment runbook. Maintenance afterwards is a separate agreement, never the condition for taking what you paid for.
- How long does a first version take?
- It depends on the scope, which is why the proposal carries a date before we start. What does not change is the rhythm: something working and deployed every two weeks, in an environment you log into, from the first delivery.
- Can you pick up a project that is already under way?
- Yes, and the first step is reading what exists: a review of the code and the deployment before quoting anything. If carrying on with whoever built it is the better option, we say so and that is where our part ends.