Service
Dashboards, portals, and the plumbing under them
The internal tool your team is currently faking with spreadsheets, or the customer portal that has been on the roadmap for a year. Next.js and TypeScript, deployed on your infrastructure.
01
The app your team is faking in spreadsheets
Every growing company runs on a few spreadsheets and a Slack channel that were never meant to be infrastructure. We replace that with software — dashboards, portals, internal tools — that does the same job without depending on someone remembering to update a tab. It is the unglamorous category of work, and usually the one with the clearest payback.
- The app, responsive and accessible
- Roles and permissions that match how you work
- APIs and integrations to your existing systems
- Error tracking and analytics from day one
02
Roles that match how you work
Permissions modelled on your actual organisation, so the right people see the right things without a workaround involving a shared login. Admins, managers, customers and read-only auditors each get a view that makes sense for them. Getting this right early avoids the rebuild that lands the day your first serious customer asks for team accounts.
03
Wired into what you already run
The tool is useless in isolation, so we connect it to the systems around it — your CRM, your warehouse, your payment processor, wherever the data actually lives. Integrations get retries and proper error handling, because third-party APIs fail regularly and your app should not lose work when they do.
04
Instrumented from day one
Error tracking and product analytics go in with the first deploy, not bolted on after the first outage. You hear about a broken page from an alert rather than a customer email, and you can see which features people genuinely use before deciding what to build next.
How it runs
Same four steps, every project
- 01
Scope
A call, then a one-page scope: what gets built, what it costs, what date it lands, and what is explicitly not included.
- 02
Build
The core of the thing first, on your infrastructure from day one. A working demo every Friday, whether the week went well or not.
- 03
Harden
The parts everyone skips — empty states, errors, retries, analytics, and the case where a user does something strange.
- 04
Ship
Live, with monitoring and a handover doc. Two weeks of support included, then you take it or we stay on.
Pricing
What this usually costs
The exact number comes out of the scoping call. These are the shapes it takes.
Standard
Monthly · pause or cancel anytime
$2,000per month
One active build at a time, delivered in order. The plan most founders start on — enough to get a product live and keep it moving.
Priority
Monthly · pause or cancel anytime
$3,600per month
Two builds running in parallel and a faster turnaround, for when there is a launch date someone else already committed to.
Embedded
Monthly · 1 month minimum
from $7,500per month
Dedicated capacity that behaves like a team member — in your standups, on your roadmap, accountable for a slice of the product.
Other things we build
Tell us what you need built
Thirty minutes, free, no proposal. You leave with a scope, a number, and a date — or an honest reason why we’re not the right people.