Darren Card · October 2026

The modern agentic product tool stack.Agents do the work. People make decisions.

My go-to stack for building with AI.

Running most of it on Dacard’s own work
Agents do thisWhere it’s built and runsAgreed by the teamEveryone reads this first
  1. 01

    Agree once, then move

    Product, engineering and data set these up front. After that they run on their own.

    Ground rules

    What we agree on together.

    HumanWrite it down firstThe problem, what good looks like, what it can cost.checked after launch
    HumanOne source of truthEvery tool knows a customer by the same ID. Each metric is defined once, with the data team.same answer everywhere
    HumanChecks before mergeTests, AI quality and security checks run on every change, automatically.every change
    HumanSecurity and spendKeys live in a vault. Personal data stays out. Spend alerts fire on their own.security · spend
  2. 02

    Load the context once

    Every agent starts from what we already know. Nobody re-explains.

    Shared knowledge

    What every agent reads first.

    GitHubDecisions logStrategy and decisions, kept in a GitHub repo.GitHub
    ClaudeClaude projectsBriefs, the glossary, past answers.Projects · memory
    Google DriveNotionDustCompany docsThe wiki and shared drives. Dust makes them searchable for agents. Read-only.approved access
    ClaudeAgent rulesHow agents work and when they stop and ask. Every mistake becomes a new rule.written rules
  3. 03

    Let agents do the legwork

    Reading, drafting, checking and summarising happen in the background.

    Daily tools

    What I’m in all day.

    Claudev0Think and buildThinking, writing, coding, prototyping.Claudev0
    GranolaSlackGoogle WorkspaceMeetings, chat and emailEvery call and thread summarised for me. Email, calendar and docs in Google Workspace.GranolaSlackGoogle Workspace
    PostHogMotherDuckUsage dataWhat users actually do, on the data team’s definitions.PostHogMotherDuck
    LinearInfisicalPlans and keysEvery plan gets a goal and a number. Keys live in Infisical, never in code.LinearInfisical
  4. 04

    Build, ship, see it live

    On my own builds I run these. On a team, engineering owns them and I see what shipped and how it’s doing without asking for a report.

    Build and run

    Where the product is built and runs.

    GitHubVercelCode and releasesBuilt with Next.js, TypeScript, Tailwind, shadcn/ui and the AI SDK. A preview on every change.GitHubVercel
    StripeSupabaseBilling and app dataBilling and app data. Read-only.StripeSupabase
    MintlifyInngestDocs and jobsAPI docs with an llms.txt agents read directly. Jobs run in the background.MintlifyInngest
    ResendPlainEmail and supportEmail the app sends, and the support inbox.ResendPlain
  5. 05

    Bring it to market

    Agents find accounts, enrich them and draft the message. A person chooses who to contact and sends it.

    Go to market

    Find, reach and keep customers.

    AttioCal.comCRM and bookingEvery customer and deal, on the same ID as the product. Calls booked in Cal.com land on the same record.AttioCal.com
    ClayLists and enrichmentAccounts found and enriched. A person checks before anyone is contacted.Clay
    Common RoomPostHogBuying signalsWho is showing intent, from the community and the product.Common RoomPostHog
    lemlistPostHogOutreachOutbound sequences across email and LinkedIn in lemlist. Lifecycle email from PostHog.lemlistPostHog
  6. 06

    Ship in a tight loop

    People start it and call it. Agents carry the middle.

    1. HumanDecideWrite down the goal.People
    2. ClaudeGitHubBuildEngineers and agents build it together.Mostly agents
    3. VercelPostHogShipRelease to a few users first.Mostly agents
    4. PostHogMotherDuckMeasureUsage and revenue, one view.Mostly agents
    5. GranolaClaudeListenCalls tell us why.Mostly agents
    6. HumanCall itKeep it, change it or stop it. Landed, watch or stalled.People
  7. 07

    Take it anywhere

    Same setup for client work, in their accounts. At a company, IT signs off first and changes go through the team that owns each system.

    Their accountsTheir repos, hosting, data and keys, from day one.GitHubVercelSupabase
    My toolsI bring my own tools.ClaudeGranolaLinear
    Prototype firstClickable first, production later.Claude Designv0
    My rulesThe goal, the checks and the call come with me.goal · checks · call
  8. 08

    Every tool, in one place

    Grouped by job, in the order the work happens.

    ToolLayerUseHow Claude connects
    Plan2 tools
    ClaudeDaily toolsAnalysis and specsClaude.ai, Cowork
    LinearDaily toolsPlans and resultsConnector
    Collaborate3 tools
    SlackDaily toolsTeam chatConnector, read-only
    Google WorkspaceDaily toolsEmail, calendar and docsConnector
    GranolaDaily toolsMeeting notesConnector
    Shared knowledge2 tools
    NotionShared knowledgeWiki and specsConnector, read-only
    DustShared knowledgeCompany knowledge, searchable by agentsRead-only
    Design3 tools
    Claude DesignDaily toolsPrototypesPart of Claude
    v0Daily toolsUI draftsVia GitHub
    Listen LabsDaily toolsUser interviews, run by AIAPI
    Build7 tools
    Claude CodeBuild and runBuilds and opens PRsDesktop app
    GitHubBuild and runCode and checksConnector
    VercelBuild and runHosting, previews and firewallConnector
    SupabaseBuild and runApp dataRead-only
    StripeBuild and runBillingRead-only
    InngestBuild and runBackground jobsDashboard
    ResendBuild and runEmail the app sendsAPI
    Quality and security2 tools
    Better StackBuild and runUptime checks and alertsAPI
    InfisicalDaily toolsKeys and secretsCommand line, MCP
    Data and insights2 tools
    PostHogDaily toolsUsage, flags, replays and errorsConnector
    MotherDuckDaily toolsWarehouse and shared metricsConnector
    Go to market5 tools
    AttioGo to marketCustomers and pipelineAPI
    ClayGo to marketLists and enrichmentAPI
    Common RoomGo to marketBuying signalsAPI
    lemlistGo to marketOutbound sequencesAPI
    Cal.comGo to marketBooking callsAPI
    Docs and support2 tools
    MintlifyBuild and runAPI docs and llms.txtConnector, read-only
    PlainBuild and runSupport inboxAPI