Meagan SwensonBack to the main site
Case study · Mission Control · October–November 2026

Built with Claude, with Claude built in

Mission Control runs a small web studio, from the first conversation with a client to launch day. I built it with an agentic workflow in Claude Code. Then I built an AI feature into it: Navigator drafts a client proposal from the intake. Both are live, with a demo anyone can try.

43user stories, each with acceptance criteria before any code
937automated tests: 837 Pest, 77 Vitest and 23 browser tests
14architecture decisions on record, from hosting to AI limits
45 daysfrom the first commit on October 4 to live AI drafts on November 18
The problem

A studio's work is scattered

I ran a web studio for 13 years. Scope, colors, design feedback and launch checks lived in emails, spreadsheets and memory. Turning a client's wishes into a priced proposal took an evening.

Mission Control puts that in one place, in four modules: Scope (intake and proposals), Palette Lab (color contrast), Proofmark (comments pinned on designs) and Launch Control (automated checks and a go/no-go board). Clients get their own portal, Launchpad, with one list of everything waiting on them.

Laravel 13PHP 8.5React 19TypeScriptInertiaTailwind 4MariaDBClaude API
How it was built

The agentic workflow

I direct, Claude Code builds, and I review every change. The same five steps ran for every feature.

  • 1. Story first. A user story with acceptance criteria, approved before any code.
  • 2. One story at a time. Claude Code builds it in small commits, with feature tests, and unit tests for real logic.
  • 3. Review per story. Correctness, security and accessibility, with the findings written into the commit message.
  • 4. Decisions on record. Significant choices become an ADR; ideas out of scope go to a backlog.
  • 5. CI on every push. Secret scan, code style, static analysis (Larastan level 7), TypeScript, tests on MariaDB, and every autopilot tour in headless Chromium with an accessibility scan. Then a deploy, and a browser test that clicks through the live site.

The project's rules live in a CLAUDE.md file that every session reads: the stack, the commands that must pass, the patterns to reuse and the mistakes not to repeat. It grew with each lesson below.

What I'd do differently

Lessons, now rules

  • List the host's limits on day one. The app runs in a subfolder on shared hosting with no shell, no queue worker and possibly no proc_open. Some of this I found mid-build; one-off server tasks now need a web route.
  • Check a library before adding it. A notification library injected styles at runtime and broke the strict Content-Security-Policy. It was removed; new libraries are checked for this first.
  • Test the real site, not just the server. Pages looked fine in the subfolder while links in the browser pointed at the site's root. CI now checks the route prefix, and a browser test clicks through production after every deploy.
  • Mirror production's quirks in CI. The production database defaulted to an engine without transactions. A test now guards the engine, and CI runs with the same default.
  • Order the safety nets. The app's AI cap was first set above the API account's spend limit, so the account would have stopped first and the warning email never sent. The cap now sits below it.

Hire me for AI work

I'm available for part-time, remote contract work as CodeLaunch: AI features in real products, built and tested like the rest of the app.

Watch the demoSource on GitHubEmail meLinkedIn