Workflow templates

A template turns an empty workflow into a staffed assembly line in one step. Choose Start from a template on a new, empty workflow, or pick one when you add a workflow to a factory.

What a template sets up

1. The stations. The workflow's columns are replaced with the template's.
2. The workers. The agents the template needs are installed into your workspace — once, however many templates use them — and each is put on its station.
3. The routes. How each worker starts, and where a card goes when it passes or fails.
4. The manager. The agent asked when work is stuck, chosen for the template's kind of work, installed and switched on. The picker names it before you choose, and you can change it from the workflow's header. See Workflow managers.

The workflow runs the moment it opens. Everything a template sets is ordinary configuration, so change any of it afterwards — see Staff your first station.

Templates apply to an empty workflow only: no cards and no agents. One with work in it refuses, so a template can never overwrite what you have done.

The shape most of them share

• The first station has a way out. A story its agent finishes passes to the next worked station and starts the pipeline; you can ask to review the stories first.
• The first station is a conversation. Its agent has no triggers: you open it, ask for what you want — write me user stories for refunds — and it writes cards into its column. See Conversations.
• The middle stations start when a card is dropped in, pass forward, and fail back to the station that can fix the problem.
• In most, the last station before the end is a person.
• The final column has no worker. The card is finished.

Finding one

The picker groups templates by category and searches their names, descriptions and tags — someone looking for "invoices" finds Invoicing & collections without knowing it is filed under Finance.

Start a business

Idea validation — Ideas → Customer & problem → Market research → Competitors → Experiment design → Go / no-go → Validated Find out whether an idea is worth building before anything is built: the customer, the evidence, the competition and the cheapest test.

Business plan — Outline → Business model → Pricing → Go-to-market → Financial model → Review → Founder sign-off → Final A plan written section by section: the model, the market, pricing, the go-to-market and the numbers, reviewed before you sign it off.

MVP build & launch — Scope → Design → Build → QA → Landing page → Launch approval → Launched From a validated idea to a launched first version: scope, design, build, QA, a landing page and the launch itself.

Fundraising round — Strategy → Pitch deck → Financials → Investor research → Outreach drafts → Founder review → Sent Run a raise as a pipeline: the strategy, the deck, the numbers behind it, investor research and outreach you approve before it goes.

Brand & website launch — Brief → Brand identity → Website copy → Design → Build → SEO check → Approval → Live Positioning first, then the identity, the copy, the site and an SEO check before it goes live.

Pricing & packaging — Questions → Research → Model → Revenue impact → Pricing page → Decision → Rolled out Decide what to charge: research, a model, the page that sells it and a test before you commit.

Run a business

Quarterly planning (OKRs) — Proposals → Key results → Baselines → Budget check → Leadership review → Committed Set the quarter: proposed objectives, the numbers behind them, a feasibility check and leadership sign-off.

Weekly operations — Inbox → Triage → In progress → Review → Done One place for everything the business needs done this week, triaged, worked and reviewed.

Process & SOP library — Processes → Map the process → Draft procedure → Plain-language edit → Owner approval → Published Write down how the business runs: map each process, draft the procedure, test it on someone new and publish it.

Vendor selection — Needs → Research → Scoring → Contract review → Budget check → Decision → Signed Buy well: written requirements, a scored shortlist, a contract check and a budget check before anyone signs.

Policies & compliance — Requirements → Draft → Security review → Plain-language edit → Approval → In force Get the policies a growing company needs written, checked for risk and approved — with what needs a lawyer clearly marked.

Client project delivery — Requests → Plan → In delivery → Quality check → Client review → Delivered For agencies and consultancies: scope, plan, deliver, check the work and get the client's sign-off.

Board & investor update — Topics → Metrics → Financials → Narrative → Edit → Approve & send → Sent The monthly update, assembled: the metrics, the finances, the narrative and an edit before you send it.

Sales

Outbound prospecting — Target accounts → Research → Qualify → Draft outreach → Approve → In sequence → Disqualified Target accounts researched, qualified and written to — with the first email approved by you before anything is sent.

Deal pipeline — New leads → Qualification → Discovery → Proposal → Terms → Negotiation → Won → Lost A sales pipeline where each stage does its work: qualification, a discovery summary, the proposal and the terms.

Proposals & RFPs — Incoming → Draft response → Pricing → Contract check → Edit → Approval → Submitted Answer an RFP without the scramble: requirements broken out, a draft, pricing, a contract check and an edit.

Marketing

Content production — Brief → Research → Draft → Editorial review → Human approval → Published From a brief to research, a draft and an editorial review, published only after you approve.

SEO program — Opportunities → Audit → Content plan → Write → On-page check → AI search check → Approval → Published An SEO backlog that works itself: audit, a content plan, the writing, on-page checks and AI-search readiness.

Email campaign — Campaign ideas → Sequence plan → Copy → Edit → Tracking → Approval → Scheduled Plan the sequence, write it, edit it and get the numbers set up before the first send.

Social media calendar — Ideas → Draft posts → Edit → Approval → Scheduled → Published A steady social presence: ideas turned into posts, edited and approved before they are scheduled.

Product launch — Launch plan → Positioning → Launch page → Email → Social → Tracking → Go / no-go → Launched Everything a launch needs, in order: positioning, the page, the emails, social, and tracking so you know if it worked.

Conversion experiments — Hypotheses → Test design → Variant → Build → Running → Readout → Decision → Shipped A growth backlog: a hypothesis, a valid test design, the variant, and a readout you can trust.

Customers

Support desk — New tickets → Triage → Draft reply → Approve reply → Escalated → Resolved → Closed Tickets triaged and answered, with the reply approved by a person and a help article written when the question keeps coming back.

Customer onboarding — New customers → Success plan → Kickoff → Setup → Adoption check → Live Every new customer gets a plan built around what they bought the product for, and a check that they got there.

Feedback to roadmap — Feedback → Themes → Size the demand → Prioritise → Stories → Roadmap review → Planned → Not now Customer feedback that goes somewhere: grouped into themes, sized, prioritised and turned into stories.

Renewals & churn rescue — Accounts → Health review → Usage analysis → Recovery plan → Outreach → Approve → In progress → Renewed At-risk accounts worked deliberately: a health review, a recovery plan, the outreach and your approval.

Finance

Month-end close — Close tasks → Reconcile → Accruals & adjustments → Reports → Variance review → Sign-off → Closed The close as a checklist that checks itself: reconciliations, accruals, the reports and a review before sign-off.

Invoicing & collections — To bill → Prepare invoice → Approve → Sent → Overdue → Follow-up sent → Paid Get paid: invoices prepared and checked, approved by you, and overdue ones chased politely and on schedule.

Budget & forecast — Requests → Cost it → Cash-flow impact → Prioritise → Approval → In budget → Deferred Build the budget from requests: each one costed, checked against cash, prioritised and approved.

People

Hiring pipeline — Roles → Job description → Edit → Open → Screen → Interview kit → Hiring decision → Offer → Not moving forward Hire with structure: the role defined by outcomes, a consistent screen, an interview kit and a written decision.

Employee onboarding — New hires → Onboarding plan → Accounts & access → Manager review → First week → 30-day check-in → Onboarded A new hire's first ninety days, planned by week with owners, accounts set up, and a check-in that actually happens.

Performance reviews — Review cycle → Gather evidence → Draft review → Tone & clarity edit → Manager approval → Delivered Reviews written from evidence, calibrated, and delivered by the manager — not invented the night before.

Product

Agile discovery — Ideas → Business analysis → INVEST review → Gherkin acceptance → Ready Turn rough ideas into ready stories: analysis, an INVEST review and Gherkin acceptance tests.

User research — Questions → Research plan → Interview guide → Fieldwork → Synthesis → Findings → Shared Research questions answered properly: a plan, an interview guide, synthesis into a journey and findings you can act on.

Roadmap planning — Opportunities → Score → Strategy fit → Size it → Roadmap review → On the roadmap → Parked Opportunities scored, checked against strategy and sized before they earn a place on the roadmap.

Software

Software delivery — Backlog → Design → Development → QA → Human review → Done Stories from a business analyst, then design, a React engineer who opens draft pull requests, QA and your sign-off.

Bug response — Reported → Reproduce → Fix → Regression → Done Reproduce a report, fix it in a draft pull request and prove the regression is gone.

Secure delivery — Requirements → Threat model → Development → QA → Security review → Approval → Done Software delivery with a threat model up front and a security review before your approval.

API delivery — Contract → Implementation → Contract tests → Security → Documentation → Done Contract first: implementation, contract tests, a security pass and documentation.

Incident response — Reported → Triage → Investigation → Mitigation → Verification → Postmortem → Done Triage, investigate, mitigate and verify, and finish with a postmortem.

Accessibility audit — Scope → Automated checks → Keyboard review → Screen reader review → Remediation → Verification → Done Audit a product area, remediate what is found and verify it with the same tester.

Commerce release — Backlog → Build → Checkout QA → Mobile QA → Merchant approval → Done Storefront changes built, then checkout and mobile QA, then the merchant signs off.

Platform migration — Inventory → Compatibility analysis → Migration → Data verification → Regression → Approval → Done Inventory what exists, migrate it, and verify the data and behaviour before approval.

Tech debt paydown — Debt register → Assess → Refactor → Regression → Review → Done → Won't fix Debt paid down on purpose: each item assessed for risk, fixed in a draft pull request and regression-checked.

Data & analytics delivery — Requests → Define the metric → Build → Data verification → Review → Live From a question to a trusted number: the metric defined, the pipeline built, the data verified and the dashboard reviewed.

Robotics simulation — Requirements → Design → Simulation → Safety review → Human hardware approval → Done Design and simulate before anything touches hardware, with a safety review and a human gate.

Building a factory from templates

Templates are per workflow, and a factory holds several. A software team might start with Software delivery, Bug response and Incident response side by side, then add routes between them — see Handoffs between workflows.

These are starting points, not rules. The agents are your workspace's once installed.