Fulcrum Works · Automation studio · Cleveland, Ohio
We build AI systems for mid-market operations teams — the classify-route-approve-file work that eats your best people's afternoons. Machines handle the routine. Your people handle the judgment.
Fig. 1 — The automation floor · live
12,447items processed today
318.2hours returned this week
The line, station by station
Every workflow we ship runs the same disciplined line. The order matters — each station only trusts what the one before it verified.
Email bodies, PDF attachments, portal exports, the fax your biggest customer still insists on — each item is read and typed on arrival: invoice, order, claim, request. When confidence drops below threshold, the system doesn't guess. It queues for a person and learns from the answer.
Typical accuracy after week three: 98.7% · below-threshold items: routed to review, never auto-processed
The fields your ERP actually needs — PO number, terms, quantities, tax treatment, remit-to — lifted off the page and validated against your master data before anything moves. A vendor name that almost matches is a flag, not a match.
Field-level validation against your system of record · three-way match where a PO exists
Approval chains, dollar thresholds, category owners, out-of-office coverage — encoded once, applied every time. The forwarding-and-hoping that used to happen in inboxes now happens in rules you can read, printed on one page.
Routing rules live in plain language, versioned · your team edits them without us
Anything inside policy is stamped and logged. Anything unusual — a new vendor, a price variance, a missing PO — diverts to the human lane with full context attached and a one-click decision waiting. That lane is a feature of the system, not a failure of it.
Median exception rate across live floors: 4.6% · every exception returns as training signal
Posted to the system of record and archived with a complete trail: what arrived, what was read, what was matched, who approved, and when. Your auditor will ask. The floor will answer.
Immutable event log per item · SOC 2 controls inherited from your existing systems
Operations logbook
We measure every engagement the way an operations team would: cycle time, touchless rate, exception rate. Three recent entries, metrics as logged.
Accounts payable · 3,900 invoices / month
11 days2.1 days
Invoice cycle, receipt to posting
Eleven days to pay an invoice, and nobody could say where the time went. We mapped fourteen handoffs and removed eleven. Headcount change: zero — the team took collections back in-house instead.
Order intake · fax, email & portal
34 hrs/wk6 hrs/wk
Manual order entry, whole team
Six people retyping faxed and emailed orders into the ERP, every day, forever. The floor now reads all three intake channels; the team handles the 6% of orders that genuinely need a phone call.
Claims intake & first-touch routing
26 hrs38 min
First response to a new claim
A claim used to sit in a shared inbox until someone triaged the morning pile. Now it's classified, severity-scored, and on an adjuster's desk before the claimant has hung up. Complex claims still go straight to senior staff — by rule, not by luck.
Worksheet W-4 · Return on automation
Slide in your own numbers. The assumptions are printed at the bottom, because a payback estimate without assumptions is a sales pitch.
¹ 62% is the median automatable share across our last twelve deployments. Yours may be 40–80%; the audit measures it before anything is built.
² $7,500 audit + typical single-workflow build ($48,000) + first-year run cost ($9,000). Larger scopes cost more; we quote fixed after the audit.
Panel B · Connections
No platform migration, no rip-and-replace. If it has an API, an export, or an inbox, the floor can read from it and write to it.
PATCH PANEL B · 121 INTEGRATIONS SHIPPED TO DATE
Standard operating procedure
Fixed fee, on your floor. We sit with the people doing the work, map every handoff, and hand back a systems map with a build / no-build call per workflow — including the workflows we think you should leave manual.
One workflow, end to end, with the exception lane live from day one. Your team approves every automated decision until the accuracy numbers earn autonomy — typically three weeks of shadow mode before the first unattended run.
Measured in gauges, not vibes: cycle time, touchless rate, exception rate, on a dashboard your COO and our engineers read from the same page. We expand only where the numbers say to.
Request form
The systems audit: two weeks, $7,500 fixed, and a build / no-build answer for every workflow we map. If automation won't pay back, the audit says so — that's what it's for.