Module 1 · M-01Live module

Pre-Cohort Screening.

Assess founder readiness, problem-solution maturity, validation gaps, and program fit before selection decisions are made.

Best place to start
Best place to start: before selection decisions

Use Screening when you have a founder application, a pitch summary, or a pre-incubation candidate, and you need to decide admit, hold, or redirect — before mentor or workshop time is committed.

Built for idea-stage and pre-seed founder screening.

Module SpecM-01
Core JobDecide who to admit, hold, or redirect
InputsApplication · founder summary · evidence
OutputFounder Readiness & Program Fit Report
Runtime< 2 minutes
ModeSelf-serve · PAYG · Pilot eligible
01What screening decides

What this workflow helps you answer.

  1. Q01Is this founder too early for our current program?
  2. Q02How sharp is the problem-solution logic?
  3. Q03What support gap matters most right now?
  4. Q04Is this founder better suited to pre-incubation, cohort admission, or a hold-and-reassess path?
  5. Q05What should the program know before committing mentor or workshop time?
02Demo

Try the screening demo.

Use this quick screening demo to see how Clarification Studio for Incubators evaluates founder readiness before deeper support begins.

This demo helps your team assess
  • 01How clear the venture is
  • 02How strong the problem-solution logic is
  • 03What validation gaps are visible
  • 04What support priority is most important
  • 05Whether the founder is too early, promising but under-validated, or ready for structured support

Designed for idea-stage and pre-seed founders.

What to put in
Paste founder application or venture summary Upload founder application

Rough notes are fine — fill what you have. The sample is pre-filled so you can run it as-is.

SCREENING DEMOM-01 · Founder Readiness & Program Fit
Idle
Inputs · 10 fields

Use a real founder name, startup name, or working title.

Choose the sector that best fits the founder's idea.

Select the founder's current stage of development.

Write what the founder is trying to build, in simple language.

Describe the likely customer as specifically as possible.

State the problem in the founder's own words if possible.

Describe how the founder believes the problem should be solved.

This can include interviews, pilots, waitlists, sales, feedback, usage, or early traction.

Examples: customer too broad, weak proof, unclear payer, weak monetisation, too early, weak problem logic.

Select the type of program or support environment this screening is for.

Pipeline
  1. 01 · Parsing founder intake
  2. 02 · Scoring readiness and maturity
  3. 03 · Mapping program fit
  4. 04 · Detecting validation gaps
  5. 05 · Drafting story layer
  6. 06 · Compiling structured report
Output preview · 7 fields
F01Opportunity Snapshot
Awaiting
F02Founder Readiness Level
Awaiting
F03Problem-Solution Maturity
Awaiting
F04Validation Gaps
Awaiting
F05Support Priority
Awaiting
F06Program Fit Recommendation
Awaiting
F07Suggested Route
Awaiting
Sample artifact (preview)
REPORT · FR-2026-0148Founder Readiness & Program Fit Report
v1.2 · ~6 min read · 9 sections
F01
Opportunity Snapshot
Founder / Venture
Tomi Adeyemi · Halocrate
Sector
B2B logistics SaaS
Stage
Pre-seed
Venture Type
Product
Program Evaluated For
Incubation
First Read
Coachable; not cohort-ready yet
Venture Summary

Halocrate is a route-reconciliation tool for mid-market 3PL operators (50–250 vehicles) in Lagos and Ibadan, replacing manual end-of-day spreadsheets with an automated workflow tied to driver, customer, and exception data.

Bottom-Line First Read

Real problem, real conviction, no priced pilot — early but coachable, admit only with conditions.

F02
Founder Readiness Level
Early but coachableLevel 3 of 5
  • 01Too early for deeper support
  • 02Needs pre-validation work first
  • 03Early but coachable
  • 04Ready for structured support
  • 05Ready for deeper engagement

Tomi has earned a Level 3 read: the problem is real and the language is the customer's own, but the venture has no design partner, no priced pilot, and no defined wedge. The instinct to update on evidence is present; the discipline to convert evidence into commitments has not been demonstrated yet. With one priced pilot and one named partner, this profile is a quarter away from Level 4.

Readiness Summary7 rows
  • Venture ClarityModerateDirection is named; the wedge is not
  • Customer ClarityModerateMid-market 3PL ops named, but persona detail thin
  • Problem DefinitionStrongPain is real and validated through 11 interviews
  • Solution LogicWeakConcept-level only; no design partner committed
  • Commercial LogicWeakNo pricing hypothesis, no priced pilot scheduled
  • Validation DisciplineModerateUpdates on evidence but moves slowly
  • Program ReadinessModerateCoachable; needs scoping support before deep cohort
F03
Problem-Solution Maturity Assessment
Stated Problem

End-of-day reconciliation eats 4–6 hours per branch and hides revenue leakage.

Stated Solution

Workflow that ties driver, customer, and exception data into a single review surface.

Current Customer

Mid-market 3PL ops leads in Lagos (50–250 vehicles).

Fit · PartialProblem · RealCustomer · SpecificSolution · Concept-level

The problem and customer hold up under pressure; the solution is still a concept. Eleven interviews confirm the pain and the buyer, but no observed workflow shows which step the product owns first. The link between pain and product is plausible — it is not yet earned by evidence.

Key observation

The maturity ceiling here is solution scoping, not customer discovery. Treat further interviews as low-value until a design partner is named.

F04
Customer and Market Read
Customer Specificity

Specific by segment and city; persona detail (role, tenure, decision power) is still thin.

Buyer / User / Payer

Ops lead is user and recommender; finance signs. The two are not separated in current pitch.

Market Realism

Grounded — founder cites real fleet sizes, not TAM slides.

Nigeria-Reality Check6 rows
  • Trust DynamicsModerateOps leads engage; procurement trust not earned yet
  • Informal / Formal Market FitStrongFormal mid-market 3PL — clean buying surface
  • Payment LogicWeakNo tested model — seat, usage, or outcome unclear
  • Channel LogicModerateWarm-intro motion works; outbound untested
  • Operational FeasibilityStrongPrototype runs on real route data from 2 partners
  • Regulatory AwarenessModerateAware of data-handling; no DPR mapping yet

The market read is honest. Trust is being earned with ops, not yet with procurement, and payment logic is the weakest link. The founder treats the Nigerian mid-market 3PL space as a formal buying surface, which is accurate — but channel and pricing have not been tested against that buyer in any structured way.

F05
Validation Gaps · Top 3
G-01

Solution shape not tested against real workflow

Gap
What is missing

No design partner has run the prototype end-to-end inside a live reconciliation cycle.

Why it matters

Without one observed workflow, the founder is guessing which step to own first.

If ignored

Build effort will scatter across three half-features instead of one usable wedge.

G-02

Pricing logic undefined — no willingness-to-pay signal

Gap
What is missing

No pricing hypothesis put in front of a buyer; no priced pilot proposed.

Why it matters

Pricing decides the buyer, the channel, and the sales motion — not the other way round.

If ignored

Founder will optimise product for a buyer who would never have paid anyway.

G-03

No paid or unpaid pilot scheduled with target customer

Gap
What is missing

Eleven conversations, zero commitments to a structured test window.

Why it matters

Interviews validate pain; pilots validate fit. The gap between them is where most ventures stall.

If ignored

Cohort time will be spent re-litigating the problem instead of testing the solution.

F06
Support Priority Assessment
Primary support priority

Solution framing — scope the wedge with one design partner

Until one customer's actual workflow has shaped the solution surface, every other support layer is premature.

Why this comes first

Solution shape is the blocker that gates pricing, channel, and pilot design. Fixing it unlocks the next three decisions in sequence.

Do not prioritise yet

Fundraising prep, brand work, hiring plans, or any second-segment exploration. They will absorb time without changing readiness.

F07
Program Fit Recommendation
Suitable for early-stage intake with conditionsSuggested route · Admit with targeted support conditions
  • 01Too early for current program
  • 02Better suited to pre-incubation
  • 03Suitable for early-stage intake with conditions
  • 04Suitable for structured cohort participation
  • 05Suitable for deeper acceleration support

The founder clears the bar for early-stage intake but not for unconditional cohort entry. Admit with two conditions: a named 3PL design partner by week 2, and a priced pilot offer drafted by week 4. If either slips, re-route to pre-incubation.

F08
Program Team Note
What the team should know immediately
  • 01Conviction is grounded — founder does not over-claim
  • 02No priced pilot; the next decision is pricing, not product
  • 03Solution surface is too wide for one customer to feel addressed
What the team should watch next
  • 01Whether a 3PL design partner is named within 14 days
  • 02Whether a one-sentence wedge emerges by week 3
  • 03Whether pricing hypothesis is tested in at least two calls
Internal operating note

Pair Tomi with a scoping-oriented mentor, not a strategy generalist. Cohort value here is operational discipline, not vision work.

Narrative interpretation · TNIC story layer

Founder Readiness Story

Tomi is an operator-type founder who has spent enough time inside mid-market 3PL workflows in Lagos to recognise a real, recurring pain. He is building Halocrate with quiet conviction rather than performance: eleven customer conversations, a working concept doc, and a way of describing the problem that ops leads themselves use. The ambition is grounded, the framing is honest, and the stage is genuinely early.

The tension shows up between his language and his evidence. He speaks like a founder who has product-market signal, but he has no priced pilot, no design partner, and no defined wedge. The next step is being treated as a product question — what to build, in what order — when it is actually a scoping and pricing question. That gap is what makes him feel earlier than he sounds, and why the solution surface is still doing too many jobs at once.

For the program, this reads as admit with conditions, not hold. Tomi is coachable in the way that matters: he updates on evidence and he does not over-claim. With one named 3PL design partner, a priced pilot, and a one-sentence wedge by week three, he moves from 'early but coachable' to genuinely cohort-ready inside a quarter. Selective coaching on scoping and pricing will return more than broad mentorship on strategy.

F09
Structured Recommendation Summary
Admit with conditionsFinal screening recommendation

Tomi sits at Level 3 readiness — early but coachable. The problem and customer are validated; the solution shape, pricing, and pilot motion are not. The three top gaps (solution-in-workflow, pricing logic, scheduled pilot) all point to the same primary priority: solution framing with one design partner. Admit to incubation with two non-negotiable conditions — named design partner by week 2 and priced pilot offer by week 4. If both land, this founder moves quickly. If either slips, route to pre-incubation and reassess at week 6.

SHORT
Screening Quick Summary
Founder / Venture
Tomi Adeyemi · Halocrate
Readiness Level
Early but coachable
Top Gap
Solution shape untested in real workflow
Support Priority
Solution framing with one design partner
Program Fit
Early-stage intake with conditions
Recommended Route
Admit with targeted support conditions
03Simulations

See realistic screening scenarios.

SCN-01Scenario 01

Promising founder, but too early for cohort support

Founder input

A founder wants to build an agritech platform that helps smallholder farmers get access to farm inputs and buyers. The founder believes the problem is that farmers are being cheated by middlemen and do not get fair access to market. The proposed solution is a mobile platform connecting farmers directly to suppliers and offtakers. The founder has spoken to a few farmers informally but has not yet tested pricing, onboarding, or delivery logistics.

What the system surfaces
  • S01The problem is real but broad
  • S02Customer definition is still weak
  • S03Trust and logistics are major issues
  • S04The solution is too platform-led too early
  • S05Validation discipline is still low
  • S06Founder is promising, but better suited to pre-incubation than cohort admission
Recommended route
Needs pre-validation work first
SCN-02Scenario 02

Coachable founder with strong pain logic and visible gaps

Founder input

A founder is building a WhatsApp-first savings and contribution tool for market traders who already use ajo systems informally. The founder argues that traders save consistently but lack usable digital infrastructure that respects their trust patterns. The solution is a lightweight WhatsApp-led product that digitises contributions and gives members better visibility. The founder has interviewed 20 traders and 3 market leaders but has not yet tested fee tolerance or fraud concerns.

What the system surfaces
  • S01Customer is specific
  • S02Problem appears real and recurring
  • S03Trust logic is central
  • S04Payment logic and fraud concerns remain unproven
  • S05Solution direction is stronger than many early-stage submissions
  • S06Founder is suitable for structured support with a focused validation agenda
Recommended route
Admit with conditions / targeted support
SCN-03Scenario 03

Strong creative instinct, weak business structure

Founder input

A founder wants to build a platform that helps emerging African creatives collaborate, showcase work, and find commercial opportunities. The founder believes the problem is that young creatives lack visibility and access. The solution is described as a community platform with mentorship, exposure, and marketplace features. The founder has a good network and strong creative instincts but limited business model clarity.

What the system surfaces
  • S01The desire is understandable, but the business logic is broad
  • S02Audience and customer are not clearly separated
  • S03Monetisation logic is weak
  • S04Community, marketplace, and platform are being mixed too early
  • S05Founder may need offer clarity and business-shape work before deeper cohort support
Recommended route
Better suited to pre-incubation / focused refinement
04Output value

What the screening output gives your team.

One structured artifact. Six operational signals. Ready for an admit panel on Monday.

V-01Signal

Founder readiness level

V-02Signal

Problem-solution maturity read

V-03Signal

Top validation gaps

V-04Signal

Support priority

V-05Signal

Program fit recommendation

V-06Signal

Suggested next founder route

Live preview · OUT-01
7 fields generated
Summary firstFounder Readiness & Program Fit Report
Sample
  • 01Founder readiness level: Early but coachable
  • 02Program fit: Suitable for intake with conditions
  • 03Top validation gap: Solution shape untested in real workflow
  • 04Support priority: Solution framing with one design partner
  • 05Recommended route: Admit with targeted conditions
Full artifact hidden — open to see every section
05Use cases

Useful for.

01Cohort selection
02Pre-incubation filtering
03Startup competitions
04Entrepreneurship centres
05Accelerator intake
06Founder pipeline triage
Next step

Screen better before you support deeper.

Use structure before selection. It saves time, resources, and false optimism later.