01Managed outcome
Managed Deputy
A fuller handoff for work that needs output, rhythm, quality checks, reporting, and clean offboarding.
- Outcome handled
- Delivery rhythm managed
- Progress reported
- Quality reviewed
- Handoff protected
Two operating paths
Pick the operating shape before the person.
02Embedded support
Embedded Deputy
A closer-to-team model for support that plugs into agreed tools and workflows while oversight remains visible.
- Closer to your team
- Works inside agreed tools
- Better for collaboration
- More day-to-day control
- Oversight remains
Both paths include
What stays protected in both paths
Matched for the work
Support is chosen for the role, communication rhythm, and responsibility level.
Clear onboarding
Role, tools, expectations, and access are agreed before support begins.
Access rules
Sensitive tools and customer-facing systems are handled with approval and boundaries.
Quality oversight
Work is reviewed through a visible rhythm, not left floating.
Proper offboarding
Access, files, handoffs, and continuity are treated as part of the work.
Which path fits?
Use the amount of day-to-day control as the signal.
Managed Deputy
Choose this when:
- You want outcomes, not another person to manage
- The work is recurring
- You need delivery rhythm and reporting
- You want That Deputy to own more of the process
Operating lifecycle
From role need to clean handoff
- 01
Role need
What work needs to be handled, and why now?
- 02
Responsibility level
What tools, customers, data, or workflows will the role touch?
- 03
Match and onboarding
The deputy is matched, expectations are set, and access rules are agreed.
- 04
Delivery rhythm
Work begins with a clear communication and review rhythm.
- 05
Quality and continuity
Output is reviewed, gaps are corrected, and the process is documented.
- 06
Offboarding or expansion
If support ends, access and handoffs are cleaned up. If it works, responsibility can expand.
Operating standard
Not loose outsourcing. Not payroll bloat.
That Deputy is built to add specialist development, project delivery, creative, and marketing capacity with clearer matching, better operating rules, and accountability around the work.
Not random freelancers
Instead: Matched support with an operating layer.
Not hidden access
Instead: Onboarding, approvals, and offboarding.
Not unmanaged work
Instead: Rhythm, reporting, and quality oversight.
Not every role remote
Instead: Support is reviewed before acceptance.
Next step
Know which path fits your team?
Tell us what role you need covered and how close the support needs to sit to your team.