Every piece of software a contractor uses sits on top of someone else's infrastructure: a database engine, a mail system, a server to run on. The question is never whether to use outside infrastructure — everyone does. The question is what you build yourself and what you rent, and whether that choice is made on purpose or by accident.
OAS draws that line deliberately, and the same line shows up everywhere in how the system is built.
What OAS builds itself
The parts that are specific to running a contracting business are built in-house, because OAS needs to define those business rules itself. That includes:
- Which business a lead belongs to, and the server-side controls that keep each contractor's inquiries associated with the right business.
- The customer record itself — matching a new inquiry to someone already on file by name, phone or email, and leaving an uncertain match for a person to decide rather than guessing.
- Recorded inquiries, status changes and notes, organized in one ordered history.
- The OAS team's attention-first overview, helping operators identify records that need follow-up.
These decisions encode what OAS knows about a contractor's business that a generic tool does not: that a false match is worse than a duplicate contact, that a lead is not the same thing as a form submission. Using an off-the-shelf product unchanged would mean accepting someone else's rules for those decisions.
What OAS rents
For general infrastructure needs, OAS uses established managed services instead of building and operating equivalent systems itself:
- OAS uses Supabase for its primary application database and sign-in infrastructure.
- Outgoing email — lead alerts, notifications — is delivered through Resend's mail infrastructure, not an in-house mail server.
- The application itself runs on Vercel's hosting, not on a machine OAS operates.
None of these vendors decide what a lead is, when a contractor should be alerted, or how a customer's history is organized. Those services handle substantial infrastructure responsibilities, including storing data, managing authentication, delivering email, and hosting the application. OAS remains responsible for the application rules: how customer and lead records are structured, when actions are triggered, and which authorized users can access them.
Why the split matters to you
A mail provider or a hosting company sells the same service to thousands of businesses, none of them contractors specifically. Nothing about how it works understands what a lead is, what a false match costs you, or why a missed inquiry matters more on some days than others. Those decisions live in the part OAS built, not the part it rented — which is why that part is where the engineering attention goes.
That is the whole idea: build the part that is actually about your business, and rent everything that is not.
If you want to see how your customer relationships are kept, get in touch.