A8gent
Templates

Free templates, prompts, and checklists. No newsletter wall.

Prompt packs, rollout checklists, scoping scripts, MCP server skeletons. Download, fork, and ship.

ForBuilders, operators, agenciesSEO teams, founders, content operatorsFounders, operators, team leadsOperators, agencies, foundersManagers, HR teams, enablement leadsFounders, operators, implementation leads
All 14Use 14
Use
Template

AI Agent Prompt Templates Pack

A free AI agent prompt pack with reusable prompts for planning, testing, debugging, and improving business agent workflows. Copy them straight in.

ai agent prompt templates
Beginner · 2.6 hr
Use
Template

AI Agent SEO Checklist

A free AI agent SEO checklist for publishing pages with clear intent, internal links, schema, and conversion paths, so every page earns its place.

ai agent seo checklist
Intermediate · 3.4 hr
Use
Template

AI Agent Risk Checklist

A free AI agent risk checklist for deciding what an agent can do automatically and what needs human approval before anything reaches a customer.

ai agent risk checklist
Intermediate · 4.1 hr
Use
Template

AI Agent Workflow Brief Template

A free AI agent workflow brief: one page that defines the workflow before you pick tools, prompts, or integrations, so the build never drifts off.

ai agent workflow template
Beginner · 2.2 hr
Use
Template

Team AI Agent Training Plan

A free team AI agent training plan: role-based lessons that teach employees agents through real workflows instead of random prompts. Copy and run it.

team ai agent training plan
Beginner · 2.6 hr
Use
Template

AI Agent Implementation Checklist

A free AI agent implementation checklist for piloting, testing, training, and measuring agents inside real business workflows. Copy it and start now.

ai agent implementation checklist
Intermediate · 3.4 hr
Use
Template

AI Sales Agent Workflow Template

A reusable workflow template for sales agents that research prospects, draft outreach, update CRM fields, and suggest follow-ups.

ai sales agent workflow template
Beginner · 4.1 hr
Use
Template

AI Content Agent Brief Template

A content operations brief for AI agents that research topics, produce outlines, repurpose assets, and support SEO workflows.

ai content agent brief template
Beginner · 2.2 hr
Use
Template

Customer Support AI Agent SOP

A customer support AI agent SOP template covering ticket triage, reply drafting, escalation rules, and knowledge-base gaps. Free to copy and adapt.

customer support ai agent sop
Beginner · 2.6 hr
Use
Template

AI Automation Agency Starter Kit

A free AI automation agency starter kit for packaging, scoping, pricing, and delivering agent workflow services to clients without underquoting.

ai automation agency starter kit
Intermediate · 3.4 hr
Use
Template

n8n AI Agent Workflow Templates

n8n AI agent workflow templates with approval steps and error branches built in, plus how to trace every node and rewire credentials before you go live.

n8n ai workflow templates
Beginner · 4.1 hr
Use
Template

AI Automation Proposal Template

A client proposal template for selling AI automation projects with scope, timeline, risks, pricing, and maintenance clearly defined.

ai automation proposal template
Intermediate · 2.2 hr
Use
Template

Client Discovery Call Script for AI Automation

A discovery script for uncovering client workflows, bottlenecks, tools, data readiness, approval needs, and AI automation opportunities.

ai automation discovery call script
Beginner · 2.6 hr
Use
Template

Free AI Automation Audit Template (2026)

A task-inventory audit template that scores every recurring task by frequency, minutes, and rule-based-ness, then ranks your top three automation candidates.

ai automation audit template
Beginner · 3.4 hr

What this collection is for

Fourteen documents meant to be forked: prompt packs, checklists, briefs, SOPs, proposal and scoping documents, plus a set of n8n workflow templates. Change the names, put your own numbers in, ship it. No newsletter wall, no attribution requirement, client work included.

A template solves the blank-page problem and nothing else. If you want a working automation rather than a document, this is the wrong hub - build guides are. And if your process changes weekly, a template will not survive contact with it; write the process down by hand for a month first.

How to choose

Match the template to the stage you are at. Grabbing them out of order is why most end up unopened.

  1. Deciding what to automate? The AI automation audit template scores your recurring tasks and ranks the top three. It is the right first document for almost everyone, and it pairs with the ROI calculator.
  2. Scoping a specific build? The workflow brief forces the trigger, inputs, outputs and approval rule onto one page, and the risk checklist catches what a brief misses. Both are worth filling in before you talk to anyone about cost.
  3. Selling it to a client? Take the discovery call script into the call, the proposal template out of it, and the agency starter kit if you are building the practice around it. Replace every placeholder range before the document leaves your machine.
  4. Building the thing? The prompt pack and n8n templates are the construction materials. For a specific job, the sales agent workflow, support SOP and content agent brief map onto the matching playbooks.
  5. Rolling it out to people? The implementation checklist and the team training plan cover the stage where automations are actually abandoned, which is weeks two to eight rather than launch day.

Where this sits

Templates are artifacts. Playbooks are the thinking behind them, guides are the wiring, tools generate the numbers you paste in, and learn supplies the vocabulary. When a template asks which platform to name, that answer comes from platforms or a head-to-head comparison rather than from the document itself.

What to do first

Fill in the audit template for your own business this week. It takes about an hour and it produces the one thing every later step needs: a ranked list of candidate workflows with real numbers beside them. Then either follow the matching build guide or bring the filled-in document to a free automation audit, where it will cut the scoping conversation roughly in half.

Three habits make templates worth the download. Fill them in the week you get them, because a half-remembered process produces a half-useful document. Replace every placeholder range with your own figures before anything leaves your machine - a proposal still carrying sample numbers is the fastest way to lose a room, and the ROI calculator and market cost ranges exist so you do not have to invent them. And put a name against every step of a checklist; unowned steps are the ones that quietly do not happen.

Everything here is free to use commercially, rebrand and ship to clients, with no attribution required. If you are building an automation practice on top of them, the hiring checklist is worth reading from the other side of the table - it is a fair list of what a client should be asking you.

How to use these

Everything here is meant to be forked

Prompt packs, rollout checklists, scoping scripts, MCP server skeletons: download it, change the names, ship it. No newsletter wall and no license games.

A template saves you the blank-page problem, not the thinking. The prompts still need your context, the checklists still need your names, and the skeletons still need your logic. What they save you is the hours spent getting the structure right.

Pair a template with the matching course or playbook and you skip straight to the interesting part of the work.

FAQ

Questions people ask

Still stuck? Ask us directly and we will answer.

Are the templates really free?

Yes. Download and use them, no email required. A few paid packs are marked clearly and are optional.

Can I use these commercially?

Yes. Fork them, rebrand them, ship them to clients. No attribution required.

What format are they in?

Prompts and checklists are copy-paste text or Markdown. Code skeletons are in the language named on the page.

Do these stay current?

We update the high-traffic templates when tools change. The rest are structural and age slowly.

Which template should I start with?

The AI automation audit template, unless you already know exactly what you are automating. It ranks your recurring tasks so the later documents are about the right workflow.

How is a template different from a playbook or a guide?

A template is the document you fill in. A playbook is the thinking about what the agent should do. A guide is the wiring that makes it run. Most projects need all three, in that order.

Buy them all

The full Operators course for $347. Less than 3 hours of contractor time.

Operators tier. Lifetime access. Every new chapter free. Refund in 7 days if we're wrong.

How to use these

Templates that save you the structure, not the thinking

Everything in this hub is meant to be forked. Prompt packs, rollout checklists, scoping scripts, proposal documents, and server skeletons: download one, replace the names with yours, and ship it. There is no newsletter wall and no attribution requirement, including for client work.

A template solves the blank-page problem and nothing else. The prompts still need your context, the checklists still need your team's names against each step, and a proposal still needs your own numbers. What you save is the several hours it takes to work out what the document should contain in the first place, which is usually the part people abandon.

Four families of document, and the job each one does

The templates here look like a flat list and they are not. They fall into four families, and the family determines when a template is useful, who reads it, and what happens if you use it at the wrong moment. Reaching for the right family is most of the value.

Decision documents, for before anything is built

The workflow brief, the audit template and the risk checklist belong here. Their job is to turn a vague intention into something specific enough to price, and to surface the reasons not to build before anyone has spent money. A good decision document frequently ends with the recommendation to leave a workflow alone, which is exactly what it is for.

The risk checklist is the one to reach for first if the automation will touch a customer. It sorts every action the agent might take by what a wrong answer costs and whether it can be undone, which is how the human approval points get placed rather than guessed at.

Client-facing documents, for winning and scoping work

The proposal template, the discovery call script and the agency starter kit are for people selling automation rather than buying it. They cover the parts that decide whether a project goes well: what is in scope, what is explicitly out, who owns what after handover, and what happens when the client's data turns out to be worse than described.

These are the two documents most people arrive here for, and the proposal template in particular is the most-used thing on the site. Its value is not the layout. It is the scope and handover language, which is where fixed-price automation work goes wrong.

Operating documents, for after it is live

The support SOP, the implementation checklist and the team training plan are for the phase everyone underestimates. An automation with no owner stops working within a quarter and nobody notices for a month. These documents name the owner, define what gets reviewed weekly, and set out what a person does when the agent escalates.

Build artifacts, for the person doing the wiring

The prompt pack, the workflow templates and the sales and content agent templates sit closest to the actual build. They are starting structures rather than finished automations: the prompts still need your context, and the workflow templates still need your credentials, your field names and your exception branches.

Bottom line: Decision documents come before money is spent, client-facing documents win and scope the work, operating documents keep it alive after launch, and build artifacts are structure rather than a finished automation.

Matching a template to the stage you are actually at

The commonest failure with templates is not quality, it is sequence. A proposal template downloaded before anyone has scoped the workflow produces a confident document full of numbers nobody has checked. A prompt pack downloaded before the workflow is chosen produces a folder of prompts with nothing to apply them to.

The order that works: first decide whether the workflow is worth automating at all, using the audit template or the workflow brief. Then size it, which is arithmetic rather than a document, and the free calculators do it faster than any template can. Then, if you are selling the work, write the proposal, by which point the numbers in it are yours rather than placeholders. Then build, using the artifacts. Then hand over, using the operating documents.

There is one honest exception. If you have a client call tomorrow and no scoping document, take the discovery script and fill it in during the call rather than before it. Its value is the questions, and the questions work cold. Everything else in the list rewards being used in order.

Bottom line: Decide, size, propose, build, hand over: a proposal filled in before the workflow is scoped is a document full of numbers nobody has checked.

How to adapt one without breaking what makes it work

Every template here has a load-bearing part and a decorative part, and adapting goes wrong when people rewrite the first and keep the second. The load-bearing part is usually the constraints: the scope boundaries, the out-of-scope list, the approval points, the stop conditions. The decorative part is the tone, the section order and the headings, which you should change freely to sound like yourself.

Three rules cover most of it. First, replace every placeholder number with one from your own workflow before the document leaves your machine. Sample figures shipping to a client is the fastest way to lose a room, and it is the most common way these documents embarrass someone. Second, keep the out-of-scope section even when it feels negative; it is the section that prevents the argument in week six, and clients respect it more than the feature list. Third, if you delete a question from the discovery script, write down why. Half the time the reason is that it is awkward to ask, which is precisely why it belongs.

For the build artifacts, adapt by adding context rather than by rewriting instructions. A prompt that underperforms is usually missing your specific definitions, your tone rules and your examples of a good and a bad output, not missing cleverness. Add three real examples from your own work before you touch the wording.

Version them once they are yours. A template you have filled in twice is on its way to being a process, and the second use is where you should be editing your own copy rather than downloading a fresh one.

Bottom line: Change the tone freely and keep the constraints: the out-of-scope list and the approval points are the parts that prevent the argument in week six.

What these templates deliberately do not do

They do not produce a working automation. A template is a document; a deployment is a different artifact with credentials and a failure log. The workflow templates get you a structure that runs, and there is still a real gap between that and something you would put in front of a customer.

They do not contain your numbers, and they will not generate them. Placeholder ranges are placeholders on purpose. We are not going to ship a proposal template with an invented saving in it, because the person who sends it without checking would be quoting a figure that came from nowhere and would have to defend it.

They do not replace the thinking. A scoping document filled in without talking to the people who do the work produces a confident description of a process that does not exist. The prompts still need your context. The training plan still needs your team's names against each step.

They also do not lock you in. There is no attribution requirement, including for client work, and no newsletter wall in front of them. If a template ends up in your own toolkit with your logo on it and your language throughout, that is the intended outcome rather than a misuse.

Bottom line: A template solves the blank page and nothing else: it will not produce your numbers, your process, or a running automation, and the placeholder ranges are placeholders on purpose.

Templates, courses, or having it done: which line you are on

These three are not competing products, they are three different amounts of your own time. It is worth being explicit about which one you are actually choosing.

Templates are free and they save you the structure, not the work. They are the right choice when you know the job and just need the blank page solved, or when you need a defensible document today. If you have already started the same document three times and stopped, this is the correct line.

The courses sell ordering and the production material nobody writes up for free: guardrails, evaluation cases, handover, and the failure modes that appear once a real user is on the other end. The starter kit at $29 is the honest entry point, because it covers one end-to-end build and answers whether you enjoy maintaining these things before you commit further. The agency material overlaps most with the client-facing templates here, and goes considerably deeper on scoping and handover than a document can.

The done-for-you route is the right answer when the hours do not exist, which is more often than people admit. We scope it on a free call, build it, and hand it over documented with a recurring plain-language report on what ran and what it saved. The audit produces the same analysis a filled-in scoping template would, written by us, and you keep the roadmap whether or not you hire us.

Bottom line: Templates save the structure, courses save the ordering and the production knowledge, and done-for-you saves the hours: pick by which of those you are actually short of.

What each template is for, and what it will not do
TemplateStage it fitsWhat you must replaceWhat it will not do
AI automation audit templateBefore anything is builtThe workflow list and your own volumesTell you which workflow to pick without your data
AI agent workflow briefScoping one specific workflowTrigger, systems, exception rulesDiscover the exceptions nobody told you about
AI agent risk checklistBefore anything touches a customerYour action list and what a mistake costsSet your risk tolerance for you
AI automation proposal templateSelling the workEvery placeholder figure, scope and priceGenerate defensible numbers you have not measured
Client discovery call scriptFirst client conversationNothing, the questions work coldQualify a client who will not answer honestly
AI automation agency starter kitSetting up the offerPositioning, pricing and scope boundariesReplace the agency courses on handover depth
AI agent implementation checklistRollout weekOwners against each step and your datesCover platform-specific configuration
Customer support AI agent SOPAfter it is liveEscalation paths and your tone rulesWork without a named owner reading it weekly
Team AI agent training planBringing staff onto itNames, systems and your review cadenceOvercome a team that was not consulted first
AI agent prompt packBuilding and debuggingYour definitions, tone and real examplesPerform without your own context added
n8n AI agent templatesWiring the buildCredentials, field names, exception branchesShip as a production automation untouched
AI sales agent workflow templateBuilding a follow-up agentSequence timing and stop conditionsDecide when the chase should stop
AI content agent brief templateBriefing a research or content agentSources, style rules and what is off limitsPrevent confident invention on its own
AI agent SEO checklistPublishing pages about the workYour keyword map and cluster planMake thin pages rank

How to pick one

  1. 1

    Match the template to the stage you are at

    Scoping documents and proposal templates are for the stage before anything is built, when you are still deciding whether the work is worth doing. Prompt packs and skeletons are for after that decision. Grabbing them in the wrong order is the most common way a template ends up unused in a downloads folder.

  2. 2

    Start from a workflow you already repeat

    The strongest signal that a template will pay off is that the underlying task already happens every week without one. If you are reaching for a template to create a process that does not exist yet, write the process down by hand first and template it once it settles.

  3. 3

    Fill in the numbers before you send anything

    Proposal and business-case templates ship with placeholder ranges on purpose. Replace them with figures from your own workflow before the document leaves your machine. Sending a template with the sample numbers still in it is the fastest way to lose the room.

A good fit if
  • Consultants and agencies who need a defensible scoping document today.
  • Owners who want to brief a builder without paying for the briefing.
  • Anyone who has started the same document three times and stopped.
Probably not for you if
  • You want a finished, working automation. A template is a document, not a deployment.
  • Your process changes weekly. Templates reward stable, repeatable work.

Where to go next

Book the free AI automation audit

A 30-minute call and a written opportunity report inside 48 hours. You keep the roadmap whether or not you hire us.

See the done-for-you service

We scope it, build it, hand it over with documentation, and send a recurring plain-language report on what ran and what it saved.

Build guides

Once you have the template filled in, the guides walk through actually wiring the workflow up.

Automation by industry

Owner-language workflow breakdowns for trades, clinics, salons, and professional services.

AI automation proposal template

Scope, out-of-scope and handover language, which is where fixed-price automation work usually goes wrong.

Client discovery call script

The questions work cold, so this is the one template that survives being used without preparation.

AI automation audit template

The decision document: what to automate, what to leave alone, and why, before anyone spends money.

AI agent risk checklist

Sorts every action by what a mistake costs, which is how the human approval points get placed.

AI agent workflow brief

Turns a vague intention into something specific enough to price or hand to a builder.

AI agent starter kit

The one priced item in the range at $29: prompt pack, workflow picker, ROI worksheet and rollout playbook.

ROI calculator

Produces the numbers that belong in the placeholder fields, in a few minutes rather than a meeting.

Agency pricing calculator

For the proposal template: what to charge for a scoped build, before the placeholders leave your machine.

Risk scorer

Runs the risk checklist as a scored tool, sorting each action by cost of a mistake and whether it reverses.

Build vs buy calculator

The arithmetic behind the templates, courses and done-for-you choice, using your own hours.

Automation glossary

Plain definitions for the scoping and reliability vocabulary these documents use throughout.

Agency bootcamp

Where the client-facing templates come from, with the scoping and handover depth a document cannot carry.

Industry constraints, worked example

What a scoping document has to add when the workflow touches regulated records and clinical software.

Consultant vs agency

For the buyer side of the proposal template: what changes when the work goes to a firm instead of one person.

Common questions

Are these templates really free?

The templates on this hub are free to download and free to use, including on paid client work, with no attribution requirement and no email wall in front of them. The one priced item in the range is the starter kit, which is a larger bundled package rather than a single document. If you fill a template in, rebrand it and use it as your own, that is the intended outcome rather than a misuse of it.

Which template should I start with?

Work backwards from what happens next. If a client call is the next event, take the discovery script. If a proposal is due, take the proposal template but scope the workflow first so the numbers in it are real. If nothing is decided yet, the audit template or the workflow brief is the right starting point, because both are designed to surface the reasons not to build before anyone spends money on it.

Can I use these with clients and charge for the work?

Yes. There is no attribution requirement and no restriction on commercial use. The proposal template and the discovery script exist specifically for consultants and agencies, and the scope and handover language in them is the part worth keeping rather than the layout. Replace every placeholder figure with your own before anything leaves your machine, because sending a document with sample numbers still in it is the fastest way to lose a room.

Why do the templates ship with placeholder numbers instead of real ones?

Because we do not know your volumes, your rates or your data quality, and any figure we printed would be invented for your situation. Placeholders are an instruction to go and measure. The free calculators produce the numbers in a few minutes: runs per week, minutes per run, and the payback window that follows. A proposal built on figures you have measured survives a question from the client's bookkeeper, and one built on ours does not.

Will a template get me a working automation?

No. A template is a document and a deployment is a different artifact, with credentials, error handling and a failure log a person reads. The workflow templates get you a structure that runs, and there remains real work between that and something you would put in front of a customer. The build guides cover the wiring, and the done-for-you service covers it if the hours do not exist on your side.

How do I adapt a template without breaking it?

Change the tone, the headings and the order freely. Keep the constraints: the out-of-scope list, the approval points and the stop conditions. Those are the load-bearing sections and they are the ones that prevent the argument in week six. If you delete a question from the discovery script, write down why, because half the time the reason is that it is awkward to ask, which is usually why it belongs there.

Do these work if my business is not in one of the industries you cover?

Yes, because the documents are structured around the shape of the work rather than the trade. A scoping brief asks the same questions of a dental practice and a software company; what differs is the compliance section and which systems the workflow touches. The industry pages carry the trade-specific constraints, so the useful combination is a template from here and the relevant industry page for the parts that are specific to you.

What is the difference between the templates and the courses?

A template saves you the structure of a document. A course sells the ordering and the production knowledge that nobody writes up for free: guardrails, evaluation cases, handover, and the failure modes that only appear with a real user on the other end. The starter kit at $29 is the entry point and covers one end-to-end build. If you know the job and just need the blank page solved, stay on the free templates; they are not a lesser version of the paid material.

How often are these updated?

The documents change when the underlying practice changes rather than on a schedule, because scoping questions and handover terms move slowly. Anything that carries a price or a tool-specific instruction is the part that dates, and those figures live on the cost, platform and comparison pages with a checked date attached rather than inside a template. If you have filled one in twice, edit your own copy rather than re-downloading; by then it is your process, not our template.

If you would rather skip the document entirely, book the free audit. You get the same analysis a filled-in scoping template produces, written by us, in under a week.