startup flir

Public plan · illustrative example

SwiftBite Hyper-Local Delivery

An illustrative end-to-end venture plan for a lower-fee, community-based restaurant delivery network.

Sector

Logistics & Food Technology

Market

Mid-Sized Urban Centers

Chapters

30

Status

Public · read only

How to read this: this is a worked operating plan for one venture. Figures, legal structures and forecasts are illustrative and must be validated against your own market before you act on them.

Build mine

Step 2 · Discover

Public chapter

The business idea

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 elementSwiftBite operating commitment
First merchantIndependent restaurant owners generating $25,000–$60,000 monthly revenue, already using national aggregators and able to provide delivery statements. Prioritize founder-connected operators with dependable preparation times and food that travels reliably.
Merchant margin crisisExisting aggregators retain 30% of delivery food sales under the grounding assumption. Validate each prospect’s actual deductions rather than treating the headline commission as their complete delivery cost.
Merchant promiseCommission 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 promiseA 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 boundaryOperate within the specified 4-mile-radius launch zone covering downtown and the adjacent neighbourhoods. Dispatch must reject addresses outside the boundary before payment authorization.
Merchant valueMore 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 valueReliable 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 commitmentPublish delivery compensation before acceptance; remit all tips to couriers separately. Maintain a local-minimum-wage-equivalent floor through automatic top-ups, without counting tips toward the floor.
Launch assortmentRecruit restaurants into compact pickup clusters rather than maximizing catalogue size. Exclude merchants whose preparation delays or packaging failures make service unreliable until corrective trials succeed.
AcquisitionFounder-led merchant visits, permission-based outreach to existing relationships, restaurant counter signage, receipt inserts, and merchant-owned customer channels. Do not scrape aggregator customer data or require merchants to breach existing agreements.

Merchant agreement. Use a nonexclusive agreement with termination on written notice, weekly itemized settlements, downloadable order records, and a published refund-allocation policy. Reverse commission on refunded food value. SwiftBite bears courier-caused loss; merchant-caused refunds require documented evidence and an appeal route. Any optional future service must remain genuinely optional and cannot circumvent the commission cap.

Dispatch procedure. Offer service only during published periods with confirmed courier coverage. The licensed system must record acceptance, restaurant arrival, pickup, and handoff. Measure pickup waiting, delivery travel, and required repositioning or availability time; do not calculate the earnings floor from moving time alone. Where coverage cannot meet both service and compensation commitments, close ordering temporarily.

Demand record. The founder maintains a dated Airtable register of merchant interviews, public commission complaints, local news, and consented customer feedback. Record links, locality, stated problem, current provider, and willingness to transact. Review it weekly, separating general frustration from signed merchant commitments and paid orders. Public criticism alone does not authorize launch spending.

The numbers

ItemFigureBasis
Starting capital$85,000Grounding 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.99Grounding 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 targets50 merchants; 300 orders/dayGrounding file
Monthly contribution at target$3,150 (estimate)Assumes 30 operating days and illustrative contribution
City break-even targetMonth 18Grounding file; requires verified fixed-cost budget

Decisions and trade-offs

DecisionAccepted trade-off
Keep the commission cap unconditionalReduce service availability before transferring overruns into merchant surcharges.
License rather than buildAccept limited customization; require data export, fee transparency, and termination rights before signing.
Start with a disclosed minimum basketLose some small orders rather than subsidize structurally negative deliveries.
Hold a compact service footprintDecline distant demand until measured route economics support expansion.
Delay paid acquisitionFirst establish repeat ordering and contribution after actual compensation top-ups.

Do this next

ActionBy whenWhat proves it worked
Founder obtains merchant delivery statements and signs conditional agreementsBefore software commitmentRedacted statements reconcile commissions, refunds, and settlement deductions
Founder secures itemized software and processor quotesBefore contractingFixed charges, variable charges, export rights, and cancellation terms documented
Local counsel reviews courier classification, wage obligations, insurance, and tax treatmentBefore courier recruitmentWritten jurisdiction-specific clearance or revised operating arrangement
Founder runs paid route trials with participating merchantsBefore public launchTimestamped trips, actual courier earnings, refunds, and positive contribution recorded
Bookkeeper separates personal reserves from venture cashBefore launch authorizationCash 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.
Illustrative figures · validate before actingNext: Opportunity assessment

Build from your reality

Your numbers, your city, your constraints.

SwiftBite shows the depth and sequence of a finished plan. Yours is written from your own grounding file.

Start my plan