Market Sizing
CompletedGlobal TAM is broad because the product targets founders and SMBs needing feasibility, setup, and pricing workflows; the context cites software for startup formation, not a single niche. I keep it conservative versus generic business-planning software because compliance-heavy work limits total buyers.
SAM is limited to Egypt plus North Africa and the Middle East, and to first-time founders, SMBs, and accelerator-backed startups reachable through product-led, WhatsApp, and incubator channels. Pricing at EGP 299-1,500 implies a small but real annual reachable revenue pool.
SOM assumes a narrow Egypt-first wedge and founder-led outbound can close about 150 paying customers in 3 years, with ARPU near the starter-plus-upsell mix. At this stage and with MVP status, a few hundred thousand dollars annually is a realistic capture.
I use 16.5% because the space is growing with AI workflow adoption and digital payments, but trust and local compliance slow expansion. The project is pre-seed, MVP-stage, and Egypt-first, so I avoid aggressive hypergrowth assumptions.
ARPU is based on the stated pricing stack: EGP 299 starter draft, EGP 699 launch pack, and EGP 1,500 concierge handoff, with some subscription and transaction/take-rate upside. Blended annual revenue per active SMB/founder is conservatively around $180.
The core problem is not that this is a tiny market; it is that the sizing logic is not yet credible enough to support the numbers. A TAM of $1.2B and SAM of $18M imply a very specific, well-bounded buyer set, but the project context mixes founders, SMBs, startups, subscriptions, take-rate, credits, and services without proving which segment is primary. That makes the SOM of $450k look more like a guess than a bottom-up forecast. ARPU of $180 per customer per year is also not well aligned with the stated pricing. If the entry point is EGP 299 one-time and the upsells are project-based, then $180/year only works if repeat usage or subscription conversion is real. Right now, the business reads like a hybrid of software, concierge service, and marketplace take-rate, which can work, but only if you show a clear wedge and a repeatable conversion funnel. Without that, the market size may be directionally plausible but not investment-grade. What would strengthen the case is a bottom-up model: number of target founders in Egypt, conversion from outreach to paid draft, repeat rate, average orders per customer, and how much of revenue is software versus services. If you can show even 50 to 100 paying customers with retention or repeat project behavior, the SAM and SOM become much more believable.
Against LivePlan and Upmetrics, the only defendable angle is local specificity: Egypt-first setup workflows, Arabic-first UX, and compliance-aware handoff. The risk is that this becomes a generic planning tool with a local wrapper, which is easy to copy. The company needs to own one narrow founder job so clearly that it becomes the default workflow for that task in its beachhead market.
Founders in Egypt and the broader MENA region still waste time stitching together consultants, templates, spreadsheets, and local experts just to get launch-ready. The pain is not lack of information; it is execution friction, trust, and the absence of a guided workflow that turns an idea into a usable feasibility pack. That creates a real opportunity for a localized AI product that starts with one high-value job: generate a feasibility draft, checklist, and pricing starting point in minutes, then route sensitive steps to human review. The wedge is narrow enough to be productized, but broad enough to expand into subscriptions, credits, and paid handoff services once users trust the workflow. The market is attractive because the buyer is already paying today, just inefficiently, through consultants and fragmented services. Global tools like LivePlan and Upmetrics prove the category exists, but they do not solve the local context problem. An Egypt-first product with Arabic UX, local setup logic, and a clear service layer can win the beachhead if it shows repeat usage, not just one-off document generation. The investment case depends on proving that this is software with a repeatable workflow, not a template shop. If the team can show paid drafts, repeat customers, and a clear conversion path from free or low-cost intake to higher-value handoff, then the market can support a venture-scale outcome across Egypt first and then the broader Arabic-speaking region.
- TAM/SAM/SOM are not built from a transparent bottom-up model
- ARPU does not clearly match the stated pricing and revenue mix
- The product definition is still too broad to size a single market accurately
| Name | Note |
|---|---|
| LivePlan | A mature business-planning SaaS that shows there is demand for planning tools, but it is not a proof of your local market size. |
| Upmetrics | An AI-assisted business plan product that validates willingness to pay for drafting workflows, but not Egypt-specific compliance demand. |
| Bplans | A content and template business that proves search demand for planning help, though it is not a direct software revenue benchmark. |
| Year | Customers | Revenue Usd |
|---|---|---|
| 1 | 50 | 12000 |
| 3 | 350 | 90000 |
| 5 | 900 | 180000 |
| Label | Year3 Revenue Usd | Assumption |
|---|---|---|
| Conservative | 60000 | The product stays mostly manual, with low repeat usage and limited conversion beyond the first draft. |
| Base case | 120000 | A narrow Egypt-first wedge converts paid drafts into occasional repeat projects and modest subscription uptake. |
| Aggressive | 250000 | The team proves repeat demand, expands channels, and adds meaningful service and transaction revenue. |
healthy
CAC can be low if founder-led outbound and WhatsApp are the main channels. LTV is only healthy if repeat drafts, subscriptions, or paid handoff services are real; otherwise it drops quickly.
| Company | Value Usd | Year | Context |
|---|---|---|---|
| LivePlan | 0 | 0 | No public exit value is available because it remains privately held. |
| GoCanvas | 700000000 | 2021 | A workflow software acquisition that shows strategic buyers pay for vertical software with operational depth. |
This is still a pre-seed story because traction is not yet proven and the market sizing is not fully grounded. The raise should be framed as validation capital for a narrow wedge, not expansion capital for a broad platform.
Full record (inputs + outputs)
════════════════════════════════════════════════════════════
MARKET SIZING
════════════════════════════════════════════════════════════
────────────────────────── INPUTS ──────────────────────────
▸ Tam Usd
1200000000
▸ Sam Usd
18000000
▸ Som Usd
450000
▸ Cagr Pct
16.5
▸ Arpu Usd
180
────────────────────────── AI OUTPUTS ──────────────────────────
▸ Autofill Result
Tam Usd: 1200000000
Sam Usd: 18000000
Som Usd: 450000
Cagr Pct: 16.5
Arpu Usd: 180
Tam Reasoning: Global TAM is broad because the product targets founders and SMBs needing feasibility, setup, and pricing workflows; the context cites software for startup formation, not a single niche. I keep it conservative versus generic business-planning software because compliance-heavy work limits total buyers.
Sam Reasoning: SAM is limited to Egypt plus North Africa and the Middle East, and to first-time founders, SMBs, and accelerator-backed startups reachable through product-led, WhatsApp, and incubator channels. Pricing at EGP 299-1,500 implies a small but real annual reachable revenue pool.
Som Reasoning: SOM assumes a narrow Egypt-first wedge and founder-led outbound can close about 150 paying customers in 3 years, with ARPU near the starter-plus-upsell mix. At this stage and with MVP status, a few hundred thousand dollars annually is a realistic capture.
Cagr Reasoning: I use 16.5% because the space is growing with AI workflow adoption and digital payments, but trust and local compliance slow expansion. The project is pre-seed, MVP-stage, and Egypt-first, so I avoid aggressive hypergrowth assumptions.
Arpu Reasoning: ARPU is based on the stated pricing stack: EGP 299 starter draft, EGP 699 launch pack, and EGP 1,500 concierge handoff, with some subscription and transaction/take-rate upside. Blended annual revenue per active SMB/founder is conservatively around $180.
▸ Analysis Result
Score: 38
Credibility: shaky
Verdict Oneliner: The market is real, but the sizing and monetization assumptions are still too hand-wavy to underwrite.
Critique: The core problem is not that this is a tiny market; it is that the sizing logic is not yet credible enough to support the numbers. A TAM of $1.2B and SAM of $18M imply a very specific, well-bounded buyer set, but the project context mixes founders, SMBs, startups, subscriptions, take-rate, credits, and services without proving which segment is primary. That makes the SOM of $450k look more like a guess than a bottom-up forecast.
ARPU of $180 per customer per year is also not well aligned with the stated pricing. If the entry point is EGP 299 one-time and the upsells are project-based, then $180/year only works if repeat usage or subscription conversion is real. Right now, the business reads like a hybrid of software, concierge service, and marketplace take-rate, which can work, but only if you show a clear wedge and a repeatable conversion funnel. Without that, the market size may be directionally plausible but not investment-grade.
What would strengthen the case is a bottom-up model: number of target founders in Egypt, conversion from outreach to paid draft, repeat rate, average orders per customer, and how much of revenue is software versus services. If you can show even 50 to 100 paying customers with retention or repeat project behavior, the SAM and SOM become much more believable.
Red Flags:
• TAM/SAM/SOM are not built from a transparent bottom-up model
• ARPU does not clearly match the stated pricing and revenue mix
• The product definition is still too broad to size a single market accurately
Comparables:
• Name: LivePlan
Note: A mature business-planning SaaS that shows there is demand for planning tools, but it is not a proof of your local market size.
• Name: Upmetrics
Note: An AI-assisted business plan product that validates willingness to pay for drafting workflows, but not Egypt-specific compliance demand.
• Name: Bplans
Note: A content and template business that proves search demand for planning help, though it is not a direct software revenue benchmark.
Timeline:
•
Year: 1
Customers: 50
Revenue Usd: 12000
•
Year: 3
Customers: 350
Revenue Usd: 90000
•
Year: 5
Customers: 900
Revenue Usd: 180000
Scenarios:
• Label: Conservative
Year3 Revenue Usd: 60000
Assumption: The product stays mostly manual, with low repeat usage and limited conversion beyond the first draft.
• Label: Base case
Year3 Revenue Usd: 120000
Assumption: A narrow Egypt-first wedge converts paid drafts into occasional repeat projects and modest subscription uptake.
• Label: Aggressive
Year3 Revenue Usd: 250000
Assumption: The team proves repeat demand, expands channels, and adds meaningful service and transaction revenue.
Unit Economics:
Cac Estimate Usd: 35
Ltv Estimate Usd: 180
Ltv Cac Ratio: 5.14
Verdict: healthy
Note: CAC can be low if founder-led outbound and WhatsApp are the main channels. LTV is only healthy if repeat drafts, subscriptions, or paid handoff services are real; otherwise it drops quickly.
Positioning: Against LivePlan and Upmetrics, the only defendable angle is local specificity: Egypt-first setup workflows, Arabic-first UX, and compliance-aware handoff. The risk is that this becomes a generic planning tool with a local wrapper, which is easy to copy. The company needs to own one narrow founder job so clearly that it becomes the default workflow for that task in its beachhead market.
Investor Narrative: Founders in Egypt and the broader MENA region still waste time stitching together consultants, templates, spreadsheets, and local experts just to get launch-ready. The pain is not lack of information; it is execution friction, trust, and the absence of a guided workflow that turns an idea into a usable feasibility pa
…[truncated to fit export]