What is shared across Digital FTEs?
Across Digital FTEs in one organization, three things are shared. The wallet: every FTE draws from the same block of metered work, with per-FTE budgets inside it and no per-role charge. The workforce view: one place listing every FTE, its status, and what is waiting on whom. And platform knowledge: anything captured at signup, onboarding, checkout, or by any FTE is available to every other, shown with a provenance chip, and never asked again.
The audit trail and the credential model are also shared, so governance is one standard rather than one per role.
What stays separate?
Each Digital FTE keeps its own remit, its own targets, its own autonomy settings per class of action, its own connections scoped to its tools and properties, and its own named manager. A Finance Controller FTE at Level 2 for exact matches has no effect on a Support FTE's settings, and the Support FTE's manager cannot approve the Finance FTE's proposals unless they hold that permission.
Property isolation also stays: an FTE working on one website or store never sees another's memory, targets, or setup, however many FTEs the organization runs.
- Shared: wallet, workforce view, platform knowledge, audit trail, credential model
- Separate: remit, targets, autonomy per class, connections, manager
- Always separate: property memory, targets, and setup
Why does the second FTE take less time?
The second FTE takes less time because the first-run wizard pre-fills from what the platform already knows: company, website, workspace profile, billing details, and anything the first FTE learned about the business. It asks only for what is genuinely new to its function, proposes targets, and ends with a day-one plan.
The manager also brings habits. Reading a morning brief, approving with evidence, sending back with a reason, promoting from the record, and reviewing monthly are the same for every role. A manager who has run one Digital FTE runs the second from the first morning.
How do you keep management time bounded?
Keep management time bounded by three practices. Route each FTE's routine categories to the team member closest to that function for approval, so the manager sees only sensitive categories. Promote routine classes on the ladder as soon as the record supports it, per FTE. And use the combined morning brief in the workforce view, which puts every FTE's waiting items in one list ordered by what blocks the most.
If management time is still growing with each FTE, the remits are too wide or the ladder is being climbed too slowly. Both show up in the send-back reasons and the approval rates.
What order should you add them in?
Add Digital FTEs in the order of clearest evidence and longest approval history first: reconciliation before content, scheduling before screening, first-line support before anything customer-facing that needs judgement. The early roles build the manager's confidence in the mechanisms and give the platform knowledge that later roles reuse.
Pair adjacent roles where one's output is another's input: a Search Visibility FTE that identifies topics worth writing and a Content FTE that writes them; an SDR FTE that qualifies leads and a Marketing Strategist FTE whose campaigns generate them. The pairing shows up in each FTE's targets and in the workforce view.
What does a labelled example of a three-role organization look like?
As a labelled example for a small company: a Search Visibility FTE, an SDR FTE, and a Finance Controller FTE share one wallet and one workforce view under one operations manager. The Search Visibility FTE's approved topics feed the content calendar; its published pages are the destinations the SDR FTE's outreach links to; the SDR FTE's qualified pipeline appears in the CRM the Finance Controller FTE reconciles invoices against once deals close. Each has its own remit, targets, autonomy settings per class, and connections, and none can see another property's memory.
The manager's morning is one combined brief ordered by what blocks the most: an exception waiting on a finance decision above a routine outreach approval. Routine approvals are routed to the team members closest to each function, and the classes with clean records, exact matches and cold first-touch outreach, are promoted per FTE. The monthly review reads three reports and three usage lines against one wallet, and the block for the next cycle is sized from their sum. Adding a fourth role would pre-fill from everything the three already know and draw from the same wallet.