From enquiry to handover

  1. 01

    First conversation

    We go through what you need and why, with no obligation. We will also say when a project is not worth it or has a simpler answer.

  2. 02

    Brief and quote

    We write the brief in our own words, have you approve it, and only then produce a price and a schedule.

  3. 03

    Building in stages

    We work in stages and show working parts on a test address as we go — not percentages in a table.

  4. 04

    Handover and operation

    We deploy, hand over access, documentation and training. Faults on our side we fix at no charge.

Brief, price and schedule

We start with a conversation, with no obligation, about what you need and why. From that we write a brief in our own words and send it to you to check — if we have understood something differently, it shows here rather than at handover.

Only once the brief is agreed do we produce a quote and a schedule. For smaller, clearly bounded work we give a fixed price. For larger projects we split the work into stages, each with its own price and date — so you pay in instalments and can decide after each stage whether to continue.

The brief in writing

We set out what will be done and have you approve it before quoting.

Price up front

A fixed price for clearly bounded work, stage by stage for larger projects.

Dates with room in them

We give dates we can keep, not the ones that sound best.

Changes on clear terms

When the brief changes along the way, we tell you the effect on price and schedule before we start.

How we show progress

We do not work in silence for months. We show you working parts on a test address as we go, so you see the actual state rather than a percentage in a table. On longer projects we check in on a rhythm agreed at the start.

When we hit something — the original approach turns out not to make sense, or something is harder than expected — we say so immediately. Bad news halfway through a project is uncomfortable; the same news at handover is a problem.

What we hand over

Finished work is more than a deployed system. We hand over everything you need in order not to depend on us.

Access registered to your company

The domain, hosting, repository and service accounts belong to you, not to us.

Source code

The complete code, including its history.

Documentation

How to deploy it, where everything runs, and what to do about common problems.

Training

We go through operation with the people who will be using it.

What happens after launch

Launch is not the end of the work. Faults that appear and originate on our side we fix at no charge — that is not an extra service, it is part of delivery.

Further development and changes we agree separately, according to what you need. It might be a one-off order or an agreed amount of support each month. We will not push you into anything: if the system runs and you want nothing changed, you pay nothing.

What the price is made of

Our price comes from an estimate of the work on the agreed brief. Besides that, most systems carry running costs you pay not to us but to the providers of services — and it is better to know about them in advance than to discover them after launch.

Domain and hosting

A recurring charge for the address and the server the system runs on.

External services

Payment gateways, email delivery, maps and similar tools, where the system uses them.

Running AI

Automation is charged by the volume of data processed — we give an estimate up front and refine it after launch against the real figures.

Store fees

For mobile apps, the annual Apple and Google developer account fees.

Have a project worth talking through?

Tell us what you are dealing with. We will go through it with you and say straight away whether and how we can help.

Discuss a project