Skip to content
Faomu
Internal systems / Integration / Modernisation

Software,
carefully made.

We build the internal systems large organisations run on, and hand them over in a state your own engineers can run.

Discuss a system How an engagement works
01 — The problem

Internal software runs the business. It is rarely built as if it did.

Platforms bent out of shape.

A licensed product customised until every upgrade is a project, and nobody remembers why half the fields exist.

Projects that end at launch.

A supplier delivers and leaves. What remains is code your team did not write, cannot safely change and must still support.

Teams with no room.

Your own engineers understand the business best. They are also committed to the roadmap for the next eighteen months.

Faomu works in the space between them: a small senior team that builds the system properly, then makes sure you can run it without us.

02 — Principles

Three rules we hold every engagement to.

  • 01

    Precision

    Written scope. Agreed acceptance tests. Nothing assumed.

  • 02

    Simplicity

    Fewer moving parts. Proven technology. Code your team can read.

  • 03

    Reliability

    Designed for failure. Observable from day one. Built to be maintained.

03 — What we build

Systems your organisation uses every day.

All services
01Operational platforms

The bespoke systems that carry the core of how your organisation works: case handling, approvals, scheduling, inventory and field operations. Built around your process, not a vendor's idea of it.

How we approach it
02Integration and data

Connect ERP, CRM, finance and legacy systems through well-defined interfaces, so every team works from the same records and every change can be traced.

How we approach it
03Legacy modernisation

Replace ageing systems piece by piece while they keep running. No big-bang cut-over, and no frozen roadmap for eighteen months.

How we approach it
04Automation and applied AI

Automate repetitive work with plain rules first and language models where they earn their place, with human review, audit trails and measured accuracy.

How we approach it
05Operation and improvement

We can run what we build under a written service agreement, or train your team to run it. Either way, the system keeps improving after launch.

How we approach it
04 — Approach

We agree what done means before we write the code.

Every engagement moves through the same five stages. Each ends with a written sign-off and something you keep, so the risk you carry is never larger than one stage.

The five stages in detail
EngagementStandard terms
Survey
1–2 weeks, fixed fee
Specification
Written, signed, fixed fee
Build
Two-week increments
Price
Fixed or capped at G2
Demonstrations
On your infrastructure
Exit
At any gate
05 — Handover

What you own at the end.

Everything needed to run, change and audit the system without us. It sits in your repository and your accounts from the first week.

  1. 01Source code with its full historyYour Git
  2. 02Infrastructure defined as codeYour cloud
  3. 03Automated tests and release pipelineCI
  4. 04Architecture decision recordsMarkdown
  5. 05Runbooks for operation and incidentsMarkdown
  6. 06Training for the engineers who take overIn person
06 — Assurance

Built to pass your security review.

Your accounts

We sign in through your identity provider and work in your cloud. Access is logged and removed at handover.

Your data

Production data stays in your environment. We build and test with synthetic or masked data.

Your continuity

You hold the code, the infrastructure and the credentials. Nothing depends on Faomu continuing to exist.

Security, data and procurement

Tell us which system is holding you back.

The first conversation is an hour with a senior engineer. If we are not the right team for the problem, we will say so. Or write to [email protected].

Discuss a system