- How should an Egyptian business organize a 90-day growth plan?
- What evidence should determine whether to diagnose, test or scale?
Ninety days should produce decisions
A 90-day growth plan is not a promise that every business can scale within a quarter. It is a structure for reducing uncertainty: establish what is happening, test a plausible improvement, and expand only when evidence and operations support it. The dates create review points, not permission to ignore weak results.
For an Egyptian business, begin with the actual workflow. Who approves Arabic messaging? Who updates the website? Who contacts inquiries, and where are outcomes recorded? A plan that assumes instant approvals or unlimited sales capacity will fail operationally even if its channel idea is sensible.
Days 1–30: diagnose the constraint
The growth lead owns the diagnostic, supported by sales, finance and the person responsible for implementation. Assemble a baseline covering traffic sources, qualified inquiries or new customers, conversion stages, acquisition spending and relevant variable costs. Mark missing data rather than filling gaps with estimates presented as facts.
Interview the team handling inquiries. Review a sample of accepted and rejected opportunities, inspect the mobile conversion journey and document the offer in both customer-facing languages where applicable. Choose one constraint: weak demand capture, unclear value, poor qualification or a broken handoff.
Exit criteria: the team has one prioritized problem, a metric dictionary, a checked conversion path, named data owners and an agreed test budget. If conversion recording remains unreliable, fixing that is the next phase’s work; buying more traffic is not a substitute.
Days 31–60: run a bounded test
The channel owner runs the experiment; the analyst verifies measurement; sales records outcome quality. Write a short test card containing the audience, problem, hypothesis, change, primary metric, guardrails, spending ceiling and decision date.
Optimizely’s metrics guidance distinguishes primary metrics, secondary metrics and monitoring goals. Apply that principle by choosing one decision metric, such as accepted qualified inquiries, while monitoring costs and workload. These are planning recommendations, not platform-mandated thresholds.
Select tests using expected impact, effort, dependencies and uncertainty rather than novelty, consistent with Optimizely’s prioritization framework. A new campaign is not necessarily more valuable than repairing a confusing booking form.
Exit criteria: tracking is verified, the agreed observation window has elapsed, quality feedback is complete and the team can explain whether evidence supports continuing, revising or stopping. If the sample is too small, record the result as inconclusive; do not manufacture certainty to satisfy the calendar.
Days 61–90: scale conditionally
The growth lead recommends expansion, finance confirms affordability and the operational owner confirms capacity. Increase exposure in manageable steps while preserving the tested audience and offer long enough to understand what changed. Monitor accepted opportunities, cost, response delays and delivery constraints together.
Exit criteria: the business has a documented repeat, revise or stop decision; an updated budget; and an owner for the next cycle. Scaling may mean extending a successful test. It may also mean maintaining spending while improving conversion or follow-up.
Fill in the decision gate before launching
Create an unfilled test record with the business constraint, evidence supporting it, change under review, primary outcome, observation window, approved spending ceiling and accountable owner. Obtain the target and budget from your actual operating plan; do not copy an industry-looking number without evidence.
Write the conditions for continuing, revising or stopping before the test starts. Include what happens when sales review is incomplete, tracking changes, or service capacity becomes unavailable. Missing evidence should postpone a decision rather than be counted as a favourable result.
For an Egyptian team, check which intake paths actually exist, which language each requires, and whether quotation approval occurs outside sales. Where forms and messaging are both used, document how the original source survives the handoff. Reserve real approval capacity in the calendar. This links the quarterly sequence to the team's documented constraints rather than to an invented business story.
Keep the weekly review practical
Use a short agenda: what changed, what evidence arrived, what remains blocked and who acts next. Avoid switching the primary metric after seeing results, launching several inseparable changes or calling incomplete data a win.
Use the experiment prioritization guide to choose the next test. For help turning a backlog into an owned roadmap, contact Kitely.
