← All use cases
Sales · Call preparation

Know your prospect before the call starts

Before every meeting, a short brief is already waiting: who they are, what changed, and what to ask.

Why it matters

Before a meeting that matters, someone spends half an hour digging: the CRM, the old email threads, last year's notes, whatever the company has published since. It gets done at eight in the morning for a nine o'clock call, and half of what turns up was already written down somewhere.

Plugs into

Your CRMYour calendarEmail historyLinkedInMeeting notes

These are examples. Every use case is built around the tools you already run, whatever they are, and you keep using them exactly as before.

Then it runs on its own

  1. 1

    Reads tomorrow's calendar and works out who you are meeting

  2. 2

    Pulls the account history from your CRM and past email threads

  3. 3

    Checks what the company and the person published recently

  4. 4

    Reads your notes from previous meetings with them

Delivered where you already work

The evening before each meeting in your calendar, in whichever channel your team already uses. We set the timing around how you work, not the other way round.

EmailWhatsAppSlackTeams

What you get back

  • One page per meeting, ready before the day starts
  • What changed since you last spoke to them
  • Five questions worth asking on this call

What it actually looks like

The real output, using sample data. Every line traces back to the source it came from.

Prospect brief · Meridian ShippingOpen full size →
25 min
saved per meeting
Once it's running

Already on your screen

We build it with your team

Every workshop is built around the use cases you pick. This one is usually covered in the Accelerator, on your own tools and your own data.

  • We run it on prospects your team is really about to call
  • Your team learns how to check what comes back before trusting it
  • We adapt the brief to what your salespeople actually need to know

Want it extended, maintained and connected to more of your systems afterwards? Let's discuss →

Want this running in your team?

30 minutes. Tell us what your team spends its week on and we'll tell you which of these would save the most time.