A Sunshine Coast builder and a construction software founder say the difference between surviving and scaling is not more leads, it is cost control, clear processes, and systems that reduce mistakes before they repeat.
When builders talk about growth, the conversation often drifts straight to marketing.
More leads. More enquiries. More website traffic. More sales.
But in today’s episode of The Good Builder Podcast, Az challenged that thinking with two guests who have seen what really breaks a building business: Sean Hewitt, a Stonewood Homes franchisee on the Sunshine Coast with experience across larger operations including Creation Homes, and Jake, founder of project management platform MyConstruct.
Their message was blunt. Many builders can build. What they cannot do, at least not without help, is run a scalable business.
And no software, no matter how slick, will save a builder who has not first fixed the foundations of how the business operates.
The real ceiling for small builders
Az opened with a familiar pattern in residential construction: a capable builder sits at two to five homes per year, wants to grow, and cannot work out why the business feels harder, not easier.
Hewitt’s answer was not about skill on site.
“For scaling a building company, it’s not because you don’t know how to build,” he said. “It’s scaling a business is putting the systems in place.”
In his view, most builders get stuck because the builder is the system. If they are not there, nothing moves.
That creates a business that cannot breathe. No holidays, no time off, no capacity to think strategically. Everything relies on one person making every decision.
Hewitt framed it with a simple stress test: if you cannot take a week off and the business still runs, you do not have the right systems and people in place.
The irony is that many builders interpret that chaos as a marketing problem, when it is actually an operating model problem.
Before you chase growth, know your costs
If there was one theme that kept resurfacing, it was cost visibility.
Hewitt argued that builders rarely fail because of one bad job. They fail because of repeat mistakes that compound across multiple projects.
“A builder doesn’t fail because they have one bad job,” he said. “A builder fails because of repeat mistakes, things that continue to cost you money, and you don’t realise those costs when you’re quoting the next job.”
That is why, in his view, the first discipline of scaling is simple: know what your last builds actually cost.
Not what you thought they would cost at contract signing.
Not what the spreadsheet said before invoices landed.
The real cost, including variations, call backs, late invoices, defects, and the hidden time drains that never make it into a neat line item.
Both Hewitt and Jake highlighted the delay between construction activity and cost clarity. Invoices run on payment terms. Issues surface after handover. Supervisors buy small items ad hoc. The financial truth of a job can take months to settle.
Without a tight loop between what happened on site and what gets priced into the next job, the builder keeps underquoting the same risks.
The silent killer: untracked “little” spending
The podcast dug into what many builders quietly accept as normal: the thousands of small purchases that never get properly tracked.
Jake described the old world: supervisors with an order book, a company card, and a quick run to Bunnings for glue, fixings, or last minute materials. It feels minor, until it becomes a habit.
The problem is not one tube of adhesive. It is that those costs do not reliably find their way back to the job, or back to the estimating database, or back into decision making.
Hewitt connected it to a broader idea: waste is not just physical, it is time. A supervisor driving to a trade store is labour cost. The site pausing while someone sources missing materials is programme cost. The fix at the end becomes a defect cost.
Even when the business “owns” the leftover material, it is often a false comfort. Stock piles build up, storage becomes a headache, and eventually much of it ends up in a skip anyway.
Excel works, until it does not
For builders still running jobs on spreadsheets, Jake did not dismiss it. He said Excel can work, but only if the person running it is meticulous.
Once the business grows, spreadsheets become fragile. Formulas break. Jobs get duplicated. Files corrupt. Multiple people edit the same document. A reporting error can sit unnoticed while the business makes decisions based on the wrong picture.
Jake said he regularly sees builders compare system reports to their spreadsheet, convinced the software must be wrong, only to discover the Excel formula was the issue.
In other words, the business believed it was doing better or worse than reality, based on human error.
If scaling is about removing single points of failure, spreadsheets often become one of them.
Software is not a cure, it is a tool
Az pressed a key question: what do builders misunderstand about software?
Jake’s response was clear: software does not fix chaos. It digitises it.
Many builders buy a platform, hand out logins, and expect it to transform the business. Others have been burned by tools that require the builder to change everything to match the product, rather than the product adapting to the builder’s process.
The lesson from Jake’s side of the industry is that adoption matters as much as features. Onboarding matters. Training matters. Using the system consistently matters.
The platform is only as strong as the process wrapped around it.
He compared it to buying a nail gun and assuming that means you can build a deck. The tool is powerful, but it still needs a skilled operator and a plan.
The “Wednesday meeting” problem
One of the most practical insights came from Jake’s experience watching a builder grow: the cost of coordination.
In his earlier years, job progress was managed through weekly workflow meetings with department heads, whiteboards, paper files, and manual updates. The wage cost of those meetings alone becomes significant, especially as the business grows.
The breakthrough, he said, was moving progress visibility into a live dashboard where everyone could see job status without needing to sit in a room for hours.
That shift is not glamorous, but it is a turning point for scale. It reduces time spent chasing updates, reduces micromanagement, and gives leaders a clearer line of sight over many jobs at once.
Jake also pointed to client portals as a major pressure release valve. When clients can log in to see progress photos, updates, and documents, the business receives fewer repeat phone calls asking what is happening.
It also changes the relationship dynamic. Information becomes proactive, not reactive.
Hewitt acknowledged the risk of the “spicy client” with free time on the weekend, but still argued the portal keeps the conversation where it belongs, inside the project record, not on social media.
Quality assurance is cheaper than rework
The conversation also tied systems back to quality, and quality back to money.
Hewitt spoke about inspection and test plans and locking progress steps until the right evidence is captured. In practical terms, it is about ensuring the frame is right before it gets lined, because once it is covered, it is expensive to fix.
The same logic applied to stage claims. Hewitt said he shares standards and tolerances with clients early, defines what each stage means, and aligns payment claims to real progress, not cash pressure.
His goal is to build trust, reduce disputes, and prevent the common scenario where a builder pushes a claim and the client feels blindsided.
For Hewitt, transparency is not a moral position alone. It is an operational strategy. Trust reduces friction, and friction costs time.
Standard plans should get smarter, not just faster
As the discussion turned to volume, the guests raised a point that many builders miss: repeating a plan should not just speed up production, it should improve accuracy.
If a business has built the same plan 20 times, it should know the patterns. Where quantities run short. Where trades make the same mistake. Where a product choice leads to defects or call backs.
Yet many builders do not leverage that historical data properly. The business repeats the build, but repeats the same avoidable errors too.
Jake described situations where leftover materials shift between sites, batching becomes messy, and it becomes cheaper to throw materials away than to manage them properly.
That is not just waste. It is margin.
Growth without ego
Perhaps the most constructive note in the episode was about culture.
Hewitt spoke positively about builders sharing openly with one another without ego, even when they operate at different scales. The premise is simple: there is enough work, but not enough tolerance for poor systems, poor communication, and poor cost control.
In that environment, learning becomes a competitive advantage.
Hewitt’s approach to growth sounded less like chasing volume and more like building a business that lasts: hiring at the right time, supporting staff with tools and clear processes, protecting culture, and aiming to be the most recommended builder in his market, not necessarily the biggest.
It is a different definition of success, and one that reflects the reality of today’s building environment: reputation travels fast, and so do mistakes.
The takeaway for builders
The episode landed on a practical truth that builders across Australia will recognise.
Marketing might fill the pipeline, but systems determine whether the business survives the work.
If builders want to scale from a handful of homes to 10, 20, or more per year, the priority order matters:
- Know your real costs, not your assumptions
- Reduce repeat mistakes through process and accountability
- Put systems in place so the business runs without the owner holding everything together
- Use software as an enabler, not a crutch
- Build trust with clients through transparency and consistent communication
Or, as the guests implied throughout, the fastest way to go backwards is to grow a business that looks busy but is bleeding quietly behind the scenes.
Author: TGB Editorial
0 Comments