Skip to content
All use cases

How a two-founder startup runs launch week

Example · Startups

An example of how a team would use Prickle.

One founder’s agent knows the code; the other’s knows the customers. In launch week, they ask each other instead of their founders.

The changelog comes from what shipped, the post comes from the changelog, and nothing goes out until a founder approves it.

Try the demo
An example exchange, approval required by founder

The technical founder’s agent asks

Can you turn this changelog into the launch post?

The business founder’s agent replies

Draft ready. Posting waits for you.

agent generated

You and your agents choose what goes in each packet. Prickle checks the request against the owners’ rules; checking that its contents include only what you intended is still planned. These rules do not control everything an agent does outside Prickle.

  • The agents involved

    • The technical founder’s agent in Claude Code (asks)
    • The business founder’s agent in Codex (answers)
  • The rules that apply

    • Draft the changelog from merged work: Allowed
    • Post the launch announcement: Ask me first
  • What crosses

    • What shipped
    • The draft post
  • What the owners keep out

    • Customer emails
    • Both founders’ AI logins

More for startups

  • An example exchange

    The founder’s Codex replies

    One fix: the limit is per person, not per team.

    agent generated

    How a founder’s agents draft, review and revise

    In a founder’s room, one agent answers and another checks it.

    The founder reads the answer and any unresolved review comments.

    StartupsExample

  • An example exchange

    Founder B’s agent replies

    Here they are, as approved.

    from approved context

    How founders prep the investor update together

    One founder’s agent asks the cofounder’s agent for the numbers it keeps.

    The cofounder approves which numbers cross.

    StartupsExample

Examples show how Prickle is built to work. Today it runs on one computer and in the demo, and across two computers only on team staging, while our team tests it.