The prompts and skill downloads live here. When you are ready, text us and we will build the brain with you.
Not a seminar. A live build of how a company brain works. You leave clearer on what is possible, with first documents, first skills, and a company guideline. Then Scelta can build it with you.
Right now the day runs you. The goal is a company where every decision is backed by rationale.
Reaction, all day. Never the three things that actually move the company.
Pricing, process, people. None of it written anywhere. AI fails when that context is missing, not because it is incapable.
Just not to its potential. Someone on your team is already in ChatGPT or Claude with company data, whether leadership knows or not.
You’re not working for the AI. Now your AI is working for you.
Contractor or developer, you run the same six divisions - and each one is a stack of repeatable, document-heavy processes you already run every day. That is exactly the work AI thrives on - with a human in the loop.
An .md file. A text file. Simpler than a PDF or a Word doc, a notepad with headings, bullets, and bold. Nothing to buy. Nothing to install.
Change order - client moved a door on the south wall.
Ask AI for anything - a quote, a report, a schedule - and the answer is written in markdown first. Everything else is a conversion.
One process. One file.
Three parts. Every time. Start. Process. Output.
Ten per division. Your best people run them every single day.
Six divisions. Sixty buildables. One connected brain, with Claude at the center reading every file. Nothing lives in one person's head anymore.
If you do not set up these documents - these .md files as memories - every time you go back to AI, it forgets you.
Without a Brain
Like Adam Sandler in the movie: reintroducing yourself every morning because she has amnesia. That is AI with no company brain.
With a Brain
Everyone was blown away by Iron Man. The reason it worked: Jarvis knew who he was, what he needed, and could act for him.
This is not about buying one massive ERP. Plug in the tools you already run - and the brain reads them automatically.
If you do one thing with AI after this, record your meetings.
Ask anything about your jobs, crews, costs, and site activity
True cost per trade · job type · crew · smarter bids
Where time gets lost · which crews outperform · what kills margins
Real-time P&L · budget vs actual · change-order impact per job
Hours · location · photos · checklists · expenses · change orders · productivity
We built a skill that builds the brain with you. It interviews you like a colleague - what is your role, what do you actually do all day - then maps your divisions and writes the files.
The one prompt maps your company’s skeleton - divisions and processes only, no files. The skill builds the whole brain.
Sales. Marketing. Operations. Estimating. Field. Accounting. One Claude project per division, so the context stays with the work.
Instructions and reference files sit in the project. Chats are the jobs: named by job number and address, so Claude already knows the rules before you talk about Unit 2.
Same model as email, cloud storage, or any enterprise app. AI has a trained base knowledge - but it only gets your data through one of three doors:
A document, spreadsheet, or photo added to a conversation. Gone once the conversation ends, unless retention says otherwise.
Including things that should never be typed - passwords, SINs, banking details. This is the door most leaks happen through, because it feels like “just asking a question.”
Gmail, Drive, your CRM, your ERP. This is the door with the most reach - and the one access controls matter most for.
Your team is already using AI. Personal accounts. Company data in chats you cannot see. Context walking out the door. These three moves are how you take it back.
One page: what goes in, what never does. Passwords, SINs, banking details - never typed, never uploaded, on any tier.
One managed business account, not personal logins. Personal accounts can’t be governed - you can’t see or limit what’s connected.
On a business account, the vendor should not train on your chats or files - get that in writing. Then confirm how long they keep it and whether you can delete it.
That’s the right question - and it’s answerable, not a leap of faith. Once access is controlled at the door, the remaining question is what happens to data on the other side of it.
Where does it sit, and who can read it?
If something fails, what’s the recovery guarantee?
Where does it go once it leaves your hands - and does it come back?
An auditor watches the system operate over months, confirming controls hold up in practice, not just on paper.
The security management system itself: access granted and revoked, incidents handled, encryption at rest and in transit.
AI-specific governance, over the AI lifecycle specifically.
Your right to know what’s stored and request deletion; the bar for surviving a serious breach attempt.
Compliance teams whose job is saying no to unsafe vendors said yes to Claude. If it is safe enough for patient records and bank fraud systems, it is safe enough for job costing and daily logs.
On a business account, your chats and uploads are not used to train the model. They stay in your project. You can delete them. Claude reads what it needs to do the work, then writes back into your system.
Anthropic refused to waive rules on mass surveillance and autonomous weapons. A company that will say no to the U.S. military takes your data seriously too.
Copy this prompt. Paste it into whatever AI tool you’re already using. Swap in the vendor name. It pulls the trust center and hands you back plain answers to the doors and the certs above.
Pulls storage, backup, flow, training, retention, and current certifications from the vendor’s public trust docs.
Pick a division. This is what its first buildable looks like.
Six things. If you can repeat these, you know how a company brain works, and why Scelta should build yours with you.
You can start with one file. The brain gets built one file a week. Two ways to keep going with us.
AI for Contractors. Weekly live calls, the buildable library, and a room full of owners building the same brain you are.
We will map your company and build the brain with you. dmill@scelta.ca · 226 347 6758
CTO, Scelta
scelta.ca
AI for Contractors · AI for Developers
Weekly calls, buildable library, and the community that holds you to it.
Ask about security, the sixty files, the skill, or how Scelta builds a company brain with your team. Hard questions welcome.
