Burning through usage always sucks and not getting high quality answers suck too. They often go hand in hand and here is a quick video on how to get more out of your usage while also increasing the accuracy of answers on a Cowork project. Grab the skills in https://www.skool.com/contractor-os/about

"WhatsApp is the most successful construction technology tool ever built." — Prakash Senghani, CEO of Navatech https://www.instagram.com/p/DZXQ8rLFaij/

I'm keen to hear who everybody is, and what their goals are I assume you already know who I am. But if you don't I'm Tim. I worked for 8 years for big contractors on road, rail, renewable energy projects. I've always worked for head-contractors. I recently worked for some smaller contractors as a consultant when I left my job doing estimating and contract management. It was good, but I found it hard to see a path to scale (other than just starting a contracting business myself) So I instead decided to build software, and found that that's 100x harder than I thought and a very easy way to lose money

I've been experimenting with some different architectures for a construction site diary. If you aren't familiar with the concept, the site diary is one of the most important construction tools. You basically document everything that happens on site: who did what and how much work you got done each day. Then you use the data to feed your project control system. It also makes incredibly powerful evidence for any construction claims In this video I outlined a simple architecture using Airtable as the database, Claude and Claude dispatch for updating the diary, and WhatsApp for tracking project correspondence and tasks

Been heads down building out our full back-office automation stack at Ferguson Brothers and figured I'd share what's actually running (and what's still in progress). The three streams I'm working on: Stream 1 — Field time cards → productivity metrics Crew submits time cards in the field → routes into Notion → mapped against our cost code unit table → surfaces productivity rates by trade/task. Goal is to know our actual labour productivity so I can estimate from real numbers, not guesswork. Stream 2 — Billable receipts → job costing Any receipt that belongs on a job goes through a shared Google Drive folder structure (one folder per job) → automatically routed into JobTread as a cost → tagged and coded → shows up in the budget instantly. No more manual entry at end of week. Stream 3 — Overhead receipts → QBO direct Company expenses (materials, tools, subs that aren't job-specific) bypass JobTread and go straight to QuickBooks. Keeps the books clean without cluttering job records. The backbone of all three is Claude + JobTread MCP — Claude has live read/write access to JobTread so I can query job data, build estimates, review budgets, and push records without switching screens. Still building but the architecture is pretty much locked. Happy to go deeper on any of it. What are you building? (written with the help, guidance and tutelage of Claude).