🧭 Founder Direction · V1 · September 2026
This page explains why the first deliverable is shaped the way it is — proven catalogue work
first, bespoke work later. Current direction; for the operational month-one schedule, see the
First 30 Day SOP.
There's no single fixed "first deliverable" — but there's a clear pattern: start with
high-impact, low-custom catalogue work that can land immediately, and let the deep, bespoke
roadmap wait until proper discovery is done. Move fast on what's proven; don't rush what isn't.
The instinct might be to start building the client's big custom solution on day one. REMAP
deliberately doesn't — for a hard-learned reason.
⚠️ The cautionary tale: REMAP once built something a client called critical — only to learn
two months in that the client planned to retire that exact process within six months. The
build was wasted.
So month one (and the start of month two) deliberately lean on high-impact, low-custom catalogue
work — proven solutions that create real value immediately — while the fuller, bespoke roadmap
waits on proper discovery.
This isn't slower; it's smarter sequencing. The specialist starts from the digital-footprint
audit, industry knowledge, and catalogue suggestions, which already give roughly two months of
higher-confidence work to begin immediately. The deeper Level 2 audit flows in later to refine
and expand the roadmap from month two onward.
💡 The principle: never build on a foundation you haven't properly checked. Deliver proven value
now; build the bespoke solution once you actually understand the business.
By the time a specialist starts, there's already a substantial pipeline of identified work — it
doesn't start from a blank page:
| Source | Projects surfaced |
|---|---|
| Intelligence Tool (digital-footprint + AEO/GEO + catalogue tags for the niche) | ~6 candidate projects, before discovery even happens |
| The discovery call itself | ~3 more — new or reinforcing |
| At kickoff | 6–9 identified projects |
| Level 2 audit (month two onward) | More detailed, bespoke projects built into the roadmap |
So the client arrives at kickoff with a real runway of work already mapped — which is exactly what
makes the engagement feel substantial from day one.
The moment a client signs, three streams start in parallel (not one after another):
A "what's next" email covers all three on day one. The audit and catalogue can progress
immediately (via email and the WhatsApp bot) without waiting on specialist selection, which
takes a few days to assemble an interview panel — so nothing stalls waiting on one piece.
Month one is jointly owned by three roles — no single point of failure for the most critical
month:
💡 Note that last point: the PM tracks not just was it done but did the client clearly hear
about it — because value delivered silently is the exact failure month one is designed to avoid
(see Why Month One Matters).
🟢 confirmed · 🟡 draft/in-progress · ⚪ illustrative
This page is the why. For the how:
Part of the REMAP Founder Vision space · V1 · Last updated September 2026