Cinch

SENTI · PREP WORK IS EVERYTHING

Make a good website

Prep work is everything. You cannot scream at the model for garbage-in, garbage-out. Describe the chat before the chat happens. Write the goal, the boundaries, the deliverable, and what done looks like — then paste. The prep is the product. A build must research 50 competitor sites, keep their best features, and show the customer at least five reference sites.

Prep work is everything. Describe the chat before the chat happens. Spec website, admin, accounting, CRM, and delivery — or mark N/A — before Conductor builds. Senti holds that brief on the Seed. Do not dump a suggestion file on cinchseed.com. Do not open AI cold. Programming the Seed is not enough. Research 50 competitor sites, take the best features from them, and give the customer who ordered the website at least five reference sites to open. Do not paste those sites’ headlines onto the page. Open a Seed playbook and fill each chapter there — method by method — before Conductor builds. Just Putz It is not a Cinch Seed.

Research 50 competitor sites before the build. Take their best features. Give the customer who ordered the website at least five reference sites to open. Leave their headlines on their sites.

Method demo — think, then compile

This pack is Hometown Runner, a delivery platform — not a dining room. Senti has to think through customer order, restaurant portal (photo/PDF paper-menu draft, five-minute sign-off, 86 during service — no POS certification), driver portal, and the ledger. Do not copy another restaurant format. Your real instruction pack is filled chapter by chapter on Seed admin or the owner portal — then print or download.

  1. Method 1

    Describe the chat before the chat

    Write intent, in/out scope, source of truth, non-negotiables, and what done looks like. Exact inputs win.

  2. Method 2

    Spec every lane

    Website, admin, accounting, CRM, and delivery — all addressed or explicitly N/A. A pretty homepage alone is not a website.

  3. Method 3

    Lock delivery and money

    Check the fulfillment mode and fee rules before coding. If money is unclear, fail closed.

  4. Method 4

    Paste one job into Conductor

    Senti holds the brief. Conductor sequences one task at a time. Do not open a wandering chat.

  1. Think first for Hometown Runner. This is a hyper-local food delivery platform (DoorDash concept): customer order nearby, restaurant portal, driver/scout portal, and admin ledger. It is not a restaurant dining room, bakery, or pizza shop. Do not copy another restaurant format. Host: the live host. Done looks like: a guest orders nearby food, a restaurant accepts the ticket on the portal, a driver takes the run, and admin shows 10% → 5% scout / 5% driver, $0 platform on the order.

Senti compiled

Hometown Runner instruction pack

# Hometown Runner — Seed instruction pack

Prep work is everything. Describe the chat before the chat happens. Spec website, admin, accounting, CRM, and delivery — or mark N/A — before Conductor builds. Senti holds that brief on the Seed. Do not dump a suggestion file on cinchseed.com. Do not open AI cold. Programming the Seed is not enough. Research 50 competitor sites, take the best features from them, and give the customer who ordered the website at least five reference sites to open. Do not paste those sites’ headlines onto the page.
HARD RULE: a delivery-platform Seed (Hometown Runner, Home Town Runnner) is DoorDash-style — three role-based logins (customer, merchant, driver), restaurant portal, driver/scout portal, admin ledger. Senti must think through those apps. Platform food share stays $0 on restaurant orders (subscriptions only). Hometown charges the restaurant $0.25 per order for API expenses — not the diner, driver, or scout. The 10% is 5% scout + 5% driver. Stripe three-party Connect: restaurant, scout, and driver each have a Stripe account. Subscriptions and payouts use Stripe Connect ACH, not card. Menu is photo/PDF first (snap the paper takeout menu, five-minute sign-off, 86 during service) with website crawl as fallback; after a kitchen connects its public menu page Hometown auto-updates price and 86s — no Toast / Square / Otter / POS certification. Trip is $4.50 + $1.50/mile. Driver software ($39/$79) after 60 days free from the first successful drive. 60-day suspend. Onboarding: license, insurance, existingPlatformActive (DoorDash / Uber Eats) — no expensive background check. One-page IC agreement (liability, vehicle, indemnification). Core dispatch only: FIXED 2-mile merchant radius, 300 meter kitchen arrival geofence (Driver Arrived), 100 feet drop-off check. DoorDash-class diner flow (thin Seed): track placed → kitchen → driver assigned → at the kitchen → on the way → delivered; pickup vs delivery; leave-at-door + photo note; reorder; rate food + drop; flag a missing plate; one next offer max. No DashPass, no 15–30% diner markup, no Peak Pay, no live GPS. Scout moat: Riley sends dine-in customers (e.g. seven couples/week) because FSR traffic is ~70% dine-in and only ~5% delivery. Scout pay: one delivery a month or the 5% cascades to the next most-active signed scout at that kitchen. A restaurateur can scout another kitchen after one delivery — they cannot keep the 5% on their own. Do not copy a dining-room, bakery, or pizza restaurant format. Diner landing stays guest-only — no 1099 / $39 / GMV / Stripe / geofence / IC / ACH / background check / OCR / 86 / Red Card / POS / API expense / $0.25 / DashPass / 15–30%.

Host: the live host

## How this project is developed
1. Describe the chat before the chat — Write intent, in/out scope, source of truth, non-negotiables, and what done looks like. Exact inputs win.
2. Spec every lane — Website, admin, accounting, CRM, and delivery — all addressed or explicitly N/A. A pretty homepage alone is not a website.
3. Lock delivery and money — Check the fulfillment mode and fee rules before coding. If money is unclear, fail closed.
4. Paste one job into Conductor — Senti holds the brief. Conductor sequences one task at a time. Do not open a wandering chat.

## Chapter scripts

### 1. Intent and done line (Conductor)
Think first for Hometown Runner. This is a hyper-local food delivery platform (DoorDash concept): customer order nearby, restaurant portal, driver/scout portal, and admin ledger. It is not a restaurant dining room, bakery, or pizza shop. Do not copy another restaurant format. Host: the live host. Done looks like: a guest orders nearby food, a restaurant accepts the ticket on the portal, a driver takes the run, and admin shows 10% → 5% scout / 5% driver, $0 platform on the order.

### 2. In scope / out of scope (Atlas)
One job only for Hometown Runner: the marketplace. IN SCOPE: customer order nearby, /portal restaurant desk (pause/online, accept/decline tickets, Driver Arrived staging), /portal driver desk (go online, accept run, 300m kitchen arrival, 100ft drop-off), admin ledger, FIXED 2-mile radius. OUT OF SCOPE: reserve a table, pizza with personality, chef’s dinner plates, kitchen-ticket single-room copy, a $2,000/week restaurant promise, dynamic 8–10 mile expansion, Premier visibility tiers, weather/supply algorithms, KDS fry-fire. Source of truth is the product brief — not a restaurant website template.

### 3. Website vs logged-in product (Pixel)
Public job on the live host: find nearby kitchens and order. Pickup or delivery, track the bag, favorite a kitchen, reorder last bag, rate, flag a missing plate — DoorDash-class diner flow (best-of Uber Eats / DoorDash / Grubhub) without DashPass, Uber One, or 15–30% markup. Three role-based logins: customer, merchant, driver. Behind login: restaurant portal (photo/PDF paper-menu draft, five-minute sign-off, 86 during service, kitchen tickets accepted / cooking / ready; website crawl is fallback; connected public menu pages auto-update price and 86s) and driver portal (DoorDash-style desk + Stripe Connect payouts; scouts can snap the paper menu), plus ops admin. Soft gates: email for a customer order; merchant and driver accounts for the portals. Do not certify Toast / Square / Otter. Do not draw a plated-menu dining room on the public landing.

### 4. Non-negotiables (Quill)
Hard rules for Hometown Runner: platform food share stays $0 from restaurant orders (revenue is driver subscriptions billed on Stripe Connect ACH, not card); Hometown charges the restaurant $0.25 per order for API expenses — not the diner, driver, or scout; restaurants pay 10% on delivery GMV fully split 5% scout + 5% driver; drivers keep 100% of fee + tip + the 5% share via Stripe Connect (direct to the driver); restaurant collects the food total and pays ~2.9% processor plus the $0.25 API expense; trip is $4.50 + $1.50/mile so drivers clear the $0.76 federal mileage rate; payouts fire at a $25 minimum balance or weekly via ACH; drivers manage their own tax forms (restaurant does not issue 1099s); everybody gets 60 days free starting the first successful drive (a delivered run — not signup, first login, or first offer); after day 60 driver software is $39/month part-time or $79/month full-time (weekly $9.99 / $19.99); full-time is app-open more than 30 hours/week or 120 hours in 4 weeks; 60 days without opening the app auto-suspends the driver; onboarding is license + insurance + existingPlatformActive — no expensive background check; one-page IC agreement; FIXED 2-mile radius, 300 meter kitchen geofence, 100 feet drop-off. Fail closed if money is unclear. Do not invent “Reserve a table”, “Pizza With Personality”, “how guests use the room”, or kitchen-ticket chrome.

### 5. Admin, money, CRM, delivery (Lumen)
Admin is the ops ledger — not a host stand. Accounting is 10% fully split 5% scout / 5% driver, $0 platform food share on the order, plus $0.25 API expense from the restaurant. CRM/ops is the restaurant roster plus scout attribution. Market: DoorDash has no published US AOV (Rakuten $37.28; Q4 2025 implied ~$33 global); 8M+ US / 9M+ world Dashers in 2025, typical ~10 weeks / 4 hours. FSR mix 70% dine-in / 5% delivery. Independent median ~$850K (rough). Riley sends dine-in first (seven couples in a week), then those tables become delivery through Riley. Delivery is the product: restaurant portal + driver portal, DoorDash concept. Do not mark delivery N/A. Do not spec a single dining room.

### 6. Acceptance in five minutes (Sentry)
Five-minute test: land on Order nearby (not Reserve a table); shop is nearby kitchens / Pilot Kitchen, not seasonal small plates; diner can pick pickup or delivery, track the bag, and look up Sam Ortiz; restaurant portal shows pickup tickets and a missing-plate flag; driver portal leave-at-door + one next offer; admin shows $0 platform and 5% scout / 5% driver. Fail if pizza-with-personality, dinner service, or dining-room copy appears on Hometown Runner.

### 7. Compile the paste-ready brief (Senti)
Read every chapter as one brief. Write a single instruction Conductor can paste: build the four apps (customer, restaurant portal, driver portal, admin ledger). Do not open AI cold. Do not stamp a restaurant format.

## Senti compiled instruction
Upload this pack as one brief. Do not start a new random prompt. Work the live host in place using the chapter scripts above, in order.