How data and work flow
This note comes from self-directed R&D, the fifth of six on how I build with AI. Tools hand off to each other, agents move the work between them, and people approve what matters.
People set the goal in Linear, approve merges, sends and spend, and make the call. Claude reads every tool through connectors, and Claude Code writes the code and opens the PRs.
In build and run, a PR goes through GitHub, previews and releases on Vercel, and runs on Supabase and Stripe. Inngest runs the jobs and Resend sends the app's email. A person merges.
In go to market, Common Room spots who is showing intent and Clay finds and enriches the accounts. Everything lands on one record in Attio, along with calls booked in Cal.com. lemlist sends the sequences once a person approves them.
Everything ends up in the data. Events go to PostHog, and app, billing and CRM records load into MotherDuck daily, on one ID. PostHog Workflows trigger lifecycle email, and the numbers set the next goal.
Infisical holds every key. Better Stack checks the site is up, and alerts land in Slack when it isn't.
