Home Owner App tour Request Setup

How a shop makes money with BayFlow

Core $350 a month. 30-day trial. No per-lead fee. Sample, not a result.

One request. One job. The $350 fee on the same record.

  1. Customer finds the shop

    Google, Maps, a referral, a QR code, or the shop link.

    $0 Sample, not a result

    Money: $0 in BayFlow ads on Core. This is demand the shop already has.

  2. Customer submits the request

    Concern, photos, phone, and an optional time on /s/{shop}.

    $0 Sample, not a result

    Money: the request is a record. Not recorded yet.

  3. Shop gets a text alert

    Core queues a shop alert so the desk can see the request on a phone.

    $0 Sample, not a result

    Money: the shop gets a text alert with the request.

  4. Owner confirms the time

    Confirm Requested Time in the Owner App. The customer gets a confirmation text. Until that tap, the time is a request, not a confirmed appointment.

    $0 Sample, not a result

    Money: the visit is now eligible for reminders. Not recorded yet.

  5. Reminders go out

    A 24-hour reminder and a 2-hour reminder for that confirmed time. A customer can ask for a new future time from the reminder link. That returns the appointment to requested until the shop confirms it again.

    $0 Sample, not a result

    Money: the confirmed visit stays on the board. This page does not claim a no-show rate.

  6. Customer shows. Shop sells the repair

    The shop diagnoses, estimates, sells, and does the work.

    $0 Sample, not a result

    Money: not recorded yet. Dollars start when the owner marks Sold.

  7. Owner marks Sold and enters the job

    Repair-order number, collected revenue, and direct job cost. Those figures are shop-entered.

    $1,250 Sample, not a result

    Money: DEMO-1042 collected $1,250 minus $625 cost = $625 contribution. Sample, not a result.

  8. Owner App shows contribution against Core

    When at least one sold job has both collected revenue and direct job cost, the Owner App can show recorded contribution next to the $350 Core fee.

    $625 vs $350 Sample, not a result

    Money: one DEMO-1042 job covers Core. Four such sample jobs = $2,500 vs $350 (about 7× the fee). That is volume, not jobs required.

The shop still diagnoses, sells, repairs, and collects. BayFlow keeps the customer request and the shop-entered contribution on one record, then shows that contribution against the Core fee. Plans: Core $350, Growth $500, AI Texting $750. Sample numbers are the labeled Owner App demo job DEMO-1042, not a Yaffo result and not proof BayFlow created a sale.

Sample math, not a shop result

These dollars are a labeled sample so the arithmetic is visible. They are the Owner App demo job DEMO-1042. They are not a typical job, not a BayFlow average, and not a recorded outcome from Yaffo Auto Service or One Stop Oil & Auto.

Line Amount
Plan Core
Monthly fee real price $350
Sample ad spend $0
Sample repair-order number DEMO-1042
Sample collected revenue $1,250 Sample, not a result
Sample direct job cost $625 Sample, not a result
Sample recorded contribution $625 Sample, not a result
Jobs to cover the month 1 Sample, not a result

$350 divided by $625 is 0.56. The fee-coverage check rounds up, so one recorded sold job at this sample contribution covers the Core month. Sample, not a result.

Sample month, volume only: four DEMO-1042 jobs = $2,500 recorded contribution vs the $350 Core fee (about 7× the fee). That is four sample jobs in a period. The shop does not need four sold jobs to cover Core. One such sample job covers the month. Sample, not a result.

Change the contribution and the job count changes. This is planning math, not a promised result. It does not prove incremental lift, payback, or ROAS.

Request setup. A founder follows up.

Three fields start the conversation. 30-day trial. No per-lead fee.

BayFlow does not create search demand, guarantee delivery, sell or perform the repair, or prove incremental revenue. Published case studies need a fixed baseline, a fixed post period, matched repair orders, and the owner confirmation PUBLISH_RECORDED_EVIDENCE.