How do we work?

Two ways in, and one way of working after that.

Some businesses need software that already exists. Some need something that does not. The first conversation is about telling those apart, because paying project money for a solved problem is the most common way this goes wrong.

Licence a product

Use something we have already built

Our products are sold as a licence, billed monthly or yearly, hosted and maintained by us. You are live in days, and you pay for software rather than for a build.

  • Set-up help and your data brought across
  • Hosting, updates and support included in the licence
  • Improvements paid for by one shop reach all of them
  • Cancel without a project write-off hanging over you

Commission a build

Have us build what does not exist

When the work is genuinely particular to your business, it becomes a project — scoped, quoted and handed over, with the code and accounts yours at the end.

  • A written scope with a fixed price and a date
  • A running version early, on a real URL
  • Source, repositories and deployment accounts transferred
  • Support afterwards, from the people who built it

Plenty of businesses end up doing both — a licence for the everyday work, and a small piece of custom building where their trade is genuinely unusual. We will say which one we think you need, including when the answer is neither.

How we work

Four steps, and no surprises in the invoice.

The same sequence whether it is our product or yours.

  1. 01

    Understand the work

    We start with how the job is done today — the spreadsheet, the notebook, the WhatsApp thread. Software that ignores this gets abandoned.

  2. 02

    Agree the smallest useful version

    A scope you can picture, with a price and a date attached. Anything that can wait is written down and waits.

  3. 03

    Build in the open

    You see it running as it comes together, not at the end. Changing direction in week two is cheap; in month four it is not.

  4. 04

    Hand over, then stay

    You get the code, the accounts and the documentation. We stay on to support it, because the first month in real use teaches the most.

In practice

What this looks like week to week.

One person who knows your system

You are not handed between account managers. The people who build it are the people you talk to, and they stay on it afterwards.

A running version, early

You see the real thing on a real URL well before it is finished. Opinions formed against something working are worth far more than opinions about a mockup.

Written decisions

Anything agreed on a call gets written down and sent back. It takes ten minutes and prevents the argument three months later about what was meant.

Your accounts, from day one

Hosting, domain and database are set up in your name where possible, so nothing important is locked to us and handover is not an event.