Deployed Works Guide
The Language Of Capability-Based Work
A practical glossary for understanding capability briefs, capability profiles, deployment, fit indicators and human-reviewed shortlists.
Audience
Buyers, providers, founders, operators, hiring managers, consultants, freelancers, partners and anyone new to Deployed Works language
Time
12 minutes
Outcome
A shared vocabulary for capability-based work
Share this guide
PDF guide
Download and share with your friends and colleagues.
Use the PDF version to align teams, partners or colleagues on the language behind Deployed Works. The web guide remains the canonical version.
Related guides
Guide summary
What this guide helps you do
Who it is for
Best fit readers
- A buyer or hiring manager trying to understand how deployment differs from recruitment.
- A provider, consultant or freelancer creating a capability profile.
- A founder or operator explaining the model internally.
- A partner, support teammate or colleague who needs the language in one place.
- Anyone new to Deployed Works terminology.
Why this glossary exists
A shared language makes the category easier to use.
Deployed Works uses a different starting point from traditional recruitment. The category is easier to understand when the core terms are clear: start with work, describe capability, review proof and fit, then have better first conversations. This glossary is a practical reference, not a manifesto.
Capability Language Map
See how the core terms connect.
Use the map to explain the category quickly: start with work, describe provider capability, review fit and proof, then move into a scoped deployment.
Glossary terms
Core terms, plain-English meaning and product boundaries.
Capability
Definition: the ability to produce a useful outcome. Plain English: capability can live in a person, a specialist team, a service, software, or future autonomous systems. Why it matters: Deployed Works starts with the capability needed for work, not only a role title. Related terms: deployed capability, capability brief, capability profile.
Deployed capability
Definition: capability brought into a specific piece of work to produce progress or an outcome. Plain English: this is capability in use, aimed at a real problem or phase of work. Why it matters: it keeps the conversation focused on progress, scope and evidence. Related terms: deployment, scoped engagement, handover.
Capability marketplace
Definition: a marketplace where buyers describe work that needs doing and providers describe the capability they can deploy. Plain English: buyers bring problems and outcomes; providers bring relevant capability, proof and commercial shape. Why it matters: it gives both sides a clearer starting point than a generic role or profile search. Related terms: capability brief, capability profile, human-reviewed shortlist.
Capability brief
Definition: a structured description of work that needs doing, the outcome required and the capability needed to deliver it. Plain English: it is not a job advert. Why it matters: a good brief names the work, context, scope, timeline, budget signal and what good looks like. Related terms: Deployment Slot, fit indicators, first provider call.
Capability profile
Definition: a provider profile that explains what capability the provider can deploy, what problems they solve, what proof they have and how buyers can work with them. Plain English: it is not a CV. Why it matters: it helps buyers understand problem fit, evidence, delivery style and commercial model. Related terms: proof, commercial model, trust signal.
Buyer
Definition: an organisation or team looking for capability to help with work that needs doing. Plain English: the buyer may be a founder, operator, hiring manager, department lead or project owner. Why it matters: the buyer owns the problem, context and decision to start the work. Related terms: capability brief, Deployment Slot, human-reviewed shortlist.
Provider
Definition: a person, specialist team, consultant, freelancer, operator or service offering deployable capability. Plain English: a provider explains what they can deploy, where they fit, what proof they have and how buyers can start. Why it matters: providers are reviewed through capability, proof and fit, not just job titles. Related terms: capability profile, proof, repeatable capability offer.
Deployment
Definition: the act of bringing capability into a specific piece of work. Plain English: deployment starts with work that needs doing and brings in capability to make progress. Why it matters: deployment can be project-based, fractional, diagnostic, build-focused or advisory. Related terms: scoped engagement, deployed capability, handover.
Deployment Slot
Definition: buyer-side access that allows an organisation to publish or run a focused capability need through Deployed Works. Plain English: a Deployment Slot supports a specific capability need rather than an unlimited hiring campaign. Why it matters: it keeps buyer access aligned with focused work and current product pricing language. Related terms: capability brief, buyer, scoped engagement.
Fit indicators
Definition: structured signals that help surface areas of possible relevance between a capability brief and a provider profile. Plain English: fit indicators help organise review; they are not AI matching, not automated ranking and not a guarantee. Why it matters: they support better human review and better first conversations. Related terms: human-reviewed shortlist, proof, capability profile.
Human-reviewed shortlist
Definition: a shortlist reviewed by a human operator using the brief, provider profiles, proof and fit indicators. Plain English: it is not automated ranking. Why it matters: human review keeps the process grounded in the work, evidence and stated constraints. Related terms: fit indicators, capability brief, first provider call.
Trust signal
Definition: information that can increase buyer or provider confidence, such as identity verification, proof, references or profile completeness. Plain English: a trust signal is useful context, not a guarantee of skill, suitability or performance. Why it matters: trust signals help people decide what to inspect next. Related terms: Stripe Identity verification, proof, capability profile.
Stripe Identity verification
Definition: optional identity verification handled by Stripe Identity. Plain English: for providers, it is optional and charged at a one-off £1.25 at cost where offered. Why it matters: verification is a trust signal, not skill proof, and it does not guarantee suitability or performance. Related terms: trust signal, proof, provider.
Guided drafting
Definition: assistive drafting support that helps buyers or providers turn rough notes into clearer briefs or profiles. Plain English: the user reviews and controls what is saved, published or submitted. Why it matters: guided drafting can improve structure without replacing human judgement. Related terms: capability brief, capability profile, human review.
Proof
Definition: evidence that a provider has solved relevant problems or can credibly deploy a capability. Plain English: proof can include case studies, portfolio work, anonymised examples, metrics, testimonials and references. Why it matters: proof helps buyers inspect relevance instead of relying on broad claims. Related terms: capability profile, trust signal, fit indicators.
Commercial model
Definition: how a provider structures payment or engagement. Plain English: examples include day rate, project fee, retainer, fractional arrangement and productised offer. Why it matters: clear commercial shape helps buyers understand whether a first engagement is realistic. Related terms: capability profile, scoped engagement, repeatable capability offer.
Scoped engagement
Definition: a clearly bounded piece of work with an agreed first outcome, phase or deliverable. Plain English: it may be a diagnostic, sprint, first build phase, audit, implementation or handover-focused engagement. Why it matters: scope makes early work easier to buy, review and complete. Related terms: deployment, handover, Deployment Slot.
Handover
Definition: the documentation, training or transfer needed so the buyer can use or maintain the work after delivery. Plain English: handover turns delivery into something the buyer can operate, understand or continue. Why it matters: good handover reduces dependency and makes outcomes more durable. Related terms: scoped engagement, deployed capability, proof.
Repeatable capability offer
Definition: a clearer provider offer built around a repeatable buyer problem, first outcome, proof and boundaries. Plain English: it is a starting shape, not a promise that every project is identical. Why it matters: it helps buyers know what problem to bring and what first engagement to expect. Related terms: provider, commercial model, capability profile.
Software-led service
Definition: a service where software carries more of the delivery, workflow or operating leverage. Plain English: this is a future-facing category that may sit alongside consulting, services and software. Why it matters: it helps describe how capability may become more scalable without implying the current marketplace is only software-led. Related terms: autonomous capability, repeatable capability offer, deployed capability.
Autonomous capability
Definition: capability delivered partly or fully by autonomous systems such as agents or robots. Plain English: this is part of the broader Deployed Works thesis, not the immediate default marketplace state. Why it matters: the language should be broad enough for future capability while staying accurate today. Related terms: capability, software-led service, deployed capability.
Deployment vs recruitment
Definition: recruitment starts with a role; deployment starts with the work that needs doing. Plain English: this does not mean recruitment is dead or always wrong. Why it matters: deployment gives teams a way to progress work before, beside or instead of a full-time hire when the situation fits. Related terms: hire/deploy/wait, capability brief, deployed capability.
Example
How the language works together
A buyer writes a capability brief for work that needs doing. Providers use capability profiles to show what they can deploy, what proof supports them and what commercial model fits. Fit indicators help structure review, then a human-reviewed shortlist supports better first conversations. If the buyer proceeds, the work becomes a scoped engagement with a clear first outcome and handover.
Template
How to use this glossary
When writing a capability brief: - Use the terms to describe work, outcome, capability needed and first scope. - Avoid turning the brief into a job advert. - Keep fit indicators and human review language accurate. When creating a capability profile: - Use the terms to describe capability, proof, commercial model and boundaries. - Avoid turning the profile into a CV. - Treat verification as a trust signal, not skill proof. When explaining Deployed Works: - Link to this guide from onboarding, help docs, sales notes and internal planning. - Share the PDF with colleagues who are new to the model. - Use the related guides when someone needs the next practical step.
Common misunderstandings
Keep these boundaries clear
- "Capability" does not only mean a person.
- A capability brief is not a job advert.
- A capability profile is not a CV.
- Fit indicators are not AI matching.
- A human-reviewed shortlist is not automated ranking.
- Verification is not proof of skill.
- Deployment does not replace all hiring.
How to use this glossary
Use it when the language needs to travel
- Link to this glossary from guides and help docs when terms need explaining.
- Share it with colleagues who are new to the model.
- Use it when writing capability briefs or capability profiles.
- Use it when explaining Deployed Works internally.
- Check that fit, shortlist and verification language stays within product boundaries.
- Use the PDF version when forwarding the language to a team, partner or colleague.
FAQ
Questions this guide usually raises
Is this glossary a replacement for the practical guides?
No. This is the shared vocabulary. Use the related guides when you need to write a brief, create a profile, review a provider or decide whether to hire, deploy or wait.
Does capability-based work mean recruitment is obsolete?
No. Recruitment can still be right when the work is continuous, core and suited to a long-term role. Deployment starts with the work that needs doing and is useful when a scoped capability path fits better.
Are fit indicators automated matching?
No. Fit indicators are structured signals that support review. They are not AI matching, automated ranking or a guarantee.
Why include future terms like autonomous capability?
Because capability can live in people, teams, services, software and future autonomous systems. The term is included as category language, not as a claim about the immediate default marketplace state.
Take it with you
Download and share with your friends and colleagues.
Use the PDF version to align teams, partners or colleagues on the language behind Deployed Works. The web guide remains the canonical version.
Share this guide
Use the canonical page link. No social scripts or tracking widgets are loaded.
Use the guide
Ready to use the language in practice?
Explore the guides for writing briefs, creating profiles, reviewing providers and deciding when to deploy capability.
Read more about capability marketplaces