EchoStack

Evaluate before CRM. Your stack fires the outcome.

Define your rubric once. EchoStack returns status, fields, and next_action — your HubSpot, Slack, or n8n workflow routes the lead. EchoStack never writes to your CRM.

Start freeTry the playground

Signal

Inbound formWebhookTranscript

Evaluate

versioned rubric

status · fields · next_action

  • QUALIFIEDYour n8n → HubSpot owner
  • PARTIALAsk for missing_fields
  • FAILEDNurture or close loop

The gap

Manual follow-up vs. Evaluate-before-CRM.

Most teams lose the lead between signal and action. Add one Evaluate step — your automation routes while intent is still high.

The manual path

~2 days lost
  1. 1

    High-intent signal arrives

    0m

    Strong buy signal lands in your stack.

  2. 2

    Someone reviews it hours later

    +2h

    "Maybe tomorrow."

  3. 3

    Someone logs it in HubSpot

    +1d

    "If they remember."

  4. Follow-up goes out

    +2d

    "Lead is already cold."

vs

With EchoStack

< 5s

Qualified in seconds. Your workflow gets status, missing_fields, and next_action — then fires HubSpot or n8n while the lead is still warm.

  • Evaluated in seconds, not hours
  • You update CRM and calendar from the decision
  • Route to owner, nurture, or Slack while intent is still high

Decision returned

QUALIFIED · missing_fields[] · next_action

How it works

Set your rubric once. Branch on the decision.

BANT, MEDDIC, or custom criteria — same decision contract on every channel. Three steps from rubric to production.

Step 01

Define what good looks like

Tell EchoStack what a qualified lead, urgent ticket, or ready-to-buy moment looks like — BANT, MEDDIC, or custom detectors in plain language.

  • When a form answer set is QUALIFIED vs PARTIAL
  • When a ticket should escalate before a human debates priority
  • When a transcript is ready for the rep queue

Step 02

Wire Evaluate into your stack

Use an org API key (esk_…) and evaluation_id — or ad-hoc Criteria. Connect HubSpot, n8n, Zapier, or Make so your workflows act on the result.

  • n8n community node + Switch on status
  • Webhook normalize → POST /v1/evaluate
  • Same contract from playground to production

Step 03

Turn it on — your stack routes

EchoStack returns the decision as signals arrive. Your automation books, updates CRM, nurtures, or alerts — while interest is still high.

  • QUALIFIED → owner / stage in your CRM
  • PARTIAL → ask for missing_fields
  • FAILED → nurture or close the loop

Live sandbox

See the decision before you wire it.

Paste a form, transcript, email, or ticket. Run a live evaluation and inspect status, extracted fields, and next_action — the same JSON your production workflow branches on.

Try a scenario

Sales callWeb formSupport ticketTrial usage

Run a live evaluation — no account required

Try sales call, web form, support ticket, or trial usage scenarios. Same Evaluate engine as production.

Open playground

Integrations

Decide once. Your tools act.

Wire Evaluate into the stack you already run. EchoStack returns the qualification decision; n8n, Zapier, Make, or your backend fire CRM updates, Slack alerts, and nurture.

  • HubSpot
  • n8n
  • Make
  • Zapier
  • Calendly
  • Slack
  • LiveKit

Not Zapier with an LLM.

Generic workflow tools chain steps. EchoStack owns the qualification decision — versioned rubrics, reusable Evaluations, and a stable status contract your automation branches on.

  • Versioned rubric criteria — same rules every time
  • Reusable Evaluations, not one-off GPT prompts
  • Decision in seconds while the signal is still hot
Integration guidesAPI reference

Need something else? HTTP webhooks and REST work with any stack — caller normalizes the payload, then Evaluate.

Who it's for

Built for the evaluate step. Start where you automate.

Drop Evaluate into n8n, Make, or Zapier before CRM. Developers and conversation teams use the same decision contract.

n8n · Make · Zapier

Automation builder

Drop Evaluate before CRM, Slack, or nurture — branch on status, not guesswork.

  • Official n8n node + importable example workflow
  • Eval-first: trigger → evaluate → Switch on QUALIFIED / PARTIAL / FAILED
  • Same BANT/MEDDIC rules as API and HubSpot forms
n8n setup guideStart free

Eval API developer

REST · webhooks · your agents

One HTTP call returns status, extracted fields, and next_action — versioned rubrics, no prompt drift per integration.

Eval API quickstartStart free

Voice & conversation teams

Calls · widgets · agent transcripts

Score live or post-call conversation with the same Evaluate contract — Full Platform always-on channels are design-partner only.

Post-call transcript guideDesign partner

Pricing

Pay for decisions. Not for seats.

Evaluation API includes 500 free evaluations every month, then $0.02 per evaluation on Scale. Action Resolution and Full Platform are invite-only until GA.

Evaluation API

Qualification decision API · GA

Free500 evaluations / month · then $0.02 / eval on Scale

500 free evaluations every month.

Create a reusable Evaluation from a template or your own detectors. Send any signal with esk_ + evaluation_id — get status, extracted_fields, missing_fields, and next_action. Your workflow fires what happens next.

  • Inbound lead, support triage, intent, or custom rubrics
  • Same JSON contract: status, fields, missing_fields, next_action
  • n8n node and webhook guides — you branch on status
Start free

Same rubric at every tier — you choose who fires CRM, Slack, or nurture.

Action Resolution API

Design partners · not GA

Outcomes after Evaluate — not GA yet.

Apply as a design partner

Full Platform

Design partners · not GA

Always-on voice and chat — design partners only.

Apply as a design partner

An Evaluation is one versioned rubric (e.g. inbound BANT). Scale meters usage. Action Resolution fees apply only when that product ships and executes an outcome for you.

Design partner program

Ship one workflow in production. Help shape what ships next.

We're onboarding RevOps and automation teams with one inbound form or webhook stuck in manual review — or a GPT step that drifts. White-glove setup; four to six weeks of honest feedback.

We only publish metrics and quotes with written customer approval. These are production workflows design partners run today.

Workflows partners ship today

  • Inbound leads

    Form or webhook → BANT → your stack on status

    QUALIFIED → n8n → HubSpot owner

  • Post-call transcripts

    Transcript → fields + next_action → rep queue

    PARTIAL → ask for missing_fields

  • Support triage

    Ticket text → severity → escalate or queue

    FAILED → nurture or close loop

Who

  • RevOps, sales ops, or automation owner at a ~20–200 person B2B team
  • One named workflow: inbound form, webhook, transcript, or ticket
  • Technical owner who can wire Evaluate in n8n, HubSpot, or HTTP this month

You get

  • White-glove lead_qualification Evaluation + org API key (esk_…)
  • Weekly 30-minute check-in with the founder
  • Early input on Action Resolution — not sold as GA today
  • Say on packaging before public launch

We need

  • Evaluation API on real traffic for at least 4 weeks
  • Honest weekly feedback on what broke
  • Optional anonymized case study when you're ready — no invented metrics
Apply as a design partnerTry the playground first

Stop routing leads by hand.

Define your rubric once. Call Evaluate. Let your stack fire CRM, Slack, or nurture while intent is still high.

Start freeApply as a design partner