Today I sat down with Jake at Double AA Roofing to get his company set up. We didn't open our app for the first ten minutes. Jake already used AI. When I asked what for, he said: "just to help me with emails rather than type out three or four paragraphs, or quotes." About a month in. One chat window. One job. That's where nearly everyone starts, and it's where nearly everyone stays. So before we set up anything of ours, we set up his properly. Four things, in this order. First, we turned off training. Settings, then Privacy, then switch off the toggle that lets your conversations improve their models. Jake's answer was immediate: "rather not." Do this before you paste a single customer name, price, or job number into anything. Two clicks, once, and you never think about it again. Then we got him out of the chat window. Every new chat starts from zero. It doesn't know your pricing, your customers, how you word a scope, or anything you told it last Tuesday. You re-explain your business every single time. A project fixes that. It's a folder that remembers. Anything you tell it, upload to it, or decide inside it is still there next week. We built Jake three: estimating, CRM, and customer communication. Every quote conversation now happens inside estimating. Over a few weeks that project learns his line items, his markup language, the way he writes a scope. The outputs get better because the context builds. In a plain chat it never does. Pick the three things you do most in a week. Those are your three projects. Then we stopped him typing. I asked Jake what actually slows him down. "Biggest pain is typing out an email." So we installed Whisper Flow. Hold one key, talk, and it types, then cleans up the grammar and cuts the filler. Works in email, in texts, in the AI, anywhere there's a cursor. It isn't our product and we don't make a dollar off it. You speak roughly four times faster than you type. I've been doing it long enough that I'm closer to eight. And it keeps score, so you don't have to take my word for it. By the end of our session it had us at 159 words a minute, 29 grammar fixes, and 12 dictionary corrections. That was one meeting.

This week we met with Scott. We showed him Scelta Extract, our AI-first field management platform and how he can use AI to generate his end of day report. The math: - Writing the report into his project management software usually takes 45 minutes. - With Claude + Extract, now it takes 5. - 40 minutes a day x 5 days is 200 minutes a week - 200 x 52 weeks is 10,400 minutes, so 173.33 hours - Assume a $50 rate, x 173 is $8,666.66 a year (rounded the cents) From just ONE daily workflow. Here's how it flowed: 1. We uploaded the template of his past end of day reports to Claude 2. He talked to AI about what happened that day 3. It generated the report and filled it in on his Extract app for him 4. We asked Claude to turn it into a skill 5. Now he runs the skill every day at the end of the day Pick one workflow you do everyday, turn it into a skill. The savings add up quickly.

Thank you to everyone who attended our London In Person Event today! Photo Gallery of the Day Most of what your company knows, scopes, pricing rules, job history, how you actually run a project, lives in people's heads or gets retyped into AI from scratch every time someone opens a new chat. A company brain fixes that. This session, recorded live at our in-person AI for Contractors event in London, showed contractors how to turn a single markdown file into a change order that Claude prices and drafts for signature the same day, instead of chasing free work after the fact. 🧠 What you'll learn: - How to break your company into divisions and turn each one into markdown files Claude can actually reference - A live example of a change order file, from trigger to price to signed approval - The three "doors" that control what an AI system can see, and how to lock them down - How to set up Claude projects so estimating, accounting, and marketing stay sandboxed - How the Claude-first extraction layer we built auto-sorts a 300-page drawing set into searchable titles The full recording is attached. Steal the change order file structure, swap in your own trigger and process, and you'll have your first working file by the end of the day. Presentation 📁 Resources mentioned: Claude: claude.ai Granola: granola.ai GitHub: github.com Want us to build this for you? Start with the End State Audit: scelta.ca/ai-for-contractors/audit

We built a skill that builds the brain with you. It interviews you like a colleague would: what is your role, what do you actually do all day, and then maps your divisions and writes the files. 1. Download the skill. One file, right from this page. 2. Drop it into Claude. Drag and drop, any conversation. 3. Answer the interview. Your role, your people, how work flows. 4. Tweak the map. It proposes your divisions and processes. You correct it. 5. It writes the brain. Every file, plus the index that links them. Or you can copy the prompt below. Happy Brain building everyone 💪 ___________________________________ "I just attended Scelta's Company Brain session. I want you to map the skeleton of my company brain. Do NOT create any files yet - this is mapping only. Interview me one question at a time, like a curious colleague. Start with: what is my role, and what do I actually do all day? Then work outward: what the company builds or sells, who does what, and how work actually flows from first phone call to final invoice to paid. As you learn, map my company into six divisions - Sales, Marketing, Operations, Accounting, Finance, Field. Under each, identify the repeatable processes I run (the 8-12 that matter most per division). For each process, note who owns it today and roughly how it starts, runs, and ends - but do not write any files. When the interview winds down, show me the full skeleton as a tree: divisions, then processes, flagging the ones that live only in someone's head. That list is what we will build into files later." ___________________________________