About VariationFlow
Why I built VariationFlow
I got tired of watching good companies do the work and not get paid for it. This is the tool I wished they’d had.
The same thing kept happening
A subcontractor does the work — does it well, does it on time — and then loses a fortune at the back end. Not because the job was bad. Because a variation never got priced. A verbal instruction never got recorded. A deadline in the contract quietly passed and nobody clocked it.
The money was earned. It just wasn’t evidenced.
What made it maddening is how avoidable it all was. The people losing out were the ones actually doing the building — and the fix wasn’t working harder or arguing better. It was capturing what happened, when it happened, in a way nobody could dispute later.
So I built VariationFlow: your team captures a variation on site in about a minute — photo, location, timestamp, signature — and the system chases it all the way to payment, watching the Security of Payment deadlines for you along the way. Its sister product, QA Flow, does the same for quality: inspections, NCRs and sign-offs on the same projects, in the same tamper-evident record.
The whole mission fits in one sentence: you did the work, so you should get paid for it. Every penny.
What the product believes
Every design decision in VariationFlow comes back to one of these.
Evidence beats memory
Six weeks after the event, a photo with a location stamp and a signature wins the argument that a recollection loses. So capture has to happen on site, in the moment — and take less than a minute, or nobody will do it.
The contract clock is real
Being right doesn’t help if you were late. Software should watch every deadline on every job, because no human can hold a dozen contract clocks in their head.
A record nobody can quietly rewrite
An evidence trail is only worth something if it’s tamper-evident. Every event in VariationFlow is timestamped, append-only and hash-chained — which is exactly what makes it hold up when money is disputed.
I watched good firms do the work and lose the money — not to bad workmanship, to missing paperwork. ‘Recover revenue, protect margin’ isn’t marketing to me. It’s the thing I needed and couldn’t buy.
I read every support email and take the demos myself. If any of this sounds like your business, come and say hello.
Built for the long haul
You did the work. Get paid for it.
See it on your own projects — a 20-minute demo built around your contracts, taken by me.