Skip to content
Latchford.

Software

Built around the business you actually run.

Custom software and internal systems for the work your spreadsheet was never meant to do — quoting, scheduling, tracking, reporting, and everything the whiteboard currently holds. Handle more work without hiring someone to re-type it.

What it replaces

You already have a system

It's a spreadsheet, a whiteboard, and a group chat. We build what they've been standing in for.

Quoting and estimating tools — for the spreadsheet only one person can safely edit

Job scheduling and dispatch — for the whiteboard that runs the week

Client portals — for the inbox full of “any update?”

Inventory and stock tracking — for the binder count nobody quite trusts

Intake and booking systems — for the WhatsApp group where jobs get lost

Internal dashboards and reporting — for the month-end scramble across five files, and for knowing which work is worth taking

Industries

Who we build these for

Different trades, same spreadsheet.

Our approach

The software bends, not the business

Off-the-shelf software makes the business bend to fit it. We start from the other end: how a job moves through your company, from first call to final invoice, and where it slows down or slips through.

The software gets shaped to that — not the other way around. It's also how we keep scope honest: we build what the business needs, not everything it could imagine.

Two things tend to come out of it that nobody asks for up front. You stop being able to grow only by adding people, because the volume goes through the system rather than through somebody's inbox. And for the first time the numbers are in one place, so which jobs actually make money stops being a matter of opinion.

How we build

Understand first, build second

01

Map the work

How a job actually moves through the business, and where it leaks time or money.

02

Scope and price

A written scope and a fixed price, agreed before anything is built.

03

Build in stages

The first useful piece ships early — you work with it while we build the rest.

04

Test and hand over

Tested, documented, and handed over with every account and access in your name.

We use AI to move faster. We review everything it writes, and we test for the vulnerabilities it introduces.

See the full process

How we'd approach it

A worked example

No software case study to show yet — so here's the thinking, in the open.

The situation

A contractor is quoting from his truck at 9pm, working from a spreadsheet he can't properly open on his phone. Every quote means squinting, scrolling, and copying numbers into a text message — and some quotes just don't get sent.

How we'd build it

We'd start with his last twenty quotes and rebuild the pricing logic exactly as he runs it — materials, labour, margins, judgment calls included. The first version would do one thing: turn a walkthrough into a priced, sendable quote from a phone, in minutes, at 9pm.

The spreadsheet would stay until the tool beats it. Only then would we look at what's next — usually the follow-up: which quotes went out, which were accepted, and which need a nudge.

A worked example, not a case study — this contractor isn't a client. It's how we'd think about your version of him.

Why Latchford

Four promises, in writing

Fixed price, agreed before we start

Written scope, so you know what you're getting

You own everything — code, domain, and accounts

We're here after launch, not just until it ships

Pairs well withIntegrationsCustom software works best when it talks to the tools you already run — accounting first.

Tell us what you're trying to get done.We'll tell you what it takes.