By Greg Allan, tradesman and creator of Data First Coaching
Why does every dry run pull the renderer straight back onto the trowel?
Because render work is weather-gated, not owner-gated. The moment three clear days line up, the scaffold has to be used, the acrylic render or cement render has to go on, and the texture coat has to cure before the next front moves through, so the renderer grabs every billable hour personally rather than risk losing the window.
That squeeze is not laziness about admin. It is physics. Mixing, bagging, running the exterior in coats and watching curing time leaves no real gap in the day for quoting, for approving a builder's colour selection, or for chasing the patch repair someone asked about last week. The tools-time and the office-time are fighting for the same few dry hours, and the tools always win because the tools are time limited in a way admin is not.
Why does the quoting and colour admin pile up until the rain finally comes?
Because the good run and the quiet run are mirror images of the same problem. During the dry run the renderer is on scaffold from dawn to dusk, so quotes sit unsent, colour sign offs sit unanswered, and new enquiries go cold. When the weather finally turns, there is time to chase all of it, but no cash is coming in because nothing from the good run got locked in while it was fresh.
Then the next dry window opens, and the renderer is pulled straight back onto the tools before that chased-up work is actually booked. The cycle climbs and slides: busy on render, quiet on quoting, then busy again before the quoting ever turns into secured jobs. Left alone, that pattern repeats every time the weather does.
What number in the renderer's own data actually shows where this cycle starts?
Not a feeling about being busy. The number that tells the truth is how much of the working week the renderer personally spends on scaffold versus in front of a quote or a colour approval, tracked against the margin on jobs that got quoted properly versus the ones rushed out between coats.
A renderer working from memory usually believes the quiet weeks are the problem. Data first, the picture is often the opposite: the margin damage and the lost enquiries happen during the busy weeks, when quoting gets rushed or skipped altogether. That is the point where growth stalls, once the owner has a crew but is still spending most of the week back on the trowel covering a sick crew member, finishing a tricky bagging job, or chasing a weather window personally. Seeing that in the renderer's own numbers, rather than guessing, is what makes the fix land in the right place.
What changes when AI agents take on the quoting and colour follow-up?
An AI agent is software that does a piece of the job the way the renderer would do it themselves, using their own prices, their own wording and their own rules. For a renderer, that can mean a quote going out the same day it is asked for, or a colour selection being chased with a builder, even while the owner is up on scaffold mid texture coat.
That matters because it breaks the dependency on the quiet weeks to catch up. If AI agents are already following up quotes and colour sign offs while the dry run is happening, the renderer is not racing the rain to turn enquiries into booked work. The quoting and chasing keep moving on their own schedule, not the weather's.
How does building spare capacity in the crew change the next dry run?
Picture a renderer standing on scaffold mid texture coat, phone buzzing with a colour query from a builder and a new enquiry for a cladding job on a weatherboard exterior. With no spare capacity in the crew, that phone gets ignored until the render is on and cured. With a crew member free to pick up the next job's prep, mesh and sealer, the renderer can step down, check the margin on the new enquiry against the square metre rate it should sit at, and quote it properly before it goes cold.
That spare capacity has to exist before the dry run starts, not get found during it. A renderer who builds it in ahead of time can present a straightforward quote with a clear scope, come back with a better option covering patch and crack repair while they are there, and a best option that adds the cladding, then lock one of them in with a date on the calendar before the next rain arrives and the enquiry goes cold.
Is the next hire for a renderer another renderer, or something else?
Often it is not another set of hands on the trowel. As the crew grows, the admin wedge around the render work, scheduling scaffold access, ordering mesh and sealer, chasing colour sign off from builders and homeowners, keeps expanding to fill whatever time the owner is not personally on the tools.
The hire that actually breaks that ceiling is usually the second hire: someone with spare capacity to run that admin and scheduling load, not a second renderer doing exactly what the first one does. Without that hire, every extra crew member just creates more scaffold bookings, more colour approvals and more material orders for the owner to chase personally, which puts the renderer right back on the tools to keep up.
How does Data First Coaching approach this?
Data First Coaching starts from the renderer's own numbers, not from a general theory about busy tradies. Through the Trade Business Intelligence, Greg Allan looks at where the owner's hours are actually going week to week, which jobs are quoted properly and which are rushed between coats, and where the margin is quietly being lost during the busy runs rather than the quiet ones.
From there the coaching finds where the cycle really starts for that renderer, whether it is crew capacity, the admin wedge, or the quoting process itself, and works out what needs to change first. The how, including which agents to build and how the crew schedule gets set up, is worked through inside the Academy, with members, because the Academy is built for owners who are open minded, innovative and willing to share what they learn with each other.

