Lead story
Integration Islands
Why the quietest problem in your software stack became the loudest limit on your AI.
42 min readAlso as a PDF edition
Aditya Gaur — Ops & GTM systems for 0 → 1
Looking correct and being correct are different problems.
Case files
All work- 01LoamA markdown app for the agent era with no AI inside it, built around a press that produces byte-identical HTML on any machine.2026in development
- 02The billing platformA billing system built on one split — the number that bills is never the number that merely displays — and the audit of my own dashboard that proved the invoice had been right the whole time.2024–2026prototype
- 03A cold-email sequencer in 512 linesGmail and a Google Sheet doing the job of a seat-priced sales tool, where the hard part turned out to be deliverability rather than sending.2026shipped
- 04WealthLensA goal planner is a compounding calculator wearing a UI, and the honest version of that UI has to admit what the calculator doesn't know.2026prototype
- 05An internal wiki that refuses to persuadeA read-optimized company wiki compiled to static pages, where the auth model's one limitation ended up designing the content pipeline.2026shipped
- 06The prototype that became the specA policy-management prototype for banks where every trust-critical decision was moved out of the model and into architecture, which is why there's no confidence score in the codebase.2026prototype
- 07The metric the dashboard refuses to showAn engineering-management dashboard whose defining constraint was a policy: individual metrics are self-service only, never leadership-visible, enforced in the data layer rather than the UI.2026shipped
- 08A CRM compiled to a single HTML fileA pipeline dashboard that started as one static file with the data baked in, and whose most useful view audits the pipeline's integrity instead of reporting its size.2026shipped
Also written
All writingWiki
A living map of what I do and care about, in 12 entries. Read the wiki