Two sectors.One backbone.

We build and rebuild ERP systems, the thing a business actually runs on. Stock, orders, pricing, purchasing, money and reporting, in one place and telling the truth.

One record
of the truth.

An ERP is just this: every part of the business reading and writing the same data, instead of six systems disagreeing at month end.

01 / Retail

Jewellery.

Every piece is its own record. Most retail systems assume a SKU with a quantity behind it. Jewellery breaks that assumption on day one.

SERIALISED STOCK

One piece, one record

Serialised stock rather than SKU-and-quantity. Metal, weight, stone spec, certificate number and cost all live on the individual item, so the same ring can’t be sold twice.

Costing that moves

Metal price moves, so margin moves. Landed cost, scrap and remake tracked properly, so a piece made eighteen months ago still prices correctly today.

Repairs, bespoke and memo

The work that never fits a till: repairs in and out, custom commissions, valuations, layaway, and consignment stock you hold but don’t own.

Showroom and online, one stock

The website, the counter and the stock take reading from the same record, so the piece in the window isn’t still listed as available after it sells.

Serialised inventory Point of sale Repairs & commissions Consignment / memo Stock takes Insurance valuation Multi-channel sync

02 / Software

Financial
management SaaS.

Here we’re on the other side of the table, building the product itself for teams whose customers close their books in it.

LEDGER & RECONCILIATION

A ledger that stays correct

Double-entry that actually balances, immutable postings, and an audit trail that survives a real audit. Corrections are entries, never edits.

Multi-tenant without leaks

Per-tenant isolation enforced in the data layer rather than remembered in application code, so one customer can never see another’s numbers.

Reconciliation and close

Bank feeds, matching rules, period locks and the month-end close: the parts that decide whether finance teams trust the product or export to a spreadsheet.

Talking to their ERP

Your customers already run something. Integrations and imports that survive messy real-world data, plus migrations off legacy on-prem installs.

Double-entry ledger Multi-tenant architecture Bank feeds & matching Period close Audit trails ERP integrations Legacy migration

The hard part
is the data.

How an ERP job runs

We learn the trade first

Two weeks in the business before a line of code. If we can’t explain how you price a piece or close a period, we can’t build the system that does it.

Migration is the project

Twenty years of stock records, part-priced, half-duplicated. Getting that across cleanly is most of the work, and we plan it as such rather than leaving it to the last fortnight.

Cutover without closing

You keep trading through it. Parallel running, a dated switch, and a way back if the first week goes badly.

Then we stay on

The month after go-live is when the real questions arrive. We’re there for it, not handing you a support address.

Not one of these two

We’ll tell you if it isn’t our patch.

We take work outside these two sectors when the shape fits. If it doesn’t, you’ll get a straight no and, where we can, a name worth calling.

hello@catheadpartners.com