Case studies
What a startup would ask for
Five roles at a startup, five ordinary weeks. Each one is a single request to the agent the team already uses, and the page that comes back.
These are scenarios, not customer stories. No company, person or figure in them is real. What is real is the product: every step uses something it does today, and each page says what it does not do.
Pick the week that looks like yours
- FoundersA projection you can edit, and an update for investors that is a link rather than a deck.
- EngineeringA sprint review or a retrospective your agent assembles from the work it just did.
- ProductA feedback survey for users, and the answers read back in one place.
- PeopleA hiring board for one role, and an onboarding checklist for the person you hired.
- RevenueAn onboarding page for one customer, shared with the people on their side.
What they have in common
- Each starts with one request to an agent — Claude Code, Codex, Cursor or any of the others that connect over MCP — not with a new tool to learn.
- Each ends with a page at a real address, private until you share it, and every answer typed into it comes back to your agent as data.
- None of them runs on its own. Nothing here is scheduled and nothing sends email; a weekly update is a request you make each week.
Your first artifact is one conversation away
Connect the agent you already use, describe what you want, and it is live at a URL a reviewer opens on a phone.
Or point any MCP harness at one URL