Where this fits
You're at step one: gather a few decisions and some real files. That feeds the discovery call — then the build starts.
decisions & files
call
first tool
two & three
improving
The short, do-this version. Same caveat as the full guide: this is an early read of your brief, ahead of our discovery call — so nothing's locked, and "not sure yet" is a fine answer to anything. Read the full thinking already? This is your checklist. Haven't? It's the fast path through it.
Everything here points at one thing: we measure against real work. Wherever you see the ◆ mark, that's an artifact we use to set a baseline — the "before" we measure the "after" against. No vague claims about AI value. Real examples, real comparisons, real time saved.
You're at step one: gather a few decisions and some real files. That feeds the discovery call — then the build starts.
Two quick wins first; the serious risk tool second. Each ends with a human check (in red) before anything goes out.
Plain questions, each with a one-line why. None heavy.
A written method for rating risks — likelihood × consequence, and what each rating means? If not, one short session and we write it together, calibrated to SafeWork NSW. Biggest single swing in the plan.
Step-by-step guides for how a project runs? If written, point me at them. If not, a short writing job at the start — not a blocker.
A standard kickoff form, or do we build the approved version together? It's the one input all three tools read from.
Where does signed-off, final data live, versus works-in-progress? The tools only ever touch approved material.
Which supplier types already have a template — AV, styling, catering, entertainment, security, transport, venue — and which need building? I just need the gaps.
Who signs a risk register, and at what rating? Who signs a medium; who has to sign a high? The tool drafts; a named person signs and carries it.
Ground truth comes from real projects. Choose two.
One finished project — ideally with full approved supplier briefs ◆, a pitch deck that won ◆, and a signed risk register ◆. One project that hits all three lets us test every tool against work you actually delivered.
One current, in-flight project — fair game for a second run under real pressure.
Largely things I already have — just made explicit for this purpose. Nothing onerous.
So the pitch builder can drop into your real components instead of rebuilt copies.
Your explicit OK to use the brand and project files to build the tools, not only to look at them.
Any paid fonts or licensed images whose licence limits reuse outside BLE.
Work through the questions, pull the files together — then the next step is our discovery call, where this early sketch meets how BLE really runs and the scope gets real. From there I build and run the first tool on my own machine here, and you see it side by side with the real thing: your first visible win.