Skip to content
New guide: how to scope an AI project before you build

Platforms

Custom Software Development

Software built for the requirement that no product quite covers, delivered in stages with a team your engineers can work with.

Typical timeline
5-10 weeks
Group
Platforms
First step
Fixed-price discovery

Scope, price and acceptance criteria are agreed in writing before the build starts.

Why us

Why choose us for this work?

Written scope

Price and acceptance criteria are agreed before any build begins.

Small stages

Each stage ends with something you can click, test and inspect.

Your code

Repositories, infrastructure and documentation are yours from day one.

Your team

Mainstream languages and written decisions make future changes cheaper.

No lock-in

You can take the work to any engineer or team when we are done.

What you get

What you get from Custom Software Development

Software that fits, built in stages.

  1. 01

    Working software

    The agreed capability running against real data.

  2. 02

    Tests and CI

    Automated checks that run on every change.

  3. 03

    Documentation

    Decisions, runbooks and handover notes.

  4. 04

    A release process

    A repeatable way to ship without drama.

  5. 05

    Full ownership

    Code, accounts and infrastructure in your name.

The problem

What usually goes wrong

Custom software gets a bad name when it is built as one large release with no written scope. The alternative is a sequence of small, testable stages with clear acceptance criteria.

Who this is for. Teams with a specific requirement, an integration or a workflow that existing products do not cover.

Signs you need this

If any of this sounds familiar

  • A spreadsheet or workaround has become business-critical.
  • An off-the-shelf tool is close but the last part is missing.
  • Two systems hold the same data and need to agree.
  • You need to own the code rather than rent a tool.

How the work runs

How we deliver it

  1. 01

    Understand

    We learn the requirement and write down the acceptance criteria.

  2. 02

    Price the first stage

    Scope, timeline and price are agreed in writing.

  3. 03

    Build in weekly steps

    Working versions on a test environment, demoed every week.

  4. 04

    Test the awkward cases

    Real examples, failures and edge cases are covered.

  5. 05

    Launch and hand over

    We ship, support the first weeks, then hand everything over.

Deliverables

What you receive

  • Written scope and acceptance criteria
  • Working application with automated tests
  • CI/CD and environments
  • Architecture decisions and runbooks
  • Handover documentation

Stack

Tools we expect to use

TypeScriptReactPostgreSQLCloudflareDocker

We choose the stack to fit the problem. If your team already runs something else, we plan around it.

Questions

Common questions

How do you price custom work?

The first stage is fixed-price after discovery. Anything outside the scope is priced before we build it.

Can you work with our engineers?

Yes. We usually work alongside your team, with one accountable engineer and a weekly demo.

Who owns the code?

You do, from the first commit, including the repositories and infrastructure.

Next step

Talk through your project.

A short conversation. You leave with a clear view of what it would take, and whether this service is the right first step.

Prefer email? Write what you are working on and we will reply.

Send a note

By sending this, you agree that we may reply to your enquiry. See our privacy policy.