Quoting engine and curriculum
Open a part, then hover a box for detail or a button to see it working.
Open a part, then hover a box for detail or a button to see it working.
| Module | In the team’s tools | Where AI takes the first pass | Stays with a person |
|---|---|---|---|
| UI design | Figma | Drafting wireframes, the heaviest task in the studio and the first target | Page layout |
| Brand strategy | ChatGPT · Claude · Notion | Research, interview notes and structured briefs | Positioning |
| Editorial design | Adobe Creative Cloud | Image preparation and the repetitive parts of long layouts | Page layout, and the client's copy |
| Marketing + social | Canva · Adobe Creative Cloud · ChatGPT · Claude | Adapting one asset for every channel, and first-draft captions | The copy |
Each module was aimed at the tasks the time logs showed were eating hours, and taught Demonstrate, Duplicate, Delegate in the team’s own files.
What the agency sells:
Peter sat beside team members while they did the actual work, and watched where the hours went.
Watching the work gives a truer picture than asking people to remember it.
Daily loggingEach person logs the day against a project and a task within it, in about five minutes.
Nobody was required to log. Daily was a deliberate choice, because people reconstruct a week badly.
Heat mapAbout three months of daily logs, mapped by person, by project and by task.
The heat map went back to the team who filled it in before it went to the directors.
Eating hours?Each offering's tasks read against the hours they took. A task eating hours got a training built around it.
The targetsThe arduous tasks in each offering, with wireframing in Figma first: it ate more hours than any other task in the studio.
observed, shadowing · hours measured, daily logsUI designModule one, and the first target: wireframes drafted with Figma's AI, then taken on by the designer.
Stays with a person: page layout.
Brand strategyResearch, interview notes and structured briefs drafted with ChatGPT and Claude, and kept in Notion.
Stays with a person: positioning.
Editorial designImage preparation and the repetitive parts of long layouts handed to Adobe's AI, in the Creative Cloud tools the team used.
Stays with a person: page layout, and the client's copy.
Marketing + socialOne asset adapted for every channel in Canva and Adobe, with first-draft captions from ChatGPT and Claude.
Stays with a person: the copy.
Checkpoint namedThe founder's condition was the spine of the curriculum: copy, positioning and page layout stay with a person.
Each module named its checkpoint out loud, at the stage where the judgement sits.
Who knew whatShadowing showed who already had the skill.
One designer already knew Figma's AI features and held back, expecting the founder to disapprove.
Founder's lineThe position the founder agreed, said out loud: AI supports the people doing the creative heavy lifting, and copy, positioning and page layout stay with a person.
Saying it out loud cleared the way for the designer who had been holding back.
DemonstratePeter does the task with the tool, in the team's own project files.
DuplicateThe team member does it while Peter watches.
DelegateThey do it, and Peter steps out.
A clear lineThe team could see exactly where the machine stopped and they started.
statedDrop back a layerWhere growing pains showed, the answer was to drop back a layer and run the previous step again.
Live jobA client job in one of the offerings, in the agency's own project files.
First passThe module's technique runs on the heavy task: a wireframe, a research summary, a layout, a set of channel formats.
CheckpointThe offering's named checkpoint: copy, positioning or page layout. That call belongs to a person.
Person finishesThe designer or strategist takes the work to finished.
A person could take the work back at any stage, which removed the fear that the system would run away with a client's brand.
Reason loggedEvery change documented with its reason.
A change with a reason attached can be evaluated later. A change without one can only be repeated or undone.
Better each runThe reasons accumulated, so the process improved from one run to the next.
statedEach run inherits the reasonsThe next run starts from the reasons documented on the last one.
A website was never produced in one pass. Each run was better than the last.
29 of 31 daily29 of 31 people logging their time daily, sustained for months, on a system nobody was required to use.
measuredFounder enforcesThe founder began sceptical that AI could touch design.
Naming the checkpoint out loud turned the founder into the person enforcing adoption.
statedPermission givenOnce the founder's position was explicit, the designer who had been holding back stopped holding back.
statedSecond agreementThe relationship continued past the first engagement: a learning programme Peter is building for them, live now under its own agreement.
statedSell · Deliver · TrainEvery engagement has the same shape:
When a client gets the value they want, they're more inclined to do more.
Once they see what is possible, they bring their own ideas to the table, ready to be implemented.
The offeringsWhat the agency sells, broken into the tasks that deliver it, so every task could be logged against a job.
A module eachA module for each offering trained, built around the tasks the time logs showed were eating hours.
The founder's condition, written into every module at the stage where the judgement sits:
Demonstrate, Duplicate, Delegate, in the team's own project files.
Where growing pains showed, drop back a layer and run the previous step again.
Live client workAI takes the first pass on a live job, a person takes it through the checkpoint, and every change is kept with its reason.
29 of 3129 of 31 people logging their time daily, sustained for months, on a system nobody was required to use.
measuredEach run inherits the reasonsEvery change was documented with its reason, and the next run started from those reasons.
A website was never produced in one pass. Each run was better than the last.
Daily time logsEach person logged the day against a project and a task within it, in about five minutes.
About three months of daily logs, mapped as a heat map, before any module was built.