Skip to content

The product

One system for the whole account decision.

RevQ connects account research, buying-committee coverage, scoring, multichannel outreach, reply intelligence, meetings, and proof. The handoffs disappear because the objects never split.

A single account dossier surrounded by research, committee, message, reply, meeting, and proof artifacts.
One account object holds the system together. Research, committee, conversation, meeting, and proof are operating states, not disconnected tools.
  1. 01

    Define

    ICP, signals, products, committee

  2. 02

    Research

    Accounts, facts, people, sources

  3. 03

    Judge

    Fit, timing, coverage, reachability

  4. 04

    Coordinate

    Seat-specific multichannel cadence

  5. 05

    Converse

    Intent, memory, safety, next move

  6. 06

    Convert

    Account opportunity and meeting

The account is the unit of work. People are seated in its buying committee, conversations move its opportunity, and every decision keeps the evidence that produced it.

01 · The account object

Everything the engine knows stays attached to the account.

An account is not a company row with contacts underneath. It is a living operating file for the decision: what is true, what just happened, who matters, what has been said, and what should happen next.

01Company file
Canonical identity, resolved firmographics, sourced facts, and a durable account timeline.
02Signal ledger
One verdict for every buying signal you declared, including honest absences and source URLs.
03Score and tier
Profile fit + live timing + named adjustments, then an actionability check for reachable coverage.
04Buying committee
Required and conditional seats, matched people, confidence, evidence, lifecycle, and reachability.
05Opportunity
One account-level deal that advances from the combined behavior of the people around it.
06Conversation state
Thread summary, shared facts, asks, objections, preferences, outcomes, and narrative memory per person.

Account file · researched

Aster Vale is worth the week because fit, timing, and coverage agree.

The score is assembled from named rules and on-file evidence. Missing signals score zero, never a penalty.

astervale.io

Aster Vale Systems

B2B infrastructure · 84 employees · India

86

Tier 1 · actionable

Engineering hiring
Careers page · 7 open roles
+18Present
Fresh funding
Series A announcement · 34 days
+18Present
Platform migration
Not found in sources read
0Absent
Illustrative account data. The workflow, states, evidence fields, and execution rules shown here map to the shipping product.

02 · Research and judgment

An agent researches. A separate judge prices the evidence.

The researcher can resolve domains, search the web, read company and person sources, reconcile canonical records, and write facts, signals, contacts, and committee seats. The scorer then buys nothing: it judges only that file against your ICP and weighted rules.

01

You start the spend

Paid enrichment begins from one explicit Research & score action, with provider cost made visible.

02

Evidence survives the run

Present signals need a specific fact and source URL. Declared signals that were not found remain visible as absent.

03

Re-scoring does not re-buy research

Changing the ICP can re-judge the account from what is already on file without calling providers again.

Agentic research run

The researcher can search, inspect, reconcile, and write back to the account file.

The final score reads only what is already on file. It never buys another data point while judging.

  1. Resolve

    Confirmed astervale.io and canonical company record

    Done
  2. Read

    Website, careers page, company profile, public news

    Done
  3. Record

    14 facts and 2 live buying signals with source URLs

    Done
  4. Map

    3 required roles, 1 conditional role

    Done
  5. Research

    Every seated person: role, history, reachability

    Done
Illustrative account data. The workflow, states, evidence fields, and execution rules shown here map to the shipping product.

03 · Committee coverage

Seat the decision before you sequence the people.

Each campaign defines the roles its sale needs. RevQ creates those seats per account, fills them only when title and evidence match, preserves human verification, and treats required reachable seats as the definition of readiness.

Buying committee · 3 of 3 required seats covered

The campaign works the decision, not a list of job titles.

Each seat records its role, requirement, candidate, confidence, evidence, and reachability.

  1. Champion

    Required

    Mira Sen

    VP Engineering

    Filled

  2. Economic buyer

    Required

    Arun Mehta

    COO

    Filled

  3. Technical evaluator

    Required

    Nadia Roy

    Director, Platform

    Filled

  4. Security

    Conditional

    No person seated

    Needed for enterprise cut

    Not yet reachable

    Open

Enrollment gate passed

Only filled committee seats enter the sequence.

Illustrative account data. The workflow, states, evidence fields, and execution rules shown here map to the shipping product.

04 · Coordinated execution

Cadence is account-level. Drafting is person-level.

The opportunity qualifies once at the account. Execution fans out only to filled committee seats. At each touch, RevQ writes from the person, their role, company facts, why-now signals, relevant proof, and the conversation already established with them.

Account cadence · committee only

Three stakeholders. One account narrative. No contact-list blast.

Every touch is drafted at send time from the person, their seat, the account evidence, and the conversation so far.

  1. Day 0ChampionEmailHiring signal + release reliability
  2. Day 2Technical evaluatorLinkedInPlatform workflow + stack
  3. Day 4Economic buyerEmailScaling cost + delivered-work proof
  4. Day 7ChampionWhatsAppContinue the same conversation

Draft context: role evidence + company facts + why now + proof + thread memory

No invented claims
Illustrative account data. The workflow, states, evidence fields, and execution rules shown here map to the shipping product.

05 · Conversation intelligence

A reply is an account event, not an inbox ticket.

One structured decision reads the whole thread, classifies every intent, extracts the durable facts, and plans the next state change. Deterministic safety rules remain the backstop.

Out of office
Pause the same cadence step and resume after the stated return time.
Referral
Create or match the referred person and add them to the account file.
Left company
Suppress the old address, search for a successor, and keep the account alive.
Already a customer
Stop outreach and route the account to its owner.
Channel switch
Honor the requested channel and stop the old channel cadence.
Reschedule
Move the meeting in context without creating a duplicate.
Unsubscribe or bounce
Suppress immediately; hard bounces also park the opportunity for repair.
Legal or suspicious
Stop automation and route safely instead of improvising.

Conversation memory · Mira Sen

A reply can change the account, the cadence, the contact, and the calendar in one turn.

The engine reads the full thread and keeps durable memory per contact and campaign.

“This is relevant. Security will need to review it. Can you send an example for regulated teams and hold Thursday at 11:30?”

Intent

Interested + question

Committee

Security seat required

Meeting

Proposed time captured

Illustrative account data. The workflow, states, evidence fields, and execution rules shown here map to the shipping product.

06 · Organizational proof

Your delivery history becomes sales memory.

Store delivered projects, facts, signals, and assets once. RevQ can turn that evidence into a case-study deck for a specific audience, preserve numeric source tags, accept plain-language revision, visually inspect the rendered slides, and export PDF.

Delivered work → reusable proof

The next message can sell with what the company has already delivered.

Project facts, source links, assets, audiences, and committee angles become a structured case-study deck.

01

Project record

Scope, outcome, client, links

02

Enhanced facts

Source-backed claims only

03

Audience cut

Lead with what this seat cares about

04

Case-study deck

Draft, revise, verify, approve, PDF

“Reduced launch-documentation turnaround from five days to one.”

Project fact · source retained · numeric claim tagged in the deck

Ready for VP Engineering
Illustrative account data. The workflow, states, evidence fields, and execution rules shown here map to the shipping product.

System specification

The power is in the operating rules.

Research loop
Up to 22 tools for web, company, person, fact, signal, contact, and committee work.
Scoring
Every declared signal gets a verdict; totals are composed deterministically in code.
Channels
Email, WhatsApp, and LinkedIn, limited to what the campaign declares and the organization connects.
Enrollment
Account-level qualification, committee-only contacts, every sequence channel reachable.
Memory
Persistent conversation state per contact × campaign, shared across replies and re-engagement.
Proof
Delivered projects become sourced, audience-specific case-study decks with review and PDF.

Build the first account motion

Define the committee once. Let the system operate every account.

Early access includes hands-on campaign configuration. We will translate your ICP, buying signals, products, committee roles, channels, and proof into the first working system.