Getting-started guide
Claude, from a standing start.
You've installed the app. Over two sessions we make it genuinely useful for construction work, the kind of tool that saves you an hour before your first coffee.
Before anything
First: register. Then relax.
Scan this, give me your name, and everything in this session lands on your own pack page: the deck, the examples, the setup kit. It's already yours, so you don't need to take notes or photograph slides.
On your phone, or in the meeting chat:
stuart-training.pages.dev/s1
Three fields, ten seconds. You land straight on your pack page; bookmark it and put the phone down.
The plan
Two sessions, in order.
Set it up
Teach Claude who you are, your company and brand, and load the toolkit of skills. One-time. After this it knows your context every time you open it.
Work with it
The everyday loop: a project, your documents, a plain-English ask, a finished deliverable. Reviews, minutes, briefs, letters, trackers.
We're not touching code. This is Cowork: Claude doing knowledge work with you, on your files, in plain English. That's the whole game for now.
Plain English first
Two words worth knowing.
Cowork
Claude working alongside you on real files in a folder, reading a consultant's report, writing minutes, drafting a letter. Not a chat window you copy-paste out of. It opens your documents, does the work, and hands you a finished file.
Skills
Pre-built recipes for a specific job: "executive summary", "minutes of meeting", "commercial evaluation". You don't explain how each time. You say the trigger, Claude runs the recipe, out comes a properly formatted deliverable. We load a toolkit of them in session one.
Session 1
Part A
Set up your Claude.
Your very first Cowork project, call it "Claude Setup". Drop the pack in, and Claude interviews you, then builds your toolkit with you, skill by skill.
How the setup pack works
A project, a pack, a plan.
Start a Cowork project called "Claude Setup".
Unzip it in, say run the setup.
Who you are, your company, your brand. One pop-up at a time.
It recommends skills one by one, you say build or skip.
Nothing is bulk-copied. Claude proposes each skill, tells you what it does, and builds the ones you want around your brand, so you finish knowing exactly what's in your toolkit.
What the setup actually asks you
Four things, then you're live.
Who you are
Your role, how you like to work, how blunt you want it. Drop your CV in: Claude reads it and writes your profile so it never asks again.
Your company & brand
Company name, your logo, brand colours. This is what makes your spreadsheets and reports come out looking like your firm, not a template.
The skill build plan
Claude walks a recommended list, summaries, minutes, reviews, letters, trackers, bid evaluations, and asks skill by skill: build this one?
First-run brand prompts
The branded skills stay quiet until you first use one, then they pop up and ask for the detail they need. No huge form up front.
End of session one
What you'll walk away with.
- Claude knows you: your role and context load every time, no re-explaining.
- Your brand is baked in: deliverables come out in your company's look.
- A full toolkit installed: a dozen construction skills, one trigger phrase each.
- Nothing of mine leaks through: your outputs are yours, clean.
That's the boring-but-essential bit done once. Everything after is just using it.
Session 2
Part B
Working with Cowork.
The same loop every time, whatever the task. Learn it once on a document review, and every other job is the same shape.
The loop that never changes
Project → documents → ask → deliverable.
A folder for the job. Think of it as a site file.
Drop the drawings, reports, BOQs, emails in.
Say what you want in plain English.
A finished file, Word, Excel, PDF, back in the folder.
Master this on one task and you've mastered all of them. The shape is identical whether it's a bid evaluation or a chase email.
Workflow 1 · challenge a document
A consultant sends you a report.
The report, the letter, whatever landed in your inbox. Claude reads all of it.
Red flags, gaps, inconsistencies, and the questions you should be putting back to them.
The same findings, now a clean one-page brief with actions, owners and dates.
Executive summary.docxTwo skills, chained: document-review → executive-summary. You never named a skill. The trigger words did it.
Workflow 2 · after a meeting
You come out of a PTG with scribbled notes.
Bullet points, a voice-note transcript, a photo of the whiteboard.
A formatted MOM: attendees, decisions, actions.
Minutes of meeting.docxDistilled to prioritised actions and what's overdue: your pre-brief for next week.
Written in your voice, ready to send.
Chase emailready to sendFive skills, worked through
What each one does for you, in a real moment.
Executive summary
.docxA 40-page consultant report lands the night before a board update.
Say give me an ex summary for the board → one page: the decision, the risks, what you're recommending.
Minutes of meeting
.docxYou've just left a two-hour progress meeting with three pages of shorthand.
Say write up the minutes → a clean MOM: attendees, decisions, and an actions table with owners.
Document review
findingsA contractor's variation claim looks high but you can't see why.
Say review this, where's the padding? → red flags, gaps, and the questions to put back to them.
Commercial evaluation
.xlsxFour bids are in on different bases and you need a recommendation.
Say level these bids → a like-for-like comparison, variances flagged, ranked with a call.
Formal letter
.docxA consultant has missed a contractual deadline and it needs to be on record.
Say draft a formal letter on this → letterhead, reference number, the right firm but measured tone.
Your daily ten
The skills you'll actually reach for.
| When you need to… | Say something like | You get |
|---|---|---|
| Turn a mess into a decision brief | give me an ex summary | One-page brief, Word |
| Write up a meeting | write up the minutes | Formatted MOM, Word |
| Know what to chase next | distil the MOM | Prioritised actions + pre-brief |
| Pressure-test a consultant's doc | review this | Red flags, gaps, questions |
| Chase or escalate | draft an email to… | Email in your voice |
| Send a formal / contractual letter | draft a formal letter | Letterhead .docx |
| Score technical bids | evaluate the proposals | Weighted proposal review |
| Level & rank bid pricing | level the bids | Commercial evaluation, Excel |
| Stand up procurement tracking | procurement tracker for… | Back-planned tracker, Excel |
| Build the monthly report | build the monthly for… | Interactive dashboard |
The full toolkit
Everything in the box.
Core daily
- Executive summarydecision brief
- Minutes of meetingMOM
- MOM distilleractions + pre-brief
- Document reviewred-flag a doc
- Email drafterin your voice
- Formal lettersletterhead .docx
Procurement
- Proposal reviewweighted technical
- Commercial evaluationlevel & rank bids
- Procurement trackerback-planned .xlsx
Reporting & visuals
- Monthly reportHTML dashboard
- Design trackerconsultant .xlsx
- Org chart.pptx
- Gantt / programme.pptx
Foundation: built on your details
- Your contextwho you are
- Company Excel brandhouse style
Specialist
- Drawing analysistakeoffs, scope Q&A
Already in Cowork: the base
- Worddocx
- Excelxlsx
- PDFread & build
- PowerPointpptx
The construction skills sit on top of these four.
How to get good answers
Four habits that do the heavy lifting.
Give it the file, not a description
Don't summarise the report for it. Drop the report in. It reads faster and more carefully than any of us.
Say what "good" looks like
"For senior management", "one page", "flag the commercial risk". The clearer the target, the fewer the rounds.
One job at a time, then build
Review first, then summarise, then email. Each step feeds the next. Don't ask for all three in one breath.
Push back on it
"That's too soft", "challenge them harder", "shorter". It'll redo it. Treat it like a sharp junior, not a vending machine.
See it in the wild
A few things it's already built.
Real, live tools and dashboards from my own projects. This is the ceiling, not the floor, of what Cowork can put together once you're fluent.
Costbook.PH
A searchable construction material price lookup.
costbook.pages.dev ↗Web toolCost Estimator
An early-stage build cost estimator.
costbook.pages.dev/estimator ↗DashboardDaily Progress Dashboard
Live site progress for a super-block build.
lsb-dashboard.pages.dev ↗DashboardCM Director Dashboard
Portfolio view across a mall & office development.
parklinks-dashboard.pages.dev ↗ReportMall Repositioning Status
A fortnightly portfolio repositioning report.
mall-status.pages.dev ↗IndexDrawings & Specs Index
A searchable index of 650+ drawings and specs.
parklinks-constech.pages.dev ↗LibraryStandards Portal
A searchable design-standards library.
amg-standards.pages.dev ↗AppSOR
Site Observation Report, a construction field-reporting app.
sorapp.io ↗AppPlannr
A construction programme-planning tool.
plannr.pruneapp.io ↗Real estate · intakeFind Your Place
A property agent's branded enquiry & client onboarding form.
find-your-place.pages.dev ↗Real estate · CRMClient Database
The agent's private client CRM the leads flow into (demo data).
jane-clients-demo.pages.dev ↗WhatsApp · appActionr
Turns busy WhatsApp work groups into a live action-item checklist.
actionr-demo.pages.devFeatured build
One to hold: SOR.
Everything on the last slide is a link. This one is worth opening properly: a real app, on the real App Store, that started as a conversation like the ones you'll have today.
The itch
Site observations were photos in a camera roll and notes on paper. Turning them into a report the team could act on ate the evening.
What it does
Capture an observation on site with photos and notes, and SOR turns it into a branded PDF report, ready to share before you're off the site.
How it was built
Described in plain English, built in conversation, tested on real inspections, then shipped. No development team. The same loop you're learning today, pointed at a bigger target.
Where it is now
Live on the Apple App Store and Google Play as a Stuart Digital product, used on real construction projects.
Reading a live dashboard
Five minutes on the CM Director dashboard.
A portfolio dashboard for a live mall and office build, rebuilt every week from the project's own reports and trackers. It's access-controlled, so I'll drive. Here's how I read it.
Progress against forecast, the headline risks, this week's photos. Thirty seconds tells you whether the week was good or bad.
One schedule, three lines: the baseline we promised, the current target, and what the evidence says is really likely. The gap between the lines is the conversation.
Every headline expands: procurement gates, approvals moving or stuck, zone by zone works. You follow the red, not the whole thing.
Each figure links back to its source: the weekly report, the tracker, the letter. Nothing lives in the dashboard that can't be traced.
The action matrix and the weekly control pack are the output. A dashboard you don't act on is wallpaper.
The bigger picture
Today is stage one.
About six hours in total, across a few sittings, not one marathon. Here's the whole climb, and where each of us is on it.
Set up & the Cowork loop
You are hereConfigure your Claude, then the document-to-deliverable loop. That's today.
Everyday mastery
Run your real projects through it. Chain skills. Build the habit until reaching for it is reflex.
Dashboards & tools
Reading and shaping live dashboards and web tools, like the ones on the last slide.
Code
Where I'm atStepping in to build and change things directly. This is where it gets properly powerful, and still a long way to go.
Shipping apps
Full products, in real people's hands. The far end, for now.
That's the whole thing
Set it up once. Then just ask.
Session one: the pack goes in, Claude learns you, the toolkit loads. Session two: the project-documents-ask-deliverable loop, until it's muscle memory.
Didn't register at the start? Same code, same ten seconds:
stuart-training.pages.dev/s1