PILOT / FIXED PRICE
Two weeks. One document type. Posted into your ERP.
The document your order desk retypes today, an inbound PO or a vendor bill, ends the pilot posting into your ERP on its own, with a human review queue for the ones it cannot read. If the pilot does not work, you do not pay.
What the pilot includes
A parser built for your real layouts
Built against the document variants you actually receive, and validated on a sample set you supply.
Field mapping into your ERP
Extracted fields land in the records you already use. Postings are confirmed against a staging copy before anything touches production.
An exception queue with human review
A document the parser cannot read, or that fails validation, waits for a person. Nothing posts silently.
A runbook and handover
What to do when a new layout shows up, plus a training session for the people who run the process today.
You own the build
The parser, the mappings, and the runbook are yours. No subscription sits between you and your own documents.
The two weeks, day by day
Working days, from the first sample to the handover. The mid-point checkpoint happens on your real files, not on demo data.
Day 1-2
Document study and the first parse
We trace how the document arrives today, then build a first parser against the sample set you supply. By the end of day two you see real records extracted, not a slide deck.
Day 3-4
Field mapping into your ERP
Extracted fields map onto the records you already use. Everything posts to a staging copy of your ERP while you confirm the samples.
Day 5-6
Mid-point checkpoint on real files
You send live documents. We run them end to end and review the failure list together, so the second half of the pilot works on what actually breaks.
Day 7-8
Exceptions and validation
The human review queue gets built for the documents the parser cannot read, and validation rules decide what is allowed to post.
Day 9-10
ERP posting and runbook handover
Posting goes live against your ERP on a schedule, and your team gets the runbook and a training session.
What your team owns afterward
- The parser, and the code behind it
- The field mappings into your ERP
- The exception queue and its rules
- The runbook, written for the person who runs the process
Nothing is held back behind a subscription. If a new layout shows up in month six, the runbook says how to handle it, and your team can handle it without us.
What it costs
$4,200
Flat, for the whole pilot. The scope is agreed before we start and the price does not move. Nothing is due upfront: a free written plan, a fixed quote, your signature, then we build. And the pilot is the working test. If your documents do not end up posting into your ERP, you do not pay the $4,200.
Questions buyers ask
- What if the pilot does not work?
- You do not pay. The pilot is the working test: either your document posts into your ERP without manual keying, or no invoice happens.
- What does one document type mean?
- One layout family, like inbound purchase orders or vendor bills. If you have three document types that look different, each is its own pilot.
- Who does the work?
- A functional CTO oversees the pilot, and our trained associate team builds it with the tooling we use on every engagement.
- What do we need to supply?
- A sample set of real documents, a staging copy of your ERP, and a short block of your order desk lead in week one.
Name the document that eats your team's hours.
A short intake form, no meeting required. It produces a written pilot plan and a fixed quote, reviewed by a senior engineer.