Deployed Works Guide

Platform & trust

The Language Of Capability-Based Work

A quick reference for the few Deployed Works terms you will see most often.

Recording soon

The Language Of Capability-Based Work guide trailer

A short walkthrough for this guide will appear here.

Audience

Platform & trust

Buyers, providers, founders, operators, capability buyers, consultants, independent providers, partners and anyone new to Deployed Works language

Time

3 minute reference

Outcome

A quick reference for the few Deployed Works terms you will see most often.

Download PDF

Share this guide

PDF guide

Share this guide with your team.

Download the PDF for meetings or offline use. The web guide has the latest version.

https://www.deployed.works/guides/capability-based-work-glossaryhttps://www.deployed.works/guides

Related guides

Guide summary

What this guide helps you do

Understand the core language behind capability-based work.
Explain Deployed Works to colleagues, partners and new users.
Use shared terms when writing capability briefs or capability profiles.

Who it is for

Best fit readers

  • A buyer trying to understand the outcome-led deployment journey.

Why this glossary exists

A shared language makes the category easier to use.

The category is easier to use when its operating objects have clear meanings. This glossary follows the positive product sequence: outcome, assessment, route, match, proposal, delivery, completion and Passport evidence.

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.

Read the map from work to provider evidence, then into review and deployment. The terms are connected, but none of them claim automated ranking, guaranteed fit or guaranteed outcomes.

Glossary terms

Core terms, plain-English meaning and product boundaries.

Step 1

Capability

The ability to do useful work or produce an outcome.

Step 2

Capability brief

A clear description of the finished outcome, current problem, constraints, timing and budget.

Step 3

Capability profile

A provider page explaining what they can deliver, where they fit, what proof they have and how they work.

Step 4

Buyer

Definition: an organisation or team buying capability for an outcome.

Step 5

Provider

Definition: a person, specialist team, consultant, independent provider, operator or service offering deployable capability.

Step 6

Deployment

Definition: the act of bringing capability into a specific piece of work.

Step 7

Deployment Slot

A place on a buyer's account for one live brief. Close the brief and the slot can be used again.

Step 8

Fit indicators

Notes showing where a provider may fit the brief and what still needs checking.

Step 9

Trust signal

Information that can build confidence, such as an identity check, proof or a reference. It is not a guarantee.

Step 10

Stripe Identity verification

An optional identity document check handled by Stripe. It does not prove skill.

Step 11

Proof

Definition: evidence that a provider has solved relevant problems or can credibly deploy a capability.

Step 12

Scoped engagement

A piece of work with clear boundaries and an agreed first result.

Step 13

Handover

The notes, training and transfer needed so the buyer can use or maintain the finished work.

Example

How the language works together

A buyer saves an outcome and accepts a capability route. Provider and vendor Passports show deployable capability, evidence and boundaries.

Template

How to use this glossary

Copy into your own document
When writing a capability brief:
- Use the terms to describe work, outcome, capability needed and first scope.
- Keep the outcome separate from the proposed solution route.
- Keep fit indicators and human review language accurate.

When creating a capability profile:
- Use the terms to describe capability, proof, commercial model and boundaries.
- Keep claims, evidence and boundaries distinct.
- 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.

Common misunderstandings

Keep these boundaries clear

  • "Capability" does not only mean a person.
  • A capability brief preserves the outcome before route choice.
  • A Capability Passport separates claims, evidence and boundaries.

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.

FAQ

Questions this guide usually raises

Is this glossary a replacement for the practical guides?

No. This is the shared vocabulary.

Are fit indicators automated matching?

No. Fit indicators are structured signals that support review.

Take it with you

Share this guide with your team.

Download the PDF for meetings or offline use. The web guide has the latest version.

https://www.deployed.works/guides/capability-based-work-glossaryhttps://www.deployed.works/guides

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
Explore the guides

The people of Deployed Works

Buyers, providers and vendors build trust through the outcomes they complete.

Real capability becomes easier to trust when the people and evidence stay visible.