AI Document Processing in Australia: Intake Agents for Xero, MYOB and Your ERP
Your team still retypes customer purchase orders, delivery dockets and credit applications from PDFs and phone photos into Xero, MYOB, NetSuite, Cin7 Core or Unleashed. We build an AI intake agent that reads each document, checks it against your own records and ABN Lookup, and files a draft for a person to confirm. Working software on your own documents before you sign. Founder replies within 24 hours.
What does a document intake agent do for an Australian business?
A document intake agent reads the paperwork that arrives at your business, such as customer purchase orders, delivery dockets and trade account applications, checks each field against your own records, and files a draft in Xero, MYOB or your ERP for a person to confirm. It is a form of intelligent document processing (IDP). Fields it is unsure of go to a review queue with the original page beside them, so a messy scan slows down instead of turning into a wrong record. FactoryJet builds custom document intake agents for Australian wholesalers, manufacturers, freight firms and trade suppliers, filing into Xero, MYOB, NetSuite, Odoo, Cin7 Core or Unleashed.
OCR turns a picture of text into text. Intelligent document processing (IDP) works out what that text means and which field it belongs in. A review queue is the screen where a person confirms what the agent was unsure of. A draft is a record created in your system but not yet confirmed, so nothing ships, bills or opens until someone says yes.
Supplier invoices are their own job, with ATO tax invoice checks and approval routing, and we cover them on our accounts payable automation page, which is also where invoice OCR for supplier bills lives. This page is about the rest of the pile: the orders, dockets, forms and certificates that never fit a bookkeeping app, and usually end up retyped by the most experienced person in the office.
Eight things the intake agent does with every document
Reading the page is one step of eight. The checks and the review queue are what make the output safe to file.
Collects from every place paperwork lands
A shared orders inbox, a customer portal upload, a scanner folder or a courier app export. The agent watches each one, so nobody forwards PDFs around before work can start.
Splits and sorts the pile
One email can carry three orders and a remittance. A scanned batch can hold twenty dockets. The agent cuts files into single documents and labels each by type before anything is read.
Reads the fields you name
Customer, PO number, delivery address, item codes, quantities, prices, ABN, signature present or missing. You choose the fields per document type; the agent reads only those.
Checks them against your own records
Before a record is drafted, the agent confirms in your system that the customer is known, item code 40-118 exists, the price sits inside that customer’s price list and the ABN matches ABN Lookup.
Sends unsure fields to a person
Each field carries a score. Below your bar, the document goes to a review queue with the original page beside it. A person confirms or fixes it, and the correction is logged.
Files a draft in the right system
A sales order in NetSuite, a contact with the application attached in Xero, a receipt record in Cin7 Core or Unleashed. Where a system has a draft state, the agent uses it. MYOB sale orders have none, so they wait in the review queue until a person approves them.
Keeps the original with the record
The source document is attached to, or linked from, the record it created, so anyone can see what arrived and what was entered, months later.
Reports what it did and why
A daily summary: documents in, records drafted, documents held and the reason each was held. Your team sees the exceptions first and the routine work as a count.
Which paperwork Australian businesses hand to an intake agent first
The best first document is the one that arrives often, in many layouts, and gets typed into the same system every time. These are the ones we hear about most from established Australian businesses.
Wholesale and distribution
Customer purchase orders that arrive as PDFs, spreadsheets or photos of handwritten order pads, read and prepared as sales orders for approval in MYOB, NetSuite, Cin7 Core or Unleashed, with item codes and price lists checked first. Orders with an unknown code or an off-list price wait for a person.
Manufacturing
Supplier certificates of conformance, test reports and material data sheets matched to the batch or purchase order they belong to, plus customer drawings and order changes logged against the job. Expired or missing certificates are flagged before goods are released.
Freight, 3PL and warehousing
Consignment notes, signed proof of delivery and damage reports from carriers such as Australia Post, StarTrack and Sendle read and matched to the order, so disputed deliveries have their evidence attached before the customer rings.
Trade suppliers and B2B ecommerce
Trade account and credit applications read, ABNs checked against ABN Lookup, and the account drafted for the credit team to approve. For online B2B ordering itself, see our ecommerce development work in Australia.
Healthcare and allied health admin
Referral letters and intake forms read into the practice system for an admin person to confirm. Admin only, never clinical judgement. Health information is sensitive information, so access limits and review steps are tighter on these builds.
Accounting and bookkeeping firms
Client source documents sorted and filed against the right client and period, and missing items requested automatically. Firms that also need the client-facing side can see accountant website design.
Built into Xero, MYOB, NetSuite, Odoo, Cin7 Core and the ERP you already run
The agent works through each system’s official connection, with its own login and only the access the job needs. You do not change software to use it, and if a system offers no way in, the agent prepares the record for a person instead of guessing.
Xero
Contacts, quotes, draft invoices and attachments for the documents Xero’s own capture does not cover.
MYOB Business and AccountRight
Sale orders, customers and items through the MYOB Business API (sale orders have no draft status, so each waits in the review queue for approval before it is created as Open), which works with AccountRight, new Essentials and MYOB Business files.
MYOB Acumatica and NetSuite
Sales orders, item receipts and customer records in mid-market ERPs, each through a separate login for the agent with only the access the job needs.
Odoo, Cin7 Core and Unleashed
Sales and purchase orders, stock receipts and delivery records in the inventory systems Australian wholesalers and brands run.
QuickBooks Online
Customers, estimates and invoices for businesses on QuickBooks in Australia, filed as drafts for review.
Microsoft 365 and Google Workspace
The inboxes, shared drives and SharePoint libraries where documents arrive, plus Teams or Google Chat for review alerts.
ABN Lookup
ABN and business name checks on applications and new customer orders, through the Australian Business Register’s free web services.
Your own ERP or database
If it has an API or a supported import, the agent can file to it. Without either, the agent sets the record out field by field on the review screen, ready to enter in one sitting.
MYOB facts from the MYOB Business API overview and Sale Order reference; Xero capture facts from Xero’s smart document capture post; ABN checks from ABN Lookup web services. All read on 29 October 2026.
The agent drafts. Your people confirm orders, accounts and anything unusual.
Every field the agent reads carries a confidence score, and every document type has a bar for each field. A PO number on a clean typed order clears it easily. A quantity scrawled on a faxed order pad may not. Below the bar, the document waits in the review queue with the field highlighted on the original page.
Scores are half the safety net. The other half is checks against your records: an unknown customer, a discontinued item code, a price outside the customer’s list, a delivery address that does not match the account, or an ABN that does not match ABN Lookup. Any failed check holds the document, however confident the reading was.
Corrections are logged with who made them, so after a few weeks you can see exactly which customers, layouts and fields cause the misses. That record is what lets you move a field to automatic drafting with evidence rather than hope.
- Sorting and splitting documentstype labels, page splitsAutomatic
- High-scoring fields that pass every checkdrafted, or held for approval where there is no draft state (MYOB)Draft only
- Low scores or failed checksreview queue, original page attachedReview
- Confirming orders, opening credit accountsstock, credit, moneyAlways a person
- Deleting records, changing pricesoutside the agent’s jobNever
A document intake project in seven steps, demo before contract
Open any step to see what happens and what you hold at the end of it. Each phase is scoped, priced and signed on its own, so you can stop after any of them.
01Collect a real sample
You send a batch of documents your team has already processed, including the ugly ones: faxes, phone photos, multi-order emails. We also get read-only access to the system they end up in.
You get: A sample set and a list of document types ranked by volume.
02Write the field list and the rules
For each document type we agree which fields matter, which checks run against your records and who reviews what. This is written in plain English and signed off by the person who owns the process.
You get: A one-page specification per document type.
03Show you a demo on your own documents
An early version of the agent reads the sample, and you see its fields next to your team’s, unsure ones marked. This happens before you sign the build.
You get: A field-by-field accuracy table on your documents, and a fixed price for the build.
04Build the connections and the review queue
We connect the inboxes and folders, build the checks against Xero, MYOB or your ERP using a login with only the access the job needs, and set up the review screen where your team confirms unsure fields.
You get: A working agent in a test environment, documented and in your accounts.
05Test on past documents
The agent runs on a few hundred processed documents. We compare every field with what your team entered, then tighten rules and score bars until the misses are understood.
You get: A test report with accuracy per field and per document type.
06Supervised pilot on live paperwork
Live documents flow through, and a person reviews every draft for an agreed period. As the numbers hold, high-scoring fields move to automatic drafting. Confirming orders stays with people.
You get: Pilot results and a go-live decision that you make.
07Go live with logs and optional support
Every document, field, check and correction is logged. Defects are fixed inside the build price for the agreed cover period. After that, support is your choice, with each change quoted before we start.
You get: A live intake agent you own, with the team that built it on call if you want it.
Next step
Send ten of your messiest documents and watch the agent read them
Tell us which paperwork your team retypes and where it ends up. The demo runs on your own documents before you sign anything.
What terms apply, and what should you send for a quote?
These terms apply to every intake build. If you have a brief or an RFP, send it as it is. If you do not, the list on the right is all we need to scope the job and price it.
- Demo on your data before you sign.
- Fixed price per phase, quoted in writing. You can stop after any phase.
- You own it from day one: code, rules, test documents and logs.
- Your AI and hosting accounts, at cost, with no markup.
- Defect cover inside the build price.
- Changes quoted and approved per request, with no monthly minimum.
- Which documents arriveTypes
- Roughly how many a weekVolume
- Where they arrive: inbox, portal, scannerSource
- Which system they must end up inTarget
- Who checks them today, and howReview
- Five to ten real examples, redacted if you likeSample
Built-in capture vs an intelligent document processing (IDP) platform vs a custom intake agent
Each one is the right answer for someone. Rent first when your documents are bookkeeping paperwork. Build when the documents, the checks or the destination are particular to your business.
Swipe sideways to see every column.
| What you get | Custom intake agent (FactoryJet) | Capture built into your accounting app | Rented IDP platform |
|---|---|---|---|
| Best fit | Orders, dockets and forms that go into an ERP or inventory system | Receipts, bills and statements for bookkeeping | High volume of one standard document type |
| Checks against your own records | Customers, item codes, price lists, ABN Lookup | Duplicate and transaction matching | Usually, after you configure it |
| Destination systems | Xero, MYOB, NetSuite, Odoo, Cin7 Core, Unleashed or your own | That accounting app | The platform’s list of connectors |
| Review queue | Designed around your team and rules | The app’s own review screen | The platform’s screen |
| Time to start | A demo on your documents, then a scoped build | Same day | Days to weeks of setup |
| Who owns it | You: code, rules and logs | You subscribe | You subscribe |
| Who supports it | The team that built it, if you choose | The vendor’s help desk | The vendor, plus whoever set it up |
Built-in capture example: Xero smart document capture. Rented IDP platform examples: ABBYY Vantage and Nanonets.
OCR software, Google Document AI or a custom intake agent: which do you need?
Plain OCR software turns a scan into searchable text. That suits an archive of old dockets you want to search by PO number. It cannot tell you which number on the page is the PO number.
The cloud services add AI OCR on top. AWS says Amazon Textract extracts printed text, handwriting, layout elements and data from documents. Google lists OCR and a Form Parser inside Document AI. Microsoft describes Azure AI Document Intelligence as an OCR and intelligent document processing service. All three are building blocks for developers. None of them knows your customers, item codes or price lists.
A custom intake agent uses one of these readers for the PDF data extraction step. It then adds the part that belongs to your business: checks against your own records, a review queue built around your team, and a draft in Xero, MYOB or your ERP. We test two or three readers on a batch of your documents and pick one on measured field accuracy.
Invoice OCR for supplier bills is covered on our accounts payable automation page. Vendor descriptions on this page were read on 31 October 2026.
Do you need a custom intake agent at all?
Open the description closest to your situation. Sometimes the answer is a tool you already pay for.
Our pile is mostly receipts and supplier bills for Xero
Try built-in capture first. Xero’s smart document capture, Hubdoc or Dext may cover it. If you also need approval routing and tax invoice checks, see our accounts payable automation service.
Customers email us purchase orders in every layout imaginable
This is what an intake agent is for. Varied layouts, checks against item codes and price lists, and a sales order ready for approval in MYOB, NetSuite, Cin7 Core or Unleashed. This page is the right place.
Most of our orders already arrive through EDI or a marketplace connector
Keep what works. Structured feeds need no reading. An intake agent only earns its place on the documents that still arrive as PDFs, emails and scans alongside them.
We are not sure which paperwork costs us the most time
Start with advice. Our AI consulting service in Australia maps where the hours go and ranks the options before anything is built.
Application forms and delivery details are personal information. The build plans for that.
Trade account applications carry directors’ names and addresses. Orders from sole traders and delivery dockets carry names, phone numbers and home addresses. If your business is covered by the Privacy Act 1988, the Australian Privacy Principles apply to all of it, including while an AI model reads it.
APP 11 asks for reasonable steps to protect personal information, and to destroy or de-identify it once it is no longer needed. Since the 2024 amendment, APP 11.3 says those steps are both technical and organisational. The privacy questions in the FAQ below set out what that means for an intake agent.
If a document is sent to an AI model hosted overseas, that is usually a disclosure under APP 8: reasonable steps first, and your business stays accountable for what the overseas recipient does under section 16C. The OAIC’s AI guidance also warns against treating AI products as set and forget.
Sources: OAIC, APP 11 guidelines; OAIC, APP 8 guidelines; OAIC, privacy and commercially available AI products. This is general information, not legal advice.
- Only the pages and fields it needsthe rest masked before the model sees itAPP 11
- Encryption and named accesstechnical and organisational steps, writtenAPP 11.3
- Deletion schedule for copiesoriginals stay in your systemAPP 11
- Where each document is processedAustralian regions where availableAPP 8
- Business AI termsno training on your documentsOAIC
How much does AI document processing cost in Australia?
Flowtivity’s March 2026 Australian guide puts document processing and data entry builds at A$12,000 to A$30,000, taking 4 to 8 weeks. That is a market range, not our price, and the cost question in the FAQ adds a second guide and the GST caveat. FactoryJet quotes a fixed price per phase in writing after a short scoping call.
- Demo and scoping. We read a batch of your documents, show you the results and write a fixed-price plan.
- One document type, one system. For example, customer purchase orders into MYOB or NetSuite as sales orders held for approval.
- Several document types. Orders, dockets and applications sharing one review queue, one log and one set of privacy controls.
- Optional support. Changes quoted and approved one at a time, with no monthly minimum.
- Number of document typesBreadth
- Handwriting and poor scansReading
- Checks against your recordsRules
- Systems to file intoReach
- Sensitive information in the documentsPrivacy
- AI and hosting accountsYours, at cost
- Support after launchOptional
What ERP and document work has FactoryJet done?
Our ERP projects on Odoo, NetSuite, SAP Business One, ERPNext and custom systems have included RFQ automation, daily bookkeeping, and purchase and sales orders raised by software. Every one of them hinged on paperwork. A supplier quote request or a customer’s order had to be read correctly before the ERP could act on it.
We build Xero and HubSpot integrations. For Sow Easy we built a WooCommerce to Odoo integration, tested against Odoo’s staging system, with launch still ahead. FactoryJet has served more than 500 businesses.
The same service for US businesses, with US platforms and sources, is on our document intake AI agents page.
- OdooERP
- NetSuiteERP
- SAP Business OneERP
- ERPNext and custom ERPsERP
- XeroIntegrations
- HubSpotIntegrations
- WooCommerce to Odoo (Sow Easy)Integration
A worked example: purchase orders at a Victorian hardware wholesaler
This is an illustration of the kind of build we do, not a client case study.
A wholesaler supplies independent hardware stores across Victoria and southern New South Wales. Orders come by email as PDFs from store systems, as spreadsheets, and as phone photos of a handwritten order pad. Two people in customer service key them into MYOB as sale orders each morning, and both know which store uses old item codes.
The agent reads each order, maps old codes to current ones from a table the team keeps, checks every price against the store’s price list and prepares the sale order. Orders that pass every check go on one approval list. Orders from new stores, codes it cannot map, and prices off the list wait in the review queue with the original page attached. MYOB has no draft status, so nothing is created there until a person approves it.
The two coordinators start the day approving the checked list, which the agent then creates in MYOB as Open, then work through the held orders and call the stores that need a call. They still own every customer relationship. What changes is how much of the morning goes on typing.
AI document processing: questions Australian businesses ask
Q01What is AI document processing?
It is software that takes a document your business receives, such as a customer purchase order, a delivery docket or an application form, works out what kind of document it is, pulls out the fields you care about and puts them into your system. The AI part is what lets it cope with layouts it has never seen and messy scans. A person still checks anything the software is unsure of.
Q02Is intelligent document processing AI?
Yes. Intelligent document processing, usually shortened to IDP, is the industry name for document reading that uses AI rather than fixed templates. Older tools needed a template drawn for every supplier or customer layout. IDP uses machine learning, and now large language models, to find a PO number or a delivery address wherever it sits on the page. The name sounds grand. The job is reading paperwork accurately and saying when it is not sure.
Q03What’s the difference between OCR and IDP?
Optical character recognition (OCR) converts a scanned image into characters a computer can search. It can hand you every word on a delivery docket and still have no idea which one is the PO number. IDP goes further: it decides that one number is the order total and another is an ABN, checks them, and maps them to fields in your system. Most IDP systems use OCR as their first step. OCR alone suits searchable archives. IDP suits documents that must become records.
Q04Some customers still order with old item codes. Can the agent cope?
Yes, if your team keeps a mapping table of old codes to current ones. The agent looks up each code on the order, swaps in the current code it maps to, and shows both on the draft so a person can see the change. A code with no match in the table is never guessed. The order waits in the review queue, and once your team adds that code to the table, the next order with it goes through.
Q05Which AI is best for document processing?
No single model wins for every document. Amazon Textract, Google Document AI and Azure AI Document Intelligence are cloud reading services built for text, forms and tables. General models from OpenAI, Anthropic and Google cope well with messy layouts and free text. We test the options against a batch of your real paperwork and choose on measured accuracy and where the data is processed. A delivery docket may need a different reader from a credit application.
Amazon Textract ↗ Google Document AI overview ↗ Azure AI Document Intelligence overview ↗
Q06Can ChatGPT read a PDF and do our data entry?
It can read many PDFs well, and it is a good way to see what AI makes of your paperwork. It is a poor home for the real job. Someone still has to upload each file, check the answer and type it into your system. The OAIC also recommends, as best practice, keeping personal information out of publicly available generative AI tools. A business intake agent runs on business terms and files into your system with a log.
Q07Can it read scanned PDFs, phone photos and handwriting?
Scans and phone photos, yes, within limits: blur, glare and cut-off edges lower accuracy, so the agent scores image quality and sends poor copies to a person. Printed handwriting on forms is often readable. Joined cursive, signatures and ticks squeezed into margins are less reliable. We test your worst real examples during scoping, so you know before the build which documents the agent can take and which stay with your team.
Q08Doesn’t Xero already read documents by itself?
Partly. Xero’s smart document capture reads documents sent to Xero by email, app or upload and has the details ready for review. Xero’s July 2026 post names receipts, bills and statements, and says the feature is rolling out in beta in Australia and New Zealand. If your documents are bills and receipts for Xero, try it first. A custom agent fits documents Xero does not handle, such as customer orders, forms or dockets.
Q09Xero smart document capture, Hubdoc or Dext: which should we use?
For bookkeeping paperwork, start with what you already pay for. Xero says smart document capture is on all its small business plans, with basic extraction on Grow. On 31 October 2026, Xero’s Australian Hubdoc page redirected to that capture page. Dext calls itself a bookkeeping automation platform for receipts, invoices and business documents, and links to Xero, QuickBooks Online and Sage. A custom agent fits orders, dockets and forms bound for an ERP.
Q10Can an agent turn emailed purchase orders into sales orders in MYOB?
Yes. MYOB’s Business API works with AccountRight, new Essentials and MYOB Business files, and its Sale Order endpoint takes new orders with a status of Open or ConvertedToInvoice. There is no draft status, so an Open order is live. The agent reads the customer’s PDF, matches the customer and each item code, checks the price against your list and holds the order in its review queue. Only when a person approves it does the agent create it in MYOB as Open.
Q11Which ERPs and inventory systems can it file into?
Any system that lets outside software create a record through an API or a supported import. In Australia that usually means Xero, MYOB Business or AccountRight, MYOB Acumatica, NetSuite, Odoo, QuickBooks Online, Cin7 Core or Unleashed. Our own ERP work spans Odoo, NetSuite, SAP Business One, ERPNext and custom ERPs. Before any build we name the exact record type your system accepts from outside software, and ask whether a sandbox copy exists so testing never touches live books.
Q12Can the agent handle Peppol eInvoices?
It does not need to read them. A Peppol eInvoice arrives as structured data, not a picture, so it can go straight into the system with a few checks. Australia’s Peppol Authority is the ATO, according to OpenPeppol’s list. Our agent treats Peppol documents as a clean lane and spends its reading effort on the PDFs, scans and emails that still arrive from customers and suppliers who are not on the network.
Q13Can it check an ABN on an application form?
Yes. The Australian Business Register offers ABN Lookup web services so software can validate an ABN and pre-fill details on forms. Access is free after registration, which gives you a GUID key. On a trade account or credit application, the agent reads the ABN and business name, checks them against ABN Lookup and flags any mismatch for your credit team, so a typo or a wrong entity is caught before the account opens.
Q14How accurate is AI document processing?
It depends on your documents, so ignore any vendor’s headline figure. Clean, typed orders from regular customers read close to perfectly. Faxed dockets and handwritten forms do not. We measure accuracy field by field on a batch your team has already processed, then set a bar for each field. Fields that clear the bar flow through as drafts. Fields that fall short go to a person, so a low score slows things down rather than filing a wrong record.
Q15What happens when the agent is unsure?
It stops and asks. The document lands in a review queue with the unsure fields highlighted beside the original page, and a person corrects or confirms them in a few clicks. The agent also stops when a check fails: an unknown customer, an item code that does not exist, a price outside your list or a total that does not add up. Every correction is logged, which tells us where to tighten the rules.
Q16Do we have to train the AI on our paperwork first?
No months-long training project is involved. Current models already read most business documents well. What the agent needs is your rules: which fields matter, what counts as a valid order, which checks to run against your system and who reviews what. We write those rules with your team and test them on a few hundred past documents. Your documents are not used to train anyone’s public model.
Q17Does the Privacy Act apply to documents the agent reads?
If your business is covered by the Privacy Act 1988 and the documents hold personal information, yes. Application forms, sole trader orders and delivery details often do. APP 11 requires reasonable steps to protect that information, and since the Privacy and Other Legislation Amendment Act 2024, the OAIC says those steps include both technical and organisational measures. For example, the agent gets its own login, and that login can open only the inboxes and folders the job needs.
Q18Can our documents stay in Australia?
Often, yes. The agent’s own code, storage and logs can run in an Australian cloud region in your account. Some AI models are only offered from overseas regions. Under APP 8, before personal information goes to an overseas recipient you must take reasonable steps to make sure it does not breach the APPs, and you remain accountable for what that recipient does. We show you where each document travels before the build starts.
Q19Is our data used to train AI models?
Not on the setups we build. We use AI providers on business or API terms that exclude customer data from model training, and we record which provider processes which document type. The OAIC’s guidance says privacy obligations apply to personal information put into an AI system and to output that contains it, so we pass the model only the pages and fields it needs, and mask what it does not.
Q20How much does AI document processing cost in Australia?
Flowtivity’s March 2026 Australian guide puts document processing and data entry builds at A$12,000 to A$30,000, over 4 to 8 weeks. Web Video Digital’s August 2026 guide puts custom AI agents generally at A$15,000 to A$150,000. Neither guide says whether GST is included, so ask any vendor to quote ex GST. These are market ranges, not our prices. FactoryJet quotes a fixed price in writing after a short scoping call.
Flowtivity, Australian AI agent pricing (Mar 2026) ↗ Web Video Digital, AI agent cost (Aug 2026) ↗
Q21How long does it take to build a document intake agent?
Flowtivity’s Australian guide puts document processing builds at 4 to 8 weeks, which matches the shape of our projects: about a week to collect samples and write rules, then building, testing on past documents and a supervised pilot. One document type into one system sits at the short end. Several document types, a review queue and an ERP with no test copy sit at the long end. We confirm the plan after scoping.
Q22Can we see it working on our documents before we sign?
Yes, and that is how we prefer to start. You send a batch of documents your team has already processed, an early version of the agent reads them, and you compare its fields with what your team entered, unsure fields included. If a tool you already have, such as Xero’s built-in capture, would cover your job, we tell you then. You decide whether to go ahead with real results in front of you.
Q23Who owns the agent, and who looks after it?
You own the code, the rules, the test documents and the logs from day one, and the AI and hosting accounts can sit in your name at cost with no markup. Defects are fixed inside the build price for a cover period agreed before work starts. Support after that is optional. Each change is quoted and approved before we do it, with no monthly minimum, and we can keep managing the servers, models and connections if you want us to.
Q24What should we send you to get a quote?
A short brief is enough, and an RFP is welcome. Tell us which documents arrive, roughly how many a week, where they come from (inbox, portal, scanner, courier app), which system they must end up in, and who checks them today. Attach five to ten real examples, with personal details blacked out if you prefer. From that we can say whether the job suits an agent and give you a fixed price per phase.
See the agent read your own orders, dockets and forms
Send your name and work email. The founder replies within 24 hours to arrange a demo on a batch of your documents and a short call about the system they need to end up in. No spam, no obligation.