Every job your team closes leaves a record behind.
Repair visits, sales orders, building projects and support tickets each leave records in your systems. AI companies want the ones that show how the work turned out.
Four questions about your business. Nothing to upload.
Find your business and the records it keeps.
Each row names the records that business keeps and the question we'll ask about them on the first call.
| Business | Records it keeps | Systems |
|---|---|---|
| Field services | Call bookings, jobs, findings and photos, estimates, invoices and memberships. Which system do you use, and do notes and photos stay with each job? | |
| Construction | RFIs, official responses, change events, change orders and daily logs. Which project system do you use, and how many closed projects does it hold? | |
| Wholesale distribution | Sales orders, item fulfillments, return authorizations and credit memos. Which ERP do you run, and how far back do your orders go? | |
| Logistics and freight | Orders, bills of lading, proof of delivery, accessorial charges and invoices. Which transport system do you use, and do you track disputes as tickets? | |
| Manufacturing | Work orders, nonconformance reports, corrective actions and return authorizations. Which ERP or quality system do you use, and how many years of quality records does it keep? | |
| Office and customer teams | Support tickets, CRM history, project boards and code. Which of these does your team use, and since when? |
How one question about a drawing became a change order.
Follow one question through the records Procore keeps on a building project. The emails your team sent about it sit beside them.
One RFI on a building project
ExampleRFIProcore
A question about what a drawing means, with its cost and schedule impact.
Change eventProcore
Created from the RFI, with line items by cost code.
RFQ responseProcore
A subcontractor prices the change.
Prime potential change orderProcore
Drafted once the RFQ responses are in.
Prime contract change orderProcoreOutcome
The owner approves it, and the change joins the prime contract.
RFI emails Outlook or Gmail
Sent to the RFI's distribution list while the question was open.
Email and chat hold the reasons behind the work.
Somewhere in your inbox is the thread where your team worked out what to do about a damaged order. Messages like that explain why a job went the way it did. AI companies license email and chat so their models can learn that kind of reasoning.
If your team runs its work in a system we haven't shown, ask us.
A ticket tied to its order
ExampleTicketZendesk
Its external ID field holds the order number.
Sales orderNetSuite
The order the customer wrote in about.
What you can leave out.
- You can leave out HR files and direct messages.
- Records that belong to your clients go in only if you have the right to license them.
- If a customer contract limits some of your records, we point that out early.
- Anything else you name is left out too.
Ask us which records in your systems are worth licensing.
All we need to start is a list of the systems you run on. You won't need to export anything first.
Four questions about your business. Nothing to upload.
Prefer to write? Email hello@sixonepartners.com.