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 10 · Prepare

Public chapter

Business concept statement

Position

SwiftBite’s position is merchant margin protection, enforced through its commission cap, transparent consumer pricing, and published courier compensation. The concept is ready for merchant validation, but dispatch economics, local courier compliance, and the launch funding allocation remain unverified. Expansion, custom software, and commission increases are outside the launch mandate.

Executive-level business concept statement and one-sentence version

SwiftBite is a hyper-local delivery business for independent restaurants whose margins are being eroded by national aggregator commissions. It replaces excessive merchant charges with a transparent, capped commission and a plainly disclosed consumer delivery fee, using licensed batching and routing software to coordinate deliveries within a tightly bounded service area. Its commercial promise is straightforward: protect restaurant margins without hiding charges from customers or pushing uneconomic work onto couriers.

Commercial commitmentLaunch position
Merchant commissionCapped at 12%, versus the grounding-file comparator of 30%
Consumer delivery fee$3.99
Initial marketOne mid-sized North American city of approximately 150,000 people
Delivery boundaryFour-mile radius covering downtown and two adjacent neighbourhoods
Initial merchant profileIndependent restaurants generating $25,000–$60,000 monthly revenue

The initial merchant is an owner-operated restaurant already selling delivery meals but dissatisfied with the share of revenue surrendered to aggregators. SwiftBite’s offer addresses that existing pain rather than asking restaurants to adopt an unfamiliar revenue model. Merchant acquisition will be founder-led, drawing on established local relationships and field-sales experience. Onboarding will use the restaurant’s actual delivery statements, menu, preparation times, and operating hours to establish a commercially credible service agreement.

The merchant agreement will prohibit charges that circumvent the advertised commission cap. Commission will apply to the food subtotal, excluding taxes, tips, and the consumer delivery fee; refunds will reverse the associated commission. Customers will see the delivery fee before checkout, with no undisclosed service surcharge or preselected gratuity. Courier tips will pass through intact and will not count toward SwiftBite’s minimum-pay obligation.

Couriers will use their own vehicles and receive a published per-delivery rate, backed by a local minimum-wage-equivalent floor. SwiftBite will record assigned service time, including restaurant waiting time, and fund required top-ups rather than relying on tips. Contractor status remains subject to local legal review; the launch will not proceed on an unsupported classification assumption.

Licensed software will handle ordering, dispatch, and route batching. Batching is permitted only when preparation readiness and quoted delivery windows support it; it is not a justification for chronic waiting or cold food. The founder will own merchant relationships and daily operating decisions, with contracted technical support responsible for configuration and integration.

Growth will follow delivery density and verified contribution, not geographic coverage alone. SwiftBite will remain within its launch boundary until completed-order economics support the published merchant and courier promises. No forecast saving, service claim, or profitability statement will enter merchant-facing materials without supporting records.

The numbers

All operating assumptions below require validation before becoming budget commitments.

ItemFigureBasis
Founder experience12 yearsGrounding file; local FMCG and field sales
Starting capital$85,000Personal and family capital
Personal burn and stated runway$4,800/month; 14 monthsGrounding file; not a verified company runway
Personal reserve requirement$67,200 (estimate)Stated burn multiplied by stated runway
Capital remaining after that reserve$17,800 (estimate)Before launch costs and business losses
Illustrative food subtotal$30.00 (estimate)Assumption, not observed basket data
Merchant commission per illustrative order$3.60 (estimate)Capped rate applied to food subtotal
Platform revenue per illustrative order$7.59 (estimate)Commission plus consumer delivery fee
Published base courier payout$4.75/delivery (estimate)Proposed rate; wage-floor top-ups additional
Payment processing$1.29/order (estimate)Assumed 2.9% plus $0.30 (estimate), applied to subtotal and delivery fee; tax and tip processing excluded
Variable software and support/refund allowance$0.60/order (estimate)Provisional combined allowance
Illustrative contribution$0.95/order (estimate)Before wage top-ups and omitted processing costs
Launch contribution targetPositive from month 1Grounding-file requirement; actual variable costs included
Growth target50 merchants; 300 orders/day by month 12Grounding file
Illustrative monthly fixed-cost capacity$8,550 (estimate)Target daily volume, 30-day month (estimate), illustrative contribution; before omitted costs
City break-even deadlineMonth 18Grounding-file target; requires a fully costed city budget

Decisions and trade-offs

DecisionBinding treatment
Protect commission capNo merchant-funded payment surcharge, mandatory marketing charge, or dispatch supplement outside the cap
License rather than buildReject proprietary development commitments; require usable order, settlement, and courier exports
Maintain courier floorRestrict service windows or pause loss-making dispatch patterns rather than underpay
Preserve geographic disciplineDecline out-of-zone delivery requests until expansion economics are approved
Retain launch entityOperate as a single-member LLC; convert to a C-Corp if institutional funding is raised
Separate personal and operating cashApprove both budgets explicitly; never finance operations with merchant settlements or courier amounts payable

Do this next

ActionBy whenWhat proves it worked
Founder tests the opening statement with target restaurant ownersBefore publishing onboarding materialsInterview notes show owners can independently restate the fee promise and dispatch mechanism
Local counsel reviews merchant terms, courier status, insurance, and pay-floor calculationBefore signing service contractsWritten review and corrected agreements
Founder obtains vendor and processor quotesBefore committing launch capitalExecutable pricing schedules replace provisional allowances
Founder runs paid, bounded dispatch trialsBefore public launchSettlement records demonstrate positive contribution after waiting-time top-ups and refunds
Founder reviews Google Keyword Planner and Google TrendsBefore each messaging revisionDated local-query export; wording changes supported by observed language, not invented search demand

Risks in your situation

The founder’s merchant access is an advantage, but technical dependence is concentrated in the licensed vendor. Require settlement reconciliation, data export, support escalation, and termination assistance in the contract.

The stated personal runway leaves limited operating capital if fully reserved. Vendor deposits, insurance, refunds, and settlement timing could exhaust that balance before sustainable density emerges. Launch approval requires a funded cash forecast, not merely positive illustrative contribution.

Batching may fail when preparation times vary or demand disperses. Actual courier waiting time and wage top-ups must remain visible in contribution reporting. Merchant savings must be described as fee differences, not guaranteed incremental profit or guaranteed demand.

Evidence gate

  • ☐ Target merchants accurately paraphrase the commercial promise without prompting.
  • ☐ Signed terms preserve the commission cap and prohibit hidden consumer charges.
  • ☐ Local review supports courier classification, insurance, and the published pay-floor procedure.
  • ☐ Paid trial records establish positive contribution using complete variable costs.
  • ☐ Vendor quotations and cash forecasts support the launch without using settlement liabilities.
  • ☐ Search-language evidence is dated and locally relevant; unsupported demand claims are removed.
  • ☐ The same approved opening appears in pitch, press, and onboarding materials.
Illustrative figures · validate before actingNext: Business model

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