// field_notes
Field Notes
Field Notes examines the decisions, constraints, and failure modes behind software products and operational systems.
The notes are written for founders, operators, agencies, and technical buyers deciding what to build, what to buy, what to stabilise, and what should remain deliberately simple.
Some address buying decisions, operational failure, product ownership and handover; others document technical implementation patterns. They do not represent named customer case studies unless explicitly stated.
Build vs. Buy: When Off-the-Shelf Internal Tools Stop Scaling
A build vs buy framework for internal tools: when Retool, Airtable, and Sheets are the right call, the five signals you have outgrown them, and the real math.
Related service: Technical Review
read →How Much Does a Custom Web Application Cost? A Builder's Breakdown
A scoping framework for custom web application cost: the six drivers that move a range, carrying cost, and red flags in quotes that look too low.
Related service: Technical Review
read →Nine Ways Webhooks Fail in Production — and the Patterns That Survive
Nine production webhook failure modes — duplicate delivery, retry storms, silent 200s — and the patterns that survive: idempotency keys, HMAC, DLQ replay.
Related service: Internal Systems & Automation
read →Multi-Tenant Data Isolation: The Failure Modes That Leak Customer Data
Where multi-tenant systems actually leak data — missing tenant filters, cross-tenant caches, superuser jobs — and why Postgres row level security fails closed.
Related service: Websites & Product Builds
read →Postmortem: How MVPs Die of Silent Scope Absorption
An illustrative scope-creep model showing how silently absorbed additions break delivery plans, and the boundaries that keep change explicit.
Related service: Technical Review
read →Read all five published notes here or follow the feed directly.
rss --subscribe →