Step 8 · Research & analysis
Public chapterAI and tech strategy analysis
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.
| Component | Proposed selection | Procurement condition |
|---|---|---|
| Merchant ordering and dispatch | Shipday white-label package | Demonstrate branded ordering, merchant separation, batch routing and complete exports in the purchased tier |
| Payments | Stripe Connect through native integration | Confirm local availability, merchant onboarding, split settlement and transparent refunds |
| Customer messages | Twilio, connected through native webhooks or managed n8n | Demonstrate consent capture, delivery receipts and duplicate suppression |
| Mapping | Dispatch vendor’s supported Google Maps or Mapbox integration | Disclose provider, usage charges, restrictions and outage behaviour |
| Operations dashboard | Vendor dashboard plus restricted reconciliation sheet | Export orders, courier activity, payouts and exceptions without manual re-entry |
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.
| Launch control | Initial setting |
|---|---|
| Service boundary | Grounded launch radius: 4 miles; downtown and adjacent neighbourhoods |
| Maximum batch | 2 orders (estimate), pending food-quality trials |
| Added customer delay from batching | Maximum 8 minutes (estimate) |
| Pickup-to-door allowance | Maximum 25 minutes (estimate), subject to stricter merchant food limits |
| Stale courier location alert | After 3 minutes (estimate) |
| Customer late-order message | When predicted arrival exceeds quoted window by 5 minutes (estimate) |
| Missing webhook alert | After 2 minutes (estimate) without expected acknowledgment |
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.
| Recurring procedure | Owner and schedule |
|---|---|
| Reconcile captured payments, completed deliveries and payouts | Founder; daily |
| Review routing-provider releases, pricing notices and deprecations | Integration specialist; monthly |
| Test material mapping or dispatch updates on saved routes | Specialist; before production activation |
| Export recovery files and test restoration | Founder; weekly |
| Delete operational location history | After 30 days (estimate), unless a documented dispute or legal obligation requires retention |
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.
| Item | Figure | Basis |
|---|---|---|
| Starting capital | $85,000 | Grounding file |
| Founder living reserve | $67,200 (estimate) | Grounded monthly burn multiplied by grounded runway |
| Available before venture expenditure | $17,800 (estimate) | Capital less living reserve |
| Configuration ceiling | $3,000 (estimate) | Fixed-price integration contract |
| Fixed technology allowance | $350/month (estimate) | Licensing, automation and maintenance; usage separately |
| Technology runway allocation | $7,900 (estimate) | Configuration plus 14 months of fixed technology |
| Remaining venture cash | $9,900 (estimate) | Before insurance, legal, acquisition and other operations |
| Illustrative food subtotal | $30 (estimate) | Test basket, not observed demand |
| Commission / delivery fee | 12% / $3.99 | Grounded cap and consumer fee |
| Revenue per illustrative order | $7.59 (estimate) | Commission plus delivery fee |
| Courier base / wage top-up allowance | $5 / $0.50 (estimate) | Published launch proposal; top-up is uncapped |
| Processing | $1.29/order (estimate) | Assumed 2.9% plus $0.30 on food and delivery |
| Messaging / routing / refund allowance | $0.08 / $0.10 / $0.25 (estimate) | Variable-cost planning assumptions |
| Illustrative contribution | $0.37/order (estimate) | Revenue less listed variable costs; excludes fixed overhead |
Decisions and trade-offs
| Decision | Accepted trade-off |
|---|---|
| License rather than build | Less customization; no proprietary application maintenance |
| Prefer native integrations | Reject a cheaper package requiring fragile custom connections |
| Keep founder-led exception handling | Lower fixed payroll, but constrain opening hours to supported coverage |
| Preserve fee cap and wage floor | Pause unprofitable availability rather than hide surcharges or underpay couriers |
Do this next
Deadlines run from chapter approval.
| Action | By when | What proves it worked |
|---|---|---|
| Obtain binding package and usage quote | Business day 5 (estimate) | Scope and cancellation terms fit allowances |
| Validate contractor status and pay calculation locally | Business day 7 (estimate) | Written advice defines covered time, waiting and applicable expenses |
| Contract integration specialist | Business day 10 (estimate) | Fixed price, milestone acceptance and credential handover signed |
| Run merchant-and-courier rehearsal | Business day 20 (estimate) | Event logs, settlements and recovery drill reconcile |
| Approve limited paid launch | Business day 25 (estimate) | Actual contribution and pay-floor checks pass |
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.