FAQ

Questions, answered.

Common questions about working with OperatorOS. If yours is not here, ask it on the call.

General

Who we are.

What OperatorOS is and how it differs.

Who is OperatorOS?

OperatorOS is an AI systems consultancy. Davis McMurrain works as the AI Systems Architect, with engineers and joint partners sourced per project to ship knowledge systems, workflow automation, decision logic, voice agents, and integrations into the tools you already run.

What makes OperatorOS different from other AI agencies?

Three things. A consult phase before any build, so scope is defined in writing before either side commits. A build inside your environment from day one, so you own all accounts, code, and infrastructure. And a production focus: we ship working systems, not prototypes or proof-of-concepts.

What industries do you work with?

Operators across e-commerce, real estate, professional services, healthcare, and SaaS. The common thread is businesses that want to use AI to automate operations and improve customer experience.

Who actually does the work?

Davis McMurrain leads as AI Systems Architect. Engineers and joint partners are sourced per project to match the scope and stack. You always know who is on your engagement.

Can I see examples of your work?

We discuss past projects and show relevant demos during the discovery call. Due to client confidentiality, case studies are not published publicly without permission.

Working together

How engagements run.

From the first call to the build.

How do I get started?

Book a 30-minute discovery call. We map your operation, current systems, and where AI is the right tool. No commitment to a build.

What happens during a discovery call?

We spend the call mapping your operation, current systems, and where work breaks down. Davis runs it as an AI Systems Architect, not a sales rep. The goal is a clear read on whether the right next step is a build, a smaller piece of work, or no engagement at all.

Do I need to prepare anything before the call?

Not required. It helps to think through your biggest operational bottlenecks and the workflows that consume the most time. If you already have a specific system in mind, bring it. Otherwise we will surface it together on the call.

What happens after the consult?

Within 48 hours you receive a written plan covering the problem statement, system architecture, milestones, timeline, and price. If the scope is a fit, build kicks off in your environment. If not, you keep the plan.

What is the difference between the consult and the build?

The consult is roughly three months of AI Systems Audit, architecture design, GTM strategy, and local agent and Claude Code consulting. You get a clear plan and tangible artifacts. The build is the four-to-six week delivery cycle: discovery, build, deploy, handoff. Many clients run them as one continuous engagement.

Pricing

What it costs.

Project-based, scoped in writing.

What does pricing look like?

Pricing is project-based and depends on scope. After the discovery call, you receive a written plan with transparent pricing within 48 hours. No hourly billing, no surprise charges.

How does pricing work for the build phase?

Each build is scoped individually based on complexity, integrations, and timeline. Fees typically range from $3,000 to $30,000. A focused single-system build is usually $3,000 to $8,000. Multi-system architecture runs $10,000 to $30,000. Underlying API and hosting costs are paid directly by you to the providers, with no markup from us.

Do you offer retainers?

Yes. After handoff, retainers cover monitoring, feature additions, model upgrades, and scaling. Month-to-month with no lock-in.

Where do voice agent costs go?

Voice agents are one of five capability areas. We build them when they make sense for the scope. Usage costs go to the provider directly, no markup from us.

Technical

What it runs on.

Stack, deployment, and security.

What does the system run on?

Next.js and TypeScript on the interface side. A typed service layer with an operational database, cache, and background queues. OpenAI, Anthropic, and Retell AI on the AI layer. n8n for workflow orchestration. The exact components are picked per project and documented in the plan.

Can you work with our existing codebase?

Yes. We regularly integrate with existing systems and codebases. During the consult phase we assess your current stack and plan how new work fits in.

Do you handle deployment and infrastructure?

Yes. Continuous integration, deployment pipelines, monitoring, and alerting are configured from day one. Everything runs inside your cloud accounts so you keep full control.

How do you handle data security?

All data stays inside your environment and your accounts. Secrets are never committed to code. Authentication uses industry-standard protocols such as OAuth and JWT. Row-level security is applied where the underlying database supports it, and dependency audits and security patches run on a schedule.

Integrations

Connecting your tools.

Setup, credentials, and upstream changes.

Who handles the integration setup?

We do. You don't configure OAuth flows or API connections yourself. We scope them in discovery, build them during the engagement, and hand off all credentials and documentation at the end.

What if my tool isn't in your standard list?

Custom connectors are included in every project scope. If it has an API or a structured data export, we integrate it.

Who owns the integration credentials after handoff?

You do. All API keys, OAuth tokens, and webhook configs are documented and transferred on delivery day. We don't retain any access after a project closes.

What happens if an upstream API changes after handoff?

Breakage within your 90-day post-launch window is covered. We fix it. After that, the handoff runbook documents how to update each connector. The integrations are yours to maintain, not locked to us.

Support

After launch.

How to reach us and what is covered.

How do I reach you during a project?

Direct access via Slack, email, or your preferred communication channel. Most teams use async communication. Weekly sync calls are available on request.

What if I need changes after delivery?

Every project includes a 90-day support window for questions and minor adjustments. Larger changes are scoped as follow-on work or handled under a retainer.

What happens if something breaks after handoff?

The 90-day support window covers any issues that arise after delivery. For ongoing coverage, retainers keep the team available.

What happens after the 90-day support window?

The system is yours, with complete documentation and a runbook. For ongoing work, new systems, or architecture evolution, a retainer gives you monthly engineering hours and priority access. You can also re-engage project-by-project as needs arise.

Still have a question?

Bring it to a 30-minute call. No pitch decks. Just the work.

Architecture first100% client-ownedSourced team per project