SaaS platform
DiagNow
SaaS platform for inspection firms: field capture, pollutant reports, CRM and billing in one place.
Discover the projectWe build complete web products: accounts, subscriptions, billing, dashboards, APIs. An architecture designed to grow instead of being rewritten after a year.
Our approach
01
The data model decides everything else
It is the one choice that is very difficult to undo. Who owns a record: a user, a team, an organisation? If you start with a user tied to a single company and a client wants three subsidiaries six months later, the migration touches every query in the application. We ask that question on day one, even when you only sell to freelancers.
02
An MVP that proves something
An MVP is not a smaller version of the final product: it is the smallest product capable of testing whether somebody will pay. We deliberately keep the back office and the automation of rare cases lean; we never cut corners on authentication, permissions or tests of the main journey. Six to ten weeks is enough to validate the premise.
03
Subscriptions, billing and roles
Accounts, invitations, roles, free trials, plan changes, invoices, VAT, failed-payment retries. This part looks incidental and regularly accounts for a third of the build. We lean on proven components like Stripe rather than rewriting them, but we test this area thoroughly: this is where bugs cost money directly.
04
Tests and continuous deployment
A product that changes weekly without a safety net eventually slows to a halt: nobody dares touch the code. We cover the critical journeys (sign-up, payment, the main action) and automate deployment. The goal is not perfect coverage, it is being able to ship on a Friday without dread.
What it covers
- Product scoping and user journeys
- Accounts, roles, subscriptions and billing
- Public API and third-party integrations
- Automated tests and continuous deployment
How it runs
Four steps, no black box.
01
Product scoping
Users, journeys, data model and the scope of the first milestone.
02
Prototype
Clickable screens to validate the journeys before building.
03
Build
Two-week iterations, with a demo at the end of each one.
04
Production
Automated deployment, monitoring, then changes driven by feedback.
Questions
What people ask us about this service.
Can you take over an existing product?
Yes. We start with an audit of the code and database to determine honestly whether taking it over is viable, or whether a partial rewrite will cost less in the long run. The conclusion is documented and substantiated, even when it does not suit us.
Where is the data hosted?
Wherever you decide: Switzerland or the EU depending on your regulatory constraints and your customers’. The hosting is in your name; we can administer it without owning it.
What if we want to bring it in house later?
That is planned from the start. Documented code, a reproducible environment, no dependency on any proprietary tools of ours. We support the handover to your future team if you want it.
Selected work
What we have delivered in this field
Further reading
How we work, in detail
Product
3 min read
From MVP to SaaS: building a product you will not have to rewrite
The shortcuts you can safely take at the start, and the three decisions you must never postpone if you want to survive your first hundred customers.
Read the article
Product
3 min read
Leaving Excel behind: when a custom internal tool pays for itself
The shared spreadsheet works, right up to the day it costs more than it returns. Here are the signals and the arithmetic.
Read the articleRelated services
Six capabilities, one team.
Got a project in mind?
Describe it in three lines and we will come back within one business day with a first estimate.