Writing · 6 articles
Notes from the build.
How the systems behind the case studies were designed, what broke along the way, and the rules that kept the numbers honest.
- The triage desk that reads the meetings An AI layer that turns meeting transcripts and Slack chatter into approved, filed tasks, and why the human approval click is the whole design. Read
- Shipping a revenue warehouse solo in 8 weeks The three-layer architecture, the verification rule that kept it honest, and why a one-person team can now carry a scope that used to need five. Read
- Giving executives a database without giving them SQL How a read-only MCP server turned a Postgres warehouse into something a non-technical founder queries in plain English, and the permission model that makes it safe. Read
- The simplest RAG that works, and what a constrained environment teaches you Retrieval augmented generation in four steps, plus the design lessons that only appear when the model has limited permissions and a small context window. Read
- Replacing a form with a checkout, and the four departments in the way Conversions up more than 70%, revenue up more than 60%. The engineering was the easy part; getting operations, finance, marketing and IT to agree on what a product is was not. Read
- The payment tester that let non-engineers test payments Every tool for testing a payment API assumes you write code. Removing that assumption was worth more than optimizing the developers, and the gateway vendor adopted it as reference documentation. Read
Want the results these builds produced? Read the case studies or get in touch.