TradeFlo
Build and test the workflow
Tested on your work before anyone relies on it.
We build AI workflows around the tools your team already uses.
Why does a new setup stop being used?
A tool was bought, set up once, and nobody in the office uses it now.
The spreadsheet works for one person. When they are off, the job waits.
Nobody agreed what finished meant, so the work never gets signed off.
From your examples to a tested workflow
The AI reads, drafts and flags. A named person approves each draft before anyone uses it. Every run is logged in your own systems: what came in, what the system did, and what it passed to a person for approval. We test the workflow on a normal job and an exception you supplied, then hand it over.
Your team to Us
A normal job and one that went wrong, private details removed.
AI workflow to The person who runs it
Test output, checked against what they would have done by hand.
Us to Your team
Handover notes, including what it does not do and who to ask.
You receive: A tested workflow, with handover notes for the people using it
The test your process owner accepts
Test run: ready for the process owner
- Normal job
- AI output matches the office's own version.
- Exception job
- Missing delivery date, flagged for a person to check
- Handover notes
- Written for the person who runs the process.
- Go-live
- Waiting for the process owner to accept the test
What we will ask you
Two past jobs: one that ran smoothly and one with an exception
The person who will use the workflow each day
What finished means to you, written down before we start
Who decides
The person who runs this process checks the test output against their own work. The workflow goes live once they accept it.
Before you start
Is this custom software development?
Yes, for the step your current tools do not cover. We build it around the systems you already run, test it on your own jobs and hand it over with notes your team or another supplier can work from.
Do you run user acceptance testing?
Yes. The person who runs the process checks the test output against their own work, and the workflow goes live only once they accept it.
What happens when the AI gets something wrong in testing?
We fix it and run the same job again, from the Microsoft 365 folders or Procore project agreed at Connect. The process owner decides when the output is good enough.
Who looks after the workflow after handover?
Your team, with the handover notes, or us under a support plan. You choose before the build starts.
Can we change the workflow later?
Yes. The notes say how it is set up, so your team or another supplier can change it.
Bring a job that went wrong.
We test every workflow on your exceptions, so start with the job that caused the most trouble.
Choose your region