Ask
94
@flux_and_solder ·

first discovery call tomorrow — do you demo or just ask questions for 30 minutes Discovery Calls

Never done one of these. Someone replied to my email and booked 30 minutes tomorrow morning. I'm an engineer, I have never sold anything to anyone.

My instinct is to show them the product because that's the thing I have. Everything I read says don't demo, ask questions. But if I just ask questions for half an hour it feels like I'm interviewing them for a job they didn't apply for, and they booked expecting to see a tool.

What actually happens in these? Is there a normal shape?

10 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @proof_pilar · 5mo ago · 3 replies

    Rough shape for 30 minutes:

    • 2 min: why you got in touch, plus the honest sentence about where you are ("four customers, built it because X")
    • 15 min: their world. How do you do this today, what happens when it goes wrong, when did it last go wrong, what did that cost
    • 8 min: show the two screens that touch what they just described. Not a tour. Two screens.
    • 5 min: what happens next, with a date attached

    The reason people say don't demo is that a demo lets them be polite. They say "neat" about everything, you leave feeling great and you learned nothing. Questions first means the demo lands on something they've already told you hurts.

    And it stops feeling like an interview the moment you ask about the last time something happened rather than about how they do things in general. "When did an invoice last go out wrong?" gets you a story. "How do you handle invoicing errors?" gets you a policy statement that isn't true.

    112
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @flux_and_solder · 5mo ago

      Ran it roughly like this. The 'when did it last happen' question got me a nine-minute story about a duplicate payment in April. The whole call turned on it.

      38
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @runway_math · 5mo ago

      That's most of the job. Specific past events, never hypotheticals. People are terrible at predicting what they'd do and excellent at telling you what happened.

      26
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @iris_tanaka · 5mo ago

    Record it, with permission. You will not remember it accurately. I thought I was a good listener until I played back my first three calls and heard myself interrupting people to defend features nobody had attacked.

    Also: silence. When they finish an answer, count three before you speak. The best information in every call I've done arrived in the second half of an answer, after the pause.

    63
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @probe_to_ground · 5mo ago

    You're an engineer, so: you're not selling, you're reducing uncertainty. You have a hypothesis about what's painful and roughly what it costs them. The call either raises or lowers your confidence in it. Going in with three specific things you want to find out makes the whole thing feel much less like improv.

    Write the three down. Look at the list at minute 20. If you haven't got them, ask directly — nobody minds a direct question at minute 20.

    40
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @quietmargin · 5mo ago · 2 replies

    just demo it, people are busy and they booked to see the thing. 30 minutes of questions is annoying

    16
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @iris_tanaka · 5mo ago

      Middle path is telling them the shape up front: 'I'd like to ask about how you handle X for ten minutes so I only show you the relevant part — is that ok?' Nobody has ever said no to that, and it stops them feeling ambushed.

      14
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @mature_student_j · 5mo ago

    Don't apologise for the state of the product and don't narrate the roadmap. New founders spend a third of the call pre-defending things nobody has complained about. If a screen is ugly they'll say so, and then you say "yeah, that's next month" and move on.

    22
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @heirloom_hank · 5mo ago · 2 replies

    End with a specific next step or the call was worth nothing. Not "I'll send some information over". Something like: "I'll set up an account with your two branches already in it and send it Thursday — can you run one real job through it by the end of next week?" Then you find out whether they meant any of it.

    17
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @flux_and_solder · 5mo ago

      Did this. They said yes, then didn't, then did it eight days later after one nudge. Which I gather is also normal.

      12
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report