what we build, and how it's priced

Built to fit, not to fill a template.

Every job starts the same way — learning how the work actually gets done today — and ends with software that takes the friction out instead of adding a new layer of it.

every project is quoted to its scope. you approve a fixed quote, in writing, before we build.

How it runs

What happens after you get in touch.

Every engagement follows the same four steps, with the build delivered in two-week sprints and a live demo at the end of each.
  1. 01

    Discovery

    A call or a short workshop. We want to know who does what, where things break, and what a good day looks like for your business.

  2. 02

    Scope & fixed quote

    The features as user stories, the timeline, and one fixed price. You read it, push back, and say yes or no. Nothing is built before you say yes.

  3. 03

    Two-week sprints

    Each sprint starts with a plan you agree to and ends with a live demo on a staging link — so you watch it grow, with no big reveal at the end where you find out we misunderstood.

  4. 04

    Release & handover

    The code, the hosting, the documentation. We stay close for the first weeks of real use, because that’s when the real questions come up.

before you ask

The questions we get most.

Who actually does the work?
Our own engineers. You work directly with the people designing and building your system, with a demo at the end of every two-week sprint and no account manager between you and the work.
How is it priced?
A fixed price for an agreed scope, quoted after the first conversation. If the scope changes mid-project we agree the change and its cost in writing before we build it.
Who owns the code?
You do — source code, database and deployment, all in your own accounts. There is no platform you have to keep paying us to unlock.
What happens after launch?
A support window is included so the first weeks of real use are covered. After that you can keep us on for changes, or hand the project to another developer — it is documented for exactly that.
How long does it take?
Most projects run six to twelve weeks depending on scope. You get a date we actually believe, and a message the moment anything threatens it rather than the week after.
Do you work with existing systems?
Often. A lot of our work is replacing one painful part of a business without touching everything else, or building something that has to talk to software you already run.

not sure which one fits?

Describe the problem instead of the solution.

Usually replies within one working day. The reply comes from the people who would do the work.