Deployed Works Guide
Capability Brief Vs Job Advert
A practical comparison guide for teams deciding whether they need a job advert, a capability brief or a technical project brief.
Audience
Founders, operators, hiring managers, people teams, finance-conscious leads and anyone turning unclear work into a next step
Time
8 minutes
Outcome
A clearer choice between hiring, deployment and technical scoping
Share this guide
PDF guide
Download and share with your friends and colleagues.
Download this guide as a PDF and share it with your friends, colleagues or team. The web guide remains the canonical version.
Related guides
Brief Comparison Matrix
Choose the document that matches the work.
Use this comparison before writing a job advert, capability brief or technical project brief. The right format depends on whether the need is a durable role, a scoped deployment or a technical scoping problem.
Job advert
Best for a durable role
- The work is continuous
- A permanent owner is needed
- Responsibilities are stable enough to hire against
- The team is ready to onboard and manage
- Success depends on long-term team ownership
Capability brief
Best for deployed capability
- Progress is needed in 30-60 days
- The first outcome can be described clearly
- Specialist capability is missing internally
- The long-term role shape is not yet obvious
- A scoped engagement can reduce risk before hiring
Technical brief
Best for delivery detail
- Systems, data or dependencies need detail
- Acceptance signals need to be defined
- The team needs to explain constraints before a provider call
- Requirements are useful but not yet procurement-ready
- The detail can strengthen a capability brief
Guide summary
What this guide helps you do
Who it is for
Best fit readers
- A founder deciding whether a problem is a role, a project or a first deployment.
- A hiring manager who has a job title but not yet a clear description of the work.
- An operator trying to move an urgent workflow, AI or automation need forward.
- A people or finance lead comparing permanent headcount with a scoped engagement.
- A team writing a brief for technical work before talking to providers.
The problem
Traditional hiring starts too late in the thinking.
Teams often reach for a job advert because it is familiar. That can be right when the work is continuous, owned by one person and needs a permanent role. But when the need is urgent, scoped, specialist or exploratory, a role-shaped advert can hide the actual work. A capability brief starts with the work that needs doing, the outcome required and the capability needed to make progress.
Step by step
Build the brief around the work.
Use a job advert when the role is durable
A job advert is useful when the work is continuous, the organisation needs a permanent owner, the responsibilities are stable and the team is ready to hire, onboard and manage someone.
Use a capability brief when the work comes first
A capability brief is useful when there is a real problem, a first outcome, a timeline, a budget signal and a need for specialist capability before the long-term role shape is obvious.
Use a technical project brief when delivery detail matters
A technical project brief helps describe systems, constraints, requirements, data, dependencies and acceptance signals. On Deployed Works, that detail can become part of a stronger capability brief.
Look for the first useful outcome
If you can name the progress needed in the next 30-60 days, the work may be ready for a capability brief even if the permanent hiring plan is still undecided.
Keep recruitment in the options list
Deployment is not a claim that recruitment is wrong. It is another route for work that needs progress before, beside or instead of a permanent hire when the situation fits.
Write the brief before choosing the channel
Describe the problem, outcome, scope, must-haves, timeline, budget signal and what good looks like. Then decide whether to publish a job advert, submit a capability brief or refine a technical project brief.
Example
Same need, three different formats
Job advert: We need a full-time RevOps Manager to own systems, reporting and sales operations. Capability brief: Our sales-to-onboarding handoff is creating delays. We need workflow automation capability to map the process, clean missing HubSpot fields, reduce Slack clarification and improve account setup in the next 30-60 days. Technical project brief: The work involves HubSpot fields, onboarding forms, Slack handoff, manual account setup, permissions, reporting and acceptance criteria for the first automation or process improvement.
Template
Route choice worksheet
Work need: Is the work continuous? Does it need a permanent owner? What progress is needed in the next 30-60 days? What capability is missing internally? What systems, data or constraints matter? What would good look like after the first phase? Best route: - Job advert: - Capability brief: - Technical project brief: Reason: Next guide to use:
Common mistakes
Avoid these traps
- Writing a job advert because the team has a job title but not a clear work problem.
- Using a capability brief for work that clearly needs a permanent full-time owner now.
- Listing tools and seniority without explaining the outcome.
- Treating a technical project brief as a procurement document before the problem is understood.
- Claiming deployment replaces hiring in every situation.
Checklist
Ready to publish when
- The team knows whether the work is continuous, scoped or exploratory.
- The first useful outcome is written in plain English.
- The internal owner is named.
- The required capability is clearer than the job title.
- Technical systems, constraints and acceptance signals are captured if relevant.
- The chosen route does not overstate what deployment or recruitment can do.
FAQ
Questions this guide usually raises
Is a capability brief better than a job advert?
Not always. A capability brief is better when the work is scoped, urgent, specialist or exploratory. A job advert is better when the organisation needs a durable permanent role and is ready to hire.
Can a capability brief lead to a hire later?
Yes. A first deployment can clarify what the long-term role should be, what skills matter and whether permanent headcount is justified. It can sit before or beside recruitment.
Where does the technical project brief template fit?
Use the technical project brief template when systems, requirements, dependencies or acceptance criteria need more structure. That detail can then strengthen the capability brief.
Does deployment mean recruitment is obsolete?
No. Recruitment remains the right route for durable roles, long-term ownership and ongoing team needs. Deployment is useful when focused work needs specialist capability and a clear first outcome.
Take it with you
Download and share with your friends and colleagues.
Download this guide as a PDF and share it with your friends, colleagues or team. 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
Turn the work into a capability brief.
Compare a capability brief with a traditional job advert so teams can decide when to describe work, when to hire and when to scope a technical project.