You bring the demand. Onepath answers and books every lead. Clair runs the work behind the booked job: forecasts, payroll, cash and scorecards, in the shop's own Slack. One team for the shop, three revenue lines for us.
The shop sees one team. Behind it, each partner owns one stage of the job, from the homeowner's first search to the technician's commission.
The right homeowners find the shop and reach out.
Every lead answered, booked and traced to the dollar that brought it.
The office work that repeats every week, done in Slack.
Marketing work is asked for weekly. Operations questions come in daily, from the owner, the office manager and the dispatcher. Clair turns your book of shops into recurring task volume you share in.
On the shops you bring, for 24 months each.
Clair reads capacity every morning and tells your ads team when to push or pull spend.
A shop running payroll and cash through its channel doesn't shop for a new agency.
Completed jobs, equipment and reviews, ready to drop into service-area pages.
Illustrative: 30% of what 100 shops spend on Clair tasks each month. Spend varies by shop size and use; the rate card sets prices.
Anyone on the team asks about the business in the shop's Slack channel.
Hydra hands the question to Clair, who answers in the channel under her own name.
Work that changes a system waits on an approval card. Nothing runs until someone at the shop says yes.
Unsold estimates, memberships due and missed calls get called, texted and booked by Onepath.
On accounts you manage, Clair sends the capacity signal to your ads team or agent, and your team makes the change.
Onepath's lead and conversion data flows into HydraOS through the partner API.
Onepath answers and books leads from every channel below, and reads ad spend from Google, Meta and Microsoft to price every booked job.
Clair reads the systems a shop already runs and acts through the ones that matter, every change approved first. Nothing new for the office to learn: they ask in Slack.
Jobs, invoices, payments, technicians and memberships. ServiceTitan through Buck's certified integration; Housecall Pro through Onepath's.
Leads, spend and outcomes from Onepath across Facebook Ads and Yelp, approved callbacks from the shop's own number, and Google Ads budgets raised or trimmed to crew capacity.
Receivables, payments and vendor bills next to the forecast, for a cash outlook four to six weeks out.
Pay runs read and checked against job hours; on Gusto, commissions entered on the open payroll for the office to run.
Price lists and feeds matched to the ServiceTitan price book: increases flagged, cheaper vendors found, new prices written on approval.
Ride-along and meeting notes into technician scorecards, and the National Weather Service forecast moving the demand outlook.
The connection between Hydra and Clair is the first thing our technical session builds.
of every Clair dollar collected from the shops CI Web Group or RTM bring in.
The shop connects ServiceTitan, QuickBooks and payroll through Clair, and keeps working whatever happens to this agreement.
Hydra receives Clair's answers through the task API. Onepath shares lead and conversion data with HydraOS, as it does today.
Neither side trains models on the other's data or builds a product in the other's lane with it, during the agreement and 12 months after.
Payroll entries, ad changes and outreach wait for someone at the shop to approve them.
She answers under her own name inside Hydra, which introduces her as the shop's operations agent.
Our first shared shop will run Clair and Onepath together. The open items decide how the agreement is written.