Variations agreed on site and forgotten in the invoice
A photo, a note and a price, captured at the moment the client says yes, would pay for itself on a single job.
For builders
Every builder has heard, "I thought we'd agreed that already."
Variations, snagging, photos and “we agreed that on Tuesday” still live in WhatsApp more often than they should. That is usually where a useful product starts.
Construction software has a habit of being written for offices. Builders need something that works with dirty thumbs, changing drawings and clients who decide things standing in a half-finished kitchen.
If you have a way of working that already keeps jobs moving — and a frustration that keeps breaking it — that is worth exploring before anyone mentions an app.
I help people in the trades look at those frustrations honestly: is this a product, a process change, or a tool that already exists?
Problems builders often mention
Snagging lists that multiply
Everyone has a different list. Closing a job becomes a negotiation instead of a walk-through.
Subcontractors who need the latest drawing, not last week’s
Version control sounds like office talk. On site it is the difference between building the right thing and ripping it out.
Quotes that cannot keep up with material prices
By the time a client decides, the numbers have moved. A clearer, faster quoting habit can matter more than a fancier website.
How we would look at it
A short, honest process. The aim is to decide whether the idea is worth pursuing — not to sell you a big project.
-
1
Share the problem
Tell me what you have noticed, who it affects, and how people handle it today.
-
2
Explore the idea
A short conversation. I will tell you honestly whether I think software is the right next step.
-
3
Discovery Workshop
If it is worth going further, we turn the idea into a practical plan before anyone writes a lot of code.
Questions builders often ask
If it needs everyone to change how they work, it probably will not stick. The ideas that work are usually a better version of something people already do — photos, notes, a list — not a new daily login.
Usually that is the better path. Replacing a whole system is expensive and slow. Filling a specific gap is how most useful products start.
The first step is a written description of the problem, then a short conversation if it looks like a fit. You should not need to write a business plan or learn any technical language.
Tell me about the problem on site.
Plain language is perfect. If the idea looks worth exploring, I will invite you to a short conversation.