Powered by the RFQ Agent on the Vertiqa OS

Turn inbound RFQs into reviewed estimates in minutes.

Vertiqa's RFQ Agent parses an inbound formal RFQ into a draft estimate and a lead-stage opportunity, attaches the source document for context, and notifies a reviewer — the approve action stays human-gated, and approved estimates can't be silently edited.

Book a demoSee it in the app →

Shipped in v1.35 Estimate Approval Lifecycle + RFQ Agent

The spine of every Vertiqa agent

Every agent runs inside the same system of record — bounded by what it remembers, what it is allowed to do, and what gets written down.

Memory

Reads the inbound RFQ, the account, and the prior estimate history

The inbound source artifact, the matched account, and prior estimate revisions all live in the same Kernel as the rest of your org — the draft is built from them, not from a blank slate.

Approval

Agents can draft, but they can't approve

The estimate lifecycle is enforced in two layers (DB trigger + service guard) so agents are structurally blocked from the approve action. When a draft is ready, a reviewer is notified in-app and by email with a deep-link to the canonical /commercial/estimates/{id} workspace.

Audit

Every revision is on record

Status events are written for every transition through the estimate state machine, post-approval revisions clone into a new row (with previous_estimate_id and revision_count populated), and the provenance event ties every draft back to the inbound source artifact it was built from.

What it does

Four concrete behaviors, every one traceable to a shipped v1.35 RFQ Agent or v1.31 Draft Assist capability — no roadmap features, no aspirational claims.

Reads an inbound RFQ and answers with a draft estimate

When a structured RFQ lands on your InboundInquiry channel — from email, a conversion page, or the Voice Agent — Vertiqa's RFQ Agent parses it into a draft estimate and a lead-stage opportunity in one pass. The inbound document is preserved as a source artifact, attached to the estimate, and routed to a reviewer; nothing is sent outside your org until a human approves it.

Pulls the right line items from your kernel — not a blank slate

The draft Estimate carries the full lifecycle schema — status, opportunity_id, source artifact, previous estimate, and revision count — so every line item is tied to the account, the inbound RFQ, and any prior revisions already in your Kernel. The split- pane workspace then renders the inbound document alongside the editable line items so your reviewer can reconcile what the agent pulled against what was actually asked.

Hands you the draft on the canonical estimate workspace, with the inbound document attached

Reviewer notifications land in-app and by email, and every link deep-routes to /commercial/estimates/{id} — the canonical workspace where the inbound source artifact, the draft line items, and the lifecycle history all sit on one screen. Legacy /rfq/{uuid} URLs 301-redirect to the same place, so your team has exactly one URL to bookmark and exactly one surface to review against.

Adapts to your industry's vocabulary

v1.35 shipped pack-vocabulary maps for HVAC, Systems Integrator, Insurance, and the horizontal default — the same Estimate-status labels speak the right word for your installed pack, without forking the schema or duplicating the agent. Your reviewers see "quote", "estimate", "bid", or whatever your pack maps to; the underlying lifecycle stays one consistent surface across every vertical.

What this agent will not do

  • Never approves an estimate. The approve action is human-gated by the estimate lifecycle guard at both the DB layer and the service layer; only humans with the discount-approval permission can run it.
  • Only creates or revises drafts. The RFQ Agent can write to estimates in draft or sent status; it cannot modify approved estimates — post-approval revisions clone into a new row, never an in-place edit.
  • Won't change pricing logic, discount rules, or e-sign requirements without owner setup. The agent fills line items from the inbound RFQ; pricing models, discount thresholds, and e-sign requirements are configured by the account owner, not learned by the agent.
  • Notifies a reviewer rather than auto-sending. The agent produces a draft plus an in-app and email notification deep-linked to the canonical estimate workspace — nothing leaves your org until a human approves and sends.

Works with the kernels you already use

The RFQ Agent reads and writes through the same Kernel surfaces your team uses — no separate vendor system, no shadow data store.

  • InboundInquiry channel

    v1.31 normalized inbound across email, conversion pages, and Voice Agent sessions; RFQs ride on the same rail as every other inbound your team already reviews.

  • formal RFQ Draft Assist artifact

    v1.31 Draft Assist produces the structured RFQ artifact that the RFQ Agent consumes — human review gates apply at every step; no autonomous external send.

  • Estimate workspace at /commercial/estimates/[id]

    Split-pane layout renders the inbound source artifact alongside editable line items; legacy /rfq/{uuid} URLs 301-redirect into the same workspace.

  • Approval Inbox at /inbox

    RFQ-source rows route directly into the estimate workspace; reviewer in-app + email notifications deep-link there with no intermediate hops.

  • CRM Opportunities

    A lead-stage Opportunity is created alongside the draft Estimate; estimate-state transitions bridge into Opportunity stages through the typed lifecycle service.

  • Pack vocabulary (HVAC / SI / Insurance / horizontal)

    The same surface speaks the right word for your installed pack — estimate, quote, or whatever your pack maps Estimate-status labels to (VOCAB-01..05).

Frequently asked

Where is my data stored?
Inside the same Vertiqa Kernel that powers every other agent and surface in your org. Estimates, opportunities, and the inbound source artifacts the RFQ Agent reads from live in your organization's Kernel — not in a separate vendor system. Tenant isolation, org scoping, and permission gates are enforced at the endpoint level for every estimate and RFQ route.
What gets stored when an RFQ comes in?
One InboundInquiry row on the channel timeline, the inbound RFQ as a source artifact, a draft Estimate (status='draft') with line items pulled from the artifact, a lead-stage Opportunity created alongside the Estimate, and a provenance event linking the Estimate back to its source artifact (the v1.31 formal_rfq Draft Assist artifact). The reviewer is then notified in-app and by email with a deep-link to the canonical estimate workspace.
What happens if I reject the draft estimate?
Reject is a first-class outcome on the canonical /commercial/estimates/{id} workspace. The estimate stays in draft status — agents can only create or revise drafts, never approve — so you can edit the line items, regenerate from the same inbound source artifact, or delete the draft entirely. The only thing the agent did automatically was notify a reviewer; nothing left your org, no Opportunity stage transitioned, and no pricing was committed.
Can I edit the estimate before it's approved?
Yes. The split-pane Estimate workspace at /commercial/estimates/{id} renders the inbound source artifact alongside editable line items, so you can correct what the agent pulled before anything is approved. Approval is a separate, human-gated atomic action with a discount-gate, a status-event audit, and an Opportunity-stage transition — agents are blocked from running it. Once approved, the estimate becomes immutable; any revision clones into a new row rather than editing in place.
Which verticals is this built for — and what's it called in my industry?
v1.35 shipped pack-vocabulary maps for HVAC, Systems Integrator, Insurance, and the horizontal default — the same surface speaks 'estimate' or 'quote' or whatever your installed pack maps it to, without forking the schema. It's built first for verticals where every inbound RFQ matters: exterior services (roofing, paving, landscaping bids) and HVAC (commercial bid response) — see /exterior-services and /hvac for vertical context. A standalone Systems Integrator marketing page is not yet shipped, but the SI pack vocabulary is already live in product.

Built for businesses where every inbound RFQ matters

The RFQ Agent ships with pack vocabulary, schema, and reviewer flows tuned for verticals that win or lose on bid response.

Built for exterior services and commercial bid responseBuilt for HVAC commercial bid response

Turn inbound RFQs into reviewed estimates in minutes.

Book a demo to see an inbound RFQ become a reviewed draft estimate — source artifact, line items, lifecycle audit, and reviewer deep-link, all on a real org.

Book a demo