Web & SaaS
Web products built beyond the first release.
SaaS platforms, portals, internal tools and dashboards. We build the product, then stay close enough to make the next version better.
The work itself.
Engineered for production reliability, long-term maintainability, and clean architecture from day one.
SaaS platforms
Multi-tenant applications built to be sold. Pricing, billing and feature gating in from the start rather than bolted on.
Customer portals
Self-service interfaces that take work off your support team and give customers a reason to stay.
Internal tools
The operations software that replaces a spreadsheet nobody is allowed to touch.
APIs and data products
Developer-facing products and the backend systems behind them.
What usually goes wrong
The problems people arrive with.
The platform gets slower as more customers join, which is the worst possible time for it to happen.
What we do
We find where the time actually goes before changing anything. Usually it is a handful of queries and a missing index, not the architecture.
Billing, permissions and plan limits were added after the fact and now sit in a dozen places.
What we do
We pull them into one place the rest of the product asks, so changing a plan is a configuration change rather than a release.
Support spends its day doing things customers could do themselves.
What we do
We look at what support is asked for most, and build that into the product as something a customer can do unaided.
How the work runs
Four stages, in order.
- 1
Map the product
Tenants, roles, plans and data. Getting this wrong early is expensive to undo later.
- 2
Build the spine
Accounts, permissions and billing first, because everything else assumes them.
- 3
Ship features in cycles
Working software every two weeks, in front of real users as early as it is useful.
- 4
Watch it in production
Monitoring and error tracking from day one, so you hear about problems before your customers tell you.
Shipped with this
Products we've built.
Stack
Proven, not experimental.
Questions
Asked often enough to answer here.
How long does a first version take?
For most SaaS products, three to five months to something real customers can pay for. We would rather cut scope than quality to hit a date.
Can you take over a platform someone else built?
Yes. We start by reading it and telling you honestly what state it is in, including if the answer is that it is in better shape than you think.
Do you handle hosting?
We set it up in your cloud account and hand over the keys. If you would rather we ran it, we can, but it stays yours.