Choose a planPlans
IMPLEMENTATION / Exporters & sales teams

Know who needs a follow-up. See who is ready to buy.

Use authorized email and WhatsApp conversations to suggest lead stages, identify payment intent and surface the next follow-up with supporting context.

Explore the Meridian case ↓
✳ FDE IN PRACTICE / Meridian

From a new lead
to the next follow-up.

The Meridian sales workspace connects customer leads in Notion with Gmail activity, bringing ownership, business stage, conversations and next follow-ups into one view. It is a practical application of lead stage detection in everyday sales work.

THE PROBLEM

Leads live in spreadsheets while conversations happen in email. Managers have to ask each salesperson who has been contacted and what happens next.

THE FDE WORKFLOW

Connect lead imports, assignment, email activity and stage assessment around a shared customer record.

CONNECTED TOOLS

Notion · Gmail · Team sales workspace

meridian Sales workspace● Notion connected   ● Gmail 2/2

Workspace overview

Interface summary based on supplied screenshots
Customer leads12Registered customer emails
Outbound messages1Actual email count
Customer replies0Excludes identified auto-replies and bounces
Awaiting employee reply0Customers with unanswered threads
N
Notion lead source

Website inquiries → Scheduled import → Owner assignment

Scheduled import
New 12Contacted 0In discussion 0Quoted 0Won 0Closed 0
OwnerBusiness stageSent / repliesEmail progressLast contactNext follow-up
A summary of the overview and customer lead screens. Counts reflect the supplied screenshot snapshot and explain the interface and counting rules.
THE WORKFLOW

Keep understanding the conversation after a lead arrives.

  1. 01 / CONNECT

    Import new Notion leads

    Connect an existing lead table. The shown configuration imports new leads every five minutes; existing owners, stages and tags remain managed in the workspace.

  2. 02 / ASSIGN

    Give each lead an owner

    Assign new leads to enabled staff who have waited longest for a new assignment. Preserve existing owners. Staff sign in with their company Google account to see their own leads.

  3. 03 / ASSESS

    Read email activity in context

    Related sent and received emails are counted after a customer email is registered. Email events and conversation content inform stage assessment alongside sent, replied and awaiting-reply states.

  4. 04 / FOLLOW UP

    Turn an assessment into action

    Confirm the business stage and arrange the next follow-up. Managers can review contact progress, overdue follow-ups and deal status in the team view.

EXAMPLE STAGE LOGIC

A reason behind
each stage.

These examples explain the business logic. Conditions and the scope of automatic updates are configured around the team's process during delivery.

Stages, signals and next actions
StageReference signalNext action
NewA new customer enters the workspaceAssign an owner and prepare outreach
ContactedAn actual outbound email is recordedWait for a reply and plan follow-up
In discussionA meaningful reply starts a requirements conversationClarify needs and open questions
QuotedA formal quote has been sent in the conversationConfirm feedback and next steps
Won / closedAn explicit outcome is confirmed by the ownerHand off execution or record a closure reason

Track business status and email activity separately.

Sending an email changes email statistics; progressing a business stage depends on context and team rules. Distinguish auto-replies and bounces from meaningful customer responses, and verify payment intent. Salespeople can confirm and correct the assessment.

What does the team gain?

  • A complete customer record: source, owner, stage and email activity together.
  • A clear follow-up queue: who needs a reply and when to contact them again.
  • A team progress view: assignment, contact, replies, overdue work and outcomes tracked separately.
Discuss your lead follow-up process ↗

Lead scoring & stage detection

Use authorized email and WhatsApp conversations to suggest lead stages, identify payment intent and surface the next follow-up with supporting context.

A connected business process

Conversation → Summarize → Suggest stage → Confirm → Update CRM

What we build

  • Conversation summaries
  • Sales-stage classification
  • Intent signals with evidence
  • Follow-up reminders
  • Human corrections and audit history

How we validate it

Evaluate stage accuracy and missed signals with labeled samples. Low-confidence suggestions go to review; payment intent never substitutes for payment confirmation.

Connect the next part of the workflow

See the inquiry-to-fulfillment workflow ↗
START WITH ONE WORKFLOW

Let’s find your
first workflow.

We map the busywork, connect the tools you use,
and build AI systems around your team.

Discuss your workflow ↗