Custom software studio

Software that holds the structure up.

Kingpost Software designs and builds the web applications, internal tools, and integrations that businesses actually run on — with a fixed scope, a demo every week, and the repository in your name from the first commit.

  • Fixed-price scope
  • Weekly demos
  • You own the code
Diagram of a kingpost trussA triangular roof truss. The horizontal tie beam and the vertical king post are highlighted because they carry tension; the two sloping principal rafters and the two struts carry compression. Arrows above the rafters show the load.LOADKING POSTAPEXPRINCIPAL RAFTERSTRUTWALL PLATETIE BEAM
  • In tension
  • In compression
In a kingpost truss the center post carries pure tension — it hangs the tie beam from the apex so a long span cannot sag. It is the smallest member doing the most work, and nobody ever looks at it. That is the software we build.
  • Web applications
  • Internal tools
  • System integration
  • Data pipelines
  • Legacy rescue

What we run

Three products of our own.

We build and maintain these ourselves, which is why we can talk about long-term maintenance from experience rather than principle.

How we work

Bottom chord first.

Every project gets built in the order a truss does — the load-bearing pieces before the ones anyone can see.

01

Survey

We sit with the people doing the work, read whatever code already exists, and write down what done means. You leave with a scope document and a firm price — and no obligation to build any of it with us.

1 week

02

Frame

Data model, authentication, and the single workflow that matters most, in that order. By the end you are clicking through something real on a staging URL, not looking at pictures of it.

2–3 weeks

03

Fit out

The rest of the surface, in weekly increments you review. Nothing goes more than five working days without you seeing it running, which is how scope problems get caught while they are still cheap.

4–8 weeks

04

Hand over

Deployment, runbooks, and a recorded walkthrough for whoever joins your team next. The repository was in your name the whole time; we simply stop pushing to it.

1 week

Where we're useful

Three problems we take on often.

Representative situations rather than named clients. The shape of the work is usually what you're trying to recognize when you decide whether to call.

Freight & logistics

Dispatch runs out of a forty-tab spreadsheet.

Two people know how it works and one of them is retiring. Every new lane means another hidden column, and nobody can tell you what last Tuesday looked like.

What we buildA scheduling app with the same mental model as the spreadsheet, plus roles, history, and an export that matches the old report line for line.

Manufacturing

Accounting and the shop floor disagree every month.

Job costs live in one system and inventory in another. Month-end close is four days of somebody re-keying numbers and hoping.

What we buildA nightly sync between the two, and a reconciliation report that names every mismatch and the person who has to resolve it.

Professional services

The app works, but nobody dares deploy it.

The engineer who wrote it has left, there are no tests, and a one-line change takes a week because everyone is afraid of what else it touches.

What we buildA test harness around the paths that earn money, a documented one-command deploy, and a codebase your next hire can actually read.

Terms

How engagements are shaped.

Three ways to work with us. All of them start with the survey week.

Fixed-scope project

Most common

Survey first, then one price for a defined scope. Change requests are quoted separately, so the number you approve is the number you pay.

Monthly retainer

Ongoing

A set number of engineering days each month for a product that keeps moving. Cancel with thirty days notice, no exit negotiation.

Rescue sprint

Two weeks

A fixed fee to stabilize something that is breaking now: stop the bleeding, document what you have, and tell you honestly what a proper fix would cost.