Skip to main content
ftes.aiftes.ai

Hire a Digital FTE.It owns the work.You own the call.

12 reasons
to hire a Digital FTE

A Digital FTE is an autonomous digital employee that owns a whole job function inside the tools you already run. It proposes, you approve, and every claim arrives with its evidence. Here is the case, one reason at a time.

  1. Reason 01: It owns a whole job, not a task.

    A chatbot answers. An agent runs a task. A Digital FTE holds a job: it plans the week, does the work, hands it over for approval with its reasons and sources, and reports on the targets it is accountable for.

    Each role in the catalogue is one cell on this field. The Cash Officer FTE finds the cash frozen in stock; the Controller FTE loads the costs your platform ignores; the Buyer FTE turns both into an order you sign. Browse every role.

    [ 01.A ] The workforce field: one hex prism per role in the catalogue (41 today), each carrying its role glyph. The cells that rise and light are a handover in progress; the lines are the hand-offs; the card is a proposal waiting for you.
  2. Reason 02: Nothing leaves your company without your approval.

    Every publish, send, spend, markdown and purchase order starts as a proposal in the Approvals tab, previewed exactly as it will land, with the reasoning and the evidence attached. You approve, modify, or send it back with a note, and the note becomes a rule the role applies from then on.

    Hard limits sit above everything: price floors, refund limits, ad and frequency caps, the cash ceiling. An action that would cross one is refused and queued, never quietly trimmed to fit. How control works.

    Approvals

    2 waiting on you

    • Performance Ads FTE · Launch · needs your approval

      Proposed · policy pre-check passed

      Meta prospecting set B · 3 creatives

      • Set A is at target ROAS for 6 days; B tests a new hook on the same audience.
      • Daily cap $150 — inside the account cap you set.

      Creative preview · audience · attribution plan attached

    • Search Visibility FTE · Draft · ready for review

      WRITE · worth it

      Why answer engines rank differently from Google

    Illustrative · figures are samples

    [ 02.A ] An illustrative approvals queue: two proposals, each with its verdict, its reasons and its evidence, and nothing sent until you decide.
  3. Reason 03: You manage it like a direct report.

    No new dashboard for your team to learn. A Digital FTE reports into a workspace you review the way you review a direct report: a morning brief, a queue of decisions, the numbers it is accountable for, and the targets you set.

    At month end you hold the review a manager would hold: what it proposed, what you approved, what it measured, and what it got wrong. See the full workspace tour.

    Workspace · Search Visibility FTE · Today

    Morning brief · Monday 08:00

    Yesterday: 3 drafts fact-checked, 1 refresh published, 0 escalations.

    Waiting on you

    2 to review
    Share of answers
    31%
    Published this week
    4
    Waiting on you
    2
    Spend vs budget
    62%

    Workspace · Search Visibility FTE · Approvals

    Approvals

    1 waiting on you

    • Search Visibility FTE · Draft · ready for review

      WRITE · worth it

      Why answer engines rank differently from Google

      • No page on the site answers this query; 3 competitors do.
      • Tracked in 2 of 5 AI assistants for the brand — the gap is measurable.

      9 claims · 9 sourced · 0 flagged

    Workspace · Search Visibility FTE · Performance

    Share of answers
    31%+4 pts
    Published this week
    4
    Waiting on you
    2
    Not connected yet
    Unmeasured

    Share of answers · 12 weeks

    Measured, not estimated

    Workspace · Search Visibility FTE · Targets

    • Be cited in 3 of 5 AI assistants for the brand

      Measured weekly · 2 of 5 today

      On track
    • Own the answer for 'answer engine optimization'

      Ranking 6 → 4 this month · refresh queued

      At risk
    • Refresh every page that decays more than 20%

      3 refreshed this month · 0 pending

      Done
    • Publish two fact-checked articles a week

      FTE-suggested · awaiting your approval

      Proposed · your call
    1. 01 · 06:30

      The morning brief is waiting.

      What needs your signature comes first, then yesterday, what it noticed, and spend against budget.

    2. 02 · 09:10

      A proposal lands in Approvals.

      With its verdict, its reasons and its evidence. Approve, modify, or send it back with a note.

    3. 03 · 14:00

      It notices, and it asks.

      Detections arrive as ranked hypotheses with evidence, never certainties.

    4. 04 · 17:30

      Measured against the contract.

      Every target carries a status and its evidence. What it cannot measure stays unmeasured.

    [ 03.A ] A day with the Search Visibility FTE: the frame on the left follows the step you are reading. Illustrative frames, real tabs, sample figures.
  4. Reason 04: There is a role for every job a team or a store pays for.

    The catalogue holds 41 roles. Three marketing roles ship with a full workspace today and apply to any business with a website, a social presence or an ad budget. The rest are department roles: finance, sales, HR, support, strategy, and the e-commerce workforce, thirty roles in nine departments, read as an org chart rather than a feature list.

    Hire one or several; they share one wallet and one workspace, and each reports to you on its own targets. See the e-commerce org chart.

    01020304050607080910
    1. 01Office of the Owner

      Decisions taken and landed

      2 roles

    2. 02Finance

      True margin, cash released, dollars recovered

      3 roles

    3. 03Merchandising

      Sell-through and markdown avoided

      5 roles

    4. 04Product Quality

      Return rate and return cost

      3 roles

    5. 05Customer

      Repeat rate and owned-channel revenue

      5 roles

    6. 06Demand

      Contribution per channel, citation share

      7 roles

    7. 07Operations

      Shipping as a share of revenue, promise kept

      3 roles

    8. 08Retail

      Sales per trading hour

      1 role

    9. 09Supply

      On-time delivery and vendor quality

      1 role

    10. 10Every industry

      Marketing, finance, sales, HR, support, strategy

      11 roles

    11. 41 roles today. One hex each.

      The org chart
    [ 04.A ] The org-chart field: every role in the catalogue, ordered by department. Rose bands 01–09 are the 30 e-commerce roles; the ink band is the 11 roles every industry can hire. Counts come from the catalogue file.
  5. Reason 05: Every number on this page is one we can count.

    Most pages in this category open with a number nobody can check. This one does not. The only figures on this page that are not labelled illustrative are counts of things we can point at: roles in the catalogue, departments on the org chart, industries with a page, systems named on the integrations page, guides in the library.

    Inside the product the rule is the same: every KPI a Digital FTE reports is measured, never estimated, and anything not connected yet is shown as unmeasured. Read the library.

    Digital FTEs you can hire
    41
    in the catalogue today
    e-commerce departments
    9
    the org chart on the industry page
    industries with a page
    7
    each with its own roles and tools
    systems it works in
    64
    named on the integrations page
    guides, every claim checkable
    441
    in the library, answer-first
    [ 05.A ] Five counts computed from the site's own data files at build time. No market statistics, no performance claims; the sample figures inside product frames are labelled illustrative.
  6. Reason 06: Autonomy is earned, one class of action at a time.

    A Digital FTE starts at Level 0: it proposes only. When a class of action, a routine order-status reply, an exact reconciliation match, an alt-text fill, has a long, clean approval record, you can promote that class to run without a gate. Anything else stays where it was, and any level can be taken back from Setup in one click.

    Most managers run most roles at Level 0 or 1 indefinitely, and that is a perfectly good outcome. The higher levels exist for the repetitive, low-value, high-volume work where a human approval adds nothing but delay. The autonomy ladder, explained.

    L0L1L2L3
    1. L0

      Proposes only. Every draft, launch, send or spend waits in Approvals. This is where every FTE starts.

    2. L1

      Low-risk on its own. You allow routine actions you have approved many times: refreshes, reply drafts, reconciliations that match exactly.

    3. L2

      Acts inside caps. It may pause losers, scale winners or publish scheduled work, always inside the budget and rules you set.

    4. L3

      Runs the week. Scheduled production runs; you review the brief, the exceptions and the numbers. Any level can be taken back at any time.

    • 01Approval gates on every publish and every dollar of spend.
    • 02An autonomy ladder you climb on your terms, and can step back down.
    • 03Budgets and balances always in view. Never a surprise.
    [ 06.A ] The autonomy stairs: four levels, granted per class of action on the approval record, reversible at any time. Level 0 is lit because every FTE starts there. The three guarantees hold at every level.
  7. Reason 07: It works inside the systems you already run.

    No rip-and-replace. A Digital FTE connects to the systems your team runs today, the store platform, the ledger, the CRM, the help desk, the ad accounts, the marketplaces, and does its job there, with the permissions you give it and nothing more. Connections are granted per organization and per property, and can be revoked at any time.

    All integrations.

    [ 07.A ] The stack map: the Digital FTE at the centre, the systems it works in around it, by function. Names only: a tool being listed means a role can work in it, and nothing more is claimed.
  8. Reason 08: It speaks your industry's vocabulary and follows its rules.

    A Digital FTE is not retrained per vertical; it is onboarded like a new hire, with your terms, your systems and your approval process. Onboarding captures your industry’s vocabulary, its rules and the topics it must never touch, and it never asks twice.

    E-commerce is the flagship: 30 roles in 9 departments, from cash and margin to fit, returns and marketplaces. All industries.

    [ 08.A ] The industries with a page today, the flagship first. One hexagon per role each can hire now, the same count its own page shows; the systems those roles work in are listed there.
  9. Reason 09: You pay for output, not seats.

    Every plan is a block of work, metered in tokens, not a seat. Every Digital FTE in your organization draws from the same wallet, and the balance is always visible inside the workspace. When it reaches zero the roles pause. They never overdraw.

    The pricing page lists the current plans; nothing on this page states a price, because the live catalogue is the only source of truth. See pricing.

    Organization wallet · this cycle

    Active

    62%

    of the block remaining

    100 cells · one block · hard stop at zero · no overdraft · top up any time

    Drawn by role · illustrative

    Search Visibility FTE
    41%
    Performance Ads FTE
    33%
    Social Growth FTE
    26%

    Every role in the organization draws from the same block. The balance is always in view inside the workspace; at zero the roles pause.

    [ 09.A ] The token block: one block of metered work as a hundred cells, the remaining ones standing, the spent ones flat. Shared by every role, a balance always in view, a hard stop at zero. Illustrative figures.
  10. Reason 10: Your company. Your data. Your rules.

    Multi-tenant by design: your organization’s data is scoped, your roles gate every action, and every step a Digital FTE takes is written down. Integration credentials are encrypted at rest and revocable at any time. Anything your process marks as sensitive is escalated to a person and never handled automatically.

    Read the security overview.

    ABLOG
    Field
    Your organization
    A
    Property · website, with its role
    B
    Property · store, with its role
    Log
    The audit trail every action is written to
    • 01

      Isolated by design

      Every record is scoped to your organization and to the property it belongs to. One FTE's website never sees another's.

    • 02

      Roles and permissions

      Owner, admin, member and custom roles decide who can hire, approve, publish and spend.

    • 03

      A full audit trail

      Every proposal, approval, publish and token spent is logged with who, what and when. Credentials are encrypted at rest.

    [ 10.A ] The tenant boundary: the organization as a field, each property raised on it with its own role, and the audit log every action is written to. No certification is claimed that has not been achieved.
  11. Reason 11: It tells you what it cannot measure.

    Verdicts carry reasons, scores carry itemised notes, claims carry sources, and diagnoses arrive as ranked hypotheses with evidence, never as certainties. If the platform cannot measure something, the workspace says so instead of filling the gap with a number that looks right.

    That is also why the roles can be trusted with more over time: a role that names its own misses every month has earned the next rung. How a Digital FTE is measured.

    Workspace · Search Visibility FTE · Targets

    • Be cited in 3 of 5 AI assistants for the brand

      Measured weekly · 2 of 5 today

      On track
    • Own the answer for 'answer engine optimization'

      Ranking 6 → 4 this month · refresh queued

      At risk
    • Refresh every page that decays more than 20%

      3 refreshed this month · 0 pending

      Done
    • Publish two fact-checked articles a week

      FTE-suggested · awaiting your approval

      Proposed · your call
    [ 11.A ] The Search Visibility FTE's Targets tab: each target with a status and its evidence; FTE-suggested targets wait for your approval. Illustrative figures.
  12. Reason 12: It starts this week.

    Sign up, pick a role, connect the tools it needs, and confirm the targets it proposes. It never asks for what the platform already knows. Its first brief and first proposals land in Approvals, and the first monthly review is the honest comparison against the baseline you recorded before it started.

    Every marketing click on a role lands you on that role’s start screen after any sign-in path, so the hire you chose is the one you meet. Read the docs.

    1. Mon · you

      Sign up and connect

      Create your organization; the role you clicked is added to it. Grant the tools it needs.

    2. Tue

      It proposes targets

      From what the platform already knows: never asked twice. You confirm or edit them.

    3. Wed

      First morning brief

      What it noticed, what it plans, spend against budget. Nothing has left the company yet.

    4. Thu · you

      First proposals

      Drafts, launches or orders land in Approvals with their reasons and evidence. Your call.

    5. Fri

      First review

      What it proposed, what you approved, what it measured, and what it got wrong.

    Hire a Digital FTE today and review its first proposals this week.

    [ 12.A ] The first week: the days that need you are lit, the days the role works and reports are paper. Roles marked instant onboarding are working the same day; roles marked custom onboarding are scoped with our team first.

Transparent pricing

Simple, transparent pricing.

A plan is a block of work for your whole organization. No seats, no per-role charge, and nothing leaves the company without your approval. Two ways to pay, and the first run is on us.

Way one

On the ftes.ai wallet

Buy a block of metered work. Every role you hire draws from it; the balance is always in view.

Included

  • Every role in the catalogue, hired one at a time or as a department
  • One wallet for the whole organization; no per-seat or per-role charge
  • The balance, this cycle's usage and the split per role, always in view
  • A hard stop at zero: the roles pause and tell you; nothing runs on credit
  • Your first run on us: a starting block of tokens is granted at signup

Way two

On your own model key

Bring your Anthropic or OpenAI key. The roles run on it, and ftes.ai meters nothing for those runs.

0Tokens metered
by ftes.ai

You pay Anthropic or OpenAI at their rates · per organization or per property

Included

  • Your own Anthropic or OpenAI key, encrypted at rest and revocable at any time
  • Set per organization, or per property so each website or store funds its own roles
  • Runs on your key are not metered by ftes.ai; you pay your provider at its rates
  • The same workspace, approvals, targets and audit trail as the wallet
  • Switch back to the wallet, or mix both across properties, whenever you like

First run

The first run is on us.

Every new organization is granted a starting block of 1,000,000 tokens. Brand research and your first targets run before any payment; you choose a plan, or add your key, when it is used up.

Start the first run

Workforce

Hire a department, not a role.

33 roles onboard instantly. The 8 roles marked custom onboarding, and the 30-role e-commerce org chart as a whole, are scoped with our team first: your systems, your rules, one wallet.

[ P.A ] Two ways to pay. The price is read from the live plan catalogue; the starting grant is the platform’s current setting. Plans differ by block size only.

Included in every plan.

The whole workspace, on every plan. Plans differ by the size of the block, never by what a role is allowed to do.

  • Manage

    • Today: the morning brief
    • Approvals with verdicts and evidence
    • Targets: the contract you set
    • Performance, honest to the month
  • Produce

    • Pipeline by stage
    • Library: what it owns
    • Missions: production, diagnostic, strategy
    • Memory: the brand brain it keeps
  • Connect

    • Integrations by function, with your permissions
    • A property switcher: one role, many sites
    • Bring your own model key
    • An MCP connector for Claude and ChatGPT
  • Publish

    • WordPress and Shopify
    • Your own Next.js site, through the publish package
    • A preview of exactly what will land, first
    • Nothing leaves without your approval
  • 01

    Priced by work, not seats

    A plan is a block of metered work for the whole organization. Add members, add roles, add properties: the block is what you pay for.

  • 02

    Control built in

    The balance and the split per role sit next to the work itself. At zero the roles pause and say so. There is no overdraft to discover later.

  • 03

    Your approval before anything leaves

    Every publish, send, spend and order starts as a proposal. Autonomy is granted per class of action, and can be taken back in one click.

Questions about the price.

What is a block of work?

A plan buys a block of tokens for your organization. Drafting, fact-checking, measuring, briefing and proposing consume tokens; reading your workspace does not. Every role you hire draws from the same block.

What happens when the block runs out?

The roles pause and tell you in the workspace. Nothing runs on credit and nothing is charged beyond the block. Top up, or wait for the next cycle, and they resume where they stopped.

Do members or extra roles cost more?

No. Plans are per organization: invite as many members as you need and hire as many roles as you like. Only the size of the block changes between plans.

Can I run the roles on my own model key?

Yes. Add your Anthropic or OpenAI key for the organization, or for one property. Runs on that key are not metered by ftes.ai; you pay your provider at its rates. Keys are encrypted at rest and can be revoked at any time.

Is there a free trial?

Every new organization is granted a starting block of 1,000,000 tokens, so brand research and the first targets run before any payment. When it is used up you choose a plan, or add your own key.

Which roles can I start today?

33 roles onboard instantly after signup. The 8 roles marked custom onboarding, and a whole department from the e-commerce org chart, are scoped with our team first.

The full plan list, with what each block includes, is on the pricing page.

For e-commerce brands

One analyst on your own store data, with the money attached.

Every e-commerce Digital FTE works on the commerce engine: a read-only copy of your store, refreshed every fifteen minutes, a deterministic analytics engine that computes every figure, and AI that only interprets. Questions that used to need six reports get one answer, priced in dollars, with the evidence attached — and nothing leaves without your signature.

  1. Law 01

    The backend calculates.

  2. Law 02

    The AI interprets.

  3. Law 03

    A human approves.

FAQ

Questions a manager asks.

Short answers. The docs have the long ones.

What is a Digital FTE?

A Digital FTE is an autonomous digital employee that owns a whole job function, not a task and not a chat window. It has a role, targets, a budget and a manager: you. It works inside the tools you already run, proposes its work in a workspace you review, and is measured on outcomes.

How is that different from an AI agent or a chatbot?

A chatbot answers. An agent runs a task. A Digital FTE holds a job: it plans the week, does the work, hands it over for approval with its reasons and sources, and reports on the KPIs it is accountable for. You manage it like a direct report.

Do I have to replace the software we use today?

No. The FTE connects to your existing systems, such as your CMS, ad accounts, CRM, help desk or accounting stack, and works there. There is no new dashboard for your team to learn.

What can it do without my approval?

By default, nothing that leaves your company: no publish, no send, no spend. It proposes, you approve. You can grant more autonomy step by step and take it back at any time. Every action is logged.

How is it priced?

Plans are token-metered blocks of work, not seats. Every FTE in your organization draws from one wallet whose balance is always visible; at zero the FTEs pause and never overdraw. Or bring your own model key and those runs are not metered at all. The pricing section above and the pricing page list the current plans.

Where does my data go?

Your data stays scoped to your organization and, where it applies, to the specific website or account the FTE works on. Integration credentials are encrypted at rest. Roles and permissions decide who can see and approve what.

How fast can I start?

Sign up, pick a role, connect the tools it needs, and confirm the targets it proposes. Most roles onboard instantly; roles marked custom onboarding are scoped with our team first.

Hire a Digital FTE.
It owns the work.

You own the call.