A contractor's website can bring in a steady stream of inquiries, and losing even one of them costs real work. A missed call, an estimate request nobody got back to, a customer who reached out once and never again — these aren't failures of effort. They're failures of a system that was never built to hold a relationship once the first interaction ended. OAS exists to be that system: the place a contractor's customer relationships live, independent of whichever channel brought an inquiry in.
What OAS is not
OAS is not a website builder. A contractor's site is one acquisition channel among several, and treating it as the product would mean the thing that actually matters — the customer record — disappears the day the website changes or goes away. That's the whole case for keeping the record separate from the channel; see why a customer record should outlive its website.
OAS is also not a generic CRM. A CRM sold to every kind of business encodes nobody's particular rules. It has no opinion about what a contractor's lead actually is, why a false customer match is worse than a duplicate contact, or how a job that needs a quote today differs from one still being talked through. OAS is built specifically around how a contracting business receives and works a lead, not repurposed from a tool built for somebody else's workflow. Where that line sits, and why OAS builds some parts itself and rents others, is laid out in own the customer relationship, rent the infrastructure.
What a contractor gets today
Stated exactly as it's shipped:
- When a visitor submits an inquiry through a contractor's website, OAS records that inquiry before attempting its email notification to the contractor. The full sequence — how the inquiry is matched to the right business, checked against existing customers, and surfaced to the contractor — is in what happens after someone requests an estimate.
- OAS staff can manually record an inquiry received by phone, text, email, referral, or walk-in, so a conversation that happened outside the website still lands in the same customer record.
- A contractor can sign in to their own portal and see every inquiry logged against their business, newest first. Where inquiry status and outcome controls have been enabled for a business, and the signed-in member has permission, the portal also offers them; otherwise the portal's inquiry list is read-only.
If any of this sounds like it's aimed at the contractor who's lost work to a missed call or a forgotten follow-up, it is — we've written about that problem on its own in a missed call shouldn't mean a missed job.
What's still being built
OAS can already hold an inquiry that arrived by phone, text, email, referral, or walk-in — but today, a staff member has to type it in by hand. Capturing those same channels automatically, without someone recording them manually, is still in development. Until it ships, a website inquiry is the only channel OAS's own systems pick up on their own.
Why this is worth building at all
None of this is complicated technology. What it is, is attention to a problem most software treats as somebody else's job: making sure a contractor's customer relationships survive contact with whatever channel, tool, or website happens to be in front of them this year. That's the whole bet behind OAS — not a faster website, not another dashboard, but a record of the relationship that outlasts both.
If you want to see how OAS keeps track of your own customer relationships, get in touch.