For when off-the-shelf hits its ceiling

Custom software,
measured from day one.

Bespoke web platforms, custom interfaces, APIs, and practical AI workflows. For the projects where SaaS can’t bend far enough, or where the integration work itself is the project.

Every build starts with measurable success metrics defined upfront. The dashboard that proves the build worked is shipped in the first phase, not as an afterthought at the end.

What we typically build

Four shapes of work that come up regularly. If yours doesn’t fit one of these, the discovery call will tell us whether we should still talk.

Bespoke web platforms

When your business logic doesn’t fit into the boxes a SaaS vendor designed. Think portals, configurators, multi-party workflows, internal tools — built around how your business actually runs.

Custom interfaces

Internal dashboards, admin tools, customer-facing portals. Often built on top of platforms you already use, so your team doesn’t learn a new system for every feature.

APIs and integrations

When two systems need to talk to each other and there’s no off-the-shelf connector. We build the integration, document it, and write the tests so it stays working.

AI workflow automation

Document extraction (reading invoices, contracts, applications) and workflow automation (routing the extracted data into your existing systems). Practical AI — not chatbot theatre.

How an engagement runs

Five phases. Each one has a tangible deliverable you take with you.

01

Discovery

A paid discovery phase to scope what you actually need. We map your current state, identify the real problem (often different from the assumed problem), and produce a written technical scope and price.

You take away

Written technical scope + fixed-fee proposal

02

Design

Architecture, data model, UI, and integration plan. You see the design before we write code, including how the new thing fits into the systems you already run.

You take away

Design document + signed-off architecture

03

Build

Phased delivery. We ship in small increments you can see and feedback on, not a single big-bang release six months later. Measurement is baked in from the first phase.

You take away

Working software in production, phase by phase

04

Measure

Telemetry, usage analytics, and business-outcome metrics defined upfront and live from day one. We measure whether the thing we built actually moved the number we said it would move.

You take away

Dashboard showing the metrics the build was meant to move

05

Maintain

Custom software isn’t finished when it ships. Optional ongoing maintenance covers security patches, dependency upgrades, small feature work, and the periodic refactor that keeps cost-of-change low.

You take away

Optional monthly retainer with measurable response times

How it’s priced

Fixed-fee discovery. Phased build. Optional maintenance.

From $1,500 discovery · $185/hr build

Discovery is fixed-fee from $1,500, quoted upfront. Build work is $185/hr in 2–4 week phases, or fixed-price for engagements over 40 hours where the scope is clear. Optional monthly maintenance retainer once you’re live.

We size honestly to the team you have access to. Medium-sized projects are our sweet spot — enterprise programmes need an enterprise vendor.

When we’re NOT the right fit

We’d rather tell you in the first call than three phases in.

  • You need an enterprise platform with multi-region deployment, 24/7 SLAs, and a 100-person engineering org. Small team — medium-sized projects, not enterprise programmes.
  • You need a "build it once and never touch it again" deliverable. Custom software needs care. We will not pretend otherwise.
  • You aren’t sure if the problem is real. The discovery phase is fixed-fee precisely so you can stop after that if the diagnosis says the build isn’t justified.

Common questions

What kind of stack do you build on?
TypeScript / React / Node for most projects. Postgres for data. Cloud-native infrastructure (typically Vercel, Railway, Fly.io depending on shape of the workload). We pick boring, stable tech that you or someone else can pick up later — not whatever blog post is trending.
How long does a typical project take?
Discovery: 1–3 weeks. Build phases: 6–16 weeks depending on scope. We slice work into small phases (2–4 weeks each) so you see progress and can adjust, not a single delivery six months from kickoff.
Will we own the code?
Yes. The repository is yours. The deployment infrastructure is yours. The documentation is yours. If the relationship ever ends, you keep everything and can hand it to another team without drama.
What does the AI work actually do?
Two focused things. Document extraction — pulling structured data out of unstructured documents (invoices, contracts, applications) with high accuracy. And workflow automation — taking the extracted data and routing it through your existing systems with approvals, exceptions, and audit trails. We are not building chatbots or autonomous agents.
What if we already have an in-house developer?
Even better. Some of our engagements are working alongside an in-house team — taking on the specific build they don’t have capacity for, or handling the integration work while they focus on product. We will tell you honestly whether outsourcing or hiring is the right call.

Test the methodology, free

Where does your data actually sit?

Ten honest questions across five areas. Five minutes. Get a scored picture of your current posture and a personalised next step — before you commit to anything paid.

Take the self-assessment →

Free · 5 minutes · No payment

Got something off-the-shelf can’t do?

Tell us what the system needs to do that nothing on the market does quite right. The discovery call will tell you whether a custom build is actually the cheapest way to solve it.

Book a discovery call