STCW, GWO, OPITO, BOSIET, FOET, and team-booking pathways.
Where buyers ask in operational language and your catalogue answers in approval codes.
The first commercial step
A paid, fixed-scope sprint that proves the answer, routing, and reporting pattern in 30 to 45 days.
A founding sprint takes one priority catalogue or service line, builds a private branded prototype against your real sources, captures the demand your standard analytics cannot see, and ends with a deliberate go or stop decision on day 45.
- Fixed scope
- Source-backed
- Reviewer-owned
- Day-45 stop point
Who this is for
Regulated training and safety providers with a serious catalogue and a real review process.
The sprint is built for organisations that already have approved sources, named subject-matter experts, and a commercial reason to make their catalogue easier to answer.
Confined space, working at height, rescue cover, fire safety.
Where the buyer is trying to manage real operational risk and is not sure if they need training, a service, or both.
EASA-regulated training, eligibility, recognition, renewal.
Where regulatory language and approval frameworks make a normal catalogue page hard to navigate.
Diplomas, programmes, and pathway-driven catalogues.
Where the buyer knows the problem they are solving but does not yet know the programme name.
What the buyer gets in 30 to 45 days
A working private concierge, a weekly demand memo, and a clear continuation decision.
You do not get a slide deck. You get a private branded prototype tested against real buyer questions, a weekly memo of what those questions reveal, and an honest call on day 45.
Private branded prototype
A staging deployment that preserves your header, typography, catalogue structure, and enquiry paths. No public launch without your approval.
Priority content index
One catalogue, pathway, or service line indexed against your approved source pages, FAQs, policies, and PDFs.
25 to 50 starter questions
Drawn from your sales notes, repeat enquiries, and operator memory. Mapped to source-backed answer patterns and routes.
Course and service routing
Each answer routes the buyer to the right course, service line, employer enquiry path, or human review point.
Unanswered-question capture
Failed searches and unresolved buyer questions become a structured backlog you can act on.
Weekly demand-intent memo
Top buyer questions, routes shown, no-result searches, employer signals, and suggested actions for the week.
What your team provides
A short, honest intake keeps the sprint useful.
The sprint runs faster and produces a better memo when these are in place before day 0. Rough is fine.
-
01
One priority catalogue or service line
One area where buyers get stuck — a course family, service type, or certification pathway.
-
02
25 common buyer questions
Real enquiries, sales notes, repeat FAQs, or operator transcripts. Phone-call shorthand is fine.
-
03
Source pages and documents
Course pages, policies, PDFs, approval notes, regulatory excerpts — whatever answers should actually cite.
-
04
One named review owner
A subject-matter person who can sign off answer patterns, escalation rules, and last-reviewed dates.
-
05
Preferred enquiry routes
Where a qualified buyer should land — booking page, employer form, human review, or escalation.
What it looks like
Three artefacts. One running loop.
The sprint produces three things buyers, reviewers, and operators all engage with directly.
Ask interface
A private, brand-preserving question field on your domain or a staging URL. Buyers ask in their own words. Answers are returned with citations and a clear next-step route.
- Source-backed answer
- Course or service route
- Off-scope handling
- Human escalation point
Answer pattern
Each answer is a reviewable pattern, not a prompt. Named reviewers approve before publish. Last-reviewed dates and source links are visible to the buyer.
- Approved sources
- Named reviewer
- Last-reviewed date
- Off-scope guard rails
Weekly demand memo
One page, every Monday. The questions buyers asked, the routes that worked, the searches that returned nothing, and the actions worth taking this week.
- Top buyer questions
- Routes and clicks
- No-result searches
- Suggested next actions
Sprint timeline
Day 0 to day 45.
Designed around a 30-day build and test window, followed by a deliberate review at day 45. Timing depends on source access, reviewer availability, and catalogue complexity.
Day 0
Scope the messy catalogue
Choose one catalogue, pathway, or service area where buyers get stuck. Agree the source list and the named reviewer.
Days 1 to 10
Index, question, and route
Map sources, draft starter questions, build answer patterns, and wire the course, service, and enquiry routes.
Days 11 to 30
Private concierge test
Review answer quality, route logic, off-scope handling, and operator usefulness. Weekly demand memos begin.
Day 45
Continuation decision
Stop, continue privately, expand to a second catalogue, or plan a public launch. The decision is yours and is supposed to be deliberate.
What is not included
A founding sprint is deliberately narrow.
The point is to test one catalogue properly, not to rebuild your website. The sprint stops at the boundaries below until you decide otherwise on day 45.
- No public launch without your approval
- No customer-data integration in the first sprint
- No foundation-model training on your content
- No replacement of your LMS or booking system
- No long-term commitment before the pilot proves useful
- No generic AI articles, no marketplace listing, no third-party ad tracking
Budget qualifier
Founding sprints are paid, fixed-scope pilots.
Most suitable founding sprints sit in the low five figures. The fee is fixed at scope and includes the prototype, the answer patterns, the routing logic, the weekly memos, and the day-45 review.
If a fixed-fee written diagnostic is a better starting point, the Answerability Audit exists for that.
Sprint FAQ
Questions serious buyers ask before scoping a sprint.
If the answer to your question is not here, ask it on the enquiry form. You will get a direct reply.
Is the sprint really fixed-scope?
Yes. Scope, sources, reviewer, and routes are agreed at day 0. If new scope appears mid-sprint, it goes into the day-45 decision rather than expanding the current sprint.
What happens at day 45 if it is not useful?
The sprint stops. The prototype is taken down or kept private. You keep the priority content index, the answer patterns, the captured questions, and the memos produced during the sprint.
Will the prototype be public?
Not without your explicit approval. The prototype runs on a private staging URL or behind a noindex flag on your domain by default.
Do you need our LMS or CRM access?
No. The first sprint operates on public website material, agreed source documents, and the questions you provide. Customer-data integration is a separate scope after day 45.
Who owns the answer patterns and the demand memos?
You do. The patterns, the source mappings, and the weekly memos are yours to keep regardless of the day-45 decision.
Can we start smaller than a sprint?
Yes. The Answerability Audit is a fixed-fee written diagnostic. It tests 25 buyer questions against your existing site and recommends a sprint scope, without committing to a sprint.
Start the conversation
Bring one messy training catalogue. I will show you where the hidden demand is.
Share your website, your category, and the questions buyers struggle to answer. I will reply with the right next step: a sprint call, an audit scope, or an honest no.
If I do not think there is a real opportunity, I will say so.