Work Less. Live More. Automate.

A stack we built, and still run.

Salty Home Services is our own home services company, in Utah. Its phone, intake, follow-up, reviews, scheduling, and site are all work we did — and work we keep running.

Surfboards lined up against a wall
The context

Our own shop, with one phone and no office.

Salty Home Services is our own home services company, operating in Utah. The admin load was the usual one: calls arriving while the crew was on a job, estimates waiting on a follow-up nobody owned, reviews never asked for, and a schedule living across text threads.

We connected what it already paid for, set up what was missing, and now run the result. What’s listed below is what was built and is live. There are no performance figures on this page, because publishing numbers we haven’t measured would make the rest of it worth less.

What was built

The stack, in full.

Missed-call text-back & AI answering

Built on Quo. Calls that aren't picked up get an immediate text back; the AI line answers and takes the job details when nobody is free.

Lead form into Housecall Pro

Web leads land directly in Housecall Pro with the job details attached, so dispatch works from one list.

Estimate follow-up

Sent estimates are followed up on a schedule rather than waiting for someone to remember them.

Review requests

Completed jobs trigger a review request to the customer.

Scheduling

Jobs, crews, and customer records kept in one calendar rather than spread across text threads.

SEO website

saltyhomeservices.co — built to be found for the work the shop wants and wired into the same intake.

Why it matters to you

You’re not the pilot customer.

This is the same stack, built by the same team, in a business that dispatches every day. We didn’t hand it over and leave — we still run it, which is exactly what an embedded engagement is.

Shells on sand

Work Less. Live More. Automate.

Want the same thing running on your shop? Start with the $499 Integration Audit, or book a call.