How the Build Sheet Desk Works

This desk exists because the build-versus-buy conversation is usually conducted without a sheet. Two people compare a one-off engineering estimate against a recurring charge, which is arithmetic that cannot produce a verdict, and the argument gets settled by whoever is more confident. Everything published here is an attempt to replace that with a structure and a set of blanks.

What the desk covers

One subject, treated in two halves. The build sheet half itemises what ownership contains: the components you would take on, the work each generates once live, and the decision record that makes a choice defensible later. The running costs half itemises what arrives every month, including the labour that never reaches an invoice.

The scope is the decision and the bill. This desk does not publish engine architecture, pipeline design, retry strategies or execution tactics. Those are worthwhile subjects and they are somebody else's; mixing them into a cost sheet is how cost sheets stop being usable.

How a sheet is assembled

Every page starts from the same question: what would somebody have to know to fill this in for their own situation? That produces line items rather than conclusions, and it produces blanks wherever the honest answer is that only you have the number. A sheet with blanks in it is doing its job.

Where arithmetic appears, the inputs are printed next to it and labelled as placeholders. The purpose of a worked example here is to demonstrate the shape of a calculation, never to suggest what anything costs. Substitute your own rates, hours and volumes and the same model will produce a different and more useful answer.

What this desk does not publish

No vendor prices and no plan names, because both change faster than any page can track and a stale price is worse than no price. No salary figures, no infrastructure benchmarks borrowed from other teams, and no statistics about how long anything takes. No ratings, no review counts, no testimonials, and no named-product verdicts.

There are also no invented people here. Pages are published by the Build Sheet Desk, which is the editorial name for the work rather than a person with a biography. Where something is uncertain, the page says so in the sentence rather than in a disclaimer at the bottom.

Where the numbers come from

Three sources only. Protocol facts that are publicly documented and verifiable, such as how a network fee is composed. Structural facts about how a category of service is charged, which are durable in a way that amounts are not. And illustrative arithmetic built from placeholder inputs that are printed alongside the result.

Anything that does not fall into one of those three categories is left blank, with a note about how to measure it yourself. That is a deliberate limitation: a cost model built on somebody else's numbers describes their stack, and the whole point of a sheet is that it describes yours.

Corrections

If something here is wrong, the desk would rather know. Structural errors, broken arithmetic and outdated descriptions of how a service is charged are all worth reporting, and corrections are made to the page rather than appended as footnotes. Use the contact page and include the page and the specific claim.

Commercial links on this site are marked by context rather than by disclaimer: where a page points at a hosted console, it does so because the paragraph is about the rented side of a comparison. Nothing here is financial advice, no page recommends a specific spend, and every decision described is one you make with your own money and your own sheet.