first safe pilot
Proposal draft from approved facts with source table and partner review.
Keep the first workflow at draft or review-support level before any real-world use.
aequai ~ / industries / handbook 03
$ aequai handbook --priority 03 --full-content
Professional Services AI Adoption Handbook
Proposal, research, meeting-note, and delivery-checklist AI workflows with partner review and source discipline.
priority 03readiness mapfictional/synthetic samples onlyhuman approval required
// boundary: This handbook is local review copy for readiness, training, workflow design, and evidence mapping. It is not sector authority, professional advice, public approval, regulated conclusion, production authority, autonomous operation, token/chain/network action, carbon-asset action, or customer proof.
$ aequai quick-map --pilot --path --no-go
Safe first step.
service path
Department AI Pilot Design -> AI Literacy Training
Use diagnostics, training, pilot design, governance, or simulation according to the workflow risk.
training path
Partner, delivery, research, sales, and admin paths.
Training is personalized to role, workflow, tool stack, risk profile, data boundary, and approval responsibility.
Source: professional-services-ai-adoption-handbook-v0.1.md. Source title: Professional Services AI Adoption Handbook v0.1.
$ aequai handbook-source --sections all
Full handbook content.
The sections below expose the actual handbook material: business context, workflows, first safe workflows, map, boundaries, simulation example, checklist, fictional/synthetic sample teaser, recommended AequAI path, 30/60/90 roadmap, and public-safe no-go wording.
[01]Business Contextsource-backed handbook section+ open- close
Professional services firms use proposals, research, briefs, customer materials, delivery checklists, and advisor-prep documents. AI can help draft and organize, but review ownership and source discipline are central.
Every training path is personalized to the person, team, role, workflow, tool stack, risk profile, business context, workflow maturity, data boundaries, and approval responsibilities.
[02]Typical Workflowssource-backed handbook section+ open- close
Proposal drafts, research summaries, meeting notes, delivery checklists, source maps, advisor-prep packs, and project documentation.
[03]First 5 Safe Workflowssource-backed handbook section+ open- close
- +Proposal draft from approved facts.
- +Research summary with source table.
- +Meeting-note action checklist.
- +Delivery checklist draft.
- +Advisor-prep question pack.
[04]Department / Function Mapsource-backed handbook section+ open- close
| Function | Opportunity | Training Need | Gate |
|---|---|---|---|
| Partners/owners | Decision briefs | Review discipline | Partner review |
| Sales/account | Proposal drafts | Claim-safe wording | Account owner review |
| Delivery | Checklist drafts | Source and scope control | Delivery lead review |
| Research | Summary drafts | Citation/source discipline | Research lead review |
| Admin | Meeting notes | Data boundaries | Owner review |
[05]Boundariessource-backed handbook section+ open- close
Do not present AI output as professional conclusion, customer result, advisor replacement, or public proof. Keep customer confidential materials restricted and use fictional/sanitized examples for training.
[06]Simulation Examplesource-backed handbook section+ open- close
Synthetic scenario: a consulting team drafts a proposal from approved service facts, logs source sections, and requires partner review before sending.
[07]Diagnostic Checklistsource-backed handbook section+ open- close
- +Which documents repeat?
- +Which claims require source evidence?
- +Which customer files are excluded?
- +Who approves proposals?
- +Which tool workflows are approved?
[08]Fictional/Synthetic Sample Report Teasersource-backed handbook section+ open- close
Fictional/synthetic sample: "Professional Services Proposal Approval Gate." Shows a proposal workflow, claim review, and practice plan. It is not customer proof.
[09]Recommended AequAI Pathsource-backed handbook section+ open- close
Department AI Pilot Design -> AI Literacy Training -> AI Governance Starter Kit -> AI Workflow Simulation Lab if tool-connected workflows emerge.
[10]30/60/90-Day Roadmapsource-backed handbook section+ open- close
30 days: proposal approval gate. 60 days: source discipline and delivery checklist. 90 days: team AI operating rules.
[11]Public-Safe Wording Notessource-backed handbook section+ open- close
Use draft support, source map, approval gate, and advisor-prep wording. Avoid outcome and endorsement claims.
$ aequai next --map-business
Use the handbook as a starting map.
Start with one workflow, one review owner, one data boundary, and one evidence log. Expand only after a reviewed pilot shows what to proceed with, shrink, park, or stop.