Team Skills
Design skills anyone on the team can run.
We package your brand, templates and tone into skills your whole team can use — decks, campaign assets, one-pagers, landing pages.
Someone in sales asks for a deck for an account, and it comes back in your layout, with your language and your data. On brand the first time, without a queue in front of the designer.
What we package
The work people keep asking the designer for.
Each skill is built once against your system, then run by whoever needs it.
Pitch decks
Your brand template and slide layouts, filled with the account's own context from the knowledge base.
Campaign kits
Ads, emails and landing copy that come out in your voice rather than a model's default register.
One-pagers
Product or account, on brand, produced in the time it used to take to write the brief for one.
Landing pages
Built from the same system, so a campaign does not arrive looking like it came from somewhere else.
What a skill looks like
Ask for the thing. Get it back on brand.
These are drawn from the shape of a real build, with the brand swapped for a neutral one. Your own layouts, colours and voice are what go in.
Request
Renewal deck for Northwind, 6 slides. Lead with what changed since they signed.
Skill · Pitch deck v3
- Pulled account history and last three calls
- Applied the master template and slide layouts
- Checked type, colour and tone against the brand
- Swapped two placeholder claims for real figures
Output · 6 slides
On brandNorthwind, a year in
What changed since you signed
Hours back per week
Where it is used most
What we would do next
Renewal terms
A deck, from one line of request
The skill pulls the account's context from the knowledge base, lays it into your template and checks it against the brand before anyone sees it.
Brand system · v4
Source of truthInk
#1f1c1b
Paper
#f7f5f1
Signal
#2a6df4
Clay
#c4572b
Aa
Display · serif, sentence case
Body · sans, 14 / 1.6
- LogoNever on a photograph without a plate
- SignalOne use per page, for the action
- HeadlinesA claim, not a label
The system, set once
Colours, type and the rules that usually live in the designer's head, captured as constraints the skill cannot step outside.
Tone check
Unlock the power of AI-driven insights.
Answers from your own docs, with the source attached.
Industry-leading results for teams of all sizes.
Cut onboarding questions by two thirds at Northwind.
Your voice, not the model's
Drafts are checked against the house tone. Generic phrasing is rewritten, and anything the skill cannot verify is flagged rather than invented.
Campaign kit · one brief
3 sizesStop answering the same question twice.
See how1:1
Stop answering the same question twice.
See how4:5
Stop answering the same question twice.
See how1.91:1
One brief, every placement
A campaign kit renders the same message at each size a channel needs, so nothing gets re-cropped by hand the night before launch.
Team skills
Shared with everyone- Pitch deck128 runsv3
- Campaign kit64 runsv2
- One-pager91 runsv4
- Case study22 runsv1
- Landing page3 runsNew
A library the whole team runs
Every skill is versioned. When the brand moves, the owner updates it in one place and the next run picks it up.
The distinction
Why a skill beats a template.
A template is an empty file.
Someone still has to know what goes in it, find the numbers, and write the words. That is where the queue forms.
A template does not know your account.
A skill reads from the knowledge base, so the deck arrives with that customer's context already in it.
Templates drift the moment they are duplicated.
The designer sets the system once. Everything produced from it inherits the current version, not a copy someone saved in March.
The designer stops clearing a queue and starts owning the system that produces the work.
“Sales builds their own decks now. They still look like ours.”
Head of Brand · Series B SaaS
How it works
Capture the system, build the skill, hand it over.
CaptureBuildHand over
- 01
Capture
We work with whoever owns the brand to get the rules out of their head: layout, type, tone, the things that are never allowed, and the judgement calls that usually happen in review.
- 02
Build
Each skill is built against that system and wired to the knowledge base, so output arrives with real context rather than placeholder copy.
- 03
Hand over
Your team runs them. The brand owner keeps the system and changes it in one place when it moves.
Questions
The questions buyers actually ask.
Direct answers for teams deciding whether packaged skills belong on the shortlist.
What does “design skills everyone can use” mean?
We package your brand, templates and tone into reusable skills. Someone in sales asks for a deck for an account, and it comes back in your layout, with your language and your data. Same for campaign assets, one-pagers and landing copy. The designer sets the system once instead of clearing a queue.
Does this replace our designer?
No. It moves them off production and onto the system. Someone still has to decide what good looks like, and that judgement is exactly what gets encoded into the skill.
Will the output actually be on brand?
Your rules are constraints on the skill rather than guidance next to it, so compliant output is the default. Where a judgement call is genuinely needed, the skill asks instead of guessing.
What happens when the brand changes?
The owner updates the system once and every skill inherits it. That is the main practical difference from templates, which fork the moment someone duplicates one.
Do we need the knowledge base first?
Not strictly, but skills are far better with it. Without a base, a deck skill produces your layout with placeholder content; with one, it arrives already carrying that account's context.
Also part of the system