Workflows
AI Workflows
Browse repeatable workflows that turn ZeroTwo into an AI agent for sales, engineering, operations, finance, research, and startup teams.
Competitor research
Gathers the public material on companies you name, separates positioning claims from what the product demonstrably does, and produces a comparison you can hand to a team.
Meeting preparation
Reads the invite, the account history, and the recent threads, works out what the meeting actually turns on, and produces a brief with the open items and a suggested agenda.
Revenue reporting
Pulls the period's numbers from your billing and CRM systems, reconciles the two where they disagree, and produces the recurring report in the format you already use.
GitHub triage
Reads everything that landed in the repository since the last pass, groups duplicates and stale threads, and proposes a label, a severity, and an owner for each issue left standing.
What a workflow means here
A workflow on this page is a description of a repeatable job, not a flowchart you have to assemble. There are no nodes to wire together and no branches to configure. You describe the outcome in plain language, ZeroTwo works out the steps, and the same description can be re-run whenever the job comes around again.
The shape of a workflow
Nearly every workflow here has the same three parts: a source of truth to read, a judgment to apply, and an artifact to produce. A pipeline health briefing reads the CRM, applies your definition of a stalled deal, and produces a ranked list with the reason each deal is on it. A release note reads the merged changes, decides which of them a customer would care about, and produces the copy. Naming those three parts explicitly is most of what separates a workflow that holds up from one that needs rewriting every time.
Turning a run into something reusable
Run it once by hand and read the result critically: what did it miss, what did it over-weight, what format would you rather have had. Fold those corrections back into the description rather than fixing the output. After two or three passes the description usually stops needing edits, and that is the point at which it is worth putting on a schedule or sharing with the team.
Why the groupings are by function
The workflows are grouped by team because the source systems differ, not because the mechanics do. Sales and marketing work leans on the CRM, the calendar, and ad platforms; engineering work on repositories and issue trackers; operations and finance on spreadsheets, payment processors, and accounting systems; research on the open web alongside your own documents. The underlying loop is identical across all of them — only the connected apps and the judgment change.
What to expect from a first run
Treat a first run as a draft rather than a filing. ZeroTwo is good at gathering everything relevant and giving it a structure; it does not know which account is politically delicate or which number your finance lead checks first. Expect to edit, and expect the edits to shrink as the description gets more specific. Work that turns on a judgment call every single time — pricing exceptions, personnel decisions — is better kept manual, with the agent doing the research underneath it.