SwiftBite Hyper-Local Delivery

Position

SwiftBite proceeds as a founder-operated delivery business, not a passive-income investment. The founder’s merchant relationships and field-sales experience support recruitment; launch remains conditional on affordable dispatch coverage, protected household reserves, and enforceable courier-pay safeguards.

Founder profile

Founder commitment

I accept responsibility for merchant acquisition, dispatch escalation, customer recovery, courier-payment reconciliation, and vendor accountability. My motivation is to preserve independent restaurants’ delivery margins without transferring the cost to underpaid couriers or misleading consumer charges.

I will personally handle angry merchants, missing couriers, failed handoffs, and refund disputes. I will not promise uninterrupted availability, subsidize unviable orders indefinitely, or treat exhaustion as evidence of commitment.

Operational bandwidth

The following is my proposed launch operating envelope, subject to merchant demand and funded relief coverage.

During delivery windows, dispatch takes precedence over sales meetings. Merchant onboarding occurs outside those windows. Couriers are not treated as unpaid dispatchers, and family members are not assumed to provide free operational cover.

The licensed platform is the order system of record. A restricted-access Google Sheets incident register records the merchant, courier, promised handoff, actual outcome, refund, owner, and corrective action. Personal customer details remain in the licensed platform rather than being copied into the register.

Capital risk tolerance

My maximum initial capital exposure is the stated personal and family commitment. Household reserves are ring-fenced; business losses do not automatically authorize their use.

Before deployment, the founder and each family contributor document whether funds are gifts, loans, or equity-compatible contributions. Counsel reviews any ownership promise against the single-member LLC structure.

Operational ban

SwiftBite will not accept orders without feasible courier coverage, conceal mandatory checkout charges, breach the merchant commission cap, or allow courier earnings to fall below the local minimum-wage equivalent. The published courier schedule must include waiting-time treatment and any required earnings top-up.

The founder will not build custom routing software, personally patch production code, or accept a vendor contract without data-export rights, support escalation terms, and a documented outage procedure.

Each service day ends with an incident review and a plain-language strain entry: manageable, stretched, or unsafe. An unsafe entry triggers relief coverage or service closure, not a longer shift. Repeated stretched entries trigger reduced service availability before further recruitment.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Merchant relationships may encourage unpaid exceptions and unrealistic availability promises. The founder must log concessions and refuse commitments outside funded coverage.

The reserve calculation exposes a narrow business budget. Missing insurance, licensing, legal or vendor deposits must reduce launch scope rather than consume protected household cash.

Industry burnout anecdotes are not operating evidence. The founder reviews dated local courier feedback, credible labour-market reporting and the internal strain register together; no fatigue benchmark is adopted without a source and relevant geography.

Evidence gate

• ☐ Founder accepts hands-on escalation duties and signs the workload limits.
• ☐ Personal reserves and family funding terms are documented.
• ☐ Local courier-pay safeguards and contractor arrangements have professional review.
• ☐ Quoted launch costs fit available business capital.
• ☐ Dispatch relief or explicit service-closure procedures are executable.
• ☐ Vendor outage and customer-recovery rehearsals are complete.
• ☐ Unfunded runway beyond the personal reserve is acknowledged, not assumed away.

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

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

Decisions and trade-offs

Do this next

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.

Position

SwiftBite’s opportunity remains conditional: the supplied record contains no named launch city, verified restaurant census, or merchant commitments. Existing merchant relationships support direct prospecting but do not establish transferable delivery demand. Routing contracts and courier screening remain blocked until the founder verifies the addressable merchant base, customer migration evidence, and local delivery economics.

Localized opportunity profile

Market boundary and current finding

The census covers restaurant pickup addresses inside the launch boundary, not the entire metropolitan area. The founder must anchor the radius to a named downtown dispatch point and retain the resulting map with the restaurant register.

Restaurant register

The founder owns an Airtable register assembled from municipal food-premises records, public health inspection listings, business licences, and restaurant websites. Google Maps supplies discovery leads, not final eligibility evidence. QGIS determines boundary inclusion; Google Sheets holds the reconciled demand model.

Each record must contain trading name, legal operator, pickup address, owner contact, operating status, independent ownership confirmation, monthly revenue band, current delivery channels, opening hours, cuisine, current delivery order volume, delivery-ready menu, and evidence date. Separate pickup locations remain separate supply records; an owner-level field prevents overstating independent buying decisions.

Exclude chains, permanently closed premises, addresses outside the boundary, and vendors unable to fulfil delivery orders during proposed dispatch hours. Retain excluded records with reasons rather than deleting them.

Merchant demand ledger

The founder interviews owners using their recent channel statements, not citywide delivery averages. Each owner identifies customers reachable through consented email, direct-order channels, receipt inserts, or restaurant-owned social accounts. Aggregator customer data is excluded unless reuse is expressly permitted.

Conditional agreements specify the advertised commission cap, published consumer delivery fee, no exclusivity, no onboarding payment before launch acceptance, and merchant approval of migration materials. Statements must distinguish existing delivery demand from genuinely transferable demand.

No prospect-pool assumption substitutes for the completed census. If the verified pool is smaller, the founder must demonstrate stronger conversion or reject the boundary as commercially insufficient.

A merchant-assisted trial uses existing lawful fulfilment arrangements and separately tagged restaurant links. Record completed paid orders, repeat orders, merchant source, delivery address, basket value, and acquisition expense. Survey intent and free promotional orders do not count as transferred demand.

The numbers

The following is a provisional, rounded cash-contribution model; taxes and tips are excluded from revenue. Payment processing assumes SwiftBite processes the basket and delivery fee.

Decisions and trade-offs

Do this next

Risks in your situation

Restaurant closures can shrink both supply and repeat demand. The founder checks licence changes, inspection status, and merchant confirmation monthly, marking temporary closures separately from permanent exits.

Evidence gate

• ☐ Named city, dispatch point, and boundary are recorded.
• ☐ Exact eligible count is reconciled to address-level evidence.
• ☐ Required merchant commitments include concrete migration actions.
• ☐ Paid-order evidence supports the demand forecast.
• ☐ Courier terms satisfy local classification and wage requirements.
• ☐ Quoted costs support positive contribution from launch.
• ☐ Cash coverage reaches the planned city break-even date.

Position

SwiftBite’s capped-fee model is conditionally feasible, not yet commercially validated. The standard-order model leaves a narrow positive contribution, but courier productivity, lawful compensation and contracted insurance costs remain unverified. Merchant recruitment can continue; paid delivery launches only after measured costs clear the contribution and driver-pay gates.

Feasibility report with market sizing

The founder owns the contribution ledger and courier settlement process. Amounts below use the venture’s stated dollar denomination; jurisdiction, currency, taxes and statutory obligations must be confirmed before contracts are signed.

Tips pass entirely to couriers and never offset base compensation. Tax collections are excluded from revenue; processing costs on taxes and tips must be added from actual settlement statements. Merchant settlement cannot absorb software, processing or insurance surcharges beyond the advertised commission cap.

Courier compensation is the binding constraint. Publish the base payout and adjustment formula before accepting courier commitments. Record availability, assignment, pickup, handoff, repositioning and attributable mileage in the licensed dispatch system. Reconcile earnings against all scheduled available time, including restaurant waits and empty repositioning; use any broader legally required definition.

The settlement formula is the greater of published delivery earnings or the applicable wage floor multiplied by covered hours plus attributable vehicle costs. Pay any shortfall with the regular weekly settlement, even when it makes contribution negative. Do not use unpaid waiting, tips or optimistic batching assumptions to pass this test.

The founder exports completed orders, refunds, processor charges, courier time and mileage into a locked Google Sheets ledger after each operating day. Reconcile every order to the processor and merchant payable; accrue insurance, support and licensing charges before reporting contribution.

SwiftBite applies a prominently disclosed minimum food basket instead of any small-order surcharge. Exceptional-distance, redelivery and cancellation terms appear before checkout; dispatch rejects any order whose modeled compensation requirement consumes its contribution.

The numbers

Decisions and trade-offs

The founder’s sales capacity supports recruitment, not an assumption of free dispatch labour. Operations coverage must be quoted against actual opening hours and order peaks.

Do this next

Risks in your situation

The unnamed jurisdiction prevents confirmation of minimum wage, contractor legality and insurance requirements. Personal vehicle policies may exclude delivery; neither courier declarations nor the modeled insurance allowance establishes coverage.

The launch radius does not establish route productivity. Restaurant delays, weak demand and empty return travel can erase the modeled margin. Pause affected service windows rather than underpay couriers or exceed the merchant cap.

Evidence gate

• ☐ Actual processor, software and insurance terms replace allowances.
• ☐ Paid pilot clears contribution after wage top-ups, refunds and waiting time.
• ☐ Courier classification, coverage and compensation receive local professional approval.
• ☐ Staffing quotations support promised operating hours.
• ☐ Cash forecast funds settlements without borrowing merchant or tax balances.
• ☐ Measured demand supports city break-even within the grounded target horizon.

Position

SwiftBite is merchant-sales ready but not technically or operationally launch-ready. The founder owns merchant acquisition and commercial decisions; software configuration, payment reconciliation, courier compliance, and incident response remain uncovered capabilities. Launch authority stays with the founder, conditional on a licensed stack passing the acceptance tests and a funded operating budget preserving the merchant commission cap and driver earnings floor.

Founder-and-team capability map

Licensing mandate

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

The founder is the sales engine and operational bottleneck. Uncovered service hours must remain closed.

The apparent capital runway can conceal a much smaller venture budget. Insurance deposits, processor holds, or courier true-ups may exhaust available cash before merchant acquisition produces sufficient density.

Vendor dependence is acceptable only with tested exports and a workable shutdown procedure. A low subscription quote does not compensate for inaccessible transaction data or unreliable settlement.

Evidence gate

• ☐ Founder signs the resource matrix and names relief coverage.
• ☐ Licensed workflows pass acceptance without custom engineering.
• ☐ Counsel clears courier classification, earnings methodology, and insurance.
• ☐ Merchant and consumer charges match published terms.
• ☐ Reconciled pilot orders demonstrate positive contribution after earnings true-ups.
• ☐ Fully loaded cash forecast supports launch and the grounded city break-even target.
• ☐ Vendor exit, data export, and outage procedures are tested.

Position

SwiftBite’s independent-contractor launch remains conditional on a location-specific legal clearance; the grounding file names neither the city nor its governing jurisdiction. Merchant pricing and courier wage protections remain fixed constraints: an adverse classification finding triggers an operating redesign or launch hold, not higher merchant commissions or reduced courier protections.

PESTLE-informed opportunity and threat map with implications for the plan

Regulatory register status

Classification and labor forecast

Counsel must assess the actual dispatch workflow, not merely approve an independent-contractor agreement. Review merchant-to-courier assignment, delivery acceptance, substitution, route discretion, competing-platform work, equipment ownership, complaint handling and deactivation. SwiftBite must not promise courier independence while configuring mandatory shifts, exclusive service or punitive acceptance-rate rules.

The courier agreement will publish the delivery rate and reconciliation method. Tips will not offset SwiftBite’s pay floor. The operating ledger will capture dispatch availability, acceptance, pickup, completion, cancellations, waiting and payout adjustments. Counsel must determine which intervals and expenses enter the local wage-equivalent calculation; “active delivery time” will not be assumed sufficient.

Municipal and tax register

Monitoring and escalation

The founder will maintain a shared regulatory register linked to official legislative trackers, labor-agency notices, municipal agendas and tax-authority bulletins. Each entry must contain the primary-source link, legal status, effective date, affected workflow, reviewer and implementation evidence. News coverage and organizing announcements are signals, not proof of enacted obligations.

The numbers

Illustrative economics are sensitivities, not evidence of local compliance. Fixed overhead, launch expenditure and acquisition costs remain outside order contribution.

Decisions and trade-offs

Do this next

Risks in your situation

Thin illustrative contribution leaves little room for wage reconciliation, parking delays or employment overhead. The founder’s merchant relationships cannot substitute for legal clearance, and personal runway must not be counted again as unrestricted operating capital.

White-label dispatch defaults may create control inconsistent with contractor status. Mandatory vendor settings that cannot be changed are a procurement stop, not a contract disclaimer problem.

Evidence gate

• ☐ Launch jurisdiction and applicable authorities are identified.
• ☐ Counsel has cleared actual courier practices and contracts.
• ☐ Current and pending measures have primary-source records.
• ☐ Tax, parking, permits and insurance responsibilities are documented.
• ☐ Wage reconciliation works using exportable operational records.
• ☐ Compliant order economics meet the contribution target.
• ☐ Regulatory monitoring and launch-hold authority are assigned.

Position

SwiftBite’s strongest opening is the founder’s existing merchant relationships combined with a permanently capped commission, not a claim to match incumbent reach. The sales narrative will use merchant-specific invoices; payout-speed claims remain gated until local competitor terms and SwiftBite’s settlement capability are verified.

Living competitor grid

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Personal runway substantially constrains settlement prefunding and launch expenditure. Family capital cannot simultaneously cover personal withdrawals, unavailable processor balances, and courier obligations.

The founder remains the sales and operating bottleneck. Unsupported competitor claims, payment-provider reserves, contractor reclassification, and low delivery density can erase the proposed advantage; suspend the affected claim or acquisition activity rather than breach the fee cap or wage floor.

Evidence gate

• ☐ Named competitor claims have current, consented local evidence.
• ☐ Merchant and courier payout comparisons remain separate.
• ☐ Settlement guarantees have tested rails and funded liquidity.
• ☐ Pilot orders show positive contribution after wage top-ups and actual variable costs.
• ☐ Contracts preserve the commission cap and transparent checkout.
• ☐ Promotional-offer monitoring produces verified, actionable records.

Position

SwiftBite will license dispatch and customer-ordering software, with the founder retaining operational control and a contracted integration specialist handling configuration. Shipday is the preferred trial candidate, not an approved purchase; batching, merchant branding, data export and messaging integration must pass acceptance testing before commitment. Launch remains conditional on contribution-positive deliveries and a locally validated courier-pay floor.

AI opportunity map

Accountability and purchasing. The founder owns vendor accounts, billing, merchant permissions and incident decisions. The integration specialist configures connections, documents recovery procedures and transfers credentials before final payment. No supplier may control SwiftBite’s domain, payment account or customer database.

Order-to-settlement workflow. The merchant accepts the order and confirms preparation time before dispatch releases it. The system validates the address against SwiftBite’s launch boundary, displays the complete consumer charge before payment, and preserves the accepted price in the order record. Tips remain separate from commission and pass through to couriers.

Each record carries an immutable order identifier, merchant identifier, payment reference, preparation status, courier assignment, route identifier, delivery timestamps and settlement status. Webhook retries must reuse the order identifier; failed events enter an exception queue rather than creating replacement orders.

The router proposes batches only within the service boundary and subject to food-hold and delivery-time constraints. Couriers see the published per-delivery rate, pickup sequence and proposed route before acceptance. Declines carry no punitive acceptance-score rule. Where compliant batching is unavailable, the founder chooses between a contribution-positive single delivery and pausing new orders; existing accepted orders remain SwiftBite’s responsibility.

Customer communications. Transactional templates cover merchant acceptance, courier collection, material delay and delivery completion. Messages use confirmed events and routing estimates, never invented explanations. “Your courier has collected your order. Current arrival window: {window}. Order support: {link}” is the collection template. SMS excludes full addresses and payment information; marketing consent is separate. Failed SMS delivery leaves the status page authoritative and alerts the founder when intervention is required.

Control and recovery. The founder monitors exceptions during every open delivery session. Dispatch failure stops new checkout availability; accepted orders move to the exported active-order list and direct courier contact. Payment ambiguity triggers reconciliation, not another charge.

Require multifactor authentication, merchant-scoped access, encrypted transport and contractor access removal at handover. Raw courier location history receives a short retention period; financial records follow locally confirmed requirements.

The numbers

All proposed spending is a budget allowance, not a supplier quotation. The order case excludes tax and tips; actual processing charges on those amounts must enter reconciliation.

Decisions and trade-offs

Do this next

Deadlines run from chapter approval.

Risks in your situation

Thin contribution leaves little tolerance for restaurant waiting, failed deliveries or processor charges omitted from checkout modelling. Track costs by merchant and delivery session; top-up allowances never limit actual wage-equivalent payments.

Contractor classification may conflict with the required operating controls. Obtain local advice before onboarding; change the operating arrangement if necessary.

Vendor lock-in and founder overload remain material. Require export rights, published support escalation and cancellable service; restrict availability when exception coverage fails.

Evidence gate

• ☐ Purchased software demonstrates batching and merchant isolation.
• ☐ Duplicate, missing and out-of-order events recover without double charging.
• ☐ Courier payments meet the locally validated floor.
• ☐ Paid pilot deliveries demonstrate positive contribution.
• ☐ Checkout preserves the commission cap and transparent pricing.
• ☐ Recovery files, credentials and operating procedures belong to SwiftBite.

Position

SwiftBite keeps its venture name and adopts “Your neighbourhood, delivered” as its public signature. SwiftBiteLocal.com is the preferred domain, pending availability and trademark clearance; neither registration nor clearance is established. The merchant website leads with retained order revenue, while consumer surfaces identify participating independent restaurants and show charges before payment.

Name shortlist

Brand master

The contracted designer supplies editable vector masters, monochrome marks, favicon, social avatar, web-ready images, font licence, and a concise usage sheet. The contract assigns paid-for artwork to the launch LLC and identifies any licensed components. Founder approval requires readable mobile layouts, keyboard navigation, labelled forms, and contrast testing.

Domain and account control

Use Cloudflare Registrar where supported, Cloudflare DNS, Google Workspace, and Bitwarden. The founder is account owner; the LLC is registrant and billing party. Enable registrar lock, automatic renewal, strong multifactor authentication, and renewal alerts to both the founder and an independent recovery mailbox.

Keep recovery codes offline. Give contractors delegated access, never ownership or shared founder credentials. Configure SPF, DKIM, and DMARC before merchant outreach; move DMARC to enforcement after legitimate senders are verified.

Merchant landing page: approved copy and structure

Hero: “Keep more of every delivery order.”

Supporting copy: “SwiftBite connects independent restaurants with nearby customers. Get a clear merchant agreement, local onboarding, and delivery terms you can check before joining.”

Primary button: “Request merchant terms.”
Secondary button: “See fees and service area.”

Local section: “Built around independent restaurants in our launch neighbourhoods.” Publish the service map only after actual city, neighbourhood names, and boundaries are approved. Do not describe citywide coverage.

Enquiry form: Restaurant name, contact name, work email, restaurant address, and optional telephone number. Button: “Send my request.” Confirmation: “Thanks. Your request has reached SwiftBite. The founder will contact you with merchant terms.” Keep marketing permission separate and unticked.

Footer links: merchant terms, consumer terms, privacy notice, accessibility contact, and support email. Display the LLC’s actual registered name and legally required contact details.

Consumer and courier surfaces

Consumer storefront copy: “Meet the independent restaurants delivering near you.” Show only contracted merchants; obtain logo and menu-image permission. Label unavailable addresses plainly rather than collecting payment outside coverage.

Checkout presents food subtotal, delivery charge, tax, optional tip, and final total before confirmation. No preselected tip, hidden service charge, fake countdown, or unsupported “money stays local” percentage.

Courier recruitment links to the published per-delivery rate and minimum-wage-equivalent safeguard. Publish the accounting method and top-up process before accepting applications.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

An existing SwiftBite mark could force renaming despite domain availability. Counsel clears use before signage or paid promotion.

White-label checkout surcharges could breach the cap or transparent-pricing promise. Reject incompatible vendor configurations.

Monitor confusing domains without alleging infringement automatically. Preserve evidence; route impersonation or disputed rights to counsel rather than buying domains reactively.

Evidence gate

• ☐ Name review supports use in the actual launch jurisdiction.
• ☐ Cleared domain and brand files belong to the LLC.
• ☐ Account recovery and enquiry delivery are tested.
• ☐ Signed merchant terms match every published fee claim.
• ☐ Checkout exposes all charges before confirmation.
• ☐ Service boundaries, merchant permissions, and courier pay safeguards are approved.
• ☐ Actual commitments remain within the chapter ceiling.

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.

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.

Decisions and trade-offs

Do this next

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.

Position

SwiftBite will retain the capped merchant commission and a separately disclosed consumer software fee; delivery charges and tips belong entirely to couriers. Launch remains conditional on verified courier earnings, positive order contribution, and a funded operating budget. The founder’s personal runway must not be presented as sufficient financing for city operations.

Business Model Canvas

Settlement and contract schedule

The software contract must support itemised receipts, configurable commissions, courier supplements, refunds, and downloadable settlement ledgers. The founder approves commercial terms; the bookkeeper signs off reconciliation; counsel approves classification, tax responsibilities, and courier terms before live trading.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Thin contribution leaves little protection against larger tax-inclusive processing bills, waiting time, or refunds. Contractor reclassification could invalidate the courier cost structure. The operating cash available after the personal reserve does not establish a funded path to break-even; expansion must remain conditional rather than assumed.

Evidence gate

• ☐ Signed agreements preserve the merchant cap and complete delivery-charge pass-through.
• ☐ Local counsel approves courier status, earnings measurement, and tax allocation.
• ☐ Trial settlements reconcile without unexplained balances.
• ☐ Observed orders remain contribution-positive after all supplements and variable costs.
• ☐ Checkout evidence supports the disclosed software fee.
• ☐ A funded cash-flow schedule covers the ramp without borrowing merchant or courier balances.

Position

SwiftBite can reach operating cash-flow break-even within the requested timetable without increasing merchant commission or disguising consumer charges. The base case remains narrowly funded: launch approval requires verified courier economics, a licensed software contract, and committed contingency liquidity. City-level profitability and founder-inclusive cash flow will be reported separately.

Investor-ready business plan with milestones

The founder owns merchant acquisition, cash control and software procurement. Launch is scheduled for January 2027 (estimate); service remains inside the existing launch zone throughout this plan.

All forecast figures in the following table are estimates, as marked in the column headings. Merchants means active, order-ready locations; couriers means approved active roster, not simultaneous staffing. Weekly volumes are operating checkpoints, not additional orders.

The model uses thirty trading days monthly (estimate). Opening cash deducts software setup before trading. Net cash includes founder withdrawals and onboarding; it excludes financing, income taxes and any distribution beyond the founder allowance. Merchant proceeds, sales taxes and tips remain segregated from operating cash.

The fleet manager begins as a part-time employee. Courier onboarding covers screening, document verification and dispatch training; replacement recruitment requires an explicit budget revision.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Evidence gate

• ☐ Merchant census supports the penetration claim.
• ☐ Signed supplier terms support positive contribution from launch.
• ☐ Courier earnings remain compliant after actual top-ups.
• ☐ Founder withdrawals and restricted funds are separately recorded.
• ☐ Weekly order targets reconcile to monthly cash forecasts.
• ☐ Contingency liquidity is executable.
• ☐ City profitability and founder-inclusive break-even are independently verified.

Position

SwiftBite’s pitch leads with merchant economics, disciplined delivery costs, and a tightly bounded launch territory—not national expansion forecasts. The founder’s merchant relationships are the acquisition advantage; signed merchant commitments and paid-order evidence remain unverified. Local angels receive a clearly labelled underwriting case, with funding conditional on wage-floor compliance and positive contribution per order.

10–15 slide pitch narrative

Use charcoal backgrounds, oversized cream typography, and electric-orange financial callouts. Put merchant receipts, contribution waterfalls, and the launch map ahead of product screenshots. Every slide carries a source footer; projections carry “(estimate)” directly beside the figure.

The numbers

The model uses a food subtotal excluding tax and tip. Processing assumes SwiftBite collects food value plus delivery fee; actual tax, tip, and settlement treatment must replace that assumption.

Decisions and trade-offs

Do this next

Risks in your situation

The contribution cushion is thin: additional courier compensation, vehicle allowances, refunds, or payment costs can erase it. Calculate wage equivalence using recorded working time and locally required expense treatment, not delivery time alone.

Merchant enthusiasm may not produce consumer repeat orders. The founder also remains the sales and operating bottleneck; software licensing does not remove dispatch, settlement, or support workload.

Evidence gate

• ☐ Merchant counts reconcile to permissioned records.
• ☐ Paid-order evidence supports positive contribution after wage adjustments.
• ☐ Vendor and insurance quotations replace assumptions.
• ☐ Cash forecasting supports the final raise and protects personal runway.
• ☐ Counsel approves courier arrangements and investment documents.
• ☐ Every projection is labelled; grants remain excluded until awarded.

Position

SwiftBite will launch as a single-member LLC owned and managed by the founder, retaining conversion to a C-Corporation for an institutional financing. No cofounder allocation is authorized; family funding must be classified before deposit, and a future technical-lead equity reserve remains conditional rather than issued ownership.

Structure recommendation

Formation authorization. The founder is authorized to establish SwiftBite’s operating entity, subject to name clearance and confirmation of the launch jurisdiction. The formation file must identify the legal name, registered address, registered agent, tax identifier, beneficial owner, fiscal year-end, and required local delivery-business registrations. “SwiftBite” must be registered as a trading name if different from the legal name.

Launch capitalization. Maintain the signed operating agreement, membership register, funding-source ledger, and supporting transfer records together. The register must reconcile to bank receipts; available capital is not automatically paid-in equity.

Conversion authorization. Conversion requires a signed institutional term sheet, tax review, lender-consent review, and counsel’s jurisdiction-specific conversion plan. Counsel must address contract continuity, license assignment, insurance endorsements, tax elections, and the successor ownership register before effectiveness.

The following reserve is a planning scenario, not an outstanding LLC interest or promised compensation. It assumes no other equity, convertible securities, or investor issuance.

No technical-lead grant is approved now. Future grants require an approved stock plan, valuation, vesting and departure provisions, exercise terms, and signed confidentiality and intellectual-property assignments. A software license does not transfer the vendor’s underlying intellectual property to SwiftBite.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

• Courier liability: Require a delivery-appropriate insurance review covering SwiftBite’s exposure and couriers’ vehicle use. Personal auto policies may exclude commercial delivery; incorporation alone cannot resolve that gap.
• Worker classification: Contractor labels do not determine status. Block launch where the proposed working arrangement fails local law; preserve the published per-delivery rate and minimum-wage-equivalent floor.
• Funding disputes: Undocumented family expectations can undermine sole ownership. Resolve repayment and ownership claims before spending the money.
• Cash confusion: Personal runway and venture capital cannot both consume the same cash. Reconcile the funding ledger before authorizing launch commitments.

Evidence gate

• ☐ Operating jurisdiction, formation record, tax identifier, and required registrations are verified.
• ☐ Signed ownership register shows only the founder; every family transfer has enforceable documentation.
• ☐ Business banking and personal reserves are separated and reconciled.
• ☐ Courier classification, wage-equivalent procedures, and delivery insurance are cleared.
• ☐ Merchant and consumer contracts preserve published pricing.
• ☐ Conversion pathway and conditional equity reserve are documented without outstanding grant promises.
• ☐ Filing calendar names an accountable owner and uses official sources.

Position

SwiftBite’s trademark clearance, municipal licensing status, and ownership records remain unverified; consumer marketing stays on hold until the release conditions below are documented. The LLC will own the brand assets, while licensed software remains the vendor’s property. This schedule uses the United States filing route provisionally; the founder must confirm the country, state, and municipality before authorizing applications.

Jurisdiction-specific registration

The founder is accountable for the registration file, counsel instructions, spending approvals, and marketing release. Retained trademark counsel handles clearance and trademark submissions; local business counsel verifies municipal permissions and courier-related licensing. No application, approval, or exclusive right is represented as already secured.

Counsel should assess delivery services in Class 39 and marketplace services in Class 35 against SwiftBite’s actual merchant and consumer contracts. Class selection is not authorization to expand services or claim downloadable software supplied by the white-label vendor. Applications must precede consumer marketing; registration itself may take substantially longer and is not a guaranteed launch prerequisite.

Maintain a restricted Google Drive register with folders for Entity, Licenses, Clearance, Applications, Ownership, Vendor Rights, and Watch Notices. Each record must show its owner, filing authority, submission date, receipt, status, next deadline, and accountable person. Enable multifactor authentication; counsel maintains the controlling legal docket, with founder calendar reminders as backup.

Use these terms in counsel-reviewed agreements:

Subscribe to a counsel-managed trademark watch. Founder reviews alerts weekly; counsel assesses potentially conflicting filings within two business days of referral and records any opposition deadline. Preserve screenshots, filing records, and first-use evidence before contacting another business. Use ™ where appropriate; do not use ® until registration permits it.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

A conflicting earlier user may defeat registration despite an available LLC name or domain. Trademark filings cannot prevent corporate espionage; restricted access, confidentiality obligations, and vendor controls remain necessary.

The unidentified municipality prevents a reliable license list or fee commitment. Courier classification and pay compliance require separate local review; brand registration does not validate contractor status. Official-looking trademark invoices must be verified with counsel before payment.

Evidence gate

• ☐ Jurisdiction and LLC ownership details are verified.
• ☐ Counsel has delivered written clearance for the final name and logo.
• ☐ Trademark submissions and official receipts are archived.
• ☐ Applicable operating licenses are approved, or non-applicability is documented.
• ☐ Designer assignments, vendor permissions, and merchant brand permissions are executed.
• ☐ Monitoring, legal deadlines, and renewal ownership are active.
• ☐ Marketing release is signed without implying registration or guaranteed exclusivity.

Position

SwiftBite will contract through its registered single-member LLC, with separate merchant, courier, consumer and software-provider agreements. Contractor labels and liability exclusions will not substitute for compliant operations; launch remains conditional on local counsel approving classification, wage-floor implementation, insurance and consumer terms for the selected jurisdiction.

Agreement inventory

Common execution block

“SwiftBite” means the registered LLC identified in the agreement header. Each agreement records the counterparty’s legal name, address, authorized signatory, effective date and accepted version. Merchant and courier schedules identify the service territory, payment details and required permits. Electronic acceptance must produce a timestamped, downloadable copy.

Mandatory local rights prevail over conflicting provisions. No agreement releases SwiftBite from responsibility for its own negligence, unlawful conduct or non-waivable obligations. Governing law and dispute venue must identify the actual operating jurisdiction before execution.

Merchant Service Agreement

Merchant appoints SwiftBite to transmit orders and arrange delivery within the published service territory. Merchant remains the food seller and is responsible for lawful preparation, hygiene, temperature at handoff, accurate ingredients and allergen information, packaging, menu descriptions and required food-service permits.

Merchant must confirm availability before accepting an order, seal and label each package, and disclose substitutions for customer approval. SwiftBite and couriers must not alter food contents or promise allergen safety independently of Merchant.

SwiftBite charges only the commission in the commercial schedule. The advertised cap cannot be exceeded through mandatory marketing, listing, processing or administrative charges. Optional services require a separate affirmative purchase and cannot be conditions of ordinary marketplace access.

Settlements must itemize sales, commission, taxes, refunds, adjustments and net payment. SwiftBite may deduct only documented amounts authorized by this agreement or required by law. Disputed amounts receive an itemized explanation; unrelated, undisputed proceeds remain payable.

Merchant bears refunds attributable to missing items, incorrect preparation or food defects established by available evidence. SwiftBite bears refunds attributable to its own systems or delivery administration. Contested food-safety claims go to the insurer and counsel without admissions of liability.

Each party indemnifies the other only to the extent a third-party claim results from its own breach, negligence or unlawful conduct. SwiftBite remains responsible for obligations imposed on it by law. Merchant is not responsible for courier conduct after handoff unless Merchant contributed to the loss.

Courier Services Agreement

The parties intend an independent-contractor relationship, not employment; actual working practices and applicable law control classification. Courier may reject offers, work for competitors and choose lawful routes. SwiftBite does not require exclusivity or penalize offer rejection.

Courier supplies a roadworthy vehicle, valid licence and legally required delivery-use insurance. An offer displays pickup, destination, expected distance and published delivery payment before acceptance. No acceptance creates an obligation to accept subsequent work.

SwiftBite pays the published delivery rate and any wage-floor adjustment. Recorded service time includes accepted dispatch through completion, required waiting, required return journeys and other legally compensable time. SwiftBite compares compensation excluding tips against the applicable local minimum-wage equivalent and pays any shortfall automatically. Any mandatory expense reimbursement is additional.

Customer tips belong entirely to Courier and cannot offset the delivery rate or wage-floor adjustment. Courier may correct time records and dispute payment without retaliation.

Courier must preserve seals, follow safe handling instructions, report collisions or suspected contamination immediately and protect customer information. Safety suspension requires documented grounds, notice and a human review route. No loss is automatically deducted from courier earnings.

Consumer Terms and checkout assent

Before payment, SwiftBite displays the restaurant, items, delivery charge, applicable taxes, optional tip and final total. Tips are not preselected. No additional mandatory fee appears after acceptance.

The checkout displays cancellation conditions before ordering. Restaurant rejection or SwiftBite’s inability to fulfil an order triggers a refund of unprovided items and services. Food defects, missing items and delivery failures can be reported through the order receipt; statutory remedies remain available.

SwiftBite coordinates complaints without requiring customers to pursue restaurants or couriers first. Personal information is shared only as needed for fulfilment, support, payment and legal obligations, under the linked privacy notice. Marketing consent is separate from transaction acceptance.

White-label licence and processing addendum

Require merchant and order-data export, a subprocessor register, access controls, incident notification, payment reconciliation, service availability commitments and termination assistance. SwiftBite retains its customer and merchant relationships. Reject vendor rights to impose customer charges, change merchant economics, withhold export or monetize personal data independently. Attach negotiated service levels before signing.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Misclassification, uninsured delivery use and food-safety claims can survive contractual disclaimers. The founder owns incident intake; counsel and insurers control claim escalation. Family-funded capital must not support personal guarantees hidden in vendor agreements, and software limitations must not weaken the wage floor or pricing commitments.

Evidence gate

• ☐ Local counsel approves classification and consumer enforceability.
• ☐ Every active counterparty has accepted a retrievable agreement.
• ☐ Food, vehicle and platform insurance responsibilities are verified.
• ☐ Checkout matches contracted pricing and refund terms.
• ☐ Pilot records prove wage-floor compliance and positive contribution.
• ☐ Incident escalation, data export and contract-change logs work.

Position

SwiftBite’s payment acceptance and courier dispatch remain blocked until the founder holds verified processor, insurance, licensing, and jurisdictional evidence. White-label vendors may operate the technology, but the founder retains approval authority and incident ownership. Missing evidence means no launch exception, including for a merchant-referred driver.

Compliance register with owners

Authority and jurisdiction register

The founder owns the compliance register in an access-restricted business document repository. Retained local counsel approves the jurisdiction checklist; a licensed commercial insurance broker approves coverage requirements; the software vendor supplies technical evidence.

Before activation, record the operating city, state or province, applicable privacy authority, business licenses, delivery permits, worker-classification requirements, insurance limits, reporting deadlines, and renewal dates. An unresolved requirement blocks the affected activity. LLC registration does not substitute for operating licenses.

Payment and privacy controls

SwiftBite takes payment through a PCI-validated provider's hosted checkout. Card data passes directly to that provider and never touches SwiftBite servers, support channels, analytics, or logs. Store only processor tokens, transaction references, payment status, and masked card details necessary for support. Never retain security codes.

The founder obtains the provider’s current Attestation of Compliance, the white-label vendor’s payment data-flow diagram, and a written responsibility matrix. The acquiring bank must confirm the applicable validation route; outsourcing alone does not establish SAQ eligibility or compliance.

Require unique accounts, multifactor authentication, least-privilege permissions, and logged administrative access. Merchants see their orders; couriers see assigned delivery details only. Prohibit shared accounts, personal-device exports, and card details in chat. Refunds go through the processor to the original payment method.

Publish a counsel-approved privacy notice before collecting customer information. Obtain separate, optional marketing consent. Restrict driver location collection to dispatch and delivery purposes; prohibit advertising reuse. Route access, correction, and deletion requests to the founder for identity verification and legally compliant fulfillment.

Vendor contracts must prohibit selling customer data, list subprocessors, support deletion and export, require breach cooperation, and disclose payment-page changes before release.

Courier authorization and safety

Each courier must provide identity evidence, a valid license appropriate to the vehicle, registration, and insurance documents naming the driver and vehicle. Obtain lawful consent for driving-record checks. Counsel defines permissible screening and adverse-action procedures.

The broker must verify coverage for paid food delivery, including waiting, travel to collection, and delivery. A personal auto insurance card without delivery coverage confirmation is insufficient. Obtain SwiftBite’s own broker-recommended liability coverage, including hired/non-owned auto exposure where applicable; courier coverage does not eliminate company exposure.

Maintain a dispatch eligibility record with document expiries, coverage confirmation, screening outcome, training acknowledgment, and founder approval. The vendor must support automatic blocking; absent that capability, the founder controls a verified dispatch roster.

Couriers must park before interacting with the app, use seat belts, avoid impairment, secure food loads, and report collisions or unsafe conditions immediately. No delivery deadline overrides traffic law. Allow unsafe-delivery refusal without punitive dispatch treatment.

Publish delivery rates before acceptance. Track required working time and apply a pay-floor adjustment whenever delivery earnings fall below the applicable minimum-wage equivalent, with legally required expense treatment. Counsel must approve classification and the time-accounting method; contractor labels are not sufficient.

Incident response

For suspected payment compromise, disable the affected checkout path, preserve logs, revoke compromised access, and notify the processor and counsel. Resume only after containment and required approval. Counsel controls statutory notifications.

For a collision, prioritize emergency assistance, suspend the affected courier’s dispatch, preserve evidence, and notify insurers under policy terms. Do not admit liability or request unnecessary medical information.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Thin unrestricted capital makes insurance pricing a launch constraint. Founder-only administration creates approval bottlenecks; maintain a dispatch pause rather than delegating unchecked access. White-label configuration changes can expand payment scope. Local wage, classification, or insurance requirements may invalidate the planned courier model; suspend affected operations until corrected.

Evidence gate

• ☐ Jurisdiction register approved; required licenses active.
• ☐ Acquirer accepts payment validation evidence.
• ☐ Vendor contracts and access controls pass review.
• ☐ Courier documents and delivery coverage verified.
• ☐ Pay-floor accounting and classification approved.
• ☐ Insurance costs fit contribution targets.
• ☐ Dispatch blocking and incident procedures tested.

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

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.

The numbers

Decisions and trade-offs

Do this next

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.

Position

SwiftBite will launch through founder-signed restaurants and merchant-owned customer touchpoints, with checkout and customer records retained in its licensed platform. Expansion beyond those routes is conditional on positive contribution after courier wage protection, attributable acquisition costs, and reliable delivery inside the launch zone. Paid marketplaces and commission-bearing resellers are excluded from launch.

Channel map, channel economics per route, partner terms, ful

Route ownership. The founder owns merchant recruitment, channel attribution, partner settlement, and launch dispatch. Restaurants own menu accuracy and preparation commitments; couriers own safe transport and delivery confirmation. The software vendor supplies ordering, routing, settlement exports, and consent records under a cancellable licence.

Merchant agreement. Commission applies to food subtotal only, excluding tax, tips, and delivery charges. No listing, activation, mandatory promotion, or payment-processing surcharge is added to merchant invoices. Restaurants retain menu-price control; SwiftBite does not require exclusivity or parity with another platform.

Route economics. Acquisition spend remains separate from order contribution. Referral expense is deducted from contribution whenever payable.

Fulfilment procedure. Checkout rejects addresses outside the launch boundary before payment. Restaurant acceptance releases dispatch; readiness confirmation triggers pickup. Couriers verify the receipt identifier and sealed bag, then record delivery confirmation. The founder resolves exceptions through the dispatch console; restaurants never negotiate courier pay.

The numbers

Decisions and trade-offs

Merchant distribution wins priority over paid reach. Restaurant traffic is not free: printed material, onboarding effort, and founder time remain in acquisition reporting.

The contribution hypothesis leaves little room for slow routing. Wage top-ups take precedence over margin; failing windows close rather than reducing courier compensation. City break-even remains unproven until fixed software, insurance, dispatch, and administration costs fit within actual contribution.

Do this next

Risks in your situation

Low baskets, scattered demand, and restaurant waiting can erase contribution. Contractor classification and minimum-wage treatment require local review before launch. Vendor outages must disable ordering rather than accept unfulfillable purchases. Never print SwiftBite promotions inside aggregator orders without contractual permission.

Evidence gate

• ☐ Merchant cap and transparent checkout verified against settled orders.
• ☐ Actual courier top-ups included in contribution.
• ☐ Channel cohorts identify first purchase, delivery outcome, refund, and reorder.
• ☐ Acquisition cost recovered within the observed customer cohort.
• ☐ Delivery promises met consistently without unsafe routing or unpaid waiting.
• ☐ Fixed-cost budget and remaining capital support the next channel test.

Position

SwiftBite will compete as the delivery service accountable to independent restaurants and their neighbourhoods, not as another discount app. Merchant relationships are the founder’s strongest distribution asset; paid visibility remains conditional on verified delivery economics. “Main Street Savior” is an internal campaign direction, not a public claim of community endorsement.

Positioning

The neighbourhood’s independent delivery alliance

Public platform: “Your dinner. Your neighbourhood. More stays with the restaurant.”

Merchant invitation: “You built a local business. Your delivery partner should respect that. Join SwiftBite’s founding restaurant alliance: a published commission cap, clear customer charges, and a local founder you can reach directly.”

Customer invitation: “Keep your favourites close. Order from participating independent restaurants through SwiftBite, with delivery charges shown before you commit.”

Campaign signature: “Independent restaurants. Local delivery. Straightforward fees.”

The founder recruits through existing merchant relationships, prioritising owners willing to place checkout cards, share their own signed story, and introduce neighbouring operators. Participation requires a signed merchant agreement, menu approval and successful test delivery. Marketing consent is separate and revocable; preferred placement is not contingent on praise.

Each participating restaurant receives window artwork, a counter card, a restaurant-specific QR link, an email insert and approved social captions. Links open that restaurant’s ordering page, with service availability checked before checkout. Printed materials say “Available in participating neighbourhoods,” not “citywide.”

Merchant social caption: “We’re now taking delivery orders through SwiftBite. Choose our SwiftBite ordering link when you want delivery with a transparent, capped restaurant commission. Same independent kitchen. A different delivery relationship.”

Local press pitch subject: “Independent restaurants launch a transparent-fee delivery alliance.”

Pitch body: “SwiftBite is bringing together independent restaurants in the downtown core and adjacent neighbourhoods. Participating owners are available to discuss their delivery costs using statements they authorise for publication. The founder will publish SwiftBite’s merchant commission, consumer delivery charge and courier pay policy. We invite your newsroom to speak directly with participating restaurants and observe a delivery.”

Do not use “greedy,” invent merchant hardship, imply municipal backing or describe every competitor contract as identical. Comparisons must identify their source, date and scope.

The founder maintains a weekly “neighbourhood pulse” sheet using Google Alerts, public local-business posts, merchant conversations and native social analytics. Log the original link, event relevance, permission status and customer response. Civic celebrations can trigger relevant creative; tragedies, private groups and political divisions cannot.

Paid posts feature consenting owners and their dishes. Referral links carry no cash reward at launch. Responses to complaints acknowledge the specific problem and move order details to private support; legitimate criticism remains visible.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Evidence gate

• ☐ Merchants have approved their names, stories, assets and comparison evidence.
• ☐ Advertised fees match contracts and checkout without hidden mandatory charges.
• ☐ Courier pay safeguards and local legal requirements have been validated.
• ☐ Attribution connects campaign spend to completed orders and realised contribution.
• ☐ Operating reserves remain intact after the authorised campaign commitment.
• ☐ Paid expansion passes the acquisition spending rule.
• ☐ Billboard expenditure remains blocked without separate approval and supporting evidence.

Position

SwiftBite’s founder owns merchant acquisition, contracting, and launch activation; no sales hire is budgeted before the process demonstrates repeatable conversion. Recruitment stays inside the launch zone and prioritises existing relationships with independent owners already paying aggregator commissions. Signed agreements count as pipeline progress, not acquired merchants: acquisition requires a completed, paid delivery.

Sales stages

Founder’s pipeline

Use HubSpot Free for stages, tasks, and contact history; Google Sheets for merchant economics; and Dropbox Sign for agreements. Record owner, address, delivery volume, commission evidence, preparation times, objections, next action, and expected activation date.

Reject out-of-zone locations and owners demanding hidden charges or uncapped courier availability. Park otherwise suitable merchants until they supply statements, nominate a shift lead, or resolve kitchen-capacity problems. Do not substitute total restaurant revenue for delivery sales.

On-site discovery script

“Thanks for making time outside service. Which delivery channels are you using, and can we look at the latest statement together?”

“Show me food sales, commission, promotions, refunds, and the amount actually paid into your account. Which deductions did you choose, and which were compulsory?”

“When delivery orders arrive during your busiest service, who accepts them? What causes missed orders or late handoffs? Who updates sold-out items?”

“Would you trial SwiftBite alongside your current channels? Who signs the agreement, and what must you see before agreeing?”

Close: “I’ll use your statement—not an assumed order volume—to prepare the comparison. We will only propose trading hours we can support with courier coverage.”

On-site demo script

“Here is your draft menu. Please check prices and availability, then accept this labelled test order yourself.”

“Mark this item unavailable. Now update the preparation estimate and show your shift lead where the courier handoff happens.”

“Here is the customer’s full checkout price before payment. Here is your settlement view. Let’s trace a cancellation and refund so responsibility is explicit.”

Close: “If the workflow works for your team, let’s review the agreement and choose supported launch hours. SwiftBite is not promising replacement aggregator demand.”

Owner’s proposal and economics sheet

The proposal carries the restaurant’s legal name, launch address, statement period, owner-approved assumptions, menu scope, supported hours, payout schedule, and activation conditions. Replace the illustration below with verified merchant figures before signature.

The comparison excludes tax, tips, food costs, refunds, promotions, and demand changes. Savings apply only to equivalent sales actually routed through SwiftBite.

Agreement terms: non-exclusive participation; no minimum-volume promise; no compulsory merchant charges outside the commission cap; owner-approved promotions only; written allocation of restaurant-error versus delivery-error refunds; documented payout and termination terms. Founder signs only after the licensed software and payment provider support every promised term.

Objections library

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Signatures may outpace courier capacity; pause activations rather than dilute service or driver pay. Strong relationships may inflate verbal interest; count only documented stage exits. A thin delivery basket can erase commission savings for SwiftBite; restrict unsupported hours or decline activation rather than add hidden fees.

Evidence gate

• ☐ Statement-backed economics replace illustrative figures.
• ☐ Merchant agreement preserves the advertised cap.
• ☐ Shift lead completes the operational test.
• ☐ Courier pay satisfies the local minimum-wage equivalent.
• ☐ Genuine first order reconciles through settlement.
• ☐ Weekly funnel and contribution records support continued recruitment.

Position

SwiftBite is not yet ready to represent acquisition costs, customer lifetime value, or localized profitability as verified; no supporting operating records have been supplied. The funding mandate is conditional: prove the launch city’s economics, then raise institutional capital to replicate the operating model without increasing merchant commissions or weakening courier pay protections.

Funding strategy

The founder owns the investor narrative and data-room permissions. An engaged fractional controller owns reconciliations and metric definitions; financing counsel owns corporate conversion, securities documentation, and disclosure review. These engagements remain unconfirmed until signed.

Metric policy. Merchant CAC includes sales spending, onboarding incentives, attributable travel, and founder sales time at a disclosed replacement-cost estimate. Its denominator is newly acquired merchants completing a paid order, not signed accounts. Consumer CAC includes attributable advertising, referral rewards, and acquisition discounts; its denominator is new consumers completing a paid order. Report organic, paid, and blended cohorts separately.

Contribution revenue comprises earned merchant commissions and disclosed consumer fees, excluding taxes, tips, and merchant proceeds. Deduct courier compensation and wage-equivalent top-ups, processing, refunds borne by SwiftBite, promotions, variable support, and variable software charges. Maintain a separate city operating statement that includes local overhead and founder replacement compensation.

LTV uses retained-cohort contribution, not gross merchandise value. Separate realized cumulative contribution from projected future contribution; mark projected values “(estimate).” Show cohort age, retention assumptions, and sensitivity to courier costs. Do not add merchant LTV and consumer LTV together: both reference overlapping orders.

The controller signs a verification memorandum stating procedures performed, unresolved limitations, and whether work constitutes accounting review rather than audit. The investor deck must use that exact assurance description.

Access is permissioned and logged. Investor-facing exports exclude consumer addresses, courier identity documents, payment credentials, and unnecessary personal data. Detailed commercial records are released under confidentiality arrangements.

The founder maintains a regional venture-firm register showing geographic mandate, relevant portfolio exposure, check-size fit, partner contact, referral source, and diligence status. No firm enters the active process without geographic eligibility being confirmed.

The numbers

Decisions and trade-offs

The founder’s sales relationships remain the acquisition advantage. Expansion must demonstrate that a hired local operator can reproduce acquisition results without assuming the founder personally closes every merchant.

Do this next

Risks in your situation

Personal runway may expire before the city-level profitability target. Unfunded household or operating requirements must appear explicitly in the cash forecast.

Courier contractor status does not remove wage-equivalent obligations. Record availability and delivery time under a counsel-reviewed policy; budget top-ups and classification exposure.

Licensed software creates vendor dependency. Obtain portability, routing-capacity, support, and termination terms before promising replication. Settlement funds owed to merchants or couriers are not expansion capital.

Evidence gate

• ☐ Cash, ownership, and family funding records reconcile.
• ☐ CAC is reproducible separately for merchants and consumers.
• ☐ Realized contribution is separated from estimated LTV.
• ☐ Launch-city profitability includes complete operating costs.
• ☐ Courier pay and merchant-cap compliance are documented.
• ☐ Adjacent-city diligence supports the replication budget.
• ☐ Conversion documents and financing terms receive counsel approval.
• ☐ Institutional funds clear before expansion commitments are released.

Position

SwiftBite will launch with a processor-backed order subledger, automated settlement instructions, and summarized postings to QuickBooks Online. The founder owns treasury and exceptions; a contracted marketplace bookkeeper owns reconciliation and month-end close. Launch remains blocked until processor approval, local courier-pay requirements, tax treatment, and funded payout timing are documented.

Financial-control setup

System ownership and controls

The vendor statement of work must include webhook replay, idempotent posting, payout-status tracking, complete ledger exports, and migration assistance. Reject any license requiring the founder to maintain custom payment code. The contract must identify integration-support ownership and prohibit unapproved changes to payout logic.

Order-level posting specification

The merchant agreement specifies the advertised commission cap, payout calendar, refund allocation, dispute evidence process, and consent requirements for recovery of merchant-attributable losses. SwiftBite bears its own service failures. Refunds reverse the corresponding commission; processor fees remain SwiftBite expenses unless separately lawful, disclosed, and accepted.

The courier agreement publishes delivery compensation before acceptance, preserves tips, and requires time records sufficient to calculate the local minimum-wage equivalent. Counsel must approve the compensable-time definition and contractor classification. Required supplements accrue before payout; tips never satisfy the floor.

Automation and exception routing

Checkout stops accepting payment when capture status cannot be established reliably. Fulfilled orders retain their payment obligations during outages. Routine reconciliation and payouts run unattended; exceptions require documented approval and an audit trail.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

The unspecified jurisdiction prevents final approval of contractor status, wage-floor calculations, marketplace tax collection, and payment timing. Processor reserves or delayed availability could exhaust the modest capital remaining after personal needs. Written settlement approval and a funded stress test are mandatory; merchant float is not a contingency.

Evidence gate

• ☐ Processor approves the complete merchant and courier funds flow.
• ☐ Signed contracts preserve the commission cap, transparent checkout, and courier floor.
• ☐ Test transactions reconcile across subledger, processor, bank, and general ledger.
• ☐ Failed payouts and duplicate events cannot create duplicate payments.
• ☐ Reserve funding covers documented settlement-delay exposure.
• ☐ Actual contribution supports launch without unpaid obligations.

Position

SwiftBite remains founder-operated in its launch city; expansion hiring is conditional, not an immediate commitment against family capital. The founder retains merchant relationships, pricing authority and cash control while establishing a repeatable City General Manager role. No additional market opens until local leadership, courier protections and separately funded operating capacity are in place.

Workload diagnosis

Executive scaling chart

City GMs are employees. Couriers remain independent contractors at launch, subject to local classification review. The Remote Vetting Lead uses automated workflow routing and document-expiry alerts, but retains human responsibility for clearance decisions.

City GM hiring specification

Recruit local logistics supervisors, restaurant-area managers and field-sales operators through LinkedIn, Indeed and the founder’s merchant network. Require evidence of neighbourhood knowledge, merchant retention, incident handling and operating-budget ownership. Software engineering experience is unnecessary; competent use of the licensed dispatch console is mandatory.

The offer names the launch market, cash salary, reporting line and service obligations. No bonus depends solely on delivery speed, contractor acceptance rates or suppressed refunds. Founder approval is required for fee changes, permanent service-area expansion, material vendor commitments and spending outside the approved city budget.

Standard City Manager operating playbook

Where tracked earnings fall below the local minimum-wage equivalent, SwiftBite pays the adjustment rather than transferring the shortfall to couriers. Counsel approves the time-accounting basis before activation; the GM cannot redefine qualifying time to eliminate a shortfall.

Remote driver-vetting desk

Use Checkr where jurisdictionally available, or a locally accredited screening provider, with explicit candidate consent. Collect identity, driving eligibility, required insurance and vehicle documentation through the provider’s secure portal—not shared email folders.

Automation routes complete files, flags expiry and sends status notices. The Remote Vetting Lead reviews discrepancies, applies a counsel-approved eligibility matrix and manages legally required adverse-action notices and appeals. City GMs cannot bypass clearance. Store clearance status and expiry dates in the operating roster; restrict underlying screening reports to authorized reviewers.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

The unspecified jurisdiction prevents final salary, insurance, screening and wage-floor commitments. Contractor classification remains a legal exposure that onboarding language alone cannot resolve.

The founder’s merchant relationships may conceal weak institutional retention. Require merchant records and direct GM introductions before delegation. Low contribution could make a professionally managed city unviable at target volume; neither unpaid founder labour nor delayed courier adjustments may disguise that gap.

Evidence gate

• ☐ Hiring cash is funded separately from protected personal runway.
• ☐ Local compensation and employer costs are validated.
• ☐ Counsel approves courier classification, screening and earnings-floor procedures.
• ☐ The City GM passes autonomous launch assessment.
• ☐ Courier rates, adjustments and merchant terms are published and reconciled.
• ☐ City forecasts include leadership costs and support the grounded break-even milestone.

Position

SwiftBite shall remain founder-controlled under its single-member LLC structure, supported by nonbinding advisers rather than a statutory board. Governance shall protect the merchant commission cap, published courier pay floor, transparent consumer pricing, and cash before pursuing volume. Institutional financing shall trigger a documented corporate conversion and negotiated investor rights, not informal promises of ownership or control.

Governance charter, board or advisory composition, decision-

Authority. The founder shall act as managing member, subject to the operating agreement and applicable law. Advisers cannot bind SwiftBite, direct contractors, authorize borrowing, or represent themselves as directors. The operating agreement, bank mandate, contract register, and decision log shall identify the founder’s authority consistently.

Advisory appointments. Recruit against the following mandates; appointments remain contingent on signed confidentiality, conflict-disclosure, and advisory agreements.

Decision rights. Advisory review is a control, not a transfer of member authority. The founder shall record any decision taken against advice, including the objection, cash exposure, and mitigation.

No purchase splitting is permitted. If the bank cannot support separate release, use documented independent preapproval and bank alerts to the reviewer. Emergency containment spending requires a recorded reason and independent retrospective review.

Reporting and cadence.

The founder owns the pack and minutes. Every action receives an owner, due date, and closure evidence. Maintain records in a restricted Google Workspace governance folder; use QuickBooks Online for the ledger and a shared governance register for decisions, obligations, and risks.

Core policies. Disclose conflicts before discussion; conflicted advisers withdraw from recommendations. Related-party contracts require independent review and a documented market comparison. Record family contributions as legally documented capital, loans, or gifts as applicable; prohibit implied equity entitlements.

Provide a confidential complaints address accessible to the independent adviser. Prohibit retaliation; allegations involving the founder go directly to that adviser. Ban misleading checkout charges, undisclosed merchant deductions, and courier underpayment.

Require multifactor authentication, role-based access, vendor data-processing terms, and documented deletion and incident procedures. Counsel shall approve jurisdiction-specific retention periods and notification requirements.

The founder shall nominate an emergency operating delegate, with counsel documenting limited payment and continuity authority. Store recovery credentials in a controlled password-manager emergency-access arrangement.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Evidence gate

• ☐ Operating agreement and authority register agree.
• ☐ Family funding is documented and reconciled.
• ☐ Independent review and payment controls work in practice.
• ☐ Reporting demonstrates fee-cap compliance, courier-floor compliance, and order contribution.
• ☐ Filing, covenant, privacy, and insurance obligations have owners.
• ☐ Conflicts, complaints, incidents, and succession procedures are signed and accessible.

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.

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.

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.

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.

Decisions and trade-offs

Do this next

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.

Position

SwiftBite’s citizenship programme will prioritise independent-restaurant resilience, courier wellbeing, and avoidable delivery waste within its launch zone. The founder owns delivery and reporting; no partnership or impact claim is approved until supporting evidence exists. Merchant commission limits, transparent consumer pricing, and the courier earnings floor remain unconditional operating commitments, not charitable achievements.

Citizenship charter, community-needs assessment, programme d

Citizenship charter

SwiftBite will fund practical local benefits without increasing merchant commissions, introducing hidden consumer charges, or reducing courier compensation. Participation is voluntary and has no bearing on merchant ranking, courier dispatch priority, or customer service.

A fixed share of recognised platform revenue will enter a restricted citizenship ledger each month. Funding continues during loss-making periods; unused allocations carry forward. Restricted balances cannot fund promotions, referral incentives, founder expenses, or ordinary compliance costs. The programme allocation counts as a variable cost when testing contribution per order.

The founder approves expenditure and maintains receipts, consent records, partner agreements, and outcome evidence. Any recipient connected to the founder or family must be disclosed publicly before approval. Donations cannot be conditional on commercial exclusivity, favourable reviews, or restaurant recruitment.

Community-needs assessment

The following needs are working hypotheses, not established findings. The founder will interview participants privately, record dissent, and return the resulting priority statement to respondents before committing programme funds.

The founder will publish an anonymised needs register showing the issue, supporting evidence, affected groups, proposed response, and responsible owner. Restaurant turnover and individual courier earnings remain confidential. No food-access service will be promised before a qualified partner accepts food-safety, storage, and distribution responsibilities in writing.

Programme commitments

Programme sessions must remain separate from mandatory onboarding. Required safety instruction, wage-floor top-ups, insurance, and legal compliance are operating expenses, never citizenship expenditure.

Partner agreements will define the activity, spending ceiling, safeguarding responsibilities, evidence requirements, cancellation rights, and treatment of unused funds. No partner may sell participant data or use SwiftBite participation as endorsement without written consent.

The founder participates through scheduled coordination time. Future employees may join during paid working time with manager approval. Contractors are never asked to provide unpaid delivery, training attendance, or event support; participation payments sit outside ordinary delivery earnings calculations.

The annual impact report will disclose opening funds, allocations, spending, closing funds, partner names, verified outcomes, unsuccessful activities, complaints, and corrective actions. It will distinguish attendance from demonstrated benefit and measured packaging changes from unverified emissions claims.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

Limited founder capacity could produce commitments without follow-through; unsigned proposals remain unannounced. Small launch volumes may fund only modest activity, so partners receive no guaranteed spending beyond available balances.

Contractor status does not remove wage, classification, or safety obligations. Local counsel must review participation payments and earnings-floor procedures. Complaints about ordinary service failures enter the operating remediation log rather than being reframed as citizenship successes.

Evidence gate

• ☐ Revenue allocation reconciles to cash-backed restricted funds.
• ☐ Community priorities reflect documented participant input.
• ☐ Partner scope, responsibilities, and evidence requirements are signed.
• ☐ Contribution testing includes citizenship funding and lawful courier compensation.
• ☐ Participation is voluntary, paid where applicable, and free of dispatch consequences.
• ☐ Public outcomes are supported by records and explicit limitations.
• ☐ Annual reporting has an owner, deadline, and retained evidence trail.

Position

SwiftBite is launch-stage; an acquisition mandate is premature until operating records substantiate transferable earnings and durable merchant relationships. The harvest position is a profitable regional network sold to a grocery-led strategic buyer, not an owned driver fleet or a claimed regional monopoly. Merchant commission protection, published courier compensation, and transparent consumer pricing remain binding sale conditions.

Valuation range

Confidential acquisition prospectus — controlled-distribution draft

Seller: SwiftBite, currently a single-member LLC. The founder controls buyer outreach until investors or a reconstituted board receive approval rights. Conversion to a C-Corp follows the institutional-funding trigger, not preparation of this prospectus.

Transaction perimeter: The operating entity, brand, merchant agreements, dispatch procedures, licensed-software rights where transferable, and permissioned customer relationships. Couriers retain independent choice over continued participation; the prospectus must not characterize their vehicles or future availability as acquired assets.

Strategic proposition: Offer a grocery buyer verified neighborhood delivery coverage, repeat merchant demand, and an established courier recruitment and dispatch operation. Grocery-order adjacency is contingent upside; exclude it from standalone earnings and valuation until paid pilots establish handling costs, capacity, and service reliability.

Buyer qualification register

These are screening candidates, not confirmed acquirers. The founder maintains the register using company filings, investor-relations releases, FTC and Competition Bureau notices, and PitchBook through a retained adviser. Each entry records the announcement date, transaction status, geography, disclosed consideration, and source link. Rumored or abandoned transactions cannot support valuation claims.

Required prospectus exhibits: Merchant-level revenue cohorts; courier activity and retention; dispatch coverage by neighborhood and daypart; customer repeat ordering; service failures and refunds; restaurant concentration; software dependence; and reconciled standalone earnings. Separate contracted access from actual activity. Strip identifiable customer and courier records from preliminary materials.

Negotiating mandate

Distribute the teaser anonymously. Release the prospectus under NDA; release sensitive operating records through a permissioned data room after buyer qualification. Require software-provider consent and merchant-assignment analysis before signing. Describe founder transition duties in a separate, compensated agreement rather than leaving continuing obligations embedded in the purchase price.

The numbers

Decisions and trade-offs

Retain licensed software rather than capitalize speculative proprietary technology value. Secure assignment rights, data export, and transition support during vendor negotiations.

Do not accelerate expansion to manufacture an acquisition narrative. Open additional markets only after existing-city contribution and operating break-even evidence support deployment. Reject bidders whose investment case requires breaching the commission cap or suppressing courier compensation.

Do this next

Risks in your situation

Courier participation may fall after ownership changes. Obtain consented retention evidence; prohibit guarantees of future availability.

Contractor classification, vehicle expenses, and wage-equivalent measurement could materially increase costs. Local counsel must validate dispatch practices and compensation calculations before earnings enter buyer materials.

Unknown jurisdiction, family-capital terms, and future dilution prevent credible founder-proceeds estimates. Reconcile ownership and tax treatment before accepting headline consideration.

Evidence gate

• ☐ Standalone earnings reconcile to bank, processor, and settlement records.
• ☐ Buyer shortlist reflects documented mandates, not acquisition speculation.
• ☐ Merchant retention and courier availability are evidenced.
• ☐ Software, data, and contract transfers are legally executable.
• ☐ Sale documents preserve operating-ethos protections.
• ☐ After-tax proceeds, stock restrictions, and approval rights are signed off.

Position

SwiftBite’s transition remains conditional: no signed acquisition agreement, buyer identity, purchase price, or software-transfer consent has been supplied. The founder’s proposed earn-out must protect merchant continuity without transferring control of fees, courier pay, or service quality beyond enforceable safeguards. Buyer-funded integration, licensed-software permissions, and a fixed retention definition are conditions of signing.

Succession plan

The acquisition agreement will name the founder as merchant-continuity lead, a buyer integration director as delivery owner, and the white-label vendor’s technical lead as interface owner. These are proposed contractual assignments.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

The founder’s merchant relationships are concentrated personal assets. Buyer support must shadow those relationships before handover, while the founder retains escalation access.

White-label restrictions could prevent integration or inflate switching costs. Unlicensed interfaces and premature shutdown are prohibited.

Gross retention can conceal inactive restaurants. Operational availability and departure notices must accompany the headline result; replacement sign-ups remain separate.

Evidence gate

• ☐ Vendor permissions and buyer funding are executed.
• ☐ Merchant communications, consents, and objections are archived.
• ☐ Retention meets the agreed target against the frozen cohort.
• ☐ Settlements reconcile and rollback evidence is accepted.
• ☐ Fee protections and courier-pay safeguards remain enforceable.
• ☐ Permanent support ownership and earn-out determination are documented.

Position

SwiftBite’s mentorship and investment legacy remains conditional on operating success, not an activity funded from launch capital. The founder will preserve merchant relationships, capped pricing and courier pay protections while building a modest advisory record. A regional incubator becomes eligible only after verified city profitability, an orderly operating handover and personal liquidity independent of SwiftBite’s working capital.

Legacy thesis

SwiftBite Main Street Fellowship is the proposed regional investment and advisory vehicle. Its mandate is to back businesses that improve independent merchants’ retained income, operational control or access to customers without replacing an incumbent’s extraction with their own.

The geographic mandate covers SwiftBite’s launch city and neighbouring communities accessible for merchant visits without overnight travel. Eligible businesses include merchant-owned ordering tools, inventory coordination, transparent payments, scheduling, accessible bookkeeping and shared local logistics. Applicants must identify the merchant who pays, the expense displaced and the contractual protection against future fee escalation.

Excluded businesses include concealed consumer charges, mandatory exclusivity, customer-data resale, punitive merchant termination fees and labour models dependent on unpaid waiting time. Marketplace applicants must disclose their full merchant take rate, refund allocation, customer acquisition restrictions and worker compensation calculation.

The founder serves as Founding Mentor, concentrating on merchant acquisition, field sales, route density, pricing discipline and local partnerships. The founder will not act as technical lead. An independently contracted Technical Reviewer evaluates software licensing, security, integration dependencies and vendor portability; External Counsel reviews investment documents, conflicts and worker-classification exposure.

Each advisory engagement uses a signed scope covering confidentiality, conflicts, permitted introductions and termination without penalty. The venture retains its intellectual property. Merchant introductions require merchant consent; SwiftBite order histories, customer identities and courier records remain outside fellowship diligence.

Before investing, the founder signs a memo recording merchant economics, founder references, technical dependencies, foreseeable harm and reasons for rejection as well as approval. External Counsel selects the instrument appropriate to the investee’s legal form. Proposed documents must disclose dilution, liquidation priority, information rights and transfer restrictions in plain language; undisclosed side arrangements are prohibited.

A shared Airtable register will hold referrals, screening outcomes, conflicts and advisory commitments. Feedly alerts, regional accelerator newsletters, chamber announcements and public company-formation notices will feed the register. Applicants enter through a consent-based form; incorporation alone is not treated as commercial evidence. Public fellowship reporting uses founder-approved summaries and anonymised merchant outcomes, never confidential operating data.

The numbers

Decisions and trade-offs

Do this next

Risks in your situation

The founder’s merchant access can create perceived coercion. Restaurant participation must never affect SwiftBite placement, support, pricing or contract renewal.

Published per-delivery compensation does not itself establish compliance with the local minimum-wage-equivalent commitment or contractor classification. Unresolved courier pay or classification exposure blocks activation.

An exit may never occur. No incubator lease, staffing promise or investment pledge may depend on prospective proceeds. The founder’s lack of engineering capability also requires independent technical diligence rather than relying on persuasive demonstrations.

Evidence gate

• ☐ SwiftBite’s operating targets are distinguished from verified results.
• ☐ Sustained profitability and successor responsibility satisfy the activation gate.
• ☐ Realised liquidity and protected household reserves are documented.
• ☐ Operating capital and family obligations remain protected.
• ☐ Counsel approves entity separation, conflicts and investment documents.
• ☐ Advisory agreements preserve founder autonomy and merchant consent.
• ☐ Every selected venture passes merchant-benefit and technical diligence.
• ☐ Pricing, courier compensation and data protections remain intact.