Production notes
The decisions behind software that keeps working.
Notes from Kuan, founder of Prodmake, on product decisions, production systems, launch, and operation.
Build 12 min read
Prototype to production: a practical guide to software that can operate
A practical path from a convincing prototype to production software with explicit access, data, integrations, administration, releases, recovery, and ownership.
Read the noteDefine. Build. Operate.
The notes follow the same lifecycle as the work: settle consequential decisions, build the complete system, then improve it against real operating evidence.
01
Define
What belongs in a written production plan A production plan should settle users, workflows, data, system boundaries, operating responsibilities, and the first meaningful scope before implementation begins. 7 min read What technical diligence reveals about whether a product can operate Technical diligence should inspect decision quality, access, data, delivery, recovery, ownership, and known risk—not reward fashionable architecture. ; originally published 8 min read
02
Build
What ‘running in production’ actually means A deployed interface is only one part of a production product. The full system includes access, data, administration, deployment, recovery, and ownership. 7 min read What a production product costs beyond the prototype The cost of production software is driven by operating obligations—data, access, administration, integrations, deployment, recovery, and ownership—not a screen count. ; originally published 8 min read
03
Operate
Have market knowledge that needs to become software?
Start with a written brief covering the problem, evidence, current state, desired outcome, and production constraints.
Engagements start at $12,000; most Build or Rescue scopes fall between $35,000 and $75,000; ongoing operation is scoped separately.