Step 5 · Research & analysis
Public chapterInternal analysis
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
| Resource | Current position | Assigned ownership and sourcing | Required operating output |
|---|---|---|---|
| Merchant acquisition | Founder has strong local relationships and 12 years of FMCG/field-sales experience. | Founder retains prospecting, contracting, onboarding, and account recovery. | A founder-maintained HubSpot pipeline records restaurant revenue band, decision-maker, current aggregator terms, menu readiness, signed agreement, and activation status. Merchant contracts expressly preserve the commission cap. |
| Software engineering | No founder engineering capability; no proprietary codebase. | License a white-label ordering, merchant management, dispatch, and courier suite. Purchase independent technical acceptance support rather than employ a developer. | A configured tenant, documented settings, vendor escalation contacts, and an acceptance log. Reject any supplier requiring SwiftBite to maintain application code or integrate essential functions itself. |
| Technical procurement | Founder cannot independently validate architecture, security, or integration claims. | Fixed-scope fractional technical reviewer reports directly to the founder and discloses vendor commissions. | Reviewer checks live workflows, payment ownership, data export, access controls, uptime records, recovery procedures, and the complete fee schedule. Written acceptance is required before subscription activation. |
| Dispatch and courier operations | No dispatcher or courier network is documented. | Founder is launch dispatch lead; a named, trained relief operator must cover absences before orders open. | Vendor dispatch console holds courier availability, assignments, failed deliveries, and incident notes. Founder closes ordering whenever dispatch coverage is unavailable; merchant acquisition pauses during live service coverage. |
| Courier earnings and classification | Contractor posture is specified; jurisdiction, insurance requirements, and lawful classification remain unverified. | Local counsel validates the arrangement; founder publishes delivery rates and administers earnings reconciliation. | Track delivery payments and all availability time SwiftBite requires. Apply the local minimum-wage-equivalent floor excluding tips and vehicle reimbursements. Pay any shortfall through a disclosed true-up; unresolved classification prevents launch. |
| Finance and settlement | Founder controls capital; no reconciliation capability is documented. | Contract bookkeeper establishes a ledger; founder approves refunds and settlements. | Reconcile processor receipts, merchant payables, courier liabilities, refunds, and software charges. Keep merchant funds and taxes out of available operating cash. No unexplained settlement difference may roll into the next payout. |
| Support, privacy, and continuity | No service desk or recovery procedure exists. | Founder owns customer and merchant support; SaaS vendor owns platform restoration. | Use a shared support inbox and incident register. Restrict account access by role, require multifactor authentication, export transaction records, and disable ordering during material payment or dispatch failures. |
Licensing mandate
| Contract area | SwiftBite requirement |
|---|---|
| Scope | Hosted consumer ordering, merchant menu controls, delivery-zone enforcement, courier dispatch, proof of delivery, refunds, settlement exports, and support access must work without custom development. |
| Commercial boundary | Select only within the licensing ceiling below. Quote must disclose order charges, messaging, maps, payment markups, branded-app charges, onboarding, support, taxes, and overages. No fee may be silently passed to merchants or consumers. |
| Term and exit | Require monthly renewal, cancellation on 30 days’ notice (estimate), and no volume minimum during launch. Reject termination charges that exceed the remaining approved subscription budget. |
| Data and payments | SwiftBite controls its processor relationship and can export merchants, orders, settlements, and consent records in usable formats. Contract must identify subprocessors, breach notification duties, and deletion obligations. |
| Acceptance and remedies | Subscription billing starts only after the agreed acceptance demonstration. A checkout or dispatch outage requires vendor acknowledgement within 30 minutes (estimate); unresolved critical defects block launch rather than trigger custom development. |
| Cost monitoring | Bookkeeper maintains a Google Sheets license ledger; founder reviews it monthly. Forecast fixed fees plus usage charges at actual volume and target volume. Breaching the ceiling freezes optional modules and triggers renegotiation or migration—not higher merchant commissions. |
The numbers
| Item | Figure | Basis |
|---|---|---|
| Starting capital | $85,000 | Grounding file; personal and family capital. |
| Personal reserve | $67,200 (estimate) | Grounded monthly personal burn of $4,800 multiplied by grounded runway of 14 months; assumes reserve comes from starting capital. |
| Remaining venture cash | $17,800 (estimate) | Starting capital less personal reserve; confirm funding separation before commitments. |
| Fixed SaaS ceiling | $300/month; $4,200 over 14 months (estimates) | Proposed procurement limits, not vendor quotes. |
| Setup and technical-review ceilings | $1,500 setup; $2,000 independent review (estimates) | Fixed-price purchasing limits. |
| Cash after these commitments | $10,100 (estimate) | Remaining venture cash less fixed SaaS, setup, and review; still must fund legal, insurance, operations, and settlement buffers. |
| Grounded pricing and scale | 12% merchant cap; $3.99 delivery fee; 50 merchants and 300 orders/day by month 12 | Grounding file. |
| Illustrative order revenue | $7.59 (estimate) | Assumed $30 food subtotal × grounded commission cap, plus delivery fee. |
| Illustrative variable costs | $5 courier; $1.29 processing; $0.35 support/refunds; $0.20 software usage (estimates) | Planning assumptions; courier amount must include required earnings true-ups. Processing assumes 2.9% plus $0.30 on $33.99, excluding tax. |
| Illustrative contribution | $0.75/order (estimate) | Revenue less listed variable costs; excludes fixed overhead. Not launch evidence until replaced by quotes and pilot observations. |
Decisions and trade-offs
| Decision | Boundary |
|---|---|
| License rather than build | Accept standard vendor workflows; decline bespoke features and engineering recruitment. |
| Preserve liquidity | Do not treat the personal reserve as launch working capital without an explicit founder funding decision. |
| Limit service availability | Open only when dispatch, support, and courier coverage are confirmed. |
| Protect economics and ethos | If lawful courier costs eliminate contribution, change density, service coverage, or supplier terms. Do not weaken the earnings floor or commission cap. |
Do this next
| Action | By when | What proves it worked |
|---|---|---|
| Founder confirms reserve treatment and complete cash budget. | October 5, 2026 (estimate) | Signed budget includes legal, insurance, settlement timing, and contingency. |
| Reviewer collects comparable, fully loaded vendor offers. | October 12, 2026 (estimate) | Written quotes fit the purchasing limits without omitted essential modules. |
| Counsel verifies courier terms; bookkeeper designs settlement controls. | October 16, 2026 (estimate) | Written legal clearance and reconciled sample ledger. |
| Founder runs controlled ordering, cancellation, refund, outage, and payout tests. | October 23, 2026 (estimate) | Signed acceptance log; actual costs support positive contribution. |
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.
Illustrative figures · validate before actingNext: External analysis