Use case map
Six ways the work usually starts.
Each use case starts with a model, market, advantage, bottleneck, or proof point. The route changes when the evidence changes.
01 RECON
Transfer a proven model into a mis-served market
A business model works in one region or category, while the target market still relies on fragmented, offline, or poorly localized alternatives.
- Good fit
- Best when the buyer, offer, pricing motion, and channel mechanics are already visible somewhere else.
- Exiid system
- Decode the reference model, isolate what must adapt, then test the local opportunity through validation.
- First proof
- Qualified demand, trust cues, or repeat use appears before a full product roadmap is funded.
- Output
- Build, adapt, partner, or stop with the evidence on the table.
02 Evaluation
Validate a market gap before product build
A founder, investor, or operator sees a category gap but needs to know whether the pain is structural enough to earn a venture.
- Good fit
- Best when a target market is named and the no-go decision is as useful as a yes.
- Exiid system
- Map the demand, current substitutes, channel risk, and fastest kill factor before build momentum starts.
- First proof
- A proof point is selected before the sprint, then tested with the smallest credible artifact.
- Output
- A clear build, adapt, partner, or stop recommendation.
03 Services
Turn offline demand into an online operating model
A real business has customer demand, manual work, or local distribution, but the online model is underdeveloped.
- Good fit
- Best when revenue already exists and digital leverage can change speed, margin, access, or service quality.
- Exiid system
- Translate the operating bottleneck into a product, workflow, content, or automation layer that can be tested fast.
- First proof
- A shipped proof shows whether online behavior, cost-to-serve, or activation can move.
- Output
- A practical roadmap from existing demand to online scale.
04 RAID
Build a JV around a partner advantage
A partner brings distribution, capital, domain insight, supply, regulatory fluency, or regional access that makes a transfer plausible.
- Good fit
- Best when incentives, ownership appetite, and operating roles can be made explicit early.
- Exiid system
- Use evaluation to define the thesis, then validate before moving into build, launch, and scale.
- First proof
- The partner advantage affects acquisition, trust, speed, or execution quality in a measurable way.
- Output
- An aligned venture build, JV, or advisory sprint instead of an agency-style retainer.
05 RECON
Clarify attribution before marketing automation
An eCommerce operator is spending across channels, but reporting, cohort reads, and payback clarity lag behind growth pressure.
- Good fit
- Best when paid acquisition exists and the first problem is trust in the numbers, not automation breadth.
- Exiid system
- Instrument the funnel, define cohort reads, then add automation only where the economics hold.
- First proof
- Stable attribution on acquisition tests and CAC payback visibility by channel or cohort.
- Output
- A sharper martech entry point for markets where full-stack tooling is too broad too soon.
06 RAID
Shape learning access in infrastructure-light markets
A knowledge or education category has demand, but learners face weak access, low trust, or fragmented progression.
- Good fit
- Best when the reference model proves structured paths, searchable libraries, or completion mechanics.
- Exiid system
- Adapt the learning model around trust, activation, progression, and repeat path use before expanding content breadth.
- First proof
- Repeat use on core paths and completion behavior hold after the first learning loop.
- Output
- A focused education venture that earns breadth through behavior, not inventory.
Routes
The use case decides the first move.
Exiid does not force every opportunity into the same container. The route should match the risk, evidence, services need, and partner advantage.
RECON validates the idea (Discover + Validate). RAID builds and launches after evidence clears (Build + Launch + Scale).
- 01
Evaluation
Fit check
Use when the thesis is still raw and the useful output is a clear build, adapt, partner, or stop decision.
- 02
RECON
Validation sprint
Use when the reference model is visible, but local demand, channels, trust, and risk still need pressure-testing.
- 03
RAID
Build and launch
Use when evidence clears and the work moves into build together, JV execution, or launch operations.
- 04
Services
Operating leverage
Use when AI can move a real bottleneck, online revenue path, cost-to-serve, or customer experience.