The short answer.
A workflow template is enough to start, and enough to learn what a piece of work needs from AI. A template becomes your workflow when you put in your own rules, records and standards, then test it on cases where you already know the right answer. You need a workflow built for your company when the work is particular to you, when it crosses several teams or systems, or when nobody inside has the time to capture it and test it.
Our workflow templates in the Workflows Directory are free. They are samples and a starting point, made to be customized, and we can build any workflow for your company.
What a workflow template is good for.
A workflow template is good for three things: starting fast, showing the shape of a piece of work, and giving your team something concrete to argue with.
- Starting fast.A template already sets out the inputs, steps, checks and output for a common piece of work, such as a client brief. Your team edits a draft instead of a blank page.
- Showing the shape of the work.A template shows what a good workflow contains: what it starts from, where it stops for a person to decide, and what it hands on. A prompt, a workflow template and a workflow shows the same task at all three levels of finish.
- Getting the real rules said out loud.Hand your best person a template and ask what is wrong with it. Every correction is a rule nobody had written down.
A workflow template does not know your clients, your thresholds or who signs off. Run as it stands, a template produces work that fits nobody in particular.
What you change in a template.
You change five things in every workflow template: the inputs, the rules, the exceptions, the output format and who decides. Change all five and the template becomes your workflow.
- The inputs.Name the exact records the workflow starts from, such as the export from your accounting system or the intake form. Say which fields matter and what a blank field means.
- The rules.Write in your own thresholds, terms and standards: the amount that needs a second approval, the clause you never accept, the tone your clients expect.
- The exceptions.List the cases where your best person stops and does something different, and what they do. Exceptions are where your company is most particular.
- The output format.Match the document your team already uses: its headings, order, file name and who receives it. A familiar document gets used.
- Who decides.Name the role that checks the output and where the workflow stops for that person. A person decides; a workflow prepares. Anything that sends, pays or changes a record waits for approval.
Test it on your own cases.
You test a customized template by running it on your own past cases, where you already know the right answer. Pick ten to fifteen cases from last month, including two or three awkward ones and one that went wrong at the time.
Compare each output with what your best person did and write down every miss. Each miss becomes a new rule, a new exception or a new test case. Run every case again after each change. A workflow is ready when its owner signs off every case without rewriting it. We have a plan. How do we build the first AI workflow? walks through that first build in order.
When you need a workflow built for your company.
You need a workflow built for your company in three situations, where editing a template lands worse than starting from how your team works today.
- The work is particular to your company.Your pricing method, your inspection standard, your way of writing a proposal. No template exists for it, because nobody else does it your way, and that know-how is why clients choose you.
- The work crosses several teams or systems.Work that starts in sales and ends in finance carries a handoff at every step. A workflow can be designed to pull from the systems you already run and push data back, with guardrails and a person approving. Designing those handoffs is build work.
- Nobody inside has the time.Capturing, writing and testing a workflow takes the attention of the person who knows the work. When that person also runs the work every day, the template sits half-edited.
We build workflows with you in a 3-Day Workflow Sprint or a 2-Week Workflow Sprint: one piece of work, taken from how your team does it today to a tested workflow your people run in your own ChatGPT, Claude, Copilot or Gemini. From a documented process to a workflow your team runs every week shows that path from a written procedure. See every price on the pricing page.
A “make this template yours” checklist.
Copy this next to any workflow template and fill it in with the person who does the work best.
- The work.The one piece of work this workflow prepares, in one sentence, and the team it belongs to.
- The owner.One person, by name, who keeps the workflow current and decides when it changes.
- The inputs.The exact records it starts from, and which fields matter.
- Our rules.The thresholds, terms and standards that replace the generic ones.
- Our exceptions.The cases where our best person does something different, and what they do.
- The output.Headings, order, file name and who receives it.
- Who decides.The role that checks the output, and where the workflow stops for them.
- What it never does.Anything it must not send, pay or change without a person approving.
- The test cases.Ten to fifteen past cases with known right answers.
- The miss record.Each miss, its cause and the change made, with every case run again.
- Ready when.The owner signs off the output on every test case without rewriting it.
Illustrative example.
Take a 55-person property management company. The operations lead takes a maintenance request workflow template and sits down with the senior coordinator. The inputs change first: requests arrive by email and through the tenant portal’s export, not a generic form. The rules change next: which repairs the coordinator approves alone and which go to the property manager. The exceptions take longest: after-hours leaks, and owners who approve every job. The output becomes the company’s own work order, and the coordinator decides every dispatch. They test it on fifteen past requests until the coordinator would send every work order unchanged. The owner statement workflow crosses three teams and two systems, so the company has that one built.
What is different in a company of under 200 people.
In a company of under 200 people, the person who knows the work best usually does it every day. That changes the template question three ways.
- Your rules live in a few heads.Large companies have written procedures to load into a workflow. Yours are often in one person’s memory. A template gives that person something to correct, and the corrections become the procedure.
- The same people decide and do.The workflow’s owner, checker and user are often two people, sometimes one. Name them anyway, so the workflow has a clear stop point.
- Time is the constraint.Your team can customize a template. The question is whether the person who knows the work can step away from it. When the answer is no, having the workflow built is faster.
Templates let you cover the whole company quickly: one customized template per team, then a built workflow where the work is yours alone. That is how 10X the ROI of your existing AI comes from seats you already pay for. How do we get more value from the AI we already pay for? takes that question further.
Where this fits in your plan.
Deciding between a template and a built workflow is part of planning: for each team’s first workflow, mark it “template” or “built”. How organizations plan their use of AI sets out the three steps around that choice: plan it, develop the workflows, deploy them. How to deploy AI workflows to a whole team, and keep them working covers what comes next. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, and choose what to build first.