GetSales for Sales teams

Hit your pipeline number. Your reps just sell.

GetSales builds the lists, sends each rep's LinkedIn and email steps from their own sender profile, labels the replies and drafts the answer for the rep's yes.

Sample run of GetSales. Creator hears one sentence by voice and plans the run: AI Search finds heads of sales at UK SaaS companies, the table fills with a work email, an AI score and a first line for each person, the workflow is built and starts on a spoken yes, the AI SDR is set up and drafts a reply that waits for approval, and Signals shows each new event with what it led to or what to switch on.
GetSales
CreatorBuild it by voice, in your own words

What are we working on?

Say who you sell to, or ask for anything in the app: a list, the work emails, a workflow, the replies waiting for you.

By voiceHeads of sales at B2B SaaS companies in the UK, 50 to 200 people. Find their work emails, score the fit, write a first line, then LinkedIn first and email after.

On it. Here is the plan.

PlanDone7 of 7

Heads of sales, UK SaaSRun by voice

All set. Signals land as they come.

The workflow is ready. Start it for the 142 people with a strong or good fit?

By voiceYes, start it.

Say who you sell to, or ask anything

Heads of sales, UK SaaS21251 to 200 people
Person, work emailCompanyWork emailAI scoreFirst line
Maya L.Head of Salesmaya@helio.exampleNothing found, no charge Helio AnalyticsSaaS, 140 people maya@helio.exampleNothing found, no charge Strong fit Saw the two SDR roles. Most teams hire before the pipeline is ready for them.Held: weak fit
Tomás F.VP Salestomas@ferro.exampleNothing found, no charge Ferro CloudSaaS, 85 people tomas@ferro.exampleNothing found, no charge Good fit Your post on reply rates against volume is the case we make every week.Held: weak fit
Anika B.Head of Salesanika@quanta.exampleNothing found, no charge Quanta DeskSaaS, 60 people anika@quanta.exampleNothing found, no charge Good fit Congrats on the round. The first outbound hire is usually where it gets hard.Held: weak fit
Sam K.Head of Revenuesam@tallyhouse.exampleNothing found, no charge TallyhouseSaaS, 120 people sam@tallyhouse.exampleNothing found, no charge Good fit Saw the new Leeds office. New region, same two people on outbound?Held: weak fit
Lena R.Sales Directorlena@tinbarrow.exampleNothing found, no charge TinbarrowSaaS, 175 people lena@tinbarrow.exampleNothing found, no charge Strong fit Your team page lists six AEs and one SDR. That ratio shows up in pipeline.Held: weak fit
Daniel O.CRONothing found, no charge Okra SystemsSaaS, 190 people Nothing found, no charge Weak fit Held: weak fit
Jonas P.Head of Salesjonas@meridian.exampleNothing found, no charge Meridian LabsSaaS, 55 people jonas@meridian.exampleNothing found, no charge Weak fit Held: weak fit
Eva W.VP Saleseva@kinetic.exampleNothing found, no charge Kinetic FormsSaaS, 70 people eva@kinetic.exampleNothing found, no charge Strong fit Kinetic just moved upmarket. The first enterprise quarter is mostly list work.Held: weak fit
1 to 8 of 2121 credit for a work email found and verified. A miss costs nothing.
Heads of sales, UK SaaSActiveSender profile: Jordan O.
142 peoplestrong or good fit, from the table
Connection requestWith a note96 sent
Wait until acceptedUp to 5 days41 waiting
Accepted
LinkedIn messageThe first line, by the sender38 sent
Follow-up messageNo reply in 3 days14 sent
Not accepted in 5 days
EmailFrom the sender's mailbox27 sent
Follow-up emailNo reply in 3 days12 sent

End

A reply pauses the person's steps and lands in the AI SDR inbox.
AI SDRCo-pilotAt the level each scenario sets

Replies 3

Replies from every sender profile land here

  • Maya L.LinkedInSounds useful. Can you send a short overview?Info request
  • Tomás F.EmailWhat would this cost for a team of twelve?Info request
  • Lena R.LinkedInAsk me again after the quarter.Not now

Co-pilotBook a 15 minute call

AI SDRPicked by Creator

Mode
Co-pilot, at the level each scenario sets
Tone of voice
Plain and short, no pitch
Goal
Book a 15 minute call
Replies as
Jordan O., on LinkedIn and email
Maya L.Head of Sales, Helio AnalyticsInfo request

LinkedInInvitation accepted, Monday 10:14

Thanks for connecting, Maya. Saw the two SDR roles. Most teams hire before the pipeline is ready for them. Worth comparing notes?

Jordan O.

Sounds useful. Can you send a short overview?

AI SDR draftWaits for your approval

Happy to, Maya. Here is a two-page overview of how teams your size run it with GetSales. Would 15 minutes on Thursday help?

Approve and sendEditReply as Jordan O.

Every reply labelled, with how sure it is and why.
Signals Needs me 010AllNot covered 01

Today

  1. Daniel O.·CRO, Okra Systems·New Contact·Heads of sales, UK SaaS

    1. Changed job: CRO at Okra Systems, now VP Sales at Pellbrook

      Nothing in Heads of sales, UK SaaS acts on job changes. Set up On a job change

  2. Sam K.·Head of Revenue, Tallyhouse·Connection Request Sent·Heads of sales, UK SaaS

    Heads of sales, UK SaaS·Runningstep 2

    1. Posted on LinkedIn

      Three things we changed in how our SDRs plan the week, and the one we rolled back after a month. Monday starts with the pipeline now, not the inbox. ...more

      36Jordan and 36 others9 comments · 2 reposts

      LikeLikedCommentOpen on LinkedIn

      Add a comment as Jordan...Draft

      Jordan O.posted by Engage with posts

      Curious which one you rolled back. In our experience the shared call list goes first.

      Sam K.

      It was the shared call list. Nobody owned an account after week two.

      Reply as Jordan...Draft

      A reply as Jordan

      That matches what we see. Named accounts per rep usually fix it. Did you go back to territories?

      Post itDraftCancel

      Jordan O.posted by hand

      That matches what we see. Named accounts per rep usually fix it. Did you go back to territories?

  3. Eva W.·VP Sales, Kinetic Forms·Initial Outreach·Heads of sales, UK SaaS

    Heads of sales, UK SaaS·Runningstep 4Heads of sales, UK SaaS·Pausedstep 4Pricing follow-up·Runningstep 1

    1. Opened the Pricing page

      /pricing after the home page·came by our link·her 3rd visit this week

      On a website visit · paused and asking you

      Eva is in Heads of sales, UK SaaS, step 4 of 7 (the message), on hold since 11:05.

      Remove from the workflowKeep goingMove to a workflow

      Pick a workflowPricing follow-upMove to a workflowBack

      On a website visit · done · moved to Pricing follow-up

Only people you already talk to are named, and the AI SDR is told never to mention a visit.

01

No rep spends
the week on lists

Say who you sell to. GetSales finds the people, looks for a work email for each, checked by the verifier you pick, and writes a first line for each one who fits.

  • Describe your buyers in one sentence
  • Emails found finder by finder, a miss is free
  • A first line for every good fit

02

Only new people
in every list

A person already in any table of your workspace is not added again, so each new list brings people your team does not already have. Your stoplist covers every table and every workflow.

  • A duplicate names the table it is in
  • Stoplisted people are never contacted
  • A reason on every row left out
AI Search

03

Outreach goes out
in each rep's name

One workflow sends its LinkedIn and email steps from each rep's own sender profile. Each person gets one rep on entry and keeps them, and by default a reply pauses their follow-ups.

  • Fair balance spreads people evenly
  • Prior engagement keeps a person with the rep they know
  • Paced within each account's limits

04

Each rep sees what
needs them first

Replies from every rep's LinkedIn and mailboxes land in one inbox, labelled by the AI SDR, and a price, call or legal question waits there for a person.

  • 15 labels, plus scenarios of your own
  • Needs you, Waiting on lead and Stalled come ready
  • Each rep saves a filter on their sender profile

05

Warm replies worked
toward a meeting

A reply with interest goes to your Playbook, which leads it toward your goal, such as a call. Each scenario sets whether the AI SDR's answer goes out on its own or waits for the rep's OK.

  • Engage, Discover, Bridge, Offer, Book
  • A buying signal goes straight to the offer
  • Not now gets a follow-up when they said
AI SDR

06

Reach a buyer while
they are still looking

On a site switched to People, the visit play pauses the steps of someone you wrote to and asks what next. A key page you mark, such as pricing, gives their open thread a call task.

  • Keep going, move them or take them out
  • Whoever works the thread is told
  • The AI SDR is told never to mention a visit

At Companies, a visit names the company only. Visitors from the EU, the EEA or the UK have to consent, and you confirm it in the site's settings.

07

See which step
fills your pipeline

Each sending step shows what it sent and what came back, and the Dashboard follows your people from added to won. Edit a draft beside the live version and publish when it is ready.

  • Each rep's replies and reply rate on the Dashboard
  • A step that falls behind, marked
  • People already in stay on their version
Workflows

All set

Your reps start the day on replies.

Sign up free: Playtables stay free with your own API keys, and LinkedIn and email come with a 7-day trial. Say who you sell to, and Creator builds the run.

Sample of a plan from Creator in GetSales, every step done: search, table, work emails and AI score, first lines, workflow, AI SDR and Signals.
GetSales
PlanDone7 of 7

Heads of sales, UK SaaSRun by voice

  1. SearchAI Searchsearching236 found
  2. Tablefrom the searchadding rows212 rows
  3. Work emails and AI scoreper rowworking142 fit
  4. First linesfor every fitwriting142 written
  5. WorkflowLinkedIn, then emailbuildingwaits for your OKstarted
  6. AI SDRfor the repliessetting upCo-pilot
  7. Signalson the tableswitching onon

All set. Signals land as they come.

The reason you get more sales is AI.