Step 18 · Build & grow
Public chapterLaunch
Position
SwiftBite will open through a merchant-first weekend, using participating restaurants’ existing customer relationships rather than paid consumer acquisition. The founder owns merchant activation and dispatch; the licensed software provider owns production support. Public ordering remains gated on courier-pay compliance, transaction reconciliation, and positive contribution after wage-equivalent top-ups.
Launch plan
| Launch commitment | Binding operating instruction |
|---|---|
| Merchant cohort | Recruit the brief’s 10 independent restaurants inside the existing 4-mile launch radius. Select merchants with responsive owners, reliable kitchens, and active customer channels. |
| Weekend exclusivity | Signed addendum makes SwiftBite each participant’s exclusive third-party delivery checkout during agreed launch windows; collection and dine-in remain unaffected. Review existing aggregator contracts before signing. No continuing exclusivity or automatic renewal. |
| Merchant terms | Commission remains capped at 12%; no launch surcharge, activation charge, or mandatory discount. |
| Consumer terms | Display the $3.99 delivery fee before checkout. Show taxes and optional tips separately; prohibit preselected tips and concealed service charges. |
| Operating windows | October 16–17, 2026, dinner service, 17:00–21:00 local time each day (estimate). |
| Acquisition restriction | Restaurant-owned email, social accounts, website links, packaging inserts, and staff referrals only. No purchased audiences. |
| Timing | Owner | Execution and acceptance record |
|---|---|---|
| October 1–5, 2026 (estimate) | Founder | Secure signed merchant addenda, named kitchen contacts, current menus, payout details, allergen information, and channel permissions. Reject merchants whose exclusivity conflicts with existing agreements. |
| October 6–8, 2026 (estimate) | Founder and vendor implementation lead | Configure merchant-specific storefront links and attribution tags. Confirm service-area rejection, sold-out controls, order acknowledgments, cancellation messages, delivery fees, and capped commission calculations. Complete a real payment, refund, courier assignment, and merchant settlement reconciliation. |
| October 9–11, 2026 (estimate) | Founder and courier lead | Inspect pickup access and delivery boundaries. Run dinner-time routes using actual kitchens. Verify insurance, contractor arrangements, local wage-equivalent calculation, and the vendor’s handling of location outages. |
| October 12–14, 2026 (estimate) | Merchant owners | Publish approved previews and send customers directly to their restaurant’s SwiftBite page. Feature existing popular dishes and optional family bundles; prohibit fabricated savings claims. Founder checks every live link and checkout. |
| October 15, 2026 (estimate) | Founder and vendor support | Conduct a production-like rehearsal. Load-test checkout and dispatch at twice the planned peak (estimate). Test duplicate webhooks, unavailable drivers, payment timeouts, and refunds. Publish a written go/no-go decision. |
| Launch service windows | Founder as incident commander | Open ordering only after kitchen readiness and courier availability checks. Merchants post their direct links at opening. Release remaining customer messages only while dispatch remains green. |
| October 18–20, 2026 (estimate) | Founder and bookkeeper | Reconcile every payment, refund, payout, tip, and courier adjustment. Interview participating owners and review customer complaints. Approve repeat service only after the evidence gate closes. |
Merchant-ready customer message
“Your favourites from [Restaurant] are available for local delivery through SwiftBite this launch weekend. Order directly here: [restaurant link]. Check your address, delivery charge, taxes, and estimated arrival before paying. Collection and dine-in remain available through our usual channels.”
Live control desk
Use the vendor console for dispatch, Stripe for payment records where supported, Grafana Cloud for available vendor telemetry, Slack for incident coordination, and a restricted Google Sheet for the reconciliation ledger. Contractually require production support and access to checkout latency, dispatch events, and failed-order logs.
| Signal | Intervention threshold | Required response |
|---|---|---|
| Checkout latency | Above 2 seconds at the 95th percentile for 5 minutes (estimate) | Vendor investigates; founder pauses additional merchant broadcasts. |
| Dispatch acknowledgment | No routing response within 10 seconds (estimate) | Verify payment state, assign manually, and prohibit blind payment retries. |
| Courier acceptance | Assignment unaccepted after 90 seconds (estimate) | Courier lead contacts available drivers; founder pauses the affected merchant if coverage fails. |
| Paid orders awaiting assignment | More than 3 for 5 minutes (estimate) | Suspend new orders until the queue clears. |
| Customer recovery | Promised arrival missed by 15 minutes (estimate) | Contact customer with an updated arrival or cancellation/refund choice; record responsibility and cost. |
The numbers
| Item | Figure | Basis |
|---|---|---|
| Starting capital | $85,000 | Grounding file |
| Protected personal runway | $67,200 (estimate) | Grounding-file monthly burn multiplied by stated runway |
| Business cash remaining | $17,800 (estimate) | Capital less protected runway |
| Launch spending ceiling | $6,500 (estimate) | Includes setup, licensing, legal checks, rehearsal, support, and operating losses |
| Remaining business reserve | $11,300 (estimate) | Excludes merchant proceeds and customer tips |
| Weekend volume | 120 completed orders (estimate) | Capacity ceiling, not a demand forecast |
| Average restaurant subtotal | $40 (estimate) | Must be validated against participating menus |
| Revenue per order | $8.79 (estimate) | Capped commission on assumed subtotal plus consumer delivery fee |
| Published courier base | $6 per completed delivery (estimate) | Plus wage-equivalent adjustment; tips passed through separately |
| Other variable costs | $1.75 processing; $0.25 software; $0.25 recovery reserve per order (estimates) | Processing allowance includes tax/tip sensitivity; replace with contracted charges |
| Contribution before wage adjustment | $0.54 per order; $64.80 weekend (estimates) | Revenue less listed variable costs |
| Courier coverage | 5 active couriers; 3 deliveries per courier-hour (estimates) | Rehearsal-dependent throughput, not guaranteed earnings |
Decisions and trade-offs
| Decision | Accepted trade-off |
|---|---|
| Protect family runway | Reduce launch scope rather than fund unresolved operating losses from protected cash. |
| Pay the wage-equivalent floor | Calculate adjustments using all accepted availability time, not merely completed-trip time. Obtain local advice on expenses and classification before contracting. |
| Maintain transparent pricing | Improve routing, basket mix, and kitchen readiness rather than exceed the commission cap or add hidden fees. |
| Avoid launch discounts | Test ordinary-price repeatability; warm customers receive convenience, not subsidised demand. |
Do this next
| Action | By when | What proves it worked |
|---|---|---|
| Obtain vendor quote and support commitment | October 5, 2026 (estimate) | Signed scope fits spending ceiling |
| Validate courier model locally | October 8, 2026 (estimate) | Written legal, insurance, and pay-calculation clearance |
| Confirm merchant campaign readiness | October 14, 2026 (estimate) | Signed addenda and tested customer links |
| Authorise opening | October 15, 2026 (estimate) | Rehearsal passes without unresolved critical defects |
Risks in your situation
Merchant followers may not convert; do not treat the volume ceiling as committed revenue. Kitchen concentration can overwhelm couriers despite spare platform capacity; stagger broadcasts and pause individual storefronts. Wage adjustments can erase the narrow contribution margin; reduce service scope rather than underpay. Contractor classification or inadequate vehicle coverage blocks launch until corrected.
Evidence gate
- ☐ Merchant agreements, menu permissions, and exclusivity checks are complete.
- ☐ Checkout, routing, refunds, and settlements reconcile without unexplained differences.
- ☐ Courier payments meet the verified local floor, excluding tips.
- ☐ Actual contribution remains positive after adjustments and recovery costs.
- ☐ Vendor incidents are resolved and customer complaints assigned.
- ☐ Repeat-service spending remains inside unprotected business cash.
Illustrative figures · validate before actingNext: Distribution