Aspiring first-time founders, MSME aspirants who think they want to start something but have not committed, career-changers entering self-employment, retired professionals exploring an encore career, and existing solopreneurs assessing whether to scale to a real business. The diagnostic does not ask whether you have the idea; it asks whether you have the bedrock to execute on any idea.
What does it measure?
30 questions across five dimensions: market knowledge, financial literacy, sales and customer acquisition, operations and delivery, regulatory and compliance. Each question scored 0-3 deterministically. Output: total score, tier verdict, dimension-level breakdown, top three gaps, 90-day fill plan with specific actions per gap.
When to take it?
Take this before you commit serious time or capital — ideally before you quit your job or take outside investment. Re-take after 90 days of executing the fill plan; tier movement is common. Re-take annually as a maintenance check even after launch — operating businesses regress on dimensions when founders specialise too narrowly.
Where does the result apply?
Results are general (market knowledge applies anywhere) but the regulatory questions are jurisdiction-specific. The diagnostic flags this — if you are India-based, the specific tax IDs and licenses differ from a UK or UAE founder. Use the country selector below the result to filter the gap-action plan to your jurisdiction.
Why this diagnostic?
Most first-time founders fail not because the idea was wrong but because the bedrock was missing. They could not read their books. They had not sold anything before. They did not know which licenses to register. The diagnostic surfaces these dimension-level gaps in 12 minutes — earlier than any failure would.
Which questions matter most?
The questions weighted heaviest are sales (you must know how to sell or the business does not exist) and unit economics (without contribution margin, scaling loses money faster). The most-skipped questions in beta tested with founders were the regulatory ones — most aspiring founders avoid these and pay for the avoidance later.
Whose framework underwrites it?
The diagnostic is composed by AJG editorial drawing on conversations with 200+ first-time MSME founders, the failure-mode literature on small-business mortality (US SBA failure data, India MSME ministry distress data, UK Insolvency Service trends), and the operational frameworks taught in venture-incubator programmes (Y Combinator, Techstars, NSRCEL, Antler).
How does the scoring work?
Scoring is deterministic and transparent: each question has 4 choices weighted 0-3. Sum is 0-90 for 30 questions, normalised to a 0-100 percentage. Tier thresholds at 30%, 55%, 75%. Dimension-level scores computed separately so a founder strong on market and weak on regulatory is correctly diagnosed. No machine learning, no opaque weighting — every input traces to a published number.
Totality lens · 32 points to ponder · 16 user POV + 16 developer POV · this tool
User POV — for the practitioner using this tool
Eight dimensions
1 · Possibility
A first-time founder can in principle assess every dimension of operating readiness — capital runway, revenue traction, team-formation, customer-discovery rigour, market timing, regulatory exposure — across all 23 readiness axes the diagnostic surfaces. Few do; most fixate on the one or two axes their network has trained them to over-weight (typically capital), under-investing in axes (regulatory, customer-discovery, team-formation cadence) where the actual failure mode usually sits.
2 · Plausibility
A founder honestly attempting all 23 axes typically reveals 4-7 weak axes within the first diagnostic pass, of which 2-3 are critical-path. That much is realistic. What is less realistic is closing all of them in parallel — most founders can address 2 axes substantively per quarter, so a complete readiness uplift takes 6-12 months of disciplined sequencing rather than the few weeks most assume.
3 · Probability
Of founders who run the diagnostic, take the recommendations seriously, and revisit quarterly, perhaps 60-70 percent reach defensible readiness across the 23 axes within 18 months. The remaining 30-40 percent stall on one or two specific axes — typically distribution channel uncertainty or pricing power confusion — and either pivot or wind down. The diagnostic itself does not change the base rate; sustained re-application does.
4 · What works
What works at this stage: running the diagnostic before raising capital, not after; treating axis-scores as a hypothesis to invalidate rather than a verdict to accept; revisiting quarterly with version-tracked scores; sharing scores with co-founders and key advisors for triangulation; building remediation plans for the bottom 3 axes specifically rather than spreading attention across all 23.
5 · What doesn't work
What does not work: running the diagnostic once and treating it as final; over-indexing on capital-axis at the expense of the operational axes; sharing scores selectively with investors to "look ready" rather than with advisors to actually become ready; conflating axis-improvement with cosmetic-improvement (better deck, better narrative) without underlying change in the diagnosed weakness.
6 · Common pitfall
The most common pitfall is treating the readiness score as a proxy for fundability. The two correlate but the causation runs from readiness to fundability, not the other way. Founders who optimise for fundability (polish, deck, narrative) without addressing the underlying readiness gaps typically raise smaller rounds at worse terms and run into operating walls within 12-18 months post-raise.
7 · Counter-intuitive insight
Counter-intuitively, the founders who score lowest on initial diagnostic but address the gaps systematically usually outperform founders who score highest initially. Initial high scores often reflect surface readiness (good deck, polished narrative) rather than depth. Initial low scores at least surface what needs work. The diagnostic punishes self-deception more than it punishes inexperience.
8 · Highest-leverage move
The single highest-leverage move at the readiness stage is to pick the bottom 2 axes (those scoring weakest) and assign each a measurable 90-day remediation plan with a specific output. Generic "improve customer discovery" produces nothing; specific "interview 30 customers in segment X using Y questionnaire by date Z" produces the actual learning that moves the axis-score.
Eight user intents
9 · Who gains most
First-time founders within 6-18 months of launch, second-time founders pivoting into a new sector, intrapreneurs preparing to spin out, accelerator-cohort applicants benchmarking against peer cohorts. The 25-45 age band dominates; younger founders use the diagnostic to compress learning, older founders use it to sequence sub-team assembly.
10 · Irreducible essence
The irreducible essence: 23 readiness axes scored honestly, weakest 2-3 selected for 90-day remediation, repeat quarterly, share with co-founders and advisors. The diagnostic is a sequencing tool not a verdict.
11 · Optimal timing
Best applied 6-12 months pre-raise (to actually shape the company toward readiness), not 1-2 months pre-raise (too late to change underlying gaps). Quarterly re-application thereafter through the first 24 months. After product-market-fit signals stabilise, the diagnostic transitions from readiness-tool to maturity-tracker.
12 · Where it matters most
Geographically agnostic — the 23 axes apply across markets. Specific axes weight differently by market: regulatory in healthcare/fintech/biotech weighs more in regulated geographies; distribution-channel in consumer-goods weighs more in retail-fragmented geographies; capital-runway weighs more in capital-thin emerging markets.
13 · Why misunderstood
Founder readiness is misunderstood because the early-stage ecosystem rewards confidence-displays (pitch competitions, accelerator demo days, founder-friend conversations) more than honest self-assessment. The diagnostic forces honest self-assessment which the ecosystem incentive structure actively discourages. That is precisely why it works for founders who use it.
14 · Highest-leverage sub-paths
Of the 23 axes, the highest-leverage cluster for first-time founders is: customer-discovery rigour (axis 4), team-formation cadence (axis 11), pricing-power clarity (axis 17). For second-time founders: market-timing read (axis 8), regulatory exposure (axis 14), distribution-channel ownership (axis 19). For intrapreneurs spinning out: capital-runway design (axis 1), founder-equity-split structure (axis 22).
15 · Whose advice to trust
Trust: peer founders 1-2 years ahead of you (they remember what you face now), portfolio operating partners at funds that have backed your stage previously, customers who have purchased from you with money. Ignore: pitch-competition judges (selection bias), social-media founder-content (survivorship bias), well-meaning but inexperienced advisors (no skin in your game).
16 · How to proceed differently
Proceed by running the diagnostic in one sitting (60-90 min), inviting your co-founders to do the same independently, comparing scores, picking the bottom 2 axes by consensus, building a 90-day remediation plan with a measurable output per axis, and rerunning the diagnostic at the 90-day mark. Track scores in a quarterly spreadsheet keyed by axis × date.
Developer POV — for the architect, maintainer, AI tool, future contributor
Eight dev dimensions
17 · Data architecture
Founder-readiness composes from data/atlas-founder-readiness.php (the 23-axis schema with question-set, weight, threshold-good/warn/bad bands), the diagnostic engine in includes/atlas-diagnostic-engine.php (handles scoring, axis-clustering, remediation-suggestion logic), and includes/atlas-readiness-narrative.php (composes the per-axis narrative paragraphs at render time). Single-file render; no database; deterministic PHP composition per SO #14.
18 · Schema markup
SoftwareApplication schema fires on the toolkit page (the diagnostic is an interactive tool); ItemList of the 23 axes; HowTo schema for the diagnostic-running flow. The 23-axis question-set is exposed as Quiz schema with associated Question + AcceptedAnswer arrays. The remediation-suggestion logic emits Recommendation schema per axis-band-result.
19 · Internal linking
Forward to /toolkit/skill-half-life/, /toolkit/cofounder-fit/, /toolkit/founder-burnout/ (sequential ATLAS toolkit). Outward to /capital-raises/{stage}/, /accelerators/{program}/, /investors/{firm}/. Cross-content injector pulls Library + ScopeScape matches on tokens "founder", "readiness", "diagnostic", "early-stage". Link weaver hyperlinks the 23 axis names automatically.
20 · Page-speed posture
Page payload ~22 KB total (CSS + 23-axis question-set + scoring engine + result-narrative + 32-point totality block). Render ~280-450 ms server-side. JS for the diagnostic interactivity is ~8 KB minified vanilla (no framework). LCP element typically the page hero. Cumulative Layout Shift near zero (no async-loaded content shifts the layout).
21 · Mobile UX
Diagnostic question-set renders one-axis-at-a-time on mobile, swipe-or-tap navigation; full-grid view on desktop. Tap-targets ≥48px on every axis-button. Sticky progress-bar at top showing axis N of 23. Result-display collapses score-rings to single-column at narrow viewports. Per ui-directive.php WCAG AAA.
22 · Accessibility
Diagnostic uses semantic <fieldset> + <legend> per axis with <input type="radio"> + <label> for the answer-options. Keyboard navigation works without mouse. Focus-visible outline on every interactive element. Result-display uses semantic <table> with proper <thead> + <th scope="col"> for screen-reader navigation. Color contrast AAA body / AA threshold-bands.
23 · SEO saturation
URL: https://allfrontierglobal.com/toolkit/founder-readiness/. Canonical per page. OG title + description + url + type=website. Twitter card. Sitemap inclusion via /sitemap-fragments/atlas-toolkit.xml. IndexNow ping on edit. SoftwareApplication schema. The 23-axis result-display renders as crawlable HTML for indexing axis-specific queries.
24 · Extensibility
To add a 24th axis: append to data/atlas-founder-readiness.php $axes array with required fields (id, name, question, weight, threshold_good, threshold_warn, threshold_bad, remediation_template). Diagnostic engine auto-picks up. Total ship time ~30 min including handwritten remediation-template prose.
Eight dev intents
25 · Who maintains
Joint maintenance (Amit + Vinod). Diagnostic question-set edits are bilateral; axis-additions require both principals to agree on weight + threshold-bands. Result-narrative remediation prose is handwritten per-axis (currently 23 unique paragraphs, ~2,800 words).
26 · What tech stack
Tech: PHP 8.3 (Nestify Nginx flat-file), vanilla JS for diagnostic interactivity (~8 KB), CSS custom properties for theming, no framework dependency. Helpers: ajg_atlas_founder_readiness_axes(), ajg_atlas_score_axis(), ajg_atlas_remediation_template().
27 · When to refresh
Diagnostic question-set refreshed semi-annually as ecosystem shifts (e.g., new investor expectations, regulatory changes). Axis weights revisited annually. Remediation-template prose updated as new patterns emerge from peer-founder feedback. IndexNow on edit.
Why 23 axes specifically rather than 10 or 50: 10 misses critical-path axes (regulatory, distribution-channel, founder-equity); 50 produces axis-fatigue and false-precision. 23 is the empirical sweet-spot derived from interviewing 60+ early-stage founders about what they wished they had been forced to assess pre-raise.
30 · Which dependencies
Critical: atlas-founder-readiness.php (23-axis schema), atlas-diagnostic-engine.php (scoring), atlas-readiness-narrative.php (remediation). Optional: per-axis PDF deep-dive, per-axis case-study links. Required for diagnostic render: schema + engine; narrative degrades gracefully if absent (shows score without remediation prose).
31 · Whose responsibility
Same ownership (Amit + Vinod). 23-axis schema verified against published founder-failure analyses (CB Insights post-mortem reports, ProductHunt post-mortems, Failory data) plus direct interviews. Schema attribution in axis-meta field. Remediation prose composed from observed-pattern synthesis, not from third-party content.
32 · How to extend
To add a new axis cluster (e.g., adding a "social-impact-readiness" cluster of 3-5 axes): (1) decide cluster theme; (2) draft axes individually; (3) define weight + thresholds; (4) write remediation-template prose per axis; (5) add cluster-grouping logic to ajg_atlas_axes_clusters() helper. Total ship: ~3-4 hours including content.