Deployed Works Guide

How To Write A Capability Brief

Turn a live business need into a clear capability brief: outcome, context, scope, must-haves, timeline, budget signal and what good looks like.

Submit your first capability briefView all guidesDownload PDFCopy template

Audience

Buyers, founders, operators and hiring managers

Time

9 minutes

Outcome

A brief a specialist provider can understand and respond to

PDF guide

Download this guide as PDF

Same guide, same canonical URL and same next step. The web guide remains the canonical version.

https://www.deployed.works/guides/write-a-capability-briefhttps://www.deployed.works/launch/cohort-1
Download PDFCopy template

Related guides

Technical project brief templateDownload a free technical project brief template for AI, automation, product and internal tools work. Use it to scope outcomes, requirements, timeline and budget.Open guide

Guide summary

What this guide helps you do

Describe the outcome before deciding who should do the work.
Separate the problem, scope and must-have capability.
Give providers enough context to respond usefully.
Avoid turning flexible work into a permanent job advert by accident.

Who it is for

Best fit readers

  • A founder who needs specialist work done in the next 30-60 days.
  • An operator turning a messy internal problem into a clear brief.
  • A hiring manager who wants fewer irrelevant applicants.
  • A team that needs capability but is not ready to hire full-time.

The problem

Traditional hiring starts too late in the thinking.

Most teams start by writing a job advert, even when they do not need a permanent hire. That pushes them into CV screening, recruiter noise and vague conversations before the work has been properly described.

Step by step

Build the brief around the work.

Step 1

Start with the outcome

Write what needs to be true when the work is complete. A brief should start with the result, not the job title.

Step 2

Describe the current problem

Explain what is blocked, slow, manual, risky or unclear today. Useful providers need context before they can suggest a sensible approach.

Step 3

Name the capability needed

Use plain language: product engineering, workflow automation, data integration, AI implementation, internal tools or fractional product leadership.

Step 4

Define the scope

State what is in scope, what is out of scope and whether this is discovery, delivery, rescue work or ongoing support.

Step 5

Separate must-haves from nice-to-haves

Must-haves should be few and defensible. Nice-to-haves help fit, but should not exclude strong providers too early.

Step 6

Give timeline and budget signal

You do not need a final procurement document. Give enough commercial shape for providers to know whether the work is realistic.

Step 7

Describe what good looks like

Add acceptance signals: working workflow, migrated service, shipped MVP, reduced manual steps, clearer reporting or a decision-ready plan.

Example

Weak advert into stronger brief

Instead of: “We need a senior backend developer.” Try: “We need to migrate a Node backend service to Rust over the next three months. The outcome is a stable API layer, documented migration plan and reduced runtime cost. Must-haves: production backend experience, Rust, Node, PostgreSQL and async API work. Budget signal: £500-£800/day or equivalent project pricing.”

Template

Capability brief template

Copy into your own document
Outcome:

Current problem:

Capability needed:

Scope:
- In scope:
- Out of scope:

Must-have skills or context:

Nice-to-have experience:

Timeline:

Budget or rate signal:

What good looks like:

Questions still open:

Common mistakes

Avoid these traps

  • Starting with a job title instead of the work.
  • Listing every possible skill as a must-have.
  • Hiding budget or timeline until late in the conversation.
  • Writing a permanent job advert for a project-shaped need.
  • Using vague phrases such as “rockstar”, “hands-on” or “fast-paced” instead of concrete outcomes.

Checklist

Ready to publish when

  • The outcome is clear in the first paragraph.
  • The current problem is understandable to someone outside the company.
  • Must-haves and nice-to-haves are separate.
  • Timeline and budget/rate signal are included.
  • The brief explains what good looks like.
  • The brief invites a focused provider conversation.

FAQ

Questions this guide usually raises

Is a capability brief the same as a job advert?

No. A job advert usually describes a role. A capability brief describes work that needs doing and the capability required to do it.

Do I need to know the exact provider type?

No. You can describe the outcome and context first. The provider may be an independent professional, consultant, fractional leader or specialist team.

Should I include budget?

Yes, if you can. A budget or rate signal saves time and helps providers judge whether the work is realistic.

Does Deployed Works use AI matching?

No. Deployed Works currently uses structured profiles, guided briefs, fit indicators and human-reviewed early matching.

Take it with you

Download this guide as PDF

Same guide, same canonical URL and same next step. The web guide remains the canonical version.

https://www.deployed.works/guides/write-a-capability-briefhttps://www.deployed.works/launch/cohort-1
Download PDFCopy template

Use the guide

Turn the work into a capability brief.

A practical guide for describing work that needs doing without turning it into a job advert.

Read the companion blog post
Submit your first capability brief