Mata.Works / scoped pilot
Job Closeout Draft
Turn field notes into a customer update someone can approve.
An alarm-system installer records the work, but the customer's invoice only says 'completed.' The office still needs to explain what was done and what is waiting.
Try it / fictional jobs
A clearer last message.
Choose a team note, prepare its sample recap, and edit the draft before approving it. These prepared examples show the review flow; this demo does not call an AI service.
No account needed. This sample stays in your browser and resets when you leave. Use made-up details only.
Team's note
Check the recorded work and the next step. Add a price or warranty promise only when an approved record supports it.
Before you commit
What the first version would include.
- You bring
- Five team notes and the customer updates you wish they had produced. Remove personal details before sharing examples.
- We deliver
- A draft recap with work done, checks recorded, open items, and a review step before sending.
- We check together
- Count drafts accepted, edits needed, and unsupported claims caught during review.
- You approve
- The scope, delivery schedule, build price, ongoing Care, and expected provider costs before work starts.
The pilot has a written quote. Provider entry prices in the guide cover the tools only; your build and Care are separate.
See an example of the complete bill →Technical approach and providers
Gemini for transcription and drafting; Supabase for the approval queue; Railway for the workflow; Twilio if approved recaps go by text.
We confirm compatibility with your systems, required access, and the provider costs in your proposal before building.
Go deeper
Read the plan. Hear the conversation.
The installer or office reviewer checks the draft. It must not invent test results, monitoring status, prices, or guarantees.