Brief from the client's facts
Turn a client brief into a draft using only supplied facts and labelled assumptions.
AI training for agencies teaches strategists, writers, designers, account managers and project leads to use AI assistants on client work while protecting client confidentiality and checking every claim before it reaches the client. Tosheo.ai is being built to deliver that as role-specific practice for teams.
Turn a client brief into a draft using only supplied facts and labelled assumptions.
Apply the per-client rule and use only approved business tools.
Use supplied brand examples and explain where a draft departs from them.
Remove invented statistics, forecasts and comparisons before a client sees the work.
Alder Bikes is a fictional client. The brief: a commuter bike launching in March, a budget for paid social and email, an audience of city commuters, and three product facts about weight, gearing and a built-in lock. Use an AI tool to draft a one-page campaign plan. Remove any statistic, forecast or competitor claim not in the brief, and bracket every assumption. Submit the plan and a short note to the client lead explaining your edits.
Every factual statement comes from the brief; no invented statistics, forecasts or comparisons remain.
Assumptions are clearly marked so the client lead can confirm or reject them.
The note explains the main edits in language a client lead could share.
It covers the work that fills an agency week: turning a client brief into a first plan, drafting copy in the client's voice, summarising research, preparing presentation narratives, writing meeting notes and status reports, and turning a specification into test cases or a project plan. It also covers the agency-specific risk: you are handling someone else's confidential material, under someone else's contract.
AI for marketing agencies is often discussed as a speed question. In practice the harder questions are about trust. Can the account team show the client what was AI-assisted? Is the client's unreleased product information going into an approved tool? Has a person checked every figure in the deck?
Check the client contract first, agree an internal rule, and only put client material into tools and plans the agency has approved for it. Many master services agreements and non-disclosure agreements restrict how confidential information is processed or shared, and some clients have their own AI rules for suppliers. The account lead should know which clients allow AI-assisted work and under what conditions.
Vendor terms matter too, and they differ by plan. Anthropic's privacy centre, for example, states that by default it does not use inputs or outputs from its commercial products for model training, with an exception where users submit feedback or otherwise allow it. Consumer plans and other vendors can differ, so check the current terms for the exact plan your agency uses. This is general information, not legal advice.
Record whether each client allows AI-assisted work, and any conditions such as disclosure or approved tools.
Use the agency's business accounts, not personal ones, for anything containing client material.
Remove unreleased product names, financials and personal data unless the task genuinely needs them.
If a client expects to know where AI was used, keep a short note on each deliverable.
A good one uses the brief's facts, labels its assumptions and leaves the strategy decisions visible. Here is a worked example. A fictional client, Alder Bikes, wants a campaign plan by tomorrow for a new commuter bike. The brief supplies: launch in March, a budget for paid social and email, an audience of city commuters, and three product facts about weight, gearing and a built-in lock.
The prompt: "Draft a one-page campaign plan from this brief. Use only the facts supplied. Mark every assumption in brackets. Do not include audience statistics, forecasts or competitor claims."
A weak draft, from a prompt that asked for a data-driven plan, includes audience percentages, a forecast click-through rate and a claim that the bike is the lightest in its class. None came from the brief. In a client meeting, any one of them invites a question the agency cannot answer.
The reviewed plan sets out channels, timing and messages built on the three product facts, with bracketed assumptions such as "[confirm whether existing customers can be emailed]". The strategist adds a short note explaining what they changed. That note, not the speed of the draft, is what the client is paying for.
The core habits are shared, but the practice should match each person's work. Tosheo.ai is being built so each person is invited with a role and gets a path that adapts to their diagnostic result.
Account managers practise status reports and meeting summaries checked against the notes. Copywriters practise drafting in a supplied brand voice and removing unsupported claims. Strategists practise research synthesis with opened sources. Designers practise writing creative rationales and briefs for image tools, and checking the tool's terms and the client contract on usage rights before any generated asset reaches a client. Project managers and QA staff in development agencies practise turning a specification into a plan or test cases, marking every inferred requirement. Deep coding training for engineers is not included.
The owner or operations lead signs up, selects roles, chooses the tools the team uses and invites people by email or link. Lessons take 10 to 15 minutes and end with a hands-on task graded by AI against a visible rubric; a score can be flagged for review. Practice scenarios include the situation every agency knows: a client wants a plan by tomorrow.
Managers see skill progress and completion, never chat logs. The planned Growth plan adds custom roles and up to five company documents, such as the agency's own process guide, isolated per company and never used for training. A final practical assessment leads to a recognised certificate that a team member can share and an agency can mention in a pitch, as long as it describes the credential accurately. Tosheo.ai is pre-build. Everything described here is planned launch scope, not a record of customer training, assessment results or outcomes.
It is not right if you want to build and resell your own AI course to clients; custom course authoring is not included. It is not suited to engineering teams who need hands-on coding or machine learning engineering training.
It does not include SSO, LMS integrations, Slack or Teams bots, or enterprise contracts at launch, and lessons are English only. If a client requires specific tool training, such as an enterprise Copilot rollout, the vendor's own material may be the better match. The product is pre-build, so an agency needing training before launch should start with the free guides.
Follow the contract and the client's expectations. Some clients require disclosure or restrict AI use; others are content as long as quality and confidentiality are protected. Agree the rule per client and keep a short note on deliverables where disclosure is expected.
Only if the client contract allows it and you use a business plan your agency has approved, after removing anything the task does not need. Vendor training and retention terms differ by plan, so check the current terms.
Yes, for the non-engineering work: briefs, rationales, plans, specifications, test cases and client communication. Deep coding training for engineers is not included.
Team members can share the recognised certificate with its verifiable URL. Describe it accurately as a completed practical assessment, not as proof of results for clients.
Planned pricing is per seat per month with a five-seat minimum on Team and a 20-seat minimum on Growth, which adds custom roles and document grounding. Figures are on the pricing page and may change before launch.
Explore the planned role-specific lessons, practical tasks and manager view.