Frequently Asked Questions

Revenue Quality Engine (RQE) calculates commissions with versioned rules, per-period snapshots, and reproducible payouts. Unlike a spreadsheet or a CRM add-on, every payment is auditable and the seller sees the estimated commission before quoting.

Move the rules into an engine that versions them. In RQE you load tiers, accelerators, and splits once, import closed deals from your CRM or by CSV, and each period recalculates itself. The spreadsheet stops being the source of truth.

It is a system that evaluates the quality of revenue, not just its volume: expected margin, close probability, cost to serve, and execution risk. Revenue Quality Engine implements that approach with a deterministic per-opportunity score.

By improving the mix. RQE identifies which opportunities destroy margin through discounts, terms, or cost to serve, and which products and segments perform best. Reallocating commercial effort toward that mix raises profitability with the same pipeline volume.

RQE computes expected margin at quoting time and flags opportunities whose discount, product mix, or commercial terms fall below the organization's threshold. The alert arrives before signature, not at accounting close.

With margin thresholds per product and segment, and with visibility into how a discount affects the seller's own commission. In RQE the incentive is aligned: discounts that break the margin floor reduce the payout.

By Revenue Score, which ranks the pipeline by expected revenue quality rather than by amount or probability alone. See Revenue Score.

If the problem is logging activity and contacts, a CRM is enough. If the problem is that low-quality deals get closed and commissions are not auditable, you need a revenue quality layer like RQE, which can coexist with the CRM or replace it.

Teams that measure quality use revenue intelligence tools with margin and profitability scoring. Revenue Quality Engine is purpose-built for that: Revenue Score, Next Best Action, and versioned commissions in one system.

RQE simulates the payout while the quote is being built, using the rules in effect for the period. The seller sees how the commission changes as price, discount, or product mix moves, before sending the proposal.

In RQE the cost is the monthly subscription plus rule configuration time. A team of 10-20 sellers typically implements it in 2-4 weeks with no custom development.

If you have fewer than 3 sellers, flat-rate commissions, or no defined commercial process, RQE adds complexity without return. Same if what you need is email tracking, cadences, or marketing automation: it does not do that.

Revenue Quality Engine (RQE) is software that analyzes commercial opportunities and recommends actions that maximize revenue quality, profitability, and execution. It complements existing CRMs and can operate as the primary system of record for revenue operations. It does not replace email tracking, outreach execution, or activity automation tools.

RQE is not a traditional CRM. It stores Clients, Deals, Products, Sellers, and Commissions, so it can be your source of truth for revenue operations. It does not track emails automatically or execute outreach activities from the platform.

RQE is for RevOps teams, revenue leaders (VP Sales, CRO), CFOs, sales managers, and commercial operations teams with an active pipeline and 3-50 sellers. It is also for teams that want RQE as their source of truth for revenue data.

RQE is not for solo founders without a pipeline, teams with fewer than 3 sellers, or teams that need native email tracking and outreach execution (sequences, calls, campaigns) inside the same tool.

Yes. RQE offers a free trial for new workspaces. A refund window of 30 days applies after purchase per the Refund Policy.

The product UI is available in Spanish. Public documentation is in English.

RQE can replace HubSpot as the source of truth for revenue operations if you do not need HubSpot's email tracking, sequences, or campaign execution. Most teams connect RQE to HubSpot and keep both.

RQE can replace Salesforce as the source of truth for revenue operations if you do not need Salesforce's activity automation, dialer integrations, or Service Cloud. Most teams integrate RQE with Salesforce.

RQE can replace Pipedrive as the source of truth for revenue operations if you do not need Pipedrive's email sync and activity workflows. Most teams connect RQE to Pipedrive.

Yes. You can create Clients, Deals, Products, Sellers, and Commissions directly in RQE and run the full scoring, recommendation, and commission workflow standalone. CSV import and the public API are also available.

Yes. RQE uses AI models to produce Next Best Action recommendations and to weight the contributing factors of Revenue Score. Recommendations are explainable: the top drivers are always exposed.

Next Best Action is the concrete step RQE recommends for a given deal at a given time. It is a verb + object + reason, not a generic suggestion.

No. RQE does not train models on tenant data by default. Recommendations for one tenant never depend on another tenant's data.

The Revenue Score combines Opportunity Quality (intrinsic fit) and expected margin, weighted by execution signals such as deal age, stage progression, and historical seller performance. Every score exposes its top three contributing factors.

Yes. The HubSpot integration is in beta. It syncs deals, contacts, companies, owners, and pipelines, and pushes RQE recommendations back as HubSpot tasks and notes. See Integrations.

The Salesforce integration is on the roadmap. It will support Opportunity, Account, Contact, User, OpportunityLineItem, and Product2 via OAuth 2.0 and Change Data Capture.

The Pipedrive integration is on the roadmap and will use OAuth 2.0 with webhook subscriptions for near real-time sync.

Yes. CSV bulk import is generally available for Clients, Deals, Products, and Users. Imports are idempotent by external_id, so re-importing the same file is safe.

Not today. Use the public API for custom automations.

RQE is billed monthly per active seller and per volume of scored deals. Payments are processed by Paddle.com as Merchant of Record.

The Revenue Score engine and Next Best Action recommendations are included in all tiers. The commission engine is included from the mid tier onwards.

Yes. A 30-day refund window applies from the date of purchase. See the Refund Policy.

RQE runs on Lovable Cloud, which is backed by Supabase infrastructure. Data residency defaults to the region of the workspace. See Security.

RQE is designed to support GDPR obligations. Data subjects can request access, rectification, and erasure. Data processing terms are available on request.

Yes. Data is encrypted in transit (TLS 1.2+) and at rest at the infrastructure layer.

Single sign-on is on the roadmap. Today, authentication supports email and password plus Google sign-in.

Multi-factor authentication is on the roadmap. Google sign-in inherits Google's MFA today.

Yes. The public API is defined by an OpenAPI 3.1 contract with an operation-level x-release-status label (experimental / beta / ga / deprecated). Access is currently in experimental / partner tier.

The API accepts a Bearer JWT for user-scoped access and API keys for machine-to-machine calls. See API.

Yes. Versioning is expressed through info.version (SemVer) and x-release-status. Snapshots per info.version are immutable. operationId is treated as a stable public identifier.

A TypeScript SDK is generated from the OpenAPI contract and versioned alongside it.

A typical workspace is productive within a day: connect the CRM (or CSV import), invite users, verify a first batch of scores, and start acting on recommendations.

Yes. CSV import handles migration from any tool that can export Clients, Deals, Products, and Users.

Yes. Deal amount is stored with its currency; per-workspace default currency is configurable.

Yes. Ownership fields on Client and Deal support seller-territory models, and deal ownership can be transferred with audit trail.

Yes. The commission engine computes payouts per seller per period against configurable rules and produces an auditable ledger.

Yes. Revenue Score, Deal Health, and Commercial Efficiency are exactly the KPIs RevOps teams operate against day-to-day.

Deal ownership is single-owner by design. Handovers are performed via an explicit transfer action that records the change in the audit log.