Skip to content
Gate City Wolfe

Custom software

Built for one business. Yours.

Off-the-shelf software is the right answer more often than consultants like to admit. But when the thing that makes your company good is the exact thing no product supports, you end up paying for the gap in people’s time — forever, and quietly.

What this usually looks like

The shapes this work tends to take

Different industries, same underlying problem: the way this business actually runs has outgrown the tools available to buy.

The spreadsheet that became load-bearing

It started as one person's tracker and now the whole company depends on it. Three people have their own copy, the formulas break quietly, and nobody dares touch the macro. That is a real system — it just needs to become a real system.

Internal tools nobody sells

Scheduling, approvals, intake, inspections, compliance records. The processes specific enough to your business that no vendor builds them, which is exactly why they are still being run by hand.

Systems that will not talk

Your accounting package, your supplier's portal and your field app each hold a piece of the truth, and somebody retypes between them every week. That person's job is the integration we should have written.

Reporting you can trust

Numbers assembled from one source instead of three exports and a reconciliation. If two reports can disagree, people stop believing either of them.

Portals for customers or subs

A single place for the people outside your company to see status, send documents or approve something — instead of a thread nobody can find later.

Getting out of a platform that nearly fits

Migrations off tools you have outgrown, including the unglamorous part: moving years of history across without losing it or trusting a CSV round-trip to get it right.

How we scope

The first thing we do is try to make the project smaller

Most software disappoints because it was specified in a room rather than observed in a workplace. Before anything gets built we want to watch the process, find the one or two steps where the pain actually is, and cut everything else.

  1. 01

    Understand it properly

    We sit with the people doing the work. Not a requirements document — the actual job, including the workarounds nobody mentions in meetings because they have stopped noticing them.

  2. 02

    Agree the smallest useful version

    The slice that pays for itself first. You get something real in weeks and we both learn from it being used, which beats guessing for six months.

  3. 03

    Fixed price, in writing

    Scope and number agreed before work starts, per phase. If we estimated badly, that is our problem to absorb, not a change order for you.

  4. 04

    Build it where you can see it

    Regular working software, not status reports. You can change direction while changing direction is still cheap.

Questions

Before you call

What size of project do you take on?

From a single tool that saves one person a day a week, up to the system a business runs on. Below a certain size we will tell you it is not worth paying anyone for and point you at something off the shelf. Above a certain size we will tell you who else should be involved.

What do you build with?

Mostly TypeScript, React and Postgres, deployed on infrastructure we run and monitor. That is a deliberately boring, well-documented stack — it means you are not locked to us by a technology nobody else knows, and another developer could pick it up if you ever needed them to.

Who owns the code?

You do, outright, and it is written into the agreement. You get the repository, the deployment setup and the documentation. We have no interest in holding your business hostage to a password.

Do you do fixed price or hourly?

Fixed price per phase, agreed in writing before work starts. Hourly puts the risk of our estimating mistakes on you, and it rewards us for being slow. Neither is a good way to start a working relationship.

What about after it is built?

Software that is being used needs changing — that is a sign it works, not a failure. We offer an ongoing arrangement for hosting, monitoring, backups and changes, or we hand it over complete if you have your own people. Both are fine, and you are not penalised for picking the second.

Will you sign an NDA?

Yes, happily, and before you tell us anything confidential. Send yours over or ask us for one.

Get in touch

Describe the problem, not the solution

You do not need a spec to start. Tell us what is slow, what breaks, or what you keep doing by hand — working out what to build is the job.

Based in New Hampshire, working with companies here and in northern Massachusetts.

0/4000

Goes straight to my inbox. No newsletter, no CRM sequence, no sharing it with anyone.