The Human Translator Problem: why most subcontractors have a hidden bottleneck between the field and the ERP.

Consumer · Amazon

Wireless Headphones

Prime · Free delivery tomorrow

$49.99

Buy Now

Seconds

Construction subcontractor

Fieldneeds material

Human translatormanual entry · backlog

Supplierorder placed

Hours to days

The pattern we see almost everywhere

We talk to a lot of specialty trade subcontractors, including drywall, mechanical, electrical, acoustical, framing, and concrete. Roughly 72% of them run the exact same hidden workflow inside their purchasing operation. We've started calling it the Human Translator Problem.

Here's the pattern:

1. A superintendent in the field knows what they need to order for a project.
2. Instead of placing the order directly, they relay the need to someone internal, such as a project manager, purchasing coordinator, or office admin.
3. That internal person becomes the translator. Their job is to take an informal request ("I need two-inch EMT on Friday") and turn it into a formal purchase order: find the right supplier, get pricing, pick the right cost code, enter it into the ERP, and send it out.
4. Total elapsed time: hours to days. Sometimes longer if the translator is in a meeting, out sick, or just backed up.

Superintendent

knows the need

Translator

PM / coordinator / admin

ERP

PO entered + coded

Supplier

order placed

Nobody designed this workflow. It grew. And once you see it, you see it everywhere.

The Amazon contrast

Compare that to how a consumer buys something on Amazon. The journey looks like this: I have a need → I found it → click buy. Seconds. The order is placed, the data is captured, the supplier is notified, the receipt is filed, the shipment is tracked. Nobody translates anything. The system absorbs the intent directly from the person who has it.

In construction, that same journey takes hours or days and routes through a human whose job is essentially mechanical translation between two systems: the field's brain and the ERP. The person with the need and the person who places the order are two different people, separated by a phone call, a text thread, or a "let me get back to you when I'm at my desk."

Why the human translator exists

Before anyone gets excited about replacing this role, it's worth being honest: the translator isn't a bug. They're a load-bearing role. They do real work that protects the business:

Catch budget overruns

Before they post and ripple through the job cost.

Flag weird orders

"Why are you ordering this? It's not in scope."

Know the right supplier

Which vendor for which material on which job.

Encode tribal knowledge

Approval thresholds, cost codes, buyout boundaries.

Strip them out and orders get worse, not better. That's why every attempt to "just let the field place orders directly" eventually gets walked back. The translator is doing more than data entry. They're exercising judgment.

What happens under load

The trouble is that a translator has a fixed amount of attention. When work is light, they catch everything. When work is heavy, as it is most of the time at a growing subcontractor, they start triaging.

As one operator told us: when you get busy, you start rubber-stamping. The PO comes in, you don't have time to check the budget, you don't have time to verify the supplier, you push it through. The judgment that justifies the role quietly drops out, and what's left is just slow data entry.

Software doesn't rubber-stamp. That's the point of this whole post.

The math nobody talks about

Here's something that should make every operator pause. A growing sub will spend tens of thousands of dollars a year on their ERP or accounting system, whatever combination of Sage, Foundation, Acumatica, QuickBooks, or spreadsheets keeps the books. That's the line item everyone sees on the budget.

The line item nobody adds up is the people-time spent feeding the ERP. Add up the PM hours, the coordinator hours, the admin hours, and the after-hours catch-up time across a full year of purchasing, and it's routinely hundreds of thousands of dollars. Sometimes more than the ERP itself by an order of magnitude.

ERP software

Visible cost

Tens of thousands

$ / year

The line item everyone sees.

People-time on purchasing

Hidden cost

Hundreds of thousands

$ / year

The line item nobody adds up.

Amazon:zero people-time per order.

Amazon spends zero people-time placing each order. That's not a software comparison. That's a structural one.

The reframe: digitize the translator

The opportunity isn't to eliminate the translator role. It's to digitize the work it does.

Take the rules and instincts the translator runs in their head, including budget checks, supplier routing, cost coding, approval thresholds, and anomaly detection, and encode them so an AI can apply them every time, instantly, on every order. Then split the work the way it should have always been split:

Today

Need 2" EMT · Friday

Reorder drywall · Bldg 4

Anchors — out of stock

Add'l rebar for pour

+ 11 more

Bottleneck

Every order queues behind one person. The backlog grows faster than they can clear it.

With Punch

Routine order · auto-coded · sent

Routine order · auto-coded · sent

Exception · routed to a person

Routine flows through. Exceptions get judgment with full context attached.

The 90% of orders that are routine flow through automatically. Within budget, approved supplier, known cost code, normal quantity: there's nothing for a human to add. The 10% that are weird get routed to a human with the full context already attached. They're exercising judgment, not chasing data.

The role doesn't disappear. It gets elevated.

What changes when you do this

• A purchase order reaches the supplier in about 60 seconds, not hours or days. The field stops waiting for the office.
• The purchasing coordinator stops being a bottleneck and starts being a decision-maker.
• The ERP stays accurate in real time, because nothing is sitting in someone's inbox waiting to be keyed in.
• Budget overruns get caught on the first reorder instead of at month-end close.
• You can grow the company without linearly growing the back office.

For most subs we talk to, that last point is the one that matters. The bet on hiring more purchasing admins to support more projects is the same bet most operators are quietly trying to avoid.

How Punch fits

Punch is procurement software for subcontractors that does exactly this. The field sends a natural-language request, typed in the app, spoken into the mobile app, or emailed in plain English. Punch turns it into a properly-coded PO and sends it to the right supplier — in about 60 seconds. Then it writes the order into the ERP.

You configure the guardrails, including budgets, approval thresholds, supplier preferences, cost-coding rules, and who needs to sign off on what, and Punch enforces them on every order. Routine orders flow through. Anything outside the rules gets routed to the right person with the full context attached.

Three ways to interact: web, mobile, or email. The field picks whichever one fits the moment. The office sees the same source of truth either way.

Related reading

For more on the workflows behind this post, see the Construction Purchasing Guide, the deep dive on Construction Purchase Orders, and the operator-focused guide to Purchasing for Subcontractors.

Want to see what this looks like for your team?

Walk us through how purchasing works at your company today and we'll show you, concretely, where Punch fits in. No slides, no pressure.

Book a working session