How we work

A clear path, an agreed price

From the first conversation to working software, with a scope and a price you agree to before we start.

01Understand
02Design
03Build
04Run
During the project

You see how far we have got, without asking us

Every project has its own page in our client portal. You open it whenever you want and check which milestones are done and how much of the budget has been used.

Click anything in it. Every name and figure is made up.

What is open right nowActive projects and incidents, unpaid invoices, and the proposals waiting on your approval.

Open the client portal

You get access when the project starts. Your own company’s data is all you can see.

The process, up close

What each step means

01

Understand

We start with the problem and the constraints around it. We read your request and come back with a structure for the work, split into milestones. The budget follows once you have approved that structure.

02

Design

You get clickable screens before we write production code, and the data model underneath them. Changing a screen at this stage takes an afternoon.

03

Build

Iterations are short and each one ends with software that runs. Nothing sits half-finished for a month while we work on something else.

04

Run

After launch we watch how it behaves in real use and fix what shows up. Whether we stay on for that or hand it to your own team is your call.

Ways to work together

A project, a partnership, or a second opinion

One team covers all three. What differs is how long we stay and how much of the work is agreed up front.

Project build

You have a clear outcome in mind.

A defined product, platform or feature. We scope it first, then quote once and build to that scope. Fits when the outcome is clear enough to put a price on.

Ongoing partnership

A single build will not cover it.

We act as your product engineering team and work in short cycles on whatever the product needs next. The same senior people stay with you as it grows.

Advisory & review

You need senior judgement, fast.

Architecture reviews, technical due diligence, a second opinion before you commit. Days, not months.

Pricing

Requesting a project is free, and you send the request from the portal as soon as you register. Most projects are fixed-scope, and the quote arrives in two steps: you approve the structure of the work first, then the budget for the project. Work starts after the second approval. Longer partnerships run on a monthly fee, agreed before the first month starts.

When the scope changes mid-build, and on a long project it usually does, we price the change on its own and you decide before we start it. Every line on your invoice is one you agreed to beforehand.

Asking costs nothing

You open an account in the portal and describe what you need, without paying for any of it. The first invoice comes after you have approved the structure of the work and then the budget.

Working software, early

You get something you can open and use long before the project ends. Your notes on it decide what we build next.

Direct access

Your questions are answered by the person who wrote that part of the system.

You own it all

Code, designs, accounts and infrastructure are yours throughout the project. Ask for a handover at any point and you get all of it, documented.

If this fits, start here

A few sentences are enough to start. We answer every request personally, usually within a day.

you approve the quote · you own everything we make

Projects start in our client portal. You register there, then send a project request. Or just email [email protected].