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

Platforms

Enterprise Software

Internal platforms and business systems that fit the way your organisation works, with the security and structure that implies.

Typical timeline
8-16 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?

Modelled on reality

We map roles, approvals and data ownership before designing the software.

Secure by design

Access control, audit trails and data boundaries are part of the first version.

Owned by you

Repositories, infrastructure and documentation are yours from day one.

Changeable

The domain model and interfaces are written down so your team can change them.

No per-seat platform fee

You pay for the build and the infrastructure, not a licence on your own staff.

What you get

What you get from Enterprise Software

A system that matches the organisation.

  1. 01

    A working platform

    The core process running in one system, with the data in one place.

  2. 02

    Roles and approvals

    Permissions and limits enforced in code and visible in the interface.

  3. 03

    An audit trail

    A readable record of who changed what and when.

  4. 04

    Integrations

    Connections to the systems of record you already run.

  5. 05

    Documentation

    Architecture decisions, runbooks and handover notes.

The problem

What usually goes wrong

Off-the-shelf tools rarely match the way a real organisation operates. Teams end up with spreadsheets, a second system and a set of workarounds that nobody wants to own.

Who this is for. Organisations whose processes are specific enough that a generic tool creates more work than it removes.

Signs you need this

If any of this sounds familiar

  • A critical process is held together by spreadsheets.
  • Roles and approval limits live in email threads.
  • Two systems hold the same data and disagree.
  • Changes to the tool require a vendor call.

How the work runs

How we deliver it

  1. 01

    Map the organisation

    We document roles, processes and data ownership.

  2. 02

    Agree the scope

    The first stage, its price and its acceptance criteria are written down.

  3. 03

    Build in stages

    Weekly demos from a test environment, with decisions recorded as we go.

  4. 04

    Test with real cases

    Approvals, conflicts and permissions are tested with real examples.

  5. 05

    Launch and hand over

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

Deliverables

What you receive

  • Domain model and role definitions
  • Application with access control and audit trail
  • Integrations with existing systems of record
  • Automated tests, CI/CD and monitoring
  • Architecture decisions and handover docs

Stack

Tools we expect to use

TypeScriptPostgreSQLReactCloudflareTerraform

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

Questions

Common questions

Can it integrate with our existing stack?

Yes. We plan around your systems of record rather than asking you to replace them.

Who owns the platform?

You do, from the first commit. Code, infrastructure and documentation stay with your team.

Can our engineers take it over?

That is the design goal. We use mainstream languages and pair during handover.

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.