AI is going to help you ship something great: it should also prepare you for the boring side of success.
I build business software, which isn't as boring as it sounds: I’ve helped prevent wildfires by guiding goats into fields to eat brush. I’ve gotten mental health professionals billions in payments from insurers. I’ve shipped tanks on ships.
Basically, I love creating the button that makes a user feel like they just cheated at their job. They’ve been correlating data across three screens, exporting to a spreadsheet, doing the real work outside the application (looking at you, Hubspot), and feeding it back in. You watch them do it, you understand the domain well enough to see what’s really happening, and you collapse the whole mess into one click. That’s the craft. That’s why I do this.
But You Can’t Skip the Foundation
None of that magic exists without the boring stuff underneath. The data model, the forms, the validation, the CRUD that nobody celebrates but everybody needs. Budgets and timelines are ruthless about this: the foundation eats your quarter, and when someone above you says “it works, ship it,” the magic button gets de-prioritized into the backwaters of the backlog.
This is where AI is my magic button. It fast-forwards us past the foundation, doing the models, endpoints, forms, and validation so we can get to the real work before the budget runs out or the roadmap shifts underneath us. Hand-building the interactions that require you to actually understand the domain, not just model it.
AI didn’t take the craft away from me. It gave me a faster path to it.
And Then It Ships
The magic button works. Users love it. The product gets traction. Revenue shows up. And right behind revenue, questions.
What PII does this system touch? Show me the requirements traceability. How was this feature designed and who reviewed it? Where’s the documentation? You want me to spend a week on a data categorization and classification framework?
And then use it on every new feature?
People think compliance is a problem for healthcare, finance, and government. It’s not. It’s a problem for success. Any commercial software that handles user data will face questions about GDPR, PII, data retention, and audit trails. The questions assume you were keeping records from day one, not from the day you got big enough to attract attention.
We Built a House Without Permits
We weren’t keeping records from day one. We were building. The agents that compressed our foundation didn’t capture the design decisions, the architectural tradeoffs, the reasoning behind the approach. That context lives in chat logs that expired last month. The specs, if they exist, are stale prompts in someone’s terminal history. The PRs got merged because the feature worked and the deadline was yesterday.
Beautiful house. People moved in. Inspector’s at the door asking for permits nobody pulled.
It’s boring stuff, but every feature shipped without traceability is a permit that didn’t get filed. Process debt compounds exactly like tech debt, except nobody discovers it until someone with authority comes asking. And retroactive permitting, after the tenants are already in? I once lost a year of an entire team's time to it.
What If the Tool Filed as It Built?
The tooling market is focused on pouring foundations faster, but the hard problem was never “build the house.” It was “build the house and be ready when the inspector shows up.” We compressed the construction and did nothing for the permits.
We built Cate to do the boring parts, and not just in code. The boring parts that protect the exciting parts.
From spec to merge, everything’s on file. Before code starts, Cate’s planning workflow produces issues with acceptance criteria, codebase context, diagrams, and test plans. That spec isn’t just documentation for humans; it’s the context agents use to build. After implementation, PRs link to issues, commits link to PRs, and the whole chain is traceable in the tools your team already uses: Jira, GitHub, GitLab, Linear. Structured templates mean every developer and every agent produces the same artifacts, every time. When someone asks “how was this built and why,” the answer is already on the board.
Inspections during construction, not after occupancy. Your team’s quality gates (linting, formatting, tests, validation) run before every PR. An AI review agent reads the diff against the original spec and flags gaps before a human reviewer ever sees it. The standards are yours; Cate enforces them so you don’t have to.
Your industry, your permits. The templates, PR messages, issue formats, and workflow prompts are Markdown you control. If your industry requires a specific compliance section in every spec, add it to the template. And if those templates don’t exist for your situation, Cate makes it easy to build them. Cate handles the practices that are universal. You define the ones that are specific to your world.
Cost per issue, not per month. When your manager asks what AI is costing and what it’s producing, you have per-issue answers, not a monthly aggregate with no connection to the work. But that’s a bigger conversation, and one for another day.
Build the House. File the Permits. Get to the Magic.
The point was never to slow down. AI compresses the foundation, and that’s real, valuable, worth celebrating. The point is that success has requirements beyond working code, and the tools that help us build faster should also prepare us for what success brings.
The permits aren’t just for the inspector, either. They’re context that makes the next phase of construction better. Agents build better code when the specs, decisions, and research from prior work are already on file. Humans review faster when there’s rationale next to the diff.
The boring part of the process is what lets us keep the house after the inspector arrives. Automate that, and we’re free to do what we’re actually good at: building the thing people care about.
I need to wrap this up, because while I was writing it, I got these:
[devcontainer/resolve] [6/6] Preflight passed
[sdk/containerSpawn] devcontainer exec....That’s a Cate+Opus session telling me a magic button just came online. And I have the paperwork to prove it.
That’s the bet we’re making with Cate: file the permits while you build, so you’re ready for success when it shows up. Request early access or get in touch.