Resources

The owner’s
reading room.

Playbooks written for people who run the register and the marketing. Everything here is readable on this page — no gated PDFs, no email capture, no fluff.

Playbooks

Read it here. Use it tonight.

Each one opens in place — grounded in how the platform actually charges, forecasts and fulfills.

Your first offer: a 7-day launch plan

Day 1 — claim and verify. If you haven’t already, the AI has likely assembled your profile from public listings. Confirm it’s yours and verify — Google Business Profile is instant, and most businesses finish in under ten minutes.

Day 2 — get the storefront straight. Hours, phone, menu. A wrong “open now” kills the sale before your offer ever matters, because the traveler app closes with your hours, not your headline.

Day 3 — draft the offer. One item you’re proud of, a discount in plain numbers. Daily budgets run $10–200; start at $15–25. Radius runs 5–60 miles; start at 20–30 so you’re reaching drivers before their exit, not after it. On audience: road trippers respond roughly 20% above the family baseline, couples a bit below it, and EV drivers are the most selective — pick one segment, don’t blast all four.

Day 4 — publish through the review gate. Read the offer once as a stranger, then confirm you’ve reviewed it. Nothing goes live without that confirmation, and drafts are never visible to travelers — so take the extra minute.

Day 5 — work the queue. Orders arrive with payment authorized and wait for your accept. The traveler is moving at 70 mph; acceptance speed is part of the product.

Day 6 — adjust one variable. Widen the radius before raising the budget. Reach scales with both, but miles are free and dollars aren’t. You pay on traveler engagement, not impressions, so a wider net costs nothing until it works.

Day 7 — read the numbers and decide. Analytics shows redemptions per offer. Keep what converted, retire what didn’t, and scale the winner. That loop — one week, one variable at a time — is the whole game.

Pricing your offer without killing margin

Start with what HitDaHiway actually takes: 6% per order on Starter, 4% on Pro Merchant, 3% on Premium — charged on the discounted subtotal, never on taxes. Rejected and canceled orders carry no commission at all.

Do the worked example before you set a discount. A $30 ticket at 20% off is a $24 subtotal; at Starter’s 6% the commission is $1.44, so you keep $22.56 — from a customer who was otherwise driving past. The discount is the big number in that math, not the commission. Protect the discount side first:

  1. Discount where the margin lives. Drinks, sides and add-ons absorb 20% far better than your proteins do.
  2. Set a minimum purchase. Every offer supports one. A 15% discount riding on a $25 minimum behaves completely differently from the same discount on a $6 check.
  3. Cap it. Use the total redemption cap and the per-traveler limit so a hit offer is a good week, not a margin incident.
  4. Prefer bundles to deep percentages. A family road-trip meal at a set price protects margin better than 30% off the menu, and travelers read a bundle as a decision already made.

Then let volume pick your plan. Pro’s $59/month buys you two points versus Starter, so it pays for itself once you clear roughly $2,950/month in platform orders; Premium’s extra point over Pro breaks even around $14,000/month and adds instant payouts at 1.5% (next-day payouts are free on every plan). Annual billing takes 20% off either fee. Upgrade when the math says so — not before.

The 60-second traveler: designing for drive-by intent

On HitDaHiway, the distance from first glance to paid checkout is about a minute. The journey has nine touchpoints — discovered, matched, offer card, detail page, checkout, route, arrival, payout, repeat — but the traveler experiences the first five in the time between two exits. Everything you write should assume it will be read at a glance by a passenger while the driver asks “well?”

Name the thing, not the vibe. “10% OFF tacos” beats “great value” every time, because a number is a decision and an adjective is homework. Your business name should say what you are; the offer line should say what it costs.

Let distance do the selling. The card shows how far away you are. Under a few miles, you’re an impulse; at twenty-plus you need a stronger hook, because you’re asking for a detour, not an exit. Match the depth of the offer to the length of the ask.

One photo, one dish, tight crop. The image is thumbnail-sized on a moving phone. A single plate fills it; a dining room disappears in it.

The detail page closes; your hours confirm. When the passenger taps through, your About paragraph and photo strip do the convincing — and “open now” does the closing. Checkout itself is a Face-ID moment, so the last mile isn’t your problem. Your problem is the accept button: the order arrives while they’re still driving toward you, and a fast acceptance is the difference between a table filled and a car that kept going.

From authorized to fulfilled: run orders without dropping one

Every order lands in your portal as payment authorized — the traveler confirmed, their card is authorized, and nothing is captured until you act. From there you have exactly two moves, and both are honest ones.

Reject costs nothing. A rejected order carries zero commission and the traveler’s card is never charged — the authorization is simply released. Out of brisket at 7 PM? Reject fast. A quick honest no keeps your rating; a dangling authorization loses the traveler and the next one they would have told.

Accept starts the clock. Commission accrues when you accept, and the traveler’s app starts tracking your kitchen from that moment. Accept only what you can serve, then mark the order fulfilled at handover — that’s what moves the money and closes the loop on their side of the windshield.

Refunds are proportional, not punitive. A full refund reverses the order’s commission entirely; a partial refund reverses it in proportion. Fixing a mistake never costs you platform fees on the part you gave back.

Duplicates can’t happen. Order submission is idempotent: when a spotty highway connection resubmits the same order, the platform returns the original instead of creating a second one. You will never see — or be paid commission on — a phantom duplicate, so work the queue without second-guessing it.

Last thing: every accept, reject, fulfill and refund is written to your audit log. When a dispute shows up three weeks later, you argue with receipts.