Step 9 · Research & analysis
Public chapterName, domain, and website
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
| Element | Approved specification |
|---|---|
| Public name | SwiftBite |
| Signature | Your neighbourhood, delivered. |
| Merchant headline | Keep more of every delivery order. |
| Consumer headline | Order from the independents around you. |
| Merchant positioning | Local delivery. A capped commission. Clear terms. |
| Voice | Direct, neighbourly, specific; no corporate superlatives or unsupported earnings claims |
| Primary colour | Deep evergreen, #174C3C |
| Background | Warm cream, #FFF8EE |
| Accent | Burnt orange, #B84322; not the sole indicator of status |
| Typography | Inter, self-hosted under its applicable open-source licence |
| Logo | SwiftBite wordmark with a simple street-corner symbol; no speed streaks, national flags, or restaurant imagery implying endorsement |
| Photography | Participating owners and storefronts, with written permission; no stock photographs presented as local merchants |
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
| Asset | Instruction |
|---|---|
| SwiftBiteLocal.com | Preferred merchant website and branded email domain; register only after availability and counsel’s name-screen review |
| SwiftBiteLocal.ca | Defensive candidate only if the launch jurisdiction and registrant satisfy Canadian eligibility requirements |
| SwiftBite.com | Inspect ownership and potential confusion; do not assume availability or negotiate before counsel reviews |
| City-specific variants | Maintain a watchlist using the actual launch and neighbouring city names; no speculative buying spree |
| Social handles | Request @SwiftBiteLocal; record availability and use the same identity wherever obtainable |
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.”
| Pricing block | Display |
|---|---|
| Merchant commission | Capped at 12% |
| Consumer delivery fee | $3.99 |
| Merchant fee basis | Commission applies to the food-and-beverage subtotal, excluding tax, tip, and consumer delivery fee; proposed contract basis, subject to signed approval |
| Additional merchant charges | No mandatory platform, processing, or service surcharge outside the advertised cap |
| Comparator | Publish a merchant-specific comparison only against a verified statement and matching fee basis |
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
| Item | Figure | Basis |
|---|---|---|
| Starting capital | $85,000 | Grounding file |
| Personal burn commitment | $67,200 (estimate) | Grounded monthly burn multiplied by grounded runway |
| Capital remaining before other venture costs | $17,800 (estimate) | Starting capital less that commitment; not unrestricted website funding |
| Launch coverage | 4-mile radius; downtown and 2 adjacent neighbourhoods | Grounding file |
| Merchant comparison | 12% versus 30% | Grounding file; comparison requires matching bases |
| Difference on a $30 food subtotal | $5.40 retained (estimate) | Commission difference only; not incremental profit |
| Identity and landing-page allowance | $900 (estimate) | Fixed-scope contractor procurement ceiling |
| Name-screen legal allowance | $400 (estimate) | Preliminary review, not full trademark prosecution |
| Domain, email, hosting allowance | $250 (estimate) | Initial-year planning allowance; obtain quotes |
| Chapter spending ceiling | $1,550 (estimate) | Sum of allowances; founder approval required before commitment |
Decisions and trade-offs
| Decision | Accepted trade-off |
|---|---|
| Retain SwiftBite, qualify with “Local” in the domain | Less distinctive than a coined name; clearance remains mandatory |
| Merchant-first landing page | Consumer acquisition waits for contracted supply and verified coverage |
| License storefront and routing software | Accept vendor interface constraints; require custom-domain support and exportable merchant data |
| No premium-domain purchase in the launch budget | Revisit naming rather than consume operating capital |
| Lightweight website without advertising pixels initially | Less attribution detail; fewer consent and data-sharing dependencies |
Do this next
| Action | By when | What proves it worked |
|---|---|---|
| Founder obtains name screen and domain quotes | October 7, 2026 (estimate) | Written review and dated availability record |
| Founder registers cleared assets and secures accounts | October 9, 2026 (estimate) | LLC ownership record and tested recovery |
| Designer delivers kit and merchant page | October 20, 2026 (estimate) | Accepted source files and working enquiry routing |
| Founder approves fees, coverage, and vendor checkout | October 23, 2026 (estimate) | Signed terms, service map, and checkout captures |
| Founder checks neighbouring-city domain variants | Monthly (estimate) | Dated watchlist using ICANN Lookup and registrar searches |
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.