Humetry
The workforceHow we deliverPricingSecurity and controlPractitionersPartnersStart a conversationSign in
Pricing

A desk, priced like a desk.

You know what it costs to staff a role, whether through your own team or an outsourcing partner. Humetry gives you a clear monthly price for that role, based on its responsibilities, workload and agreed service standards, plus a one-time deployment fee. You pay for the work we take ownership of, never for the number of AI agents we use to deliver it.

The desk line: one equivalent desk, one yearTypical loaded costs; type yours below
0k20k40k60k80k100k
Onshore specialist, loaded65,000 to 90,000
Offshore centre or BPO, per FTE25,000 to 45,000
Humetry, Operate Band A21,600
today, per year–with Humetry, per year–the difference–
What one equivalent full-time desk costs for a year. The two comparison bands are typical loaded costs and are yours to overwrite; Humetry's mark is Operate's Band A for twelve months, the band sized to the volume one specialist handles. Type what a desk costs you today and how many you run, and the line reads your own numbers.

The recurring fee, per desk per month

A desk is one role on one entity in one system. Each kind of work is priced on its own table, in its own unit: change points for Build, tickets and alerts for Run's first line, incidents, problems and requests for L2 and L3, pieces of work for Operate. Build is one fee for the whole chain, so a change is billed once from requirement to release. A band is read from the volume handled in a month.

A change is one requirement taken to your analyst's acceptance: small counts 1 point, medium 2, large 4; an extra-large change is split before it starts. Build is one fee for the whole chain: a change is billed once, from requirement to release, whichever desks it passes through. A change not accepted is not billed.

Band A · the changes a pod of three carries in a monthAn analyst, a developer and a tester on one ERP: a handful of reports, screens and interfaces a month.
Band B · about three pods' monthA change portfolio across one ERP and its integrations, released monthly.
Band C · about eight pods, a build teamA rollout or a large programme of change across several systems.

The desks one fee coversBusiness and functional analysis, architecture, ERP, platform, custom, integration and data development, testing, release and change.

A ticket or an alert is one item taken to its resolution or its routing, with the evidence attached.

Band A · one first-line agent's monthA regional service desk's first line, business hours.
Band B · about three agentsFirst line for a mid-sized company, extended hours.
Band C · about ten agents, around the clockAround the clock, across regions and tools.

The desks on this tableService desk, access and identity administration, monitoring and event management, security alert triage.

An incident, a problem or a request is one item taken to its resolution, its root cause or its fulfilment.

Band A · one L2 and L3 engineer's monthL2 and L3 for one ERP or one platform.
Band B · about three engineersSeveral applications and their interfaces, one support model.
Band C · about eight engineersThe application estate of a large group, its batch and its patch cycles.

The desks on this tableApplication support, batch and interface monitoring, ERP technical administration, patching, cloud operations.

A piece of work is one invoice, receipt, dispute, order or request taken to completion and verified in your system.

Band A · the volume one specialist handlesA single desk on one entity: a regional AP inbox, a lockbox, a deductions queue.
Band B · the volume of a small teamA shared-service tower for a mid-sized company: all AP for a group of entities, cash application for a region.
Band C · the volume of a centre's towerA tower as an offshore centre runs it: every invoice, every receipt or every order of a large group.

The desks on this tableFinance and accounting, master data, supply chain and procurement, customers and sales, people.

USD per desk per month. Above Band C, or across many entities and systems, the fee is set in the proposal from the measured volume.

Before the first month

Two fees, each paid once, both on the card. The pilot proves the desk in your own systems; the deployment fee brings it into service, and comes back to you when the engagement continues.

01 · The pilot · 12 to 16 weeks
from25,000USD

One entity, one system, one or two desks, the historical sample with held-back cases, shadow operation, supervised production, the scorecard.

The pilot, its thresholds and its five measures →
02 · The deployment fee, once
from15,000USD

Discovery and process mapping, the integration to your systems, the acceptance thresholds, and the three evaluation stages of the pilot, per desk and per system in scope.

03 · The recurring fee
from1,600USD per desk per month

Per desk per month on the desk's own table, Build one fee for the whole chain, from the first month in service. Never per agent.

Inside every desk's fee
  • The workers, their procedures and their learning, kept to your engagement
  • A named engagement owner with backup, and the weekly service report with its evidence
  • The decisions inbox for the approvals your policy reserves to your people
  • Model usage, hosting and tools, in the processing location agreed at deployment
  • The practitioner review behind escalated cases and proposed lessons
  • The full case history and evidence pack, exportable, yours if the engagement ends
Credited in full against the recurring fee on conversion to a recurring engagement.
The principle
The price of a desk is set against what that desk costs you today, and it stays below it.
Never charged
  1. Per agentNever per agent. How many agents work behind a desk is our implementation choice and is not on the invoice.
  2. A case not completed and verifiedNever for a case that was not completed and verified in your system.
  3. A change not accepted, or one change twiceNever for a change that was not accepted, and never twice for one change: the build chain is billed once, on the change points your analyst accepted.
  4. Our own worker's failuresNever for human intervention caused by our own worker's failure. Those hours are recorded, classified, and ours.
  5. A surprise at renewalNever a surprise at renewal: the band is read from the measured volume and reviewed with you, in writing, before it changes.

The bands are the card in force. When a pilot's measured volume and delivery cost move a band, the card is reissued with a new version and date, and a running engagement keeps its band until its review.

Start a conversation

Tell us where the work sits today, the systems it runs in and the volumes. We come back with a scope, a pilot proposal and a date. We reply from a named person.

Start a conversation