GROUP A · UP TO 20 PEOPLE
Content, sales or communications.
Prepare sources, work on a draft and check claims, tone and omissions before using it.
← Back to the offer
AI Partner sample
A month of work. Deliveries you can review.
A sample monthly AI engagement: 24 hours, priorities, delivery, provider coordination, testing and knowledge transfer.
An illustrative format sample, with no client data or attributed outcomes. The actual use case and agenda are agreed before you commit.
A SCOPE YOU CAN REVIEW
One priority. 24 hours a month.
Hours include sessions, preparation, delivery and documentation. This illustrative split adapts to dependencies and the work we prioritise together.
- WEEK 01 · 3 H
Prioritise with context.
Review tools and access, choose one priority and acceptance criteria. Includes the first 90-minute session.
Record: delivery, reviewer, dependencies and exclusions. - WEEK 02 · 12 H
Configure and document.
Work on the agreed workflow in your accounts. Coordinate technical dependencies with your provider.
Delivery: a version the owner can test and a work log. - WEEK 03 · 6 H
Test with the team.
Use approved examples, review quality and adjust within scope. Record blockers and decisions.
Delivery: acceptance tests and updated usage guidance. - WEEK 04 · 3 H
Review and hand over.
Second 90-minute session: demonstration, owner practice and capacity review. Documentation and next priorities.
Delivery: workflow status, hours used, access and next plan.
WHEN THE OBJECTIVE IS TEAM ADOPTION
The same workflow. Practice for every role.
An example month extending an existing workflow. We reallocate the same 24 hours: more team practice and less building.
GROUP B · UP TO 20 PEOPLE
Operations and process owners.
Review the output, handle exceptions and practise updating an instruction or source.
2 workshops × 90 min per group
First workshop: work through the case with a core guide and exercises by level. Second workshop: review work, resolve errors and repeat the task independently. That is 3 session hours per participant and 6 teaching hours in total.
Groups are adapted to actual roles. This sample covers an existing workflow and up to two groups; it does not add another development project. Preparation, workshops, adaptation, tests and documentation all count towards the 24 hours.
THE INDEPENDENCE CHECK
They can repeat it when we are not there.
A person from each group completes the task using the guide and explains their review. The workflow owner changes an instruction or source, runs the agreed tests and knows when to stop the process.
We record the baseline task, quality, time and usage. The monthly review compares observations; improvement figures come from actual work.
THE WORK AND KNOWLEDGE STAY WITH YOU
Who does what.
KDK
Your KDK contact leads the engagement and participates in implementation. Configuration, coordination, testing and documentation count towards monthly capacity. Any specialists and their roles are agreed with you.
Your business
One owner joins both sessions and allows, as a reference, one weekly hour for coordination and review. Other teams join tests for their workflow.
At handover
Your company’s accounts, configuration and decision records, a delivery log and maintenance practice. Exit terms are agreed in writing: notice, work handover and removal of KDK access.
One active priority does not mean any size of project can finish in a month. We agree deliverables feasible within 24 hours. Licences, extra capacity and work beyond scope are priced separately.