# UPVIA Numbers And Concepts Guide

## Purpose

This file is the canonical explanation of the important numbers, counts, ratios, and structural concepts used across the UPVIA project files.

Use this guide when you need to answer any of these questions:

- What does this number mean?
- Where does this number come from?
- Why was this number chosen?
- Why should it not be replaced with another number?
- Is this number a revenue value, a profit value, a cost value, a target, a context statistic, or only a display/reference number?

This guide is designed to prevent future contradictions between the website, academic templates, transcript files, and final deliverables.

---

## Source Hierarchy

When two files seem to disagree, use this priority order:

1. `UPVIA_CORRECTED_BUSINESS_PLAN.md`
2. `UPVIA_TEMPLATE_FILLED.md`
3. `UPVIA_PROJECT_OUTLINE_FILLED.md`
4. `index.html`
5. `transcripe of the pdf.txt`
6. `upvia-report-text.txt`

Why this order:

- The corrected business plan contains the full financial logic and formulas.
- The template and outline files are the course-format summaries of the same logic.
- The website is a presentation layer, not the master financial model.
- The transcript and plain-text report files are reference/output copies and must mirror the source model, not redefine it.

---

## Numbers That Were Corrected

These values were previously contradictory and must not be reused:

| Wrong value | Correct value | Meaning |
|---|---:|---|
| `250,000` | `294,800` | Year 2 revenue target |
| `113,080` | `128,080` | Year 2 operating profit before the 2.5% academic tax assumption |
| `208,140` | `223,140` | Year 3 operating profit before the 2.5% academic tax assumption |

Why these corrections matter:

- `294,800` is tied to the official 3-year projection tables and strategic targets.
- `128,080` and `223,140` must match the income statement and website financial cards.
- If even one file still uses the old values, the whole project looks mathematically unreliable.

---

## Core Concept Rules

Before using any number, classify it correctly:

1. Revenue number
- Money earned from sales.
- Example: `165,000`, `294,800`, `479,700`.

2. Direct-cost number
- Cost directly related to delivering projects.
- Example: `27,500`, `49,000`, `79,560`.

3. Fixed or operating-cost number
- Ongoing business overhead, not tied to a single project.
- Example: `7,600` monthly, `91,200` yearly.

4. One-time setup number
- Launch cost that should not repeat every year.
- Example: `15,000`.

5. Profit number
- Revenue minus defined costs.
- Example: `31,300`, `128,080`, `223,140`.

6. Post-tax academic number
- Profit after the project's course-alignment tax assumption of `2.5%`.
- Example: `30,517`, `124,878`, `217,561`.

7. KPI target
- Operational or marketing target, not booked accounting value.
- Example: `15-16` leads per month, `>=90%` on-time delivery.

8. Context statistic
- Used to justify the business environment, not to drive the internal revenue formula directly.
- Example: `500,000` VAT threshold, `90%+` SMEs, `50.7%` informal share.

---

## Brand, Timing, And Structure Numbers

| Number | Canonical meaning | Where used | Why it exists | Do not use it as |
|---|---|---|---|---|
| `2026` | Market-reference year for the project version | Business plan, website, references | Anchors the pricing and market assumptions to one time period | A growth target or fiscal period length |
| `April 13, 2026` | Date of the updated final business-plan version | `UPVIA_CORRECTED_BUSINESS_PLAN.md` | Marks the corrected model snapshot | The company launch date |
| `4` | Number of consulting stages | Business plan, website, outline | Defines the UPVIA method: discovery, feasibility, roadmap, prototype | The number of packages or customer segments |
| `3` | Number of main packages | Business plan, website | Keeps the offer ladder simple: Basic, Standard, Premium | The number of project years |
| `4` | Number of add-on services | Business plan, website | Adds upsell flexibility without changing the package structure | The number of core packages |
| `3` | Number of target customer groups | Business plan, website | Keeps segmentation focused: founders, SMEs, educational/health institutions | The number of financial scenarios |
| `3` | Number of financial scenarios | Business plan, website | Shows downside/base/upside planning | The number of years in the income statement |
| `9` | Number of listed risks | Business plan, website | Gives a structured risk register | A financial assumption |
| `44 / 44 = 100%` | Completion-lock count for the full project document | Business plan | Internal completeness check | A business KPI |

---

## Service And Delivery Numbers

| Number | Canonical meaning | Where used | Why it exists | Do not use it as |
|---|---|---|---|---|
| `60 minutes` | Discovery session duration | Business plan, website, outline | Long enough to diagnose the idea while staying low-friction for leads | A paid delivery duration for the full service |
| `5 days` | Basic package delivery time | Business plan, website | Fast validation entry-level package | Standard or Premium timing |
| `10 days` | Standard package delivery time | Business plan, website | Middle tier with feasibility and roadmap depth | Basic timing |
| `15 days` | Premium package delivery time | Business plan, website | Supports added prototype/validation work | Full company-wide project cycle cap |
| `17 working days` | Maximum end-to-end cycle reference used in positioning | Website, outline, notes | Expresses that UPVIA is still faster than slower consultancy alternatives | The exact duration of every package |
| `30 days` | Premium after-delivery support window | Business plan, website | Strengthens Premium value without turning UPVIA into a long implementation retainer | Extra development time or warranty across all packages |
| `2 simultaneous projects` | Planned parallel-capacity limit | Outline, operational notes | Protects quality and keeps a small team realistic | Annual capacity by itself |
| `12 projects` | Year 1 planned capacity and KPI cap | Business plan, website, outline | Conservative planning with buffer for quality and brand-building | A hard physical maximum for all future years |

Important distinction:

- `5`, `10`, and `15` are package delivery windows.
- `17` is the broader brand promise for the full consulting sprint envelope.
- `12` is the year-1 planning cap, not the theoretical forever limit.

---

## Package Pricing Numbers

| Number | Canonical meaning | Where used | Why it exists | Do not use it as |
|---|---|---|---|---|
| `8,000` | Basic package price | Business plan, website | Entry point for early founders with budget sensitivity | Average project revenue |
| `15,000` | Standard package price | Business plan, website | Core package with the strongest middle-market fit | Yearly revenue per client |
| `25,000` | Premium package price | Business plan, website | Highest-value offer with prototype and deck support | Default package price for all clients |
| `1,500` | Standalone consultation add-on price | Business plan, website | Small-ticket advisory add-on | Package price |
| `3,000` | Feasibility-study update add-on | Business plan, website | Low-friction expansion service | Direct delivery cost |
| `4,500` | Separate pitch-deck add-on | Business plan, website | Adds investor-facing value | Premium package equivalent |
| `6,000` | Corporate discovery workshop add-on | Business plan, website | Higher-ticket workshop option for organizations | Core package revenue assumption |

Why these prices are not interchangeable:

- `8,000`, `15,000`, and `25,000` are product prices.
- `13,750` is only the blended average revenue per project in the year-1 model.
- The average must never replace the actual package prices in pricing copy.

---

## Payment Policy Numbers

| Number | Canonical meaning | Where used | Why it exists | Do not use it as |
|---|---|---|---|---|
| `60%` | Upfront payment at contract signing | Business plan, website | Protects cash flow and reduces collection risk | Profit margin |
| `30%` | Payment at draft delivery | Business plan, website | Aligns cash receipts with work progress | Discount rate |
| `10%` | Final payment at final delivery | Business plan, website | Leaves a small final settlement amount | Tax withholding |
| `99,000` | Total year-1 advance cash implied by 60% of `165,000` revenue | Business plan | Shows that upfront cash receipts cover annual operating costs | Recognized full revenue or profit |

Key rule:

- The `60-30-10` split is a cash-collection structure.
- It is not a revenue-recognition formula and not a margin formula.

---

## Year 1 Revenue Model

### The canonical year-1 sales mix

| Item | Formula | Value |
|---|---|---:|
| Basic revenue | `4 x 8,000` | `32,000` |
| Standard revenue | `5 x 15,000` | `75,000` |
| Premium revenue | `2 x 25,000` | `50,000` |
| Add-on revenue | fixed planning allowance | `8,000` |
| **Total year-1 revenue** | `32,000 + 75,000 + 50,000 + 8,000` | **`165,000`** |

### Why these counts were chosen

- `4` Basic projects keep the model accessible to early-stage founders.
- `5` Standard projects make the middle package the commercial core.
- `2` Premium projects keep the model realistic for a new consultancy.
- `8,000` of add-ons adds small upsell revenue without assuming aggressive cross-selling.

### What `165,000` is and is not

`165,000` is:

- Total planned year-1 revenue.
- The base-case scenario revenue.
- The website year-1 revenue headline.

`165,000` is not:

- Monthly revenue.
- Profit.
- Cash collected upfront only.
- The price of one project.

---

## Year 1 Direct Costs

| Number | Meaning | Formula | Why it exists | Do not use it as |
|---|---|---|---|---|
| `1,200` | Direct cost per Basic project | planning assumption | Keeps Basic contribution realistic | Package selling price |
| `2,500` | Direct cost per Standard project | planning assumption | Reflects extra analytical effort | Gross profit |
| `4,500` | Direct cost per Premium project | planning assumption | Reflects prototype and deeper output effort | Premium selling price |
| `1,200` | Aggregate direct cost for add-ons in year 1 | planning allowance | Prevents add-ons from looking costless | Add-on revenue |
| `27,500` | Total direct project costs in year 1 | `4,800 + 12,500 + 9,000 + 1,200` | Necessary to calculate contribution margin correctly | Fixed cost or total annual cost |

Direct-cost detail:

| Item | Formula | Value |
|---|---|---:|
| Basic direct costs | `4 x 1,200` | `4,800` |
| Standard direct costs | `5 x 2,500` | `12,500` |
| Premium direct costs | `2 x 4,500` | `9,000` |
| Add-on direct costs | allowance | `1,200` |
| **Total direct costs** | sum | **`27,500`** |

---

## Year 1 Operating Costs

### Monthly operating-cost structure

| Monthly number | Meaning | Annual equivalent |
|---:|---|---:|
| `1,500` | Work tools and SaaS | `18,000` |
| `2,000` | Digital marketing and content | `24,000` |
| `800` | Internet and communications | `9,600` |
| `800` | Accounting and legal review | `9,600` |
| `600` | Meetings and transportation | `7,200` |
| `500` | Administrative and contingency | `6,000` |
| `400` | Security and technical protection | `4,800` |
| `1,000` | Equipment depreciation | `12,000` |
| **`7,600`** | **Total monthly operating cost** | **`91,200`** |

What `7,600` means:

- It is the monthly overhead budget.
- It excludes the direct per-project delivery costs.
- It excludes the one-time setup cost.

What `91,200` means:

- It is `7,600 x 12`.
- It is the year-1 recurring operating-cost budget.
- It is the fixed yearly cost base used in the year-1 income statement.

What `91,200` is not:

- Total year-1 cost.
- Cash reserve requirement by itself.
- Direct cost of serving clients.

---

## Setup, Capital, And Opening Position Numbers

| Number | Canonical meaning | Where used | Why it exists | Do not use it as |
|---|---|---|---|---|
| `15,000` | One-time setup cost expensed in year 1 | Business plan, income statement | Covers launch-stage setup burden | A recurring annual overhead |
| `50,000` | Working capital / current assets at opening | Website, business plan, balance sheet | Ensures liquidity and early operating resilience | Year-1 profit |
| `5,000` | Fixed assets at opening | Balance sheet | Represents approximate capitalized physical/technical assets | Total setup cost |
| `55,000` | Total opening assets and founder equity | Balance sheet | `50,000 + 5,000`; opening position snapshot | Total year-1 expense burden |
| `0` | Opening liabilities in the model | Balance sheet | Assumes self-funded launch with no debt | Cash balance or zero-cost business |

Why `55,000` is not the same as `15,000`:

- `15,000` is an expense line used in the year-1 profit model.
- `55,000` is an opening balance-sheet funding snapshot.
- Not all setup-related outflows are treated the same way in accounting-style presentation.
- Therefore there is no contradiction between `15,000` setup expense and `55,000` opening equity.

---

## Year 1 Profit Logic

### Canonical year-1 income logic

| Item | Formula | Value |
|---|---|---:|
| Revenue | sales mix total | `165,000` |
| Direct costs | delivery costs total | `(27,500)` |
| Contribution / gross operating profit | `165,000 - 27,500` | `137,500` |
| Operating fixed costs | recurring annual overhead | `(91,200)` |
| Setup cost | one-time launch cost | `(15,000)` |
| **Operating profit before tax assumption** | `165,000 - 27,500 - 91,200 - 15,000` | **`31,300`** |
| Academic tax assumption | `31,300 x 2.5%` | `(783)` |
| **Founder net after academic assumption** | `31,300 - 783` | **`30,517`** |

Key distinctions:

- `137,500` is not final profit. It is contribution after direct costs.
- `31,300` is the pre-tax operating profit.
- `30,517` is after the project's `2.5%` academic tax treatment.

Why `31,300` must not be replaced by `30,517`:

- The website and projection summaries are using the operating-profit framing.
- `30,517` belongs to the formal post-tax-style academic presentation.

---

## Average And Break-Even Numbers

| Number | Meaning | Formula | Why it exists | Do not use it as |
|---|---|---|---|---|
| `13,750` | Average revenue per planned project in year 1 | `165,000 / 12` | Needed for scenario and break-even reasoning | A real package price |
| `11,458` | Average contribution margin per planned project | `137,500 / 12` | Used to estimate break-even quantity | Invoice value per project |
| `106,200` | Fixed-cost base used in break-even | `91,200 + 15,000` | Combines recurring overhead plus year-1 setup | Total yearly cost including direct costs |
| `10 projects` | Break-even point | `106,200 / 11,458 = 9.27`, rounded | Shows minimum viable client volume in the base year | Guaranteed profit threshold under every possible sales mix |
| `2 projects` | Safety margin above break-even in the base plan | `12 - 10` | Shows the model has buffer | Extra guaranteed profit |
| `5.8 months` | Payback period for setup cost | `15,000 / 2,608` | Shows launch-cost recovery speed | Full business repayment period |
| `19 months` | Payback period for full working capital | `50,000 / 2,608` | Shows recovery of the wider capital base | Break-even timing |

Important warning:

- The `10 projects` break-even depends on the blended average contribution margin.
- If the sales mix changes materially, the exact break-even count can change too.

---

## Quarterly Cash Flow Numbers

These numbers belong to planning and cash sequencing, not to the package price list.

| Quarter | Projects | Revenue | Costs | Net |
|---|---:|---:|---:|---:|
| Q1 | `2` | `27,500` | `33,425` | `-5,925` |
| Q2 | `3` | `41,250` | `33,425` | `+7,825` |
| Q3 | `3` | `41,250` | `33,425` | `+7,825` |
| Q4 | `4` | `55,000` | `33,425` | `+21,575` |
| **Total** | **`12`** | **`165,000`** | **`133,700`** | **`+31,300`** |

Why the costs are `33,425` each quarter:

- The planning sheet spreads the annual total cost `133,700` equally over four quarters.
- This is a simplified planning view.
- It is not claiming every real-world month will spend the exact same amount.

Why the `2/3/3/4` project split exists:

- It reflects gradual reputation-building rather than assuming a strong sales start from month one.
- It makes the base case more believable for a new consultancy.

---

## Scenario Numbers

| Scenario | Projects | Revenue | Profit / loss | Meaning |
|---|---:|---:|---:|---|
| Conservative | `9` | `117,000` | `-8,500` | Downside case |
| Base | `12` | `165,000` | `+31,300` | Main planning case |
| Optimistic | `15` | `213,000` | `+71,100` | Upside case |

Why these scenario numbers exist:

- They show the business is sensitive to project volume.
- They prove the model is not pretending one outcome is guaranteed.

Why they should not override the main model:

- The project is built around the base-case operating plan of `12` year-1 projects.
- The conservative and optimistic rows are scenario tests, not the official year-1 target.

---

## Three-Year Growth Numbers

### Canonical three-year operating view

| Year | Model | Clients / projects | Revenue | Operating profit before 2.5% academic tax assumption |
|---|---|---:|---:|---:|
| Year 1 | Online only | `12` | `165,000` | `31,300` |
| Year 2 | Online + flexible office | `18` | `294,800` | `128,080` |
| Year 3 | Hybrid model | `26` | `479,700` | `223,140` |

### Formal three-year income statement values

| Item | Year 1 | Year 2 | Year 3 |
|---|---:|---:|---:|
| Revenue | `165,000` | `294,800` | `479,700` |
| Direct costs | `(27,500)` | `(49,000)` | `(79,560)` |
| Contribution / gross operating profit | `137,500` | `245,800` | `400,140` |
| Fixed costs | `(91,200)` | `(117,720)` | `(177,000)` |
| Setup cost | `(15,000)` | `—` | `—` |
| Operating profit before tax assumption | `31,300` | `128,080` | `223,140` |
| Academic 2.5% tax assumption | `(783)` | `(3,202)` | `(5,579)` |
| Net after academic assumption | `30,517` | `124,878` | `217,561` |

Why these year-2 and year-3 values matter:

- `294,800` is the official year-2 revenue target and must replace `250,000` everywhere.
- `128,080` is the official year-2 operating profit and must replace `113,080`.
- `223,140` is the official year-3 operating profit and must replace `208,140`.

What these numbers are not:

- They are not valuation numbers.
- They are not guaranteed contracts already signed.
- They are not monthly run-rate values.

---

## Tax And Regulatory Context Numbers

| Number | Meaning | Why it exists | Do not use it as |
|---|---|---|---|
| `500,000` | VAT registration threshold mentioned in the project | Explains why VAT is not built into the year-1 base pricing logic | A year-2 revenue goal |
| `14%` | General VAT reference mentioned in notes | Regulatory context only | The course tax assumption used in the income statement |
| `2.5%` | Academic/course-alignment profit deduction | Keeps the business-plan format aligned with the course model | Legal tax advice or guaranteed real tax treatment |
| `783`, `3,202`, `5,579` | 2.5% deductions applied to years 1-3 | Used only in the post-tax-style academic presentation | Operating profit figures |

Critical rule:

- The model explicitly says VAT is not included because year-1 revenue is below the threshold.
- The `2.5%` deduction is a course-format assumption, not a replacement for real tax/legal advice.

---

## Market And Classification Context Numbers

These values justify market reality but do not directly generate the revenue forecast.

| Number | Meaning | Why it exists | Do not use it as |
|---|---|---|---|
| `~53.36 EGP/USD` | Exchange-rate reference used for 2026 price sanity checks | Helps anchor imported tool-cost assumptions | A revenue multiplier |
| `90%+` | Share of establishments characterized as SMEs in cited context | Supports the presence of a large small-business market | Target conversion rate |
| `50.7%` | Share of private-sector establishments described as informal in cited context | Supports unmet-need reasoning | Revenue margin |
| `~2 million` | Approximate count of informal-sector establishments in cited context | Strengthens market-size argument | Reachable customer count |
| `3 million EGP` | Reference ceiling used in micro-enterprise classification note | Supports SME size classification logic | Annual revenue target |
| `< 5 employees` | Micro-enterprise classification marker | Supports venture-size classification | Staffing plan target |

Important boundary:

- These numbers explain why the opportunity exists.
- They do not prove UPVIA will automatically win that market.

---

## Sales Funnel And KPI Numbers

| Number | Meaning | Why it exists | Do not use it as |
|---|---|---|---|
| `15-16 leads/month` | Lead generation target | Back-solves a realistic funnel for `12` year-1 projects | Signed clients |
| `30%` | Leads to discovery-call conversion | Measures top-of-funnel quality | Profit margin |
| `60%` | Discovery to proposal conversion | Measures qualification quality | Same as the payment policy 60% upfront |
| `35%` | Proposal to paid-client conversion | Measures closing effectiveness | Tax or discount rate |
| `>=3 case studies` | Proof-building target | Needed for credibility in year 1 | Revenue line item |
| `>=3 referrals` | Referral-count target | Supports low-cost growth | Referral-rate percentage |
| `>=25%` | Referral-rate target | Indicates client advocacy | Share of all market customers |
| `>=20%` | Repeat or upsell rate | Indicates account expansion | Pure acquisition rate |
| `>=4.5/5` | Customer satisfaction target | Quality-control benchmark | Revenue rating |
| `>=90%` | On-time delivery target | Operational reliability benchmark | Utilization rate |

Critical distinction:

- The funnel `60%` and the payment `60%` are unrelated concepts.
- One is a conversion rate.
- The other is an invoicing structure.

---

## Capacity And Planning Logic

| Number | Meaning | Why it exists | Do not use it as |
|---|---|---|---|
| `250 working days` | Implied annual working-capacity reference in planning notes | Used to reason about theoretical project capacity | An invoiced service duration |
| `14.7` | Approximate theoretical projects from `250 / 17` | Shows the ceiling before buffer | Official sales target |
| `13` | Buffered theoretical capacity after realism adjustment | Shows disciplined planning | Official year-1 commitment |
| `12` | Actual year-1 target | Keeps the plan conservative and quality-safe | Strict permanent limit for all years |
| `18` | Year-2 project/client target | Reflects managed scale-up | Year-2 profit |
| `26` | Year-3 project/client target | Reflects hybrid-scale maturity | Year-3 revenue percentage |

---

## What Each Big Number Should Be Called

Use these exact labels whenever possible:

| Number | Preferred label |
|---:|---|
| `165,000` | Year 1 revenue |
| `27,500` | Year 1 direct costs |
| `91,200` | Year 1 operating costs |
| `15,000` | Year 1 setup cost |
| `31,300` | Year 1 operating profit before academic tax assumption |
| `30,517` | Year 1 net after 2.5% academic assumption |
| `294,800` | Year 2 revenue target |
| `128,080` | Year 2 operating profit before academic tax assumption |
| `124,878` | Year 2 net after 2.5% academic assumption |
| `479,700` | Year 3 revenue target |
| `223,140` | Year 3 operating profit before academic tax assumption |
| `217,561` | Year 3 net after 2.5% academic assumption |
| `13,750` | Blended average revenue per year-1 project |
| `11,458` | Blended average contribution per year-1 project |
| `10 projects` | Break-even point |

---

## Short Anti-Confusion Checklist

If you are editing any file, check these rules before saving:

1. Never replace `294,800` with `250,000`.
2. Never replace `128,080` with `113,080`.
3. Never replace `223,140` with `208,140`.
4. Never call `13,750` a package price.
5. Never call `31,300` the post-tax net profit.
6. Never call `30,517` the operating profit.
7. Never treat `500,000` VAT threshold as a revenue target.
8. Never confuse funnel `60%` with payment-policy `60%`.
9. Never treat scenario figures as guaranteed results.
10. Never let transcript/reference copies override the corrected business-plan model.

---

## Final Interpretation

The UPVIA project uses a small, disciplined, service-business model with:

- conservative year-1 capacity,
- a clear package ladder,
- a blended year-1 sales mix,
- controlled recurring overhead,
- one-time setup treatment,
- a rational break-even threshold,
- and a clean transition from year 1 online-only delivery to year 2 and year 3 scale.

The three most important financial anchors in the project are:

1. `165,000 / 31,300` for year 1
2. `294,800 / 128,080` for year 2
3. `479,700 / 223,140` for year 3

If those anchors stay consistent, the website, academic templates, transcripts, and final deliverables will remain mathematically aligned.

---

## Expanded Math Numbers (Added April 17, 2026)

These numbers were added by the Expanded Audit to close mathematical gaps.

### Capacity Safety Margin

| Number | Meaning | Formula |
|---|---|---|
| `108.3%` | Capacity safety margin | 13 ÷ 12 × 100 |
| `13` | Buffered capacity after realism adjustment | Theoretical max (~14.7) minus buffer |
| `72%` | Average cycle-time reduction vs traditional consulting | BPR comparison |

### Growth Math (CAGR)

| Number | Meaning | Formula |
|---|---|---|
| `70.5%` | Revenue CAGR across years 1-3 | (479,700/165,000)^(1/2) − 1 |
| `47.2%` | Project count CAGR across years 1-3 | (26/12)^(1/2) − 1 |
| `Year 7-8` | Estimated time to reach small-enterprise tier (3M revenue) | At 70.5% CAGR |

### Customer Value Math (LTV / CAC)

| Number | Meaning | Formula | Do not use it as |
|---|---|---|---|
| `17,100` | Customer Lifetime Value | 13,750 × 1.2 + 3,000 × 0.2 | Revenue per project |
| `2,000` | Customer Acquisition Cost | 24,000 ÷ 12 | Marketing budget |
| `8.6x` | LTV/CAC ratio | 17,100 ÷ 2,000 | Profit multiplier |

### Contingency Math

| Number | Meaning | Formula |
|---|---|---|
| `~31,416` | Total effective contingency reserve | 6,000 + 2,500 + 22,916 |
| `~23.5%` | Contingency as % of total costs | 31,416 ÷ 133,700 |

### Perceived Value Ratio

| Number | Meaning |
|---|---|
| `10x–20x` | Client's perceived value vs price paid |
| `92%–95%` | Client's potential savings from avoiding failed development |

### Demographic Targeting

| Variable | Value |
|---|---|
| Age range | `25–55 years` |
| Geography | Cairo / Giza / Alexandria |
| Income | Above average |

### Budget Split

| Category | Amount | % |
|---|---|---|
| Idea phase | `5,500` | `8.5%` |
| Execution phase | `128,200+` | `91.5%` |

### Opening Balance Sheet

| Item | Value | Do not use it as |
|---|---|---|
| `50,000` | Total assets = Total equity | Revenue or profit |
| `38,500` | Cash in bank/treasury | Available for spending (includes working capital reserve) |
| `0` | Total liabilities | Do not add debt without updating this |
| `7,600` | Monthly operating obligations | Annual = 91,200 |

### Innovation Classification

| Item | Value |
|---|---|
| Type | `Adaptive Innovation (تطويري/تكيّفي)` |
| Ansoff Matrix | `Product Development` |
| Comparison | Like Uber for transport — reengineered process, not new invention |

### Indirect Competitors

| Competitor | Type |
|---|---|
| "Do nothing" (skip validation) | Primary indirect |
| Friend/advisor consultation | Informal indirect |
| Free AI tools (ChatGPT) | Technology indirect |
| Dev agency "free consultation" | Sales-driven indirect |
| Incubator programs (3-6 months) | Slow-track indirect |