In construction, there’s always another estimate to review, client to update, document to chase, schedule to adjust, or project detail that needs your attention. When the business is smaller, it makes sense for the owner or project lead to stay close to everything. But as projects and responsibilities grow, those small tasks start adding up. And eventually, too much of the business depends on one person remembering what needs to happen next. That’s where having documented processes and the right support can make a real difference. Not everything needs to be automated. Not everything needs to be delegated. But recurring work that has a clear process behind it shouldn’t always have to come back to the same person. The best time to build that support is usually before things become chaotic. When you still have enough breathing room to document the process, define expectations, and decide what actually needs your involvement. The goal isn’t to remove the human element from the business. It’s to make sure the business can keep moving without the owner or project manager having to touch every single thing. If you’re starting to notice work repeatedly coming back to you, it may be worth looking at the process behind it before simply adding more to your own workload. 🙂

Google’s AI strategy makes a lot of sense, even though I don’t think Gemini is the best model yet. The ecosystem has a few layers: Workspace: Gmail, Drive, Calendar, Chat, Docs, Sheets, Slides, Forms and Sites. This is where your files, communication and project data live. Gemini and Workspace Intelligence put AI inside those tools and let it work across the same context. NotebookLM retrieves answers from a defined set of project information. Spark and Workspace Studio handle agents and automations. Canvas and Antigravity cover app prototypes and software development. For a contractor, Forms can collect site data, Sheets can hold registers, Drive can store the documents and Sites can display a dashboard. The AI sits across all of it. The limitation is model quality. In my experience, Gemini can be too brief and hallucinate more than Claude. I wouldn’t migrate just for the AI today. If you already use Google Workspace, though, the integration is very useful, provided you check every important output. Full walkthrough: https://youtu.be/E95eQFsaa9s

Something I’ve noticed after working with business owners across different industries is that the ones who eventually build something sustainable usually have one thing in common: They genuinely care about what they’re building. They care about their customers. They care about their reputation. They care about their team. And they care about getting the business right. But caring about the business doesn’t mean you should be the person handling every follow-up, admin task, customer message, or operational detail. That’s where a lot of good businesses get stuck. The owner becomes the person everyone depends on, even when systems and automation are already in place. I’ve always believed the right support isn’t about finding someone to simply “do tasks.” It’s about finding someone who can take ownership of the work and treat the business with the same level of care. Whether you’re building an eCom brand, growing a service business, or using AI to scale your operations, that human execution layer still matters. Systems create leverage. The right people make that leverage actually work. 💯

I hear a lot of confusion about the term “AI agent” in construction. To me, an agent pulls together a few different concepts: - Workflows that explain how to complete repeatable tasks - Context from your project documents, registers and correspondence - Memory about the project, your business and how you prefer to work - Tools and permissions that control what it can access and what actions it can take We then package this into an interface that we or our team can call when we need work done. The main difference between a workflow and an agent is responsibility. A workflow completes a defined task. An agent owns a narrow area of responsibility, chooses which workflows to run, checks the result and keeps a record of what it has done. Would I let an AI agent autonomously build a programme or send contractual notices? No. But I would let it monitor correspondence, identify a potential variation, update the register and draft a notice for review. That is where agents are useful today: bounded responsibilities, clear permissions and human approval. I explain the full model here: https://youtu.be/hnGixjVMD2g

A lot of founders want to scale, but scaling isn’t always about getting more clients or increasing revenue. Sometimes the real question is: can the business actually handle the growth? I’d look at these 4 things: 1. Can someone else deliver your core service without you? If everything still needs your involvement, you may have a business that depends on you rather than a business that can scale without you. 2. Do you actually know your numbers? Not just revenue. Know your margins, current costs, and what additional payroll or resources the business can realistically support. 3. Is there a repeatable way to bring in clients? If every new opportunity depends on the founder personally finding, selling, and following up with prospects, there’s a natural limit to how much the business can grow. 4. Can your current operation handle more volume? More customers won’t fix messy processes. They usually expose them faster. You don’t necessarily need everything perfect before scaling. But you should know where the weak points are and have a plan to address them. Which of these four would be the biggest bottleneck in your business right now? 🙂