What today looks like

The 60 minutes.

No coffee break — the fifteen-minute build in the second half is the break. And today you leave with a link, not a file.

PresenterSay the shape out loud: first half you watch, second half you ship.

Where you got to

You chain skills now — and you built one.

• One document through three skills: no re-typing.
• Check the handover: the chain fails at the joins, not the middle.
• One topic, one chat: the context stays with the job.
• Your own skill: you built it with skill-creator and ran it on real work.

PresenterThree minutes. Ask: “Who ran their skill this week?” The homework was three runs. Whatever the answer, the segue is the same: everything so far has been a document. Hold up a sheet of paper for the next slide.

The difference

A document is done the moment you send it. A link is still true next week.

A monthly report starts going stale the moment it leaves. When the numbers move, you make another file. A dashboard is the same content with one difference: it lives at an address. When the facts change, the thing at the address changes. Nobody asks “is this the latest version?” of a URL.

Stage 3 ended with a file. Stage 4 ends with a link you can send someone. That's the whole stage in one sentence.

monthly-report

Three documents in. One dashboard out.

Say build the monthly for Northgate. A cost report, weekly report and design tracker become one browsable dashboard: summary, progress, cost, risks and photos.

You met Northgate in stage 3 — you reviewed their report. Same project. Today it gets a dashboard.

PresenterCooking-show rule: run the trigger live so the room sees the skill ask its questions, then cut to the finished dashboard baked earlier. Watching a full build is five dead minutes; watching the start and seeing the result is thirty seconds each.

Watch the URL, not me

Change it. Deploy it. Reload it.

Before58% · risk open

After62% · risk closed

Open it before the edit.

northgate-monthly.pages.dev

Say progress moved to 62% and the facade risk closed — update the dashboard and put it live. Then: reload it. Same URL; new truth.

Nobody re-sent a file. Nobody asked who has the latest version. The address stayed the same; the truth behind it moved.

PresenterThis edit is scripted and rehearsed: the same two changes every time, run once the morning of the session. Narrate the deploy minute. If wifi is down, use these before/after frames.

What just happened

That loop is the product.

A change went from a sentence to live in front of witnesses in under two minutes. That loop — say the change, see it live — is what you're really taking from today. The dashboard is just the first thing you'll run it on.

PresenterFirst cut if running long. Fold the heading into v7's last line.

Not a demo

Five minutes on a real one.

This one is rebuilt every week from the project's own reports. It's access-controlled, so I'll drive — but it's the same skill you just watched, pointed at a live portfolio.

PresenterThis is the credibility beat. Drive it view-only. Never edit it, never share the URL, never leave it on screen while answering questions. Narrate the job — “it's Monday, was the week good or bad?” — not the interface.

The tracker that re-plans itself.

Say procurement tracker for [project]. Give it the package list and Required-On-Site dates and it back-plans tender out, award and mobilisation, with a formula-driven dashboard on top. Dates move? The plan recalculates. That's a living thing, not a spreadsheet made once.

PresenterConstruction/CM route only. In a non-construction room, skip this slide and v11 and give the 6 minutes to the v15 hands-on. Do not improvise a route for another industry — we haven't built one yet.

Live state, not a snapshot.

Say design tracker for [consultant]. Milestones, submissions, issues and lookahead become the standing format a consultant reports into every week. It is the current state of the design, not a minute of a meeting already out of date.

Both trackers chain off things you already have — the schedule feeds the baseline dates. Stage 3's lesson didn't stop applying.

PresenterConstruction/CM route only. In a non-construction room, skip v10 and this slide and give the 6 minutes to the v15 hands-on. Do not improvise a route for another industry — we haven't built one yet.

One more thing living things can do

The tool runs without you.

Say export the schedule to slides. The skill did not write one Gantt deck — it wrote a tool that builds it, and the tool runs again when the dates change. Same input, updated slides, zero re-drawing.

Documents, living pages — and tools that work without you. That third kind is a door. Behind it is stage 5, where you watch the tools get written.

PresenterDo not demo the output deck for more than one slide. The point is the idea landing, not another Gantt.

requirements-brief · driven

Watch a questionnaire get built.

Say build me a requirements brief for [the thing] — ask me what you need. It builds a branded phone form; when the stakeholder sends it, the answers arrive in your WhatsApp as one message.

The form lives at a URL. You send a link, not an attachment — which after this morning should sound familiar.

PresenterDemo the interview, not the full build. Keep the demo brief to three sections. The sell is sensible sections appearing from two plain-English answers.

15 minutes · and it goes live

Build yours — and put it live.

1

Pick one real thing you need answers about this week.

2

build me a requirements brief for [that] — ask me what you need

3

Keep it to four sections.

Preview it and fix the one thing that reads wrong.

4

deploy it

Save the URL it gives you.

Made the free Cloudflare account before today? It deploys as yours. Didn't? Hand it to me at the front and it goes live from mine before we finish — the link is still yours to send.

PresenterWalk the room. Do not sit down. Cut over-large surveys to four sections and route anyone not logged into Cloudflare to the front desk drop without ceremony. Nobody leaves without a URL.

The bit you'll remember

Every one of those is live right now.

Read three or four of the room's URLs off the screen. Open one on the projector. It is a real address on the real internet, made by someone who had never done it before today, in a quarter of an hour.

Stage 3 you left with a skill. Today you leave with an address. Send it to one real person tonight — answers arrive while you sleep.

PresenterPick volunteers during the hands-on, not now. If a form is half-finished, open it anyway — half-finished and live is the lesson.

What you unlocked

Documents, living pages, and tools.

Stage 5 opens the room where the tools come from — a terminal, a plan you approve, and a change you can read.

One action tonight

Send the link tonight.

Send your questionnaire to one real person before you go to bed. A live URL nobody visits is a file with extra steps.

Deck PDF

Scan to add Stuart to your contacts.
training.stuartdigital.io/card

PresenterName the next date. Stage 5 needs a small install before the session — the pre-session email will say so.