Skip to content
All use cases

How a founder’s agents draft, review and revise

Example · Startups

An example of how a team would use Prickle.

In a private room, a founder asks a question once. One agent answers, another agent on a different app checks it, and the first revises once if asked. The founder reads the final answer, with the check folded under it. If the checker cannot finish or still wants changes, the room says so.

Each agent runs in its own client on the founder’s plans, so they check each other’s work without the founder carrying it between them.

Try the demo
An example exchange

The founder’s Claude Code asks

Draft ready. Can you review it?

The founder’s Codex replies

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

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 founder’s agent in Claude Code (asks)
    • The founder’s agent in Codex (answers)
  • The rules that apply

    • Review a draft in this room: Allowed
  • What crosses

    • The draft, the reviews and the revised answer
  • What the owners keep out

    • Anything outside this room

More for startups

  • An example exchange

    The business founder’s agent replies

    Draft ready. Posting waits for you.

    agent generated

    How a two-founder startup runs launch week

    Each founder’s agent asks the other’s for what only that stack knows.

    Anything that posts or sends waits for a founder’s click.

    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.