A default crew for a company small enough that one person owns product, operations, growth, and research on the same day. Contexts only, with no Workflows or Connections.
For founders and first hires covering several functions at once.
Contexts
4
Product Manager, Operations Lead, Growth Lead, Researcher
How it works
An early team's real constraint is attention. Four jobs run at once, each gets a fraction of a founder's week, and the one that slips is usually research, which is the job that decides whether the other three were pointed anywhere worth going.
Four Contexts hold a function each. Product Manager supports product scope and prioritization. Operations Lead supports workflow design and ownership clarity, so the process a team is about to outgrow gets named before it breaks. Growth Lead supports revenue hypotheses and conversion opportunities. Researcher turns scattered inputs into useful insight, which is where the customer calls and the half-read notes finally add up. The bundle is those four Contexts, with no Workflows, Guardrails, or Connections.
Each job gets a considered answer rather than the ten minutes left over at the end of a day. The customer evidence sits in one place instead of four inboxes.
Installs 4 Contexts into your workspace: Product Manager, Operations Lead, Growth Lead, Researcher.
What's inside
Each context arrives ready to use and empty of your specifics. Add your private instructions and the setup answers the way your work actually runs.
Contexts
Supports product scope and prioritization.
Supports workflow design and ownership clarity.
Supports revenue hypotheses and conversion opportunities.
Turns scattered inputs into useful insight.
Releases
Shipped the four-Context founder bundle covering product, operations, growth, and research, so the function that gets the thinnest slice of a founder's week still gets a considered answer.
Sharpens the positioning, then turns it into campaign copy and a conversion read. Works from your pricing, the channels you already run, and the private instructions on each Context. Never claims a conversion lift the numbers do not show.
Splits a rough idea into scope, an implementation path, and the tests a release needs. Works from your roadmap, the repositories your team works in, and the private instructions on each Context. Never calls a release ready while a known edge case sits open.
Gives a leadership team one place to frame decisions, chase follow-through, and read morale. Works from the open decisions, your org chart, and the private instructions on each Context. Never settles a decision that belongs to the leadership team.
Get started
Start with the four questions you keep postponing to next week.
