Multi-tenant data separation, secure accounts, recurring billing and a deployment that scales when the traffic arrives. Fixed at €1 500, launched on your cloud.
The same four stages every time, so you always know which one we are in and what closes it.
The part of a SaaS product that decides whether it survives is not the interface — it is the data model, the tenancy boundary and the billing logic underneath. That is what this track builds, and it is built to be extended rather than replaced at the first growth spurt.
Tenant isolation enforced at the data layer, not hoped for in the application code. Password hashing, session handling, role-based permissions and audit-friendly logging. Plans, trials, upgrades, downgrades, proration and failed-payment recovery modelled as real states rather than flags bolted on later.
Indexed queries, cached hot paths, background jobs for anything slow, and rate limits that protect the platform from one noisy tenant. Your own business rules live in one clearly-marked layer, so changing them later does not mean touching the whole system.
Separate development, staging and production environments with secrets kept out of the repository. Automated deployment, database migrations that can be rolled back, health checks and log aggregation configured before launch — not after the first incident.
Anything outside this list is quoted in writing before it starts. Prices exclude third-party costs you pay directly, such as hosting, domains and gateway fees.
Chosen for longevity and for the next developer, not for a résumé. No dependency enters the build without a reason you could repeat back to your board.
Data model, tenancy strategy, permission matrix and billing states agreed and written down.
Schema, authentication, roles, business logic and the API surface implemented and unit-tested.
Subscription flows, proration and dunning built; indexing, caching and background jobs tuned.
Dev, staging and production configured, CI/CD wired, load-checked, launched and handed over.
Not a login to our dashboard. The actual assets, under your accounts.
This track is the server side: architecture, data, auth, billing, API and deployment. If you also need the customer-facing interface, we scope it alongside — often as a landing page plus an application UI — and quote it separately so you can see what each part costs.
You do, directly to AWS, DigitalOcean or GCP, on your own account. We configure it there rather than under ours, so you keep the billing relationship and the ability to remove us at any point.
The strategy is chosen against your compliance needs and scale — a shared schema with enforced tenant scoping, separate schemas, or separate databases. Whichever we choose, the boundary is enforced at the data layer so an application bug cannot leak across tenants.
Sometimes. We will read it first and give you an honest assessment: extend it, refactor part of it, or rebuild the backend cleanly. If a rebuild is genuinely cheaper than the repair, we will say so before you spend money finding out.
Send the brief, the mockup or the feature list. You get scope, a fixed price and a delivery date within 48 hours.