Services
We build SaaS products.
Design, development, deployment and the coordination that keeps them moving — four services, four published rates. Everything is billed by the hour, at the rate that matches the work, with nothing charged twice under a different name.
Design01
UX / UI design
Wireframes and UI flows first, screens second. The point of this phase is that everyone agrees what the software does before anyone pays for it to be built.
- Wireframes for every screen that matters
- User flows, states and edge cases
- Interface design and a reusable component set
- Clickable prototype where a decision needs one
$59 / hour
Build02
Development
Services and the interface on top of them — the part where the product becomes something people can log into and rely on.
- Data model and business rules
- Multi-tenant setup, roles and permissions
- Subscriptions, invoicing and payment integration
- Third-party integrations and APIs
- Migration of data from whatever you use now
$69 / hour
Run03
DevOps consulting
Environments, pipelines, monitoring and backups — so a release is a routine event rather than an evening everyone dreads.
- Reproducible environments, dev through production
- Automated build and deployment
- Monitoring and alerts that name the cause
- Backups with a restore that has been tested
$69 / hour
Keep on track04
Project management
Billed separately and openly, because it is real work — and because hiding it inside a development rate is how estimates quietly inflate.
- Phase plans with estimated ranges
- Written status you can forward to your board
- A decision log, so nobody relitigates March
- Coordination with your other suppliers
$79 / hour
Under the surface
What a SaaS build actually consists of.
Screens are the part everyone discusses. These are the parts that decide whether the product is still standing in three years — and they are the same whether you sell to factories, clinics or law firms.
Tenancy
One codebase, many customers
Customer-specific behaviour held as configuration rather than as branches. It is what keeps customer number thirty from costing thirty times as much as the first.
Access
Roles and permissions
Rights per operation, enforced on the server. Who may approve, who may only see, who may never — decided once and applied everywhere.
Money
Subscriptions and billing
Plans, upgrades, proration, failed payments, invoices and tax. Billing is where SaaS products leak revenue quietly, so it gets built properly or not at all.
Data
A model that survives
Schema, migrations and history. The difference between a product you can extend and one you have to rewrite is decided here, in the first month.
Edges
Integrations you don't control
Accounting systems, payment providers, ERPs, government interfaces. They go down, change format and rate-limit you — so the system is built expecting it.
Proof
Audit trail and reporting
Who changed what, when, and what the numbers were at the time. Required the moment money, stock or contracts are involved.
Ways to start
Four ways this usually begins.
A
New product from zero
An idea, a spreadsheet that outgrew itself, or a service you run manually. Starts with wireframes, ships in slices.
B
Taking over an existing system
Your developer left, or the agency did. Begins with a short review phase — nobody promises anything before reading the code.
C
A module on top of what you have
A new billing engine, a customer portal, a reporting layer — built into a system that already runs, without stopping it.
D
Deployment and operations only
The product exists but releases hurt. Environments, pipelines, monitoring and backups, handed back documented.
However it starts, it ends the same way
One-year warranty on the work, full ownership of the delivered product, and a documentation pack — physical and logical system design, operations manual, commented source, backup plan, database schema and deployment guide. See the handover →
Scope
What we don't take on.
Saying this out loud costs nothing and saves both sides a month. If your project is on this list, we will say so on the first call rather than three invoices in.
- Native mobile apps as a standalone deliverable.
- Machine learning research — modelling as a product in itself.
- Rescue jobs with no access to the existing source or infrastructure.
- Fixed-price bids on a scope nobody has written down yet.
- Work where the client cannot name a decision-maker.
To start
What we need from you.
The problem, in your words
Not a specification — the situation. What breaks, what is slow, what you cannot see.
Someone who can decide
One person on your side who can approve scope. Projects stall on absent decisions more often than on hard code.
Access, when the time comes
Source, environments, or the systems we are integrating with. We will tell you exactly what and when.
Tell us what you want built.
We reply within one business day.