AI Playbooks & Prompt Systems
Most AI capability lives in one person's head. We productise it, into a versioned prompt library and workflow playbooks that any team member can run, any new hire can inherit, and the business owns. Built around your real workflows. Yours to edit, extend, and govern.
The pattern we keep seeing.
A team trains on AI, the enthusiasts build private prompt lists, the laggards never catch up. Six months later, capability is unevenly distributed across the team, and the moment your best AI user resigns, three months of compounding capability resets to zero.
Capability is sitting in one person's head.
Your most AI-fluent staff member has 40 prompts in a private Notion. Two are in their head. When they leave, capability resets to zero.
Your house style is fragmenting.
Fourteen people write client emails fourteen ways. AI is making the gap worse, not better. The team needs one shared library, not 12 private ones.
Auditors and clients are starting to ask.
'How do you use AI?' is now in vendor questionnaires. 'Our team uses ChatGPT' isn't an answer.
What is Playbooks & Prompt Systems?
A short project that turns your team's AI know-how into a library of prompts and one-page playbooks, so new hires inherit it on day one and capability doesn't leave when staff change.
Most AI capability lives in one person's head. We productise it, into a versioned prompt library and workflow playbooks that any team member can run, any new hire can inherit, and the business owns. Built around your real workflows. Yours to edit, extend, and govern.
Edison AI builds prompt libraries and workflow playbooks for Australian SMB teams. A standard engagement produces a versioned 50–150 prompt library, 3–5 one-page workflow playbooks, a house-style brief, a manager review protocol and a governance model. Delivered in 3–5 weeks. The team owns the library; Edison hands it over fully.
The shifts you can't postpone.
Why productisation pays back this year, not next.
- 01
AI use is now a business asset class.
It compounds when productised. It evaporates when private. A versioned prompt library is an operating asset, not a personal preference.
- 02
Staff churn is back.
The cost of a senior leaver doubles when their AI capability leaves with them. The library is the insurance policy.
- 03
The fastest-growing teams document first.
Without playbooks, the second hire never matches the first. The library is the spec for every onboarding that follows.
What you get.
- 01
Workflow audit (one week, written report)
- 02
50–150 production prompts. Versioned, tagged, role-segmented
- 03
3–5 one-page workflow playbooks co-built with function leads
- 04
House style brief
- 05
Manager review protocol
- 06
Governance one-pager (owner, review cadence, change log)
Where this shows up.
Sales
Library
Discovery questions, CRM note generators, follow-up drafts and proposal first cuts.
Playbook
Lead-to-proposal workflow. The one-pager every rep can run.
Marketing
Library
Brief-to-copy, channel reformatters, audience-tailoring and headline variants.
Playbook
Campaign asset cycle. Brief to assets to launch.
Operations
Library
Status summarisers, supplier comms, handoff templates and escalation drafts.
Playbook
Weekly operating rhythm. The cadence every Monday runs on.
Customer support
Library
Reply drafts by category, tone-checkers, escalation triagers and knowledge-base updaters.
Playbook
Ticket lifecycle. Open to close, with the review gates named.
Finance
Library
Commentary drafts, variance explainers, AP/AR drafts and board-pack section drafts.
Playbook
Month-end close. The function's most repeated workflow.
Admin / EA
Library
Meeting notes, decision logs, inbox triagers and agenda builders.
Playbook
Weekly leadership cadence. The EA's operating rhythm written down.
The engagement.
- Step 01
Diagnose
Workflow audit. We shortlist 10–20 of the team's most-repeated workflows and identify which merit productisation.
- Step 02
Design
Library architecture, playbook structure, house style scaffold and tool of choice confirmed (Notion, Airtable, Claude Projects or GPTs).
- Step 03
Deploy
Co-build 50–150 prompts and 3–5 playbooks with the function leads who will own them. Every prompt tested on real work.
- Step 04
Embed
Train function leads on ownership, set the review cadence and hand over the governance one-pager. End-to-end in 3–5 weeks.
What changes.
100%
Of recurring workflows have a documented AI standard.
Every brief, draft, summary, analysis or response follows a written prompt and review protocol, no more 'do you have a prompt for that?' Slack threads.
New-hire ramp on AI workflows drops from weeks to days.
A new joiner inherits 50+ working prompts, three playbooks and a one-page operating standard on day one.
30–50%
Reduction in output variance across the team.
The gap between your best and worst-AI-using staff member visibly closes within a fortnight of rollout.
Who this works for.
This is for you if…
- You have AI-fluent staff and AI-novice staff, and the gap is widening
- You've trained the team and want capability that survives staff change
- You're rolling out AI across a function and want consistency
- You're preparing to implement AI agents and want the prompts that will sit inside them
- You want defensibility, to clients, board and auditors, on how your team uses AI
Not the right fit yet if…
- You haven't decided which AI tools the team will use
- You don't have a function lead willing to own the library
- You're looking for a one-off list of prompts rather than a governed library
How this compares.
Four common ways teams try to capture AI capability. One of them survives a staff change.
Build it yourself in Notion
- Gives
- Free, customised
- Falls short
- Always 60% done; drifts; never quite governed
- Edison difference
- Complete, governed library in 3–5 weeks
Buy a prompt-pack online
- Gives
- Cheap, immediate
- Falls short
- Generic, not your workflows, your tone or your stack
- Edison difference
- Built on your real work, in your real tools
Hire a junior to document
- Gives
- Cheaper hourly rate
- Falls short
- Without senior judgement, prompts are shallow
- Edison difference
- Founder-led architecture, co-built with function leads
Wait until you implement AI agents
- Gives
- Defer the decision
- Falls short
- Agents need prompts to work. You'll do this anyway
- Edison difference
- The productised library is the spec for the agents that follow
Annual AI offsite
- Gives
- One day of energy
- Falls short
- Faded in three weeks, never written down
- Edison difference
- Versioned, governed and owned, not a calendar moment
Edison AI
Operator-grade, founder-led, fixed quote. Built around your real stack and workflows , not a binder, a brochure, or a six-figure off-the-shelf programme.
What buyers ask first.
“We already have a Notion of prompts.”
Most teams do. The difference is architecture, governance and the playbooks the prompts plug into. We rebuild the library so it survives.
“What if AI models change?”
Prompts are written model-agnostic where possible. Where they aren't, the governance model makes review trivial. The cadence is part of the deliverable.
“We're not technical.”
You don't need to be. The library lives in your existing tool. The hard part is judgement, not tooling.
Common questions.
Where does the AI prompt library live?
Wherever your team already works. Notion, Airtable, Claude Projects or a private GPT workspace. We meet the team where they are; we don't drag them into a new tool.
Who writes the prompts?
Edison drafts the architecture and roughly 60% of the prompts. We co-build the remainder with your function leads so they can extend the library themselves later.
What's the investment range for an AI playbook engagement?
$12,000–$35,000 plus GST depending on the number of functions covered, the workflows audited and the depth of documentation.
How long does the engagement take?
3–5 weeks end-to-end. Week 1 audit, weeks 1–2 design, weeks 2–4 build, weeks 4–5 embed.
How is the AI prompt library kept current?
Nominated function owner per area, quarterly review cadence and a simple change log. We hand that governance model over with the library.
How does this differ from a workshop?
Workshops train people; playbooks productise capability. Workshops alone don't survive a staff change. Playbooks do.
Can these prompts later power AI agents?
Yes, and that's often the next step. A well-built playbook is the spec for the agents we then build inside the workflow.
What if our processes change?
They will. That's why governance and a review cadence are part of the deliverable, not an afterthought.
The same service creates different leverage depending on your industry.
Other training services.
- S01
AI Workshops for Teams
A practical AI workshop for Australian SMB teams. Half-day or full-day, on your real work, building one shared prompting standard the whole team can follow.
Learn more - S02
Role-Based AI Workflow Training
Function-by-function AI workshops that rebuild your team's most-repeated workflow with AI, so the work runs faster, looks the same every time, and doesn't depend on one person.
Learn more - S03
Executive AI Enablement
Confidential 1:1 and small-group AI coaching for Australian founders, CEOs, directors and leadership teams, on the work that actually fills your week.
Learn more - S07
Agentic Operating Model
The documented system that describes how AI assistants and human staff share work. Who owns what, who approves what, what runs automatically and what stays human. The engagement that prevents agentic AI from becoming agentic chaos.
Learn more - S05
Cybersecurity & Responsible AI Training
A practical training programme that gives your team the rules, the habits and the documentation to use AI safely, without banning the tools that are actually helping.
Learn more - S06
AI Adoption Programme
A structured six-week AI adoption programme that combines team foundations, two role-based workflow rebuilds, a productised prompt library, a responsible-use policy and fortnightly leadership check-ins.
Learn more