Frequently asked questions
Scope, maturity, integration, AI, and deployment—without ambiguity.
RevenueOS is offered as a private implementation program. The answers below distinguish current capability, implementation requirements, and future product direction.
Private Implementation Program · Selected engagements
01Is RevenueOS AI a generic CRM?
No. It is an RFQ and quote operations layer for industrial sales. It can work above an existing CRM or replace fragmented spreadsheet and email workflows where that is the better scope.
02Is it available as self-service SaaS?
No. It is currently offered through selected private implementation engagements. Scope, data boundaries, and integrations are agreed before deployment.
03Does it replace our ERP?
Usually not. ERP remains authoritative for inventory, accounting, invoicing, or fulfillment when it already performs those jobs well.
04Does the core platform require AI?
No. RFQ identity, workflow, SLA, sourcing, quotes, attribution, and audit work without an AI provider.
05Can we use our own model provider?
Yes, where the selected provider and data policy pass implementation discovery. Local and private OpenAI-compatible endpoints can also be assessed.
06Can AI change prices or select suppliers automatically?
Not silently. Suggestions that affect product identity, pricing, supplier choice, compliance, quote terms, or customer communication require an explicit human-controlled workflow.
07Can it integrate with our current website and CRM?
Most implementations start that way. The integration method depends on platform APIs, tenant permissions, data quality, and the reliability requirements of the RFQ path.
08How long does implementation take?
A focused pilot commonly targets 6–12 weeks after discovery. Multi-team ERP programs are phased and typically take longer.
09What determines price?
RFQ volume, users, integration count, workflow complexity, migration, deployment model, security, customization, and support obligations.
10Can it be self-hosted?
Yes, subject to infrastructure, security, backup, upgrade, and support discovery. A self-hosted license is annual; implementation is priced separately.
11Are AI provider charges included?
No, unless a managed AI arrangement is explicitly contracted. BYO AI usage is paid directly by the customer.
12What is the first step?
A fixed-scope Revenue Operations Assessment that documents the current workflow, loss points, integration inventory, target architecture, and implementation roadmap.
Revenue operations assessment
Start with the commercial workflow, not a software demo.
Document the current RFQ path, identify where demand disappears, and define a controlled implementation with measurable acceptance criteria.