Your own AI software lab, on contract.

Book time in our lab the way a manufacturer books time at a contract plant. Senior, US-based engineers design, build, test and run AI software inside the systems you already use. You own the product and the code.

2 benches open this quarter

Cutaway model of the Benchscale lab with the roof off: four process bays, client benches, an intake machine and a clean room, connected by green data lines.

BAY 01 · INTAKE

Every build starts with a spec.

Discovery is paid, and it comes first. We sit with whoever does the work today, read your actual documents and look at your data. Then we write down what we’ll build, the examples it has to get right, and a price we stand behind.

Bay 01, Intake: a spec sheet lies on a lit table, filled in with requirements, test cases and a green estimate line.

BAY 02 · DEVELOPMENT

Most of the work is plumbing.

Getting a model to read a scanned deed is the easy part. The work is everything around it: matching names against your title records, posting bills to QuickBooks without doubling them, and handling the one vendor whose invoices arrive as phone photos. That’s where we spend our time.

Typical systems on the bench

  • QuickBooks
  • SQL Server
  • ERP
  • SharePoint
  • Outlook
  • Teams
  • Title records
Bay 02, Development: code panels assembled into one system on the bench, with green data lines running to blocks labelled ERP, QuickBooks and Title records.

BAY 03 · QUALITY CONTROL

We test it on your worst examples.

Before launch we collect a few hundred real examples from you, including the messy ones your team complains about. Every version of the build runs against all of them. If a change makes even one of them worse, it doesn’t ship, and that rule keeps running after launch.

Sample eval run312 cases309 pass3 sent to a person

Bay 03, Quality control: a scanner gantry over a conveyor of outputs, all marked green after one failed output was pulled, fixed and returned.

BAY 04 · SHIPPING

You get the code. All of it.

It runs in your environment, with documentation written for the people who’ll maintain it. If something we built breaks in the first 30 days, we fix it at no charge. After that, keep us on retainer or take it in-house; either works.

Bay 04, Shipping: a sealed crate addressed to the client rolls out through the dock door, stamped 30-day warranty.

Example builds

From the lab.

Examples of what the lab can build across our core competencies. Client work stays confidential, so each one runs on sample data. Open any case to try it.

Capacity · Q4 2026Updated Oct 4, 2026

Reserve your bench.

A Lab retainer holds engineering hours for you every month. Pick a size to see where you’d sit on the floor. Booked bays are dimmed.

Retainer size
Client bays: B-01 booked, B-02 booked, B-03 selected, B-04 booked, B-05 booked, B-06 openB-01BOOKEDB-02BOOKEDB-03SELECTEDB-04BOOKEDB-05BOOKEDB-06OPEN

One bench, held for you every month. Enough for one product in steady development, or several smaller tools.

Bench available this quarter: B-03.

Reserve the Bench
  • Billed monthly, in advance
  • Priority scheduling over commissioned work
  • Monthly Lab Report: what shipped, hours, measured results
Top-down floor plan of the lab. Of the six client bays, booked bays are dimmed and the open bay for the selected tier is lit green.

Other ways to work

One build, or an hour with the lead engineer.

SPEC-201 · COMMISSIONED BUILDREV B

A fixed-scope project, start to finish.

For one clearly defined product. Paid discovery produces the spec and a fixed price; everything after that is built and tested against that spec.

  1. 01 Paid discovery: requirements, test cases, firm estimate
  2. 02 Development in the lab
  3. 03 Quality control on your real examples
  4. 04 Tested, documented delivery with a 30-day warranty
Pricing
Fixed, set at the end of discovery
Warranty
30 days on the delivered build
Commission a build

SPEC-301 · LAB HOURSREV B

Advisory sessions with the lead engineer.

For when you want an experienced engineer to look at a problem before you spend money on it. Sometimes the answer is “don’t build this yet,” and we’ll say so.

  • → Is our data ready for AI, and what would it take?
  • → Architecture and vendor review before you buy
  • → A second opinion on a build that’s stuck
  • → Scoping a project before you commission it
Format
In person in DFW, or remote
Booking
By the hour
Book lab hours

The monthly Lab Report

You’ll always know what the lab did.

At the end of each month, retainer clients get a short report: what shipped, how the hours were spent, and whether the numbers we agreed to track moved. It’s the report we’d want if we were the ones paying.

BENCHSCALE · LAB REPORT

September 2026

Client
Sample Distribution Co.
Retainer
Suite · 80 h
Report
LR-2609

01 Shipped

  1. 09-04 Invoice intake v2 handles credit memos
  2. 09-11 Freight lines post to COGS in QuickBooks
  3. 09-19 Quote agent answers lead-time questions from the ERP
  4. 09-26 AP exception queue moved into Teams

02 Hours · 80 of 80

  • Development44 h
  • Testing & QC14 h
  • Integrations12 h
  • Support & operations6 h
  • Reporting & reviews4 h

03 Measured results

Invoices posted with no typing
88%
Median email-to-bill time
6 min
Exceptions caught before posting
41

04 Next month

  1. → Vendor statements reconciled automatically
  2. → Quote agent drafts go to reps in Outlook
  3. → Quarterly accuracy review on 200 new invoices

Signed off · Lead engineer

End of report

Sample report. Figures are illustrative.

Security

Your data stays where it is.

Where your data lives
In your environment wherever possible: your cloud account, your database, your network. When data has to move, it goes to US-hosted infrastructure you approve, and only the data the build needs.
AI vendor terms
We use AI models under commercial terms that don't allow training on your data, and we tell you which providers and models will see it before anything is sent.
Access controls
Read-only by default, limited to the tables and folders a build needs, logged, and removed when the work ends.
The clean room: a sealed double-glass chamber around a stack of client data platters, ringed in green.

Carrollton, Texas

Close enough to visit.

We work out of Carrollton, a short drive from most of Dallas–Fort Worth. Discovery happens at your office, at the desk of whoever does the job today, because that’s where the real process lives. The people you meet are the people who build it.

A low-poly map of Dallas–Fort Worth with a single green marker where the miniature lab has landed.

Questions

Before you reserve a bench.

How retainers, builds, code ownership and your data work. Anything else, ask us directly.

What is Benchscale?

Benchscale is a contract AI software lab in Dallas–Fort Worth. Operating companies reserve engineering capacity, and a senior, US-based team designs, builds, tests and runs AI software inside the systems they already use: databases, ERPs, accounting and document archives. Clients own the product and the code.

What does Benchscale build?

Benchscale builds AI that works with a company's own systems: document AI that turns invoices, deeds and contracts into structured records; assistants that answer questions from your ERP, databases and documents; MCP connectors that give ChatGPT, Claude or Copilot secure access to your systems; governed AI workflows; hardening for AI-built prototypes; and private AI models that run in your own environment.

How does a Lab retainer work?

A Lab retainer reserves 40, 80 or 120 engineering hours a month (Bench, Suite or Dedicated Lab), billed monthly in advance. Retainer clients get priority scheduling and a monthly Lab Report showing what shipped, how the hours were spent and what changed in the numbers you track.

What is a commissioned build?

A commissioned build is a fixed-scope project for one clearly defined product. It starts with paid discovery, which produces a written spec, test cases from your own examples and a fixed price. Development, testing and a documented delivery follow, with a 30-day warranty on the delivered build.

Do we own the software and the code?

Yes. You own the product and the source code. It is deployed in your environment with documentation written for the people who will maintain it.

How do you test AI before it goes live?

Every build ships with an eval suite built from your own examples, including the messy edge cases. Each version runs against it before launch, and any change that makes a passing case fail does not ship. The suite keeps running on every change after launch.

Where does our data go?

Your data stays in your environment wherever possible: your cloud account, your database, your network. When data has to move, it goes to US-hosted infrastructure you approve. AI models are used under commercial terms that don't allow training on your data, access is read-only by default, and access is logged and removed when the work ends. For data that can't leave at all, models can run privately in your own environment.

Can ChatGPT, Claude or Copilot connect to our ERP or database?

Yes, through MCP connectors. Benchscale builds an MCP server for each system, with sign-in through your existing single sign-on (Microsoft Entra ID, Okta or Google Workspace), role-based permissions from your directory groups, and an audit log of every request.

Which industries do you work with?

Benchscale starts in two industries where the team already has production experience: oil and gas land and title, and building-materials distribution. The same work (document AI, data connections and governed workflows) applies to most operating companies.

Where is Benchscale located?

Benchscale is at 1536 Hutton Dr, Suite 100, Carrollton, Texas, in Dallas–Fort Worth. Discovery happens in person at your office across DFW, and the people you meet are the people who build it.

How do we get started?

Submit a work order on the site, email hello@benchscalelabs.com or call (972) 571-3364. A lead engineer reads every work order and replies with a few questions and a time to talk, then proposes discovery, a retainer or lab hours.

Get in touch

Submit a work order.

Tell us what the lab should build. A lead engineer reads every work order and replies personally, usually with a few questions and a time to talk.

  1. 01 We reply and set up a call
  2. 02 A short scoping conversation, in person if you’re in DFW
  3. 03 A proposal for discovery, a retainer, or lab hours

Work order

WO-····

Date

Assigned on submit

Issued to

Benchscale · Carrollton, TX

Work order details
07 Systems involved