Step 26 · Build & grow
Public chapterGrowth and scaling
Position
SwiftBite will scale merchant density and courier utilisation inside its existing launch zone before expanding geography. The preferred route is company-operated organic growth supported by nonexclusive merchant partnerships, not franchising or acquisition. Expansion remains unfunded until measured contribution, delegated operations, and unrestricted cash pass the gates below.
Growth thesis, capacity plan (staff, machinery, facilities),
The founder owns merchant acquisition, commercial terms, and capital allocation. Restaurant onboarding will favour adjacent pickup clusters, reliable preparation times, and incremental delivery demand rather than merchant count alone. No geographic expansion may dilute courier earnings or require a higher merchant commission.
| Stage | Capacity and staffing | Investment release |
|---|---|---|
| Instrument launch: months 1–3 (estimate) | Founder handles merchant sales and dispatch; contracted software vendor handles configuration and technical support | Setup allowance only; merchant acquisition spending requires positive measured order contribution |
| Build density: months 4–9 (estimate) | Recruit a part-time operations lead; maintain a vetted courier reserve; concentrate promotion around existing pickup clusters | Release operating buffer against a rolling cash forecast, not registration growth |
| Reach target: month 12 | Serve 50 merchants and 300 orders/day; schedule peak courier coverage from actual hourly demand | Staffing increases require contribution coverage or explicitly funded ramp losses |
| Establish city profitability: month 18 | Operations lead owns dispatch, incidents, courier onboarding, and merchant service | No adjacent-market commitment before city break-even and readiness approval |
| Replicate: after readiness approval | Appoint a local operating lead before signing merchants outside the original zone | Ring-fence the new market’s ramp capital before contracting |
The operations lead maintains the playbook in Notion: merchant acceptance, preparation-time updates, courier identification, food handling, missing-order resolution, refunds, weather suspension, and earnings reconciliation. Couriers receive paid practical onboarding and must demonstrate the incident procedure before activation. The founder audits exception logs but does not remain the default dispatcher.
| Capacity component | Initial operating specification |
|---|---|
| Service footprint | Existing 4-mile launch radius; no automatic radius increases |
| Peak demand assumption | 65% of daily orders within 4 peak hours (estimate) |
| Courier productivity | 3.6 deliveries per engaged hour (estimate), subject to route trials |
| Peak availability | 17 couriers, including 25% headroom (estimate) |
| Recruitment pool | 24 vetted couriers (estimate), with availability confirmed before each peak |
| Vehicles and equipment | Courier-owned vehicles; insulated bags and phone mounts verified at onboarding; no fleet purchases |
| Facilities | Remote dispatch; no depot, kitchen, or leased office |
| Software | Licensed white-label ordering and routing; require capacity alerts, order exports, earnings records, permissions, and audit logs |
Publish the courier delivery rate before each service period. Reconcile earnings against the applicable local minimum-wage equivalent, including platform-required waiting and availability time; pay any shortfall and include it in order contribution. Local counsel must approve contractor classification, insurance requirements, and the time-accounting method before recruitment scales.
| Load-control threshold | Required response |
|---|---|
| On-time delivery below 95% over a rolling week (estimate) | Freeze promotional acquisition; correct pickup and routing bottlenecks |
| Unassigned orders above 5% for 15 minutes (estimate) | Stop accepting incremental orders until capacity recovers |
| Refunds and credits above 2% of weekly orders (estimate) | Operations lead investigates merchant, courier, and software causes |
| Contribution below $0.75/order over 4 weeks (estimate) | Freeze discretionary growth; retain the commission cap and earnings floor |
Partnership contracts remain nonexclusive, prohibit resale of customer data, and require attributable order reporting. Restaurant associations may introduce merchants but receive no authority over fees, courier pay, or refunds. Any future JV must give SwiftBite approval rights over these policies, access to transaction-level records, and termination rights for concealed charges or underpayment.
The numbers
All scenario contribution excludes sales-tax collections, tips, and merchant settlement funds. Payment-cost assumptions require validation against actual taxable checkout totals and processor terms.
| Item | Figure | Basis |
|---|---|---|
| Starting capital | $85,000 | Grounding file |
| Personal reserve | $67,200 (estimate) | Stated $4,800 monthly burn multiplied by 14 months |
| Available venture capital | $17,800 (estimate) | Starting capital less personal reserve |
| Initial allocation | Setup $4,500; acquisition $2,500; operating/settlement buffer $10,800 (estimates) | Total available venture capital; spending ceilings, not quotations |
| Assumed food basket | $32 (estimate) | Planning assumption requiring order evidence |
| Revenue/order | $7.83 (estimate) | Capped 12% commission plus stated $3.99 delivery fee |
| Variable costs/order | Courier $5.25; processing $1.35; support/refunds $0.40 (estimates) | Courier rate is provisional; add earnings top-ups when incurred |
| Contribution/order | $0.83 (estimate) | Revenue less listed variable costs |
| Mature city overhead/month | $8,000 (estimate) | Operations lead $3,200; overflow $1,600; software $1,200; insurance/accounting $1,000; marketing $1,000 (estimates) |
| Month-12 contribution/month | $7,470 (estimate) | Target 300 orders/day × 30-day month (estimate) × modeled contribution |
| City break-even volume | 322 orders/day (estimate) | Mature overhead divided by modeled contribution and month length |
| Month-18 planning volume | 350 orders/day (estimate) | Produces $715 monthly city surplus (estimate), excluding founder drawings |
Decisions and trade-offs
| Route | Decision and release condition |
|---|---|
| Organic density | Approve within the launch zone; prioritise repeat orders and clustered pickups |
| Owned new location | Preferred replication route after funded readiness; maintain separate market accounts |
| Strategic alliance | Approve nonexclusive referrals; compensation must fit measured contribution |
| Franchising | Defer: operating consistency and franchise compliance remain unproven |
| Brand/method licensing | Defer: insufficient independently repeatable operating evidence |
| JV | Consider only with committed cash, named local leadership, reserved policy rights, and a documented deadlock exit |
| Acquisition | Reject during launch; no capital allocated to goodwill or integration |
Do this next
| Action | By when | What proves it worked |
|---|---|---|
| Founder obtains vendor and processor quotations | Before software commitment | Signed terms reconcile to the contribution model |
| Counsel validates courier arrangements | Before scaled recruitment | Written classification, insurance, and earnings-accounting approval |
| Operations lead tests peak routes and downtime procedures | Before promotional expansion | Logged delivery times, earnings, and recovery results |
| Founder prepares weekly cash forecast | Before each investment release | Merchant liabilities and personal reserves remain protected |
| Operations lead runs without founder intervention | Before geographic approval | Full-week incident log and service report pass thresholds |
Risks in your situation
Small baskets, dispersed pickups, and wage top-ups can erase the modeled margin. Personal reserves are not growth capital, and city break-even excludes founder living costs. Funding beyond the stated runway therefore needs an explicit plan. Contractor reclassification or software outages require immediate financial reforecasting, not weaker service standards.
Evidence gate
- ☐ Actual contribution clears the stated threshold after all earnings adjustments.
- ☐ Service quality holds under peak load.
- ☐ The operation passes the founder-absence test.
- ☐ Playbooks, vendor exports, and settlement reconciliations are complete.
- ☐ New-market ramp funding and continuing founder living costs are separately covered.
- ☐ Every expansion contract preserves capped commissions, transparent pricing, and the courier earnings floor.