Step 2 · Discover
Public chapterThe business idea
Where the founder stands
SwiftBite is a localized delivery platform connecting independent restaurants with consumers via community-based drivers, charging a transparent, capped 12% merchant fee instead of the industry-standard 30%.
What's at stake: Defining the exact fee structure and localized focus prevents the business from attempting to compete globally with multi-billion-dollar incumbents, focusing purely on underserved mid-sized cities.
Position
SwiftBite’s initial position is merchant-margin protection within a tightly bounded delivery area, not citywide coverage or discount-led customer acquisition. The founder’s merchant relationships provide the initial sales channel; software will be licensed. Launch remains conditional on verified courier economics, lawful contractor arrangements, and sufficient operating cash after personal living costs.
Idea Canvas covering the problem
| Canvas element | SwiftBite operating commitment |
|---|---|
| First merchant | Independent restaurant owners generating $25,000–$60,000 monthly revenue, already using national aggregators and able to provide delivery statements. Founder-connected operators with dependable preparation times and food that travels reliably sign first. |
| Merchant margin crisis | Existing aggregators retain 30% of delivery food sales under the grounding assumption. Each prospect's actual statement deductions are captured during onboarding; the headline commission is not treated as their full delivery cost. |
| Merchant promise | Commission never exceeds 12% of the food subtotal after merchant-authorized discounts, excluding taxes and tips. No activation charge, compulsory advertising purchase, payment-processing surcharge, exclusivity requirement, or fee-cap exception. |
| Consumer promise | A clearly displayed $3.99 delivery fee, with taxes, food prices, minimum basket, and optional tip visible before checkout. No service surcharge, preselected tip, misleading discount, or undisclosed restaurant-menu markup. |
| Geographic boundary | SwiftBite operates within a 4-mile-radius launch zone covering downtown and the adjacent neighbourhoods. Dispatch rejects addresses outside the boundary before payment authorization. |
| Merchant value | More retained delivery revenue without requiring a proprietary ordering build. SwiftBite supplies licensed ordering, dispatch, merchant reporting, and founder-led local support. Increased merchant profit remains contingent on food costs, incremental demand, and operating performance. |
| Consumer value | Reliable access to independent neighbourhood restaurants, a predictable delivery charge, and an identifiable local support contact. The offer does not depend on being cheaper than every competitor on every basket. |
| Courier commitment | Delivery compensation is shown before acceptance and all tips are remitted to couriers separately. A local-minimum-wage-equivalent floor is maintained through automatic top-ups, without counting tips toward the floor. |
| Launch assortment | Restaurants are recruited in compact pickup clusters rather than for catalogue size. Merchants whose preparation delays or packaging failures make service unreliable stay off the platform until corrective trials succeed. |
| Acquisition | Founder-led merchant visits, permission-based outreach to existing relationships, restaurant counter signage, receipt inserts, and merchant-owned customer channels. SwiftBite never scrapes aggregator customer data or asks merchants to breach existing agreements. |
Merchant agreement. Every merchant signs SwiftBite's nonexclusive Merchant Service Agreement: either party terminates on 30 days' written notice; settlements pay weekly every Tuesday with an itemized statement and downloadable order CSV; commission is reversed in full on refunded food value. SwiftBite absorbs every courier-caused loss. Merchant-caused refunds are charged back only with photo or timestamp evidence, and the merchant has 7 days to appeal. Any future add-on service is opt-in and is billed inside the 12% cap, never on top of it.
Dispatch procedure. SwiftBite takes orders only inside published service windows that have confirmed courier coverage. The licensed dispatch system timestamps acceptance, restaurant arrival, pickup, and handoff on every order. Courier earnings are calculated on engaged time — pickup waiting, delivery travel, and repositioning — not moving time alone. When live coverage cannot meet both the delivery promise and the earnings floor, ordering closes automatically until coverage returns.
Demand record. The founder maintains a dated Airtable register of merchant interviews, public commission complaints, local news, and consented customer feedback. Each entry carries the source link, locality, stated problem, current provider, and willingness to transact. The founder reviews it every Monday and reports general frustration separately from signed merchant commitments and paid orders. Public criticism alone does not authorize launch spending.
The numbers
| Item | Figure | Basis |
|---|---|---|
| Starting capital | $85,000 | Grounding file; personal and family capital |
| Personal cash requirement | $67,200 (estimate) | Stated $4,800 monthly burn multiplied by stated 14-month runway |
| Residual venture cash | $17,800 (estimate) | If personal expenses draw from the same starting capital; not yet an approved operating budget |
| Illustrative food basket | $30.00 (estimate) | Validation assumption; excludes tax and tip |
| Merchant commission | $3.60 (estimate) | Capped 12% applied to illustrative basket |
| Consumer delivery fee | $3.99 | Grounding file |
| Platform revenue/order | $7.59 (estimate) | Commission plus delivery fee |
| Merchant retained food revenue | $26.40 versus $21.00 (estimate) | SwiftBite versus stated 30% comparator; before restaurant costs |
| Merchant retained-revenue improvement | $5.40/order (estimate) | Difference on illustrative basket |
| Courier base/order | $5.25 (estimate) | Proposed published rate; wage-floor top-ups remain additional |
| Payment processing/order | $1.29 (estimate) | Assumed 2.9% plus $0.30 on food and delivery charge |
| Routing/order | $0.25 (estimate) | Unquoted variable software allowance |
| Refund/support allowance/order | $0.35 (estimate) | Pilot assumption |
| Additional processing allowance/order | $0.10 (estimate) | Provisional allowance for taxes and tips; reconcile actual charges |
| Contribution/order | $0.35 (estimate) | Before courier top-ups, fixed costs, and acquisition spending |
| Launch minimum food basket | $30.00 (estimate) | Provisional control; insufficient if actual costs exceed assumptions |
| Month 12 targets | 50 merchants; 300 orders/day | Grounding file |
| Monthly contribution at target | $3,150 (estimate) | Assumes 30 operating days and illustrative contribution |
| City break-even target | Month 18 | Grounding file; requires verified fixed-cost budget |
Decisions and trade-offs
| Decision | Accepted trade-off |
|---|---|
| Keep the commission cap unconditional | Reduce service availability before transferring overruns into merchant surcharges. |
| License rather than build | Accept limited customization; require data export, fee transparency, and termination rights before signing. |
| Start with a disclosed minimum basket | Lose some small orders rather than subsidize structurally negative deliveries. |
| Hold a compact service footprint | Decline distant demand until measured route economics support expansion. |
| Delay paid acquisition | First establish repeat ordering and contribution after actual compensation top-ups. |
Do this next
| Action | By when | What proves it worked |
|---|---|---|
| Founder obtains merchant delivery statements and signs conditional agreements | Before software commitment | Redacted statements reconcile commissions, refunds, and settlement deductions |
| Founder secures itemized software and processor quotes | Before contracting | Fixed charges, variable charges, export rights, and cancellation terms documented |
| Local counsel reviews courier classification, wage obligations, insurance, and tax treatment | Before courier recruitment | Written jurisdiction-specific clearance or revised operating arrangement |
| Founder runs paid route trials with participating merchants | Before public launch | Timestamped trips, actual courier earnings, refunds, and positive contribution recorded |
| Bookkeeper separates personal reserves from venture cash | Before launch authorization | Cash forecast funds setup, settlements, contingencies, and operating losses |
Risks in your situation
The largest immediate exposure is capital ambiguity: stated personal runway does not establish business runway. Merchant settlements must remain segregated from spending money.
Courier economics are fragile. Waiting, sparse demand, insurance requirements, or compensation top-ups can eliminate the illustrated contribution. Contractor status requires local review; a contractual label cannot override working conditions.
Commission dissatisfaction may not translate into consumer switching. Restaurants may sign without generating orders, while customers retain incumbent subscriptions. Track paid repeat use rather than merchant enthusiasm.
Evidence gate
- ☐ Merchant statements substantiate the commission problem and proposed retained-revenue improvement.
- ☐ Executable merchant terms preserve the cap without compulsory add-ons.
- ☐ Courier arrangements satisfy local requirements and the published earnings floor.
- ☐ Paid trials show positive contribution after actual variable costs and top-ups.
- ☐ Software contracts and checkout screens support every pricing commitment.
- ☐ Cash reserves and the city fixed-cost budget support launch without using merchant settlement funds.