Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
12 contributions to Construction Contractors Hub
AI agents are here but where are they best used
In the last couple of months AI players have been releasing their version of what a true agent style interface looks like. Grok Bot, Muse, Dots, Hermes and soon Duet from Anthropic. I went into more details in the video on how each perform and which one will be best for who. My main point is also that these are great for their running around tasks like picking up items that are coming up due in registers, reminders on tasks you promised in a meeting and that ad-hoc admin tasks. Work like extracting trade packages, reviewing contracts and line item pricing all still belong using skills in Claude Cowork or ChatGPT Work. You want reliable results where you know what the AI has done so you can review the output before carrying on. I'm interested in how you all are using these agents and whether it has changed much for the way you work?
1 like • 14d
Good question, Josh — the admin uses you named are real, and they're a good place to start. But if I had to pick the one spot an agent actually pays for itself for a contractor, it's the phone. Every missed call is a job that just rang your competitor. Ours answers every call, sorts out whether it's a prospect, a client, a vendor or a tech, books the appointment and logs it to the CRM — nights and weekends included. The trick is keeping the job narrow: answer, qualify, book, log. One mega-agent that does everything starts inventing answers. Here's how that missed-call flow looks in practice: https://myzoqena.com/demo?utm_source=skool&utm_medium=community&utm_campaign=missed-call Admin agents save you time. A phone agent saves you jobs.
AI in Sub-Contractor Management
I've been working on an AI-assisted subcontractor management system. It starts with the signed subcontract and agreed scope, budget and programme. Basically after procurement is done and you have locked in the sub-contractor. From there, we have each step in the process and some small, discrete Claude skills that you run to support each process. We also have a library of business templates and project information that sits behind them. Setup and mobilisation: summarise obligations, build a checklist for documents and site readiness, and agree how progress will be reported. Delivery: check performance against the plan, review payment claims against verified progress, assess variations and draft notices. For variations, check entitlement first, then price and time. This Close-out: check the final account and handover requirements, then record lessons learned and subcontractor performance for future projects. The system combines organised project records, shared business information and reusable AI workflows that you customise to your processes. Check out the walk-through: https://youtu.be/04Vw2WqI2dE
0 likes • 15d
Ty — from the sub side, the part of Tim's mobilization step that saves the most time is having one pack ready before day one: signed subcontract and scope, licenses, and a COI checked against the contract, not just on file. The COI is the one that usually holds up a start: wrong entity name, limits below the contract, or an expiry that runs out mid-job. Check the name, limits, additional insured wording, and expiry before you mobilize, and put the renewal date on your calendar. This is a clear rundown of what a COI should show: https://zoqena.com/resources/what-is-a-coi?utm_source=skool&utm_medium=community&utm_campaign=coi Get that pack right once and the rest of the system Tim described runs a lot smoother.
Sold my first project…help!
Hi all, This is a great community. I just sold my first project, an AI phone assistant who will take calls, gather information, answer questions, and schedule appointments. I’ve used ChatGPT and Claude to plan out this project. But I still have two important questions for this great community. 1) What should I charge for this first project? If it goes well, it could lead to several others with the same Contractor. 2) For any of you who have built something similar, what tech stack did you deploy? Thank you.
0 likes • 17d
Hi Andrew, congrats on the first sale — and good call measuring appointments booked and attended, not just calls answered. One piece that helped our contractor clients: keep the original inquiry linked all the way through booking, the scope visit, and the quote, so that weekly review shows where people drop off. And for calls that miss the assistant or come in after hours, an instant text-back that captures name, number, job, and service area — logged the same minute — turns callbacks into a list someone actually works through. Here is how that missed-call flow looks in practice: https://myzoqena.com/demo?utm_source=skool&utm_medium=community&utm_campaign=missed-call Happy to share what we test first on a new build if that helps.
I built an AI phone system that answers, qualifies & logs every call automatically — here's the exact stack 👇
Most construction & contracting businesses lose leads in the gap between the phone ring and the CRM. Customer calls → nobody answers → no record → ghost. Rep answers → forgets to log → same result. If you're missing 3–5 calls/day at $500–$2,000/job — that's $1,500–$10,000 walking out the door. Daily. Here's the stack that closes that gap completely: 📞 VAPI — AI voice agent handles inbound AND outbound calls 🎤 ElevenLabs — gives the AI a voice that actually sounds human ⚙️ Make.com — automation layer that captures + routes all call data 📊 Google Sheets — real-time log: name, number, job type, urgency — every call 🏗️ GHL — creates the contact + fires the follow-up sequence instantly How it works in 4 steps: 1️⃣ Homeowner or GC calls → VAPI AI answers instantly (ElevenLabs voice, sounds human) 2️⃣ Agent collects: job type, timeline, budget, contact details 3️⃣ Call ends → Make.com fires automatically 4️⃣ Data hits Google Sheets + GHL contact created + follow-up SMS out in 60 seconds For outbound: same stack, reversed. AI dials your estimate follow-up list, qualifies leads, logs every response. Zero missed jobs (AI answers after hours, weekends, no exceptions) Zero logging errors (automation, not memory) Zero follow-up delays (triggered the second the call ends) The real win? Every missed call becomes a trackable data point — not a lost job. What's the biggest gap in how your business handles inbound calls right now?
0 likes • 17d
Hi Liton, thanks for sharing the stack. The biggest gap I see most often is not the answering itself, it's what happens right after the call ends: nobody logs it, and there's no owner or callback time, so it quietly becomes a lost job — especially after hours and on weekends. What closes that gap is keeping it simple: every missed call gets an instant text-back, capture the name, number, job type, and timeline, log it to the CRM right away, and give it one owner with a callback time. That turns a missed call into a trackable follow-up instead of a guess. Here's how we set that up: https://myzoqena.com/demo?utm_source=skool&utm_medium=community&utm_campaign=missed-call
Building an AI tool to stop subs from getting held up by COIs, need your input"
Hi everyone I'm Ameet, I'm not a contractor. I'm a builder. I've spent the last few months talking to subs and GCs about one specific problem: why subs keep getting held up on mobilization because their insurance certificate bounces. Here's what I keep hearing: - Subs send the cert. GC says it's wrong. Nobody explains why. - The sub asks their broker. Broker says it's fine. GC says it's not. - This goes back and forth for weeks. The sub loses money. The GC loses time. I'm building an AI tool that reads the GC's requirements, checks the cert before the sub sends it, and tells them: ✅ This will pass ⚠️ Fix this first (with plain English instructions) 🚫 This won't pass — escalate now I'm not here to sell anything. I'm here to make sure I'm solving the right problem before I build the wrong thing. For the subs here: what's the most frustrating part of the COI process? What costs you the most? For the GCs: what do you wish subs would just get right the first time? Any feedback would be massively helpful.
0 likes • 24d
Good question, Ameet. From the contractor side, the bounce loop you describe almost always has one root cause: the sub's broker never saw the GC's actual requirements. The fix that ends most of the back-and-forth is boring but effective — publish your COI acceptance checklist once (limits, additional insured wording, waiver of subrogation, cancellation notice) and attach it to the contract, so the first cert is usually the last one. The other silent killer is expirations: policies lapse mid-job and nobody notices until the GC needs the cert at mobilization. A single shared tracker with a 30-day renewal nudge to the sub and broker wipes that out. Here's how we think about vendor compliance on our side: https://zoqena.com?utm_source=skool&utm_medium=community&utm_campaign=coi
1-10 of 12
Kentus ZOQENA team
1
1 point to level up
@kentus-zoqena-team-6775
ZOQENA — vendor compliance software. I help property managers and contractors stay on top of COI paperwork. Here to learn.

Active 5h ago
Joined Oct 4, 2026
Hawthorne, CA
Powered by