<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kulissa</title>
    <description>The latest articles on DEV Community by Kulissa (@kulissa).</description>
    <link>https://dev.to/kulissa</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211591%2Fecd6a73b-8d94-4f16-a313-146bd3a90336.png</url>
      <title>DEV Community: Kulissa</title>
      <link>https://dev.to/kulissa</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kulissa"/>
    <language>en</language>
    <item>
      <title>How to Handle "Not Interested" on a Cold Call: Cold Calling Tips and Sales Scripts for SDRs and Founders</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Mon, 16 Nov 2026 09:13:07 +0000</pubDate>
      <link>https://dev.to/kulissa/how-to-handle-not-interested-on-a-cold-call-cold-calling-tips-and-sales-scripts-for-sdrs-and-1ch4</link>
      <guid>https://dev.to/kulissa/how-to-handle-not-interested-on-a-cold-call-cold-calling-tips-and-sales-scripts-for-sdrs-and-1ch4</guid>
      <description>&lt;p&gt;"I'm not interested" is the most common reply on a cold call, and the way you handle it in the next five seconds decides whether the call ends or turns into a real conversation. These cold calling tips and sales scripts are for SDRs and BDRs on the phones every day, founders doing founder-led sales who hate cold outreach, and engineers or solutions engineers who just got handed a list and a dialer. This is objection handling for the moment before there's even a conversation to handle.&lt;/p&gt;

&lt;p&gt;The key thing to understand: "not interested" on a cold call is almost never a considered decision. The prospect doesn't know enough about you to be uninterested. It's a reflex, the same way "just looking" is a reflex in a shop. Your job isn't to argue with it. Your job is to make it safe for them to give you twenty more seconds.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why "not interested" happens so fast
&lt;/h2&gt;

&lt;p&gt;Picture the prospect's side. They're in the middle of something. An unknown number interrupts them. Within two seconds they recognise the rhythm of a sales call. "Not interested" is the fastest exit available.&lt;/p&gt;

&lt;p&gt;That means the objection is usually about one of three things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The interruption&lt;/strong&gt;, not your offer. They're busy right now.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The pattern&lt;/strong&gt;, not you. You sound like every other cold call they've had this week.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A real "no"&lt;/strong&gt;: they genuinely have no problem you can solve.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only the third one is a true rejection. The first two are invitations to do something different.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 1: Pitching harder
&lt;/h2&gt;

&lt;p&gt;The instinctive response is to speed up and squeeze the whole value proposition into one breath:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I totally understand, but we help companies like yours increase efficiency by streamlining..."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The prospect said no to a pitch, so you gave them more pitch. They hang up feeling confirmed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistake 2: Folding instantly
&lt;/h2&gt;

&lt;p&gt;The opposite reflex: "No worries, have a great day." Polite, but you just spent all the effort of getting someone on the phone and walked away without learning anything. Folding on every first "no" also means your call notes stay empty, so you never figure out which openers actually work.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 3-step response: acknowledge, permission, one question
&lt;/h2&gt;

&lt;p&gt;Here's a sales script that respects the prospect and still gives the call a chance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Acknowledge, without fighting it.&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Totally fair, you weren't expecting my call."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Short, calm, a little disarming. You're agreeing with the part that's true: you did interrupt them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Ask for a tiny, specific amount of time.&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Can I take 20 seconds to tell you why I called, and then you can tell me if it's worth another minute? If not, I'll let you go."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You're asking for something small and giving them an exit. People are far more willing to say yes when "no" stays easy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Lead with a problem, then ask one question.&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I work with sales teams where new reps take months to sound confident on calls, because they mostly practise on real prospects. Out of curiosity, how do your new hires practise before they get on the phone?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Notice what's missing: no product name, no feature list, no "we're the leading platform". Just a problem the prospect might recognise and a question about their world. If the problem lands, they start talking. If it doesn't, you've found out quickly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Variations for the most common versions
&lt;/h2&gt;

&lt;p&gt;"Not interested" comes in a few flavours. Each deserves a slightly different reply.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Not interested, we're all set."&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Makes sense. Most teams I talk to have something in place. Just so I know whether to ever call back: what are you using today for [problem]?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This turns the brush-off into discovery. Their answer tells you whether there's a gap.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Not interested, I'm busy."&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Got it, bad timing. Is it the call that's bad timing, or the topic? If it's just now, when's a better 10 minutes this week?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This separates the interruption from the offer, which is exactly the distinction you need.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Not interested, take me off your list."&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Done, I'll remove you. Thanks for telling me directly."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Respect it, mean it, and log it. Not every "no" is a test. Pushing past an explicit opt-out burns your reputation and your company's.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to know when to let go
&lt;/h2&gt;

&lt;p&gt;A good rule for cold calling: one respectful attempt to reframe, then accept the answer. If the prospect repeats "not interested" after your 20-second ask, thank them and end the call. Two more pushes rarely change the outcome, and they make the next call from your company harder.&lt;/p&gt;

&lt;p&gt;Before you hang up, there's one last question worth asking when the tone allows it:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Before I go, is there someone else on the team who thinks about [problem]? Happy to leave you alone either way."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Sometimes you've just called the wrong person.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick call checklist for "not interested"
&lt;/h2&gt;

&lt;p&gt;Keep this next to your dialer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Did I stay calm and slow, instead of speeding up?&lt;/li&gt;
&lt;li&gt;[ ] Did I acknowledge the interruption?&lt;/li&gt;
&lt;li&gt;[ ] Did I ask for a small, specific amount of time with an easy exit?&lt;/li&gt;
&lt;li&gt;[ ] Did I lead with a problem, not a product?&lt;/li&gt;
&lt;li&gt;[ ] Did I ask exactly one question about their world?&lt;/li&gt;
&lt;li&gt;[ ] Did I respect a second "no" or an opt-out?&lt;/li&gt;
&lt;li&gt;[ ] Did I log what they said, so I can improve the opener?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Practise it until it's boring
&lt;/h2&gt;

&lt;p&gt;The hard part of handling "not interested" isn't knowing the words. It's saying them calmly while your heart rate spikes because a stranger just brushed you off. That calm comes from repetition, not from reading a script once.&lt;/p&gt;

&lt;p&gt;Run a sales role play with a colleague: they open every call with "not interested" in a different tone (bored, annoyed, rushed, polite), and you practise the acknowledge-permission-question sequence until it comes out naturally. Ten rounds in a row is enough to notice the difference on your next call block.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;"Not interested" is usually a reflex, not a verdict. Acknowledge the interruption, ask for twenty seconds with an easy way out, lead with a problem and one good question, and respect a real "no" when you hear it. You'll turn more cold calls into conversations without sounding like every other caller.&lt;/p&gt;

&lt;p&gt;If you'd like to rehearse openers like this against virtual customers who brush you off like real prospects, that's what we're building with Maya, our sales coach, at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>career</category>
      <category>startup</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Negotiation Tips for Discount Requests: Sales Scripts and Closing Techniques That Protect Your Price</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Sun, 15 Nov 2026 09:17:14 +0000</pubDate>
      <link>https://dev.to/kulissa/negotiation-tips-for-discount-requests-sales-scripts-and-closing-techniques-that-protect-your-price-jo4</link>
      <guid>https://dev.to/kulissa/negotiation-tips-for-discount-requests-sales-scripts-and-closing-techniques-that-protect-your-price-jo4</guid>
      <description>&lt;p&gt;"Can you do better on price?" usually comes right at the end of a good sales call, and the negotiation tips you use in the next ten seconds decide whether you close the deal at a fair price or give away margin you'll never get back. These sales scripts and closing techniques are for founders doing founder-led sales, engineers and solutions engineers who suddenly own a quote, SDRs moving into closing, and AEs who feel their stomach drop every time a buyer asks for a discount.&lt;/p&gt;

&lt;p&gt;This isn't the same as handling "it's too expensive". That objection says the value isn't clear. A discount request often means the opposite: the buyer wants it, and they're checking whether there's money left on the table. Treat it like a price objection and you'll re-pitch someone who's already sold. Treat it like a negotiation and you keep the deal and the price.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why most people cave on discount requests
&lt;/h2&gt;

&lt;p&gt;The usual pattern looks like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Buyer: "Can you do better on price?"&lt;/li&gt;
&lt;li&gt;Seller, instantly: "I could probably do 10%."&lt;/li&gt;
&lt;li&gt;Buyer: "Great, can you do 15?"&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Three mistakes happened in two seconds:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No question was asked.&lt;/strong&gt; The seller doesn't know why the buyer wants a discount, or whether the price was actually a problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The discount came for free.&lt;/strong&gt; Nothing was traded for it, so the buyer learns that asking works.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The first number became the floor.&lt;/strong&gt; Once you say 10%, that's where the next round starts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most people cave because silence feels risky. The fix is not to become a harder person. It's to have a short sales script you've practised so many times that you don't need courage in the moment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Pause, then ask what's behind the ask
&lt;/h2&gt;

&lt;p&gt;Your first reply should be a question, not a number.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Fair question. Before I look at anything, help me understand: is it the total amount, the timing of the payment, or how it compares to something else you're looking at?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Each answer points to a different move:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Total amount&lt;/strong&gt; → maybe the scope is wrong. Adjust scope, not price.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Timing&lt;/strong&gt; → it's a cash-flow or budget-cycle issue. Adjust payment terms, not price.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Comparison&lt;/strong&gt; → they have another quote. Ask what's in it before you react.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Just checking"&lt;/strong&gt; → they were testing. Hold the price politely.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last one is more common than people think. A lot of buyers are trained to ask once. If you stay calm and friendly, many of them move on.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Hold the price once, kindly
&lt;/h2&gt;

&lt;p&gt;If they were just checking, give a short, confident answer and stop talking.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I hear you. Honestly, this is already the price we think is fair for what you're getting, and I'd rather not pad it just to discount it later. Is there anything in the scope that doesn't feel worth it to you?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then wait. Count to five in your head if you have to. The silence after a confident answer is where most deals close at full price.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Never give, always trade
&lt;/h2&gt;

&lt;p&gt;If a concession is truly needed, make it a trade. A rule worth writing on a sticky note: &lt;strong&gt;every discount buys something.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Useful things to ask for in return:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A longer commitment (annual instead of monthly)&lt;/li&gt;
&lt;li&gt;Upfront payment&lt;/li&gt;
&lt;li&gt;A faster signature date&lt;/li&gt;
&lt;li&gt;A case study, a reference call or a public logo, if they're comfortable with it&lt;/li&gt;
&lt;li&gt;A smaller starting scope that expands later&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The script:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I might be able to move on price if we can make it work on our side too. If you were able to sign by the end of this month and pay annually, I'll see what I can do. Would that work for you?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Notice the "if… then" structure. The concession is conditional. If they say no to the condition, the discount disappears without you having to take anything back.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Concede in shrinking steps
&lt;/h2&gt;

&lt;p&gt;If you do move, the size of your steps tells the buyer how close they are to your limit. Big, equal steps say "there's plenty more". Shrinking steps say "we're near the end".&lt;/p&gt;

&lt;p&gt;Bad pattern: 10% → 10% → 10%.&lt;br&gt;
Better pattern: 6% → 3% → 1%, each one tied to something new.&lt;/p&gt;

&lt;p&gt;And name a number that's specific. "We can do 6%" sounds like a calculated decision. "We can do about 10%" sounds like a guess you'd happily revise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Close the loop and confirm
&lt;/h2&gt;

&lt;p&gt;When you land on terms, don't let the call drift. Summarise and get the next step in the calendar.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"So to confirm: annual plan, paid upfront, 6% off the list price, signature by the 30th. I'll send the updated agreement today. Who else needs to see it before you sign?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That last question catches the silent approver before they surprise you next week.&lt;/p&gt;

&lt;h2&gt;
  
  
  A discount negotiation checklist for your next sales call
&lt;/h2&gt;

&lt;p&gt;Copy this into your call notes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] I asked &lt;em&gt;why&lt;/em&gt; before I offered anything&lt;/li&gt;
&lt;li&gt;[ ] I held the price at least once, calmly, and then stayed quiet&lt;/li&gt;
&lt;li&gt;[ ] Every concession was traded for something (term, timing, payment, scope)&lt;/li&gt;
&lt;li&gt;[ ] My concessions got smaller each time&lt;/li&gt;
&lt;li&gt;[ ] I used specific numbers, not "about" or "roughly"&lt;/li&gt;
&lt;li&gt;[ ] I summarised the final terms out loud&lt;/li&gt;
&lt;li&gt;[ ] I left with a signature date and the name of every approver&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  For founders and engineers: decide your floor before the call
&lt;/h2&gt;

&lt;p&gt;Founder-led sales has one extra trap: you're the person who sets the price &lt;em&gt;and&lt;/em&gt; the person who wants to be liked on the call. That's a bad combination at minute 28.&lt;/p&gt;

&lt;p&gt;Write three numbers down before any closing call:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;List price.&lt;/strong&gt; What you quote.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Target.&lt;/strong&gt; What you'd be happy with.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Walk-away.&lt;/strong&gt; Below this, you say no, kindly.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you're an engineer or solutions engineer who ends up owning the quote, agree these numbers with whoever owns revenue before the call, so you're never improvising margin in front of a buyer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this only works with sales practice
&lt;/h2&gt;

&lt;p&gt;Reading a negotiation playbook feels great. Then a real buyer says "can you do better?" in a slightly annoyed voice and your mouth says "sure, 15%" before your brain catches up.&lt;/p&gt;

&lt;p&gt;The pause, the hold, the "if… then" trade: these are reflexes, and reflexes come from sales practice, not from reading. Run a sales role play where a colleague plays a buyer who asks for a discount three times in a row, each time a bit more insistent. Do it until holding your price feels boring. That's when it's ready for a live call.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;A discount request is a buying signal, not a rejection. Ask what's behind it, hold your price once, trade every concession for something real, shrink your steps, and leave with a date. You'll close more deals at prices that actually keep your company alive.&lt;/p&gt;

&lt;p&gt;If you want to rehearse moments like this against virtual customers that push back like real buyers, that's what we're building with Maya, our sales coach, at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>startup</category>
      <category>career</category>
      <category>saas</category>
    </item>
    <item>
      <title>How to Handle "I Need to Run It by My Boss": Objection Handling and Sales Scripts for Multi-Stakeholder Deals</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Sat, 14 Nov 2026 09:16:36 +0000</pubDate>
      <link>https://dev.to/kulissa/how-to-handle-i-need-to-run-it-by-my-boss-objection-handling-and-sales-scripts-for-1n80</link>
      <guid>https://dev.to/kulissa/how-to-handle-i-need-to-run-it-by-my-boss-objection-handling-and-sales-scripts-for-1n80</guid>
      <description>&lt;p&gt;"I need to run it by my boss" is one of the most common moments in a sales call, and good objection handling here decides whether your deal moves forward or quietly dies in someone else's inbox. These sales scripts and discovery questions are for founders doing founder-led sales, engineers moving into customer-facing roles, SDRs and AEs who keep hearing this line after what felt like a great call.&lt;/p&gt;

&lt;p&gt;The problem isn't the boss. The problem is that your champion is about to pitch your product to someone you've never met, without you, using whatever they remember from a 30-minute call. That's the part you can fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "I need to run it by my boss" usually means
&lt;/h2&gt;

&lt;p&gt;The same sentence can carry very different meanings. Before you respond, figure out which one you're hearing:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A real approval step.&lt;/strong&gt; They like it, but someone else signs. This is the good version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A polite exit.&lt;/strong&gt; They're not convinced and the boss is a soft way to say no.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;They don't know how to sell it internally.&lt;/strong&gt; They want it, but they can't explain the value in their manager's language.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The boss has a specific concern&lt;/strong&gt; (budget, risk, timing) that your contact already knows about but hasn't told you.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Each one needs a different next step, so your first move is a question, not a pitch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Acknowledge, then ask one discovery question
&lt;/h2&gt;

&lt;p&gt;Don't argue with the process. Respect it, then get information.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Makes total sense, most teams want a second set of eyes on this. Can I ask: when you bring it to them, what do you think their first question will be?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This one question does a lot of work. If they answer quickly and specifically ("she'll ask what it costs compared to what we pay now"), you're in version 1 or 4. If they hesitate or go vague ("oh, just the usual"), you're probably in version 2 or 3.&lt;/p&gt;

&lt;p&gt;Follow-up discovery questions that help:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"How do decisions like this usually get made on your team?"&lt;/li&gt;
&lt;li&gt;"Has your manager looked at anything like this before? How did that go?"&lt;/li&gt;
&lt;li&gt;"Is there anything you're still unsure about yourself before you take it to them?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last question is the honest one. It gives a hesitant buyer permission to raise their own objection, which is far better than having it surface later as "my boss said no."&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Arm your champion
&lt;/h2&gt;

&lt;p&gt;If it's a real approval step, your job is to make your contact look good in front of their manager. Most deals stall here because the champion has to translate your pitch from memory.&lt;/p&gt;

&lt;p&gt;Sales script:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"When you bring this up, what would make it easiest for you? I can write a short summary in your words: the problem you described, what changes, and what the first step would cost. You can edit it or forward it as-is."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then actually write it. Keep it to five lines:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The problem&lt;/strong&gt;, in the exact words they used on the call.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What it costs them today&lt;/strong&gt; (time, missed deals, rework), only if they told you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What changes&lt;/strong&gt; if they move forward.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The smallest first step&lt;/strong&gt; and when it ends.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The one open question&lt;/strong&gt; you expect from the boss, with an answer.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No feature list. No adjectives. Managers skim, and a short note in their own team's language gets read.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Ask to be in the room (without being pushy)
&lt;/h2&gt;

&lt;p&gt;The strongest move is to join the conversation, but you have to offer it as help, not as a demand.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Totally fine if you'd rather take it on your own. If it's useful, I'm happy to join for the last 15 minutes to answer the technical or pricing questions, so you don't have to carry those."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If they say no, don't push. Ask instead:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Fair enough. What would you need from me to feel confident answering whatever comes up?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;For engineers and solutions engineers moving into sales: this is where your background helps. Offer to cover the technical questions specifically. Champions often say yes to "I'll handle the security and integration questions" when they'd say no to "can I pitch your boss?"&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Lock a next step before you hang up
&lt;/h2&gt;

&lt;p&gt;"I'll get back to you" is how deals disappear. Close the call with a date, not a hope.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"When are you seeing them? Great, how about I put 15 minutes in our calendars for the day after, so you can tell me what they said and we figure out the next step together?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is a closing technique in the honest sense: you're not forcing a decision, you're closing on a next step. If they won't commit to even a short follow-up, that's information. You're probably hearing version 2.&lt;/p&gt;

&lt;h2&gt;
  
  
  Handling the polite exit version
&lt;/h2&gt;

&lt;p&gt;If your discovery questions suggest "my boss" is really a soft no, name it gently:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Can I be direct? Sometimes 'I need to check with my boss' means 'I'm not sure this is right.' If that's the case, I'd much rather hear it now. What's giving you pause?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A real objection on the table is something you can work with. A vague one is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sales call checklist for multi-stakeholder deals
&lt;/h2&gt;

&lt;p&gt;Use this before and after any call where approval comes up:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] I asked who else is involved in the decision early in the call, not at the end.&lt;/li&gt;
&lt;li&gt;[ ] I know what the boss's first question will be.&lt;/li&gt;
&lt;li&gt;[ ] I asked whether my contact still has doubts of their own.&lt;/li&gt;
&lt;li&gt;[ ] I offered a short written summary in the buyer's words.&lt;/li&gt;
&lt;li&gt;[ ] I offered to join for part of the internal meeting.&lt;/li&gt;
&lt;li&gt;[ ] I proposed the smallest possible first step.&lt;/li&gt;
&lt;li&gt;[ ] We have a dated follow-up in the calendar.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Prevent it next time
&lt;/h2&gt;

&lt;p&gt;The best way to handle this objection is to surface it in discovery, before your pitch. Early in the call, ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Besides you, who else usually weighs in on something like this?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Asked early, it's a neutral process question. Asked at the end, it feels like you're trying to get around your contact. Asking early also lets you shape the whole call around what the decision maker cares about.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practice it out loud
&lt;/h2&gt;

&lt;p&gt;Knowing these lines is easy. Saying them calmly when a call you thought was going well suddenly stalls is harder. Founders and new reps often either rush to "can I talk to your boss directly?", which feels pushy, or accept "I'll get back to you" and never hear back.&lt;/p&gt;

&lt;p&gt;Sales practice fixes this. Rehearse the acknowledge-and-ask line until it's automatic, then run a sales role play where a colleague plays a hesitant champion and gives you the vague version of the objection.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;"I need to run it by my boss" isn't a rejection. It's a handoff. Find out what it really means with one good discovery question, give your champion a short summary they can forward, offer to help in the room, and leave every call with a date.&lt;/p&gt;

&lt;p&gt;If you want to rehearse moments like this against virtual customers that push back like real buyers, that's what we're building with Maya, our sales coach, at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>career</category>
      <category>startup</category>
      <category>saas</category>
    </item>
    <item>
      <title>How to Handle "You're Too Small for Us": Objection Handling and Sales Scripts for Founder-Led Sales</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Fri, 13 Nov 2026 09:13:21 +0000</pubDate>
      <link>https://dev.to/kulissa/how-to-handle-youre-too-small-for-us-objection-handling-and-sales-scripts-for-founder-led-sales-46f1</link>
      <guid>https://dev.to/kulissa/how-to-handle-youre-too-small-for-us-objection-handling-and-sales-scripts-for-founder-led-sales-46f1</guid>
      <description>&lt;p&gt;When you're doing founder-led sales, one objection shows up earlier and more often than almost any other: "You're a bit small for us." Sometimes it's said out loud, sometimes it hides behind "we only work with established vendors." This post is a practical objection handling guide with sales scripts for that exact moment, written for founders, engineers moving into customer-facing roles, and SDRs at early-stage startups.&lt;/p&gt;

&lt;p&gt;The goal isn't to argue the buyer out of their concern. The concern is often fair. The goal is to find out what "too small" actually means to this person, and then answer that specific risk.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "you're too small" usually means
&lt;/h2&gt;

&lt;p&gt;In practice, the phrase is a label stuck on one of a handful of real worries. Before you answer, you need to know which one you're dealing with:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;"Will you still exist in a year?"&lt;/strong&gt; Continuity risk. They don't want to migrate twice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Who do I call when it breaks?"&lt;/strong&gt; Support risk. They picture a two-person team on holiday.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Will this pass security and procurement?"&lt;/strong&gt; Process risk. They've been burned by a vendor review before.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Will my boss question this choice?"&lt;/strong&gt; Personal risk. Nobody gets blamed for picking the big name.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"I'm not actually interested."&lt;/strong&gt; A polite exit, using size as the excuse.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Each one needs a different answer. Responding to all five at once ("we're well funded, we have great support, we're SOC 2 ready, and lots of people trust us") sounds defensive and usually isn't even true for a young company.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Acknowledge, then ask a discovery question
&lt;/h2&gt;

&lt;p&gt;Don't flinch and don't oversell. Agree with the part that's true, then ask.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"That's fair, we are a small team, and I'd rather talk about it now than have it come up in procurement. When you say small, what's the part that worries you most: that we won't be around, support, or getting through your vendor review?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That one question does a lot of work. It shows confidence, it treats the buyer as reasonable, and it turns a vague objection into a specific one you can actually handle.&lt;/p&gt;

&lt;p&gt;If they answer with something vague like "just in general," try one more:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"If we were twice the size tomorrow, what would be different for you?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Their answer tells you what they really need to see.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Answer the real risk with something concrete
&lt;/h2&gt;

&lt;p&gt;Here are short sales scripts for each version. Only use what is actually true for your company. Inventing traction to win this objection is the fastest way to lose the deal later, and your reputation with it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Continuity risk&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Totally reasonable. Two things we do for that: you can export all your data at any time in a standard format, and we keep the setup light so switching away wouldn't be a project. Would it help if I showed you the export now?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You're not promising you'll exist forever. You're lowering the cost of being wrong.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Support risk&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"The upside of a small team is you'd be talking to the people who built it. Here's how support works today: [actual channel, actual response time you can keep]. What response time would you need for this to work?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Let them set the bar, then tell them honestly whether you can meet it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Process risk&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Let's find out early. Can you send me your vendor questionnaire, or tell me who owns it? I'd rather know now what we can and can't answer than surprise you in three weeks."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Asking for the questionnaire yourself is one of the strongest moves in founder-led sales. It signals you aren't hiding anything.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Personal risk&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"If you brought this to your manager, what would they ask first? Let's make sure you have an answer for that."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Now you're helping your champion sell internally, which is the actual job.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The polite exit&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If none of the questions get traction, test it directly:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"It sounds like size might not be the real blocker. Is this just not a priority right now? Totally fine if so, I'd rather know."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A clear no is worth more than a stalled maybe in your pipeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Shrink the commitment
&lt;/h2&gt;

&lt;p&gt;Small companies win against "too small" by making the first step smaller than the risk. Offer a scoped trial, a single team, a fixed end date, or a clear exit:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"What if we started with one team for four weeks, with a check-in at week two and a clean way out if it's not working? That way the risk is four weeks, not a contract."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is a closing technique that works because it's honest about the trade-off. You're not pretending to be big; you're making size matter less.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick objection handling checklist
&lt;/h2&gt;

&lt;p&gt;Use this before and after calls where size might come up:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] I know which of the five risks the buyer actually means.&lt;/li&gt;
&lt;li&gt;[ ] I acknowledged the concern before answering it.&lt;/li&gt;
&lt;li&gt;[ ] Every claim I made about support, security or continuity is true today.&lt;/li&gt;
&lt;li&gt;[ ] I asked for the vendor questionnaire or the procurement owner.&lt;/li&gt;
&lt;li&gt;[ ] I offered a smaller first step with a clear end date.&lt;/li&gt;
&lt;li&gt;[ ] I asked what their manager would need to hear.&lt;/li&gt;
&lt;li&gt;[ ] I got a clear next step or a clear no.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Practice it before it costs you a deal
&lt;/h2&gt;

&lt;p&gt;The hard part of this objection isn't knowing the words. It's staying calm when someone tells you, in effect, that your company isn't serious enough. Founders and engineers new to sales tend to either get defensive or start over-promising, and both kill trust.&lt;/p&gt;

&lt;p&gt;The fix is sales practice: say the acknowledge-and-ask line out loud until it feels boring, then do a sales role play where the buyer pushes back twice. Have a colleague play a skeptical procurement lead, or run it with a recorded call and review where your voice tightened. A few reps make a real difference on the call that matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;"You're too small" is rarely about size. It's about a specific risk the buyer can't see an answer to yet. Find the risk with one good discovery question, answer it with something true and concrete, and make the first commitment small enough that size stops mattering.&lt;/p&gt;

&lt;p&gt;If you want to rehearse objections like this one against virtual customers that push back like real buyers, that's what we're building at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>startup</category>
      <category>career</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Get Past the Gatekeeper: Cold Calling Tips and Sales Scripts for SDRs and Founders</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Thu, 12 Nov 2026 09:19:04 +0000</pubDate>
      <link>https://dev.to/kulissa/how-to-get-past-the-gatekeeper-cold-calling-tips-and-sales-scripts-for-sdrs-and-founders-2d7b</link>
      <guid>https://dev.to/kulissa/how-to-get-past-the-gatekeeper-cold-calling-tips-and-sales-scripts-for-sdrs-and-founders-2d7b</guid>
      <description>&lt;p&gt;If you do cold calling as an SDR, or you're a founder doing founder-led sales, the first person who answers the phone is often not the person you want. It's a receptionist, an executive assistant, or an office manager whose job is to protect someone else's time. These cold calling tips and sales scripts cover how to get past the gatekeeper without lying, without sounding like a robot, and without burning the account.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why most gatekeeper sales scripts fail
&lt;/h2&gt;

&lt;p&gt;The classic advice is to sound important, drop the first name and act like you already know the boss. It works sometimes, and it fails badly the rest of the time. Assistants hear dozens of these calls a week. The moment they catch a trick, you're on the "never put through" list, and they will remember your company name.&lt;/p&gt;

&lt;p&gt;A better mental model: the gatekeeper is not an obstacle, they're the first qualified person in the account. They know who owns what, when the boss is free, and which projects are live. Treat them like a source of information, not a wall.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three things a gatekeeper is listening for
&lt;/h2&gt;

&lt;p&gt;Every gatekeeper is quietly answering three questions in the first ten seconds:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Is this a sales call?&lt;/strong&gt; (Yes. Don't pretend otherwise.)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is it relevant to my boss?&lt;/strong&gt; (This is where you win or lose.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Will I get in trouble for putting this through, or for blocking it?&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Your opener should make question 2 easy and question 3 safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cold call script: the honest opener
&lt;/h2&gt;

&lt;p&gt;Here is a simple opener you can adapt:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Hi, this is Sam from Northwind. I'll be quick, I'm trying to reach whoever owns sales onboarding for your team. Is that Dana, or is it someone else?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Why this works:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You say who you are straight away. No mystery, no fake familiarity.&lt;/li&gt;
&lt;li&gt;You name a &lt;em&gt;responsibility&lt;/em&gt;, not just a person. That gives the gatekeeper a reason to help you route the call.&lt;/li&gt;
&lt;li&gt;You end with an easy question they can actually answer.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If they say "Dana's busy, what's it regarding?", don't launch into your pitch. Give one sentence of relevance:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Sure. We help sales teams get new reps ready for customer calls faster. I wanted to ask Dana two quick questions to see if it's even relevant. When's usually a better time to catch her?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Handling the common gatekeeper objections
&lt;/h2&gt;

&lt;p&gt;Gatekeepers have their own objections, and objection handling works the same way it does with buyers: acknowledge, ask, then move one small step forward.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"Can you just send an email?"&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Happy to. So it doesn't end up in the wrong place, is Dana the right person for sales onboarding, or should it go to someone in enablement?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You turn a brush-off into a routing question. Now you know who to email, and you can mention in the subject line that you spoke to their assistant.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"She's not interested."&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Totally fair, I'm not trying to waste her time. Out of curiosity, is that because you already have something in place for new rep training, or because it's not a priority right now?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Either answer is useful. One tells you about a competitor, the other tells you about timing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"What's this about?"&lt;/strong&gt; (when you sense they want more detail)&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Honestly, it's a sales call. We work with teams who hire reps regularly and want them confident on calls sooner. If that's not a fit at all, tell me and I'll stop calling."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That last line sounds risky, but it builds trust fast. Gatekeepers rarely get honesty from cold callers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ask for help, not for a transfer
&lt;/h2&gt;

&lt;p&gt;The strongest cold calling tip for gatekeepers is to ask for advice:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Maybe you can help me. If someone wanted to talk to Dana about how new salespeople get trained, what's the best way to do that without being annoying?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;People like being asked for help. You'll often get the best time to call, the person's direct line, or a hint about what's happening internally, like "she's hiring three new reps this quarter."&lt;/p&gt;

&lt;h2&gt;
  
  
  When to go around, and when not to
&lt;/h2&gt;

&lt;p&gt;Sometimes you won't get through. That's fine. You have other options:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Call early or late.&lt;/strong&gt; Many decision-makers answer their own phone before the assistant arrives or after they leave.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use a different channel.&lt;/strong&gt; A short, specific email or LinkedIn message that mentions your call: "I spoke with your office this morning…"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Go sideways.&lt;/strong&gt; Call someone else on the team, like a sales manager or a team lead, and ask who owns the topic.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What not to do: never claim a fake referral, never pretend it's a personal call, and never say "she's expecting my call" when she isn't. You might get through once. You won't get a meeting, and you'll damage the account for your whole company.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick gatekeeper sales call checklist
&lt;/h2&gt;

&lt;p&gt;Before you dial:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] I know the name &lt;em&gt;and&lt;/em&gt; the responsibility I'm calling about.&lt;/li&gt;
&lt;li&gt;[ ] I have a one-sentence relevance line, not a pitch.&lt;/li&gt;
&lt;li&gt;[ ] I have an answer ready for "send an email" that asks a routing question.&lt;/li&gt;
&lt;li&gt;[ ] I'll ask for help, not just a transfer.&lt;/li&gt;
&lt;li&gt;[ ] I'll log what I learned (best time, direct line, internal context) in the CRM.&lt;/li&gt;
&lt;li&gt;[ ] I won't use any line I'd be embarrassed to repeat to the decision-maker.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Practise the first ten seconds
&lt;/h2&gt;

&lt;p&gt;The gatekeeper conversation is short, which makes it perfect for sales practice. The opener, the relevance line and the "send an email" response are three moments you can rehearse until they sound natural instead of memorised. Sales role play with a colleague works well: ask them to play a protective assistant and push back hard, then swap roles. The goal isn't a perfect script, it's staying calm and curious when someone says no in the first five seconds.&lt;/p&gt;

&lt;p&gt;Most cold calls are decided before you ever talk to the buyer. Get the first ten seconds right, be honest about why you're calling, and the gatekeeper often becomes your best ally inside the account.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;If you want a place to rehearse calls like this with virtual customers who push back, that's what we're building at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>sales</category>
      <category>career</category>
      <category>startup</category>
      <category>productivity</category>
    </item>
    <item>
      <title>SPIN Selling for Engineers and Founders: Discovery Questions and a Sales Call Checklist That Uncover Real Pain</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Wed, 11 Nov 2026 09:12:59 +0000</pubDate>
      <link>https://dev.to/kulissa/spin-selling-for-engineers-and-founders-discovery-questions-and-a-sales-call-checklist-that-4ce</link>
      <guid>https://dev.to/kulissa/spin-selling-for-engineers-and-founders-discovery-questions-and-a-sales-call-checklist-that-4ce</guid>
      <description>&lt;p&gt;If you're an engineer, a solutions engineer or a founder doing founder-led sales, discovery questions are probably the part of the sales call that feels least natural. You know the product cold, so the instinct is to explain it. SPIN selling is a sales framework that fixes that instinct by giving you four kinds of questions to ask, in a rough order, before you pitch anything. This post turns SPIN into a practical sales call checklist with example discovery questions, a worked example, and the mistakes engineers make most often.&lt;/p&gt;

&lt;h2&gt;
  
  
  What SPIN selling actually is
&lt;/h2&gt;

&lt;p&gt;SPIN comes from Neil Rackham's book &lt;em&gt;SPIN Selling&lt;/em&gt;. The idea is simple: in larger B2B sales, the questions you ask matter more than the pitch you give. SPIN groups those questions into four types:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Situation&lt;/strong&gt;: facts about how the buyer works today.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Problem&lt;/strong&gt;: where that way of working hurts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Implication&lt;/strong&gt;: what that pain costs, and what it causes downstream.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Need-payoff&lt;/strong&gt;: what solving it would be worth, in the buyer's own words.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Engineers tend to like SPIN because it reads like debugging. Situation is reproducing the environment. Problem is finding the bug. Implication is measuring the blast radius. Need-payoff is agreeing on what "fixed" means before you ship a patch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Situation questions: ask fewer than you think
&lt;/h2&gt;

&lt;p&gt;Situation questions are the easiest to ask and the easiest to overdo. Every one of them is work for the buyer and gives them nothing back. Do your homework (website, LinkedIn, job posts) and only ask what you genuinely can't find.&lt;/p&gt;

&lt;p&gt;Good situation questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Walk me through how a new rep gets ready for their first customer call today."&lt;/li&gt;
&lt;li&gt;"Who's involved when you evaluate a tool like this?"&lt;/li&gt;
&lt;li&gt;"What does the process look like between a lead coming in and a first meeting?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep it to three or four. If you're ten minutes in and still asking about team size, you're running an interview, not a discovery call.&lt;/p&gt;

&lt;h2&gt;
  
  
  Problem questions: find where it hurts
&lt;/h2&gt;

&lt;p&gt;Problem questions invite the buyer to name dissatisfaction. They are the bridge from "this is how we work" to "this is what bothers us."&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Where does that process break down?"&lt;/li&gt;
&lt;li&gt;"What's the hardest part of that for your team?"&lt;/li&gt;
&lt;li&gt;"When a deal slips, what's usually the reason?"&lt;/li&gt;
&lt;li&gt;"What have you already tried to fix it?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last one matters more than it looks. If they've tried and failed twice, you learn what not to pitch and how much appetite is left.&lt;/p&gt;

&lt;p&gt;A simple rule: when the buyer names a problem, don't jump to your solution. Write it down and go one level deeper.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implication questions: the step everyone skips
&lt;/h2&gt;

&lt;p&gt;This is where SPIN earns its reputation, and where most founders and engineers fall short. A problem on its own is a minor annoyance. A problem connected to revenue, time, risk or reputation is a priority.&lt;/p&gt;

&lt;p&gt;Implication questions connect the dots:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"When new reps take longer to ramp, what does that do to the quarter?"&lt;/li&gt;
&lt;li&gt;"If a rep fumbles a price objection on a first call, what happens to that deal?"&lt;/li&gt;
&lt;li&gt;"How much of your own time goes into covering for that?"&lt;/li&gt;
&lt;li&gt;"Who else feels it when this goes wrong?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You are not trying to scare anyone. You're helping the buyer see the full size of something they've been living with. Often they've never said it out loud, and the moment they do, the conversation changes.&lt;/p&gt;

&lt;p&gt;A warning: implication questions can feel manipulative if you fire them in a row. Ask one, listen, reflect back what you heard, then ask the next.&lt;/p&gt;

&lt;h2&gt;
  
  
  Need-payoff questions: let them sell it to themselves
&lt;/h2&gt;

&lt;p&gt;Need-payoff questions ask the buyer to describe the value of solving the problem. The point is that they say it, not you.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"If new reps could handle the common objections before their first live call, what would that change?"&lt;/li&gt;
&lt;li&gt;"What would it mean for you to get those hours back?"&lt;/li&gt;
&lt;li&gt;"If this was fixed by next quarter, how would you know?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When the buyer answers these, you get two things: their success criteria, and the exact language to use when you finally show the product. Quote them back during the demo: "You said the biggest win would be X, so let me show you that first."&lt;/p&gt;

&lt;h2&gt;
  
  
  A worked example
&lt;/h2&gt;

&lt;p&gt;Here's a compressed discovery call for a founder selling a developer tool, using all four types:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Situation:&lt;/strong&gt; "How do you handle code review on your team today?"&lt;br&gt;
&lt;em&gt;"PRs go to one of two seniors."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Problem:&lt;/strong&gt; "Where does that slow you down?"&lt;br&gt;
&lt;em&gt;"Reviews sit for a day or two. The seniors are swamped."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Implication:&lt;/strong&gt; "When a PR sits for two days, what happens to the release?"&lt;br&gt;
&lt;em&gt;"We batch, then merge conflicts pile up, and Friday becomes cleanup day."&lt;/em&gt;&lt;br&gt;
"And the seniors?"&lt;br&gt;
&lt;em&gt;"Honestly, one of them has mentioned burning out."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Need-payoff:&lt;/strong&gt; "If reviews turned around the same day, what would that free up?"&lt;br&gt;
&lt;em&gt;"Fridays back, and I'd stop worrying about losing a senior."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Notice the pitch hasn't started. By the end, the buyer has described a retention risk in their own words. That is a much stronger opening for your demo than any feature list.&lt;/p&gt;

&lt;h2&gt;
  
  
  SPIN sales call checklist
&lt;/h2&gt;

&lt;p&gt;Copy this into your call notes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Researched the account so I ask 4 or fewer situation questions&lt;/li&gt;
&lt;li&gt;[ ] Got at least 2 problems named in the buyer's words&lt;/li&gt;
&lt;li&gt;[ ] Asked "what have you tried?" for the main problem&lt;/li&gt;
&lt;li&gt;[ ] Asked at least 2 implication questions per problem, one at a time&lt;/li&gt;
&lt;li&gt;[ ] Heard who else is affected (other stakeholders)&lt;/li&gt;
&lt;li&gt;[ ] Got a need-payoff answer I can quote back in the demo&lt;/li&gt;
&lt;li&gt;[ ] Agreed what "solved" looks like before showing the product&lt;/li&gt;
&lt;li&gt;[ ] Booked the next step with a date&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Common mistakes engineers make with SPIN
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Treating it as a script.&lt;/strong&gt; SPIN is a map, not a sequence to read top to bottom. If the buyer opens with a problem, go there.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pitching at the first problem.&lt;/strong&gt; The moment you hear a pain you can solve, the urge to demo is huge. Hold it for two more questions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Skipping implication because it feels awkward.&lt;/strong&gt; It is awkward at first. It's also the part that turns "nice to have" into "let's talk budget."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Answering your own questions.&lt;/strong&gt; Ask, then stop talking. Silence after a good implication question is the buyer thinking, not a gap to fill.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Practice the questions before the call
&lt;/h2&gt;

&lt;p&gt;Reading a list of discovery questions is easy. Asking an implication question calmly, while a buyer gives you a short, guarded answer, is a different skill. The only way it becomes natural is sales practice: role play with a teammate, record yourself, or run the same call several times until the follow-up questions come without thinking.&lt;/p&gt;

&lt;p&gt;If you want to rehearse SPIN-style discovery calls against realistic virtual customers before the real one, that's what we're building at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>startup</category>
      <category>career</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Handle "Call Me Next Quarter": Objection Handling and Sales Scripts for the Timing Stall</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Tue, 10 Nov 2026 09:06:43 +0000</pubDate>
      <link>https://dev.to/kulissa/how-to-handle-call-me-next-quarter-objection-handling-and-sales-scripts-for-the-timing-stall-4e5k</link>
      <guid>https://dev.to/kulissa/how-to-handle-call-me-next-quarter-objection-handling-and-sales-scripts-for-the-timing-stall-4e5k</guid>
      <description>&lt;p&gt;If you do founder-led sales or work as an SDR, you have heard this one more often than a flat no: "Call me next quarter." It sounds friendly, it sounds like a plan, and it quietly kills more pipeline than any price objection. This post is a practical objection handling guide for the timing stall, with sales scripts you can say out loud, discovery questions that find out what "next quarter" really means, and a short checklist to run before you hang up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why "call me next quarter" is a stall, not a schedule
&lt;/h2&gt;

&lt;p&gt;A real timing objection has a reason attached: a budget cycle, a contract renewal, a reorg, a launch freeze. A stall has no reason attached. The buyer is being polite because saying "this isn't a priority" feels rude.&lt;/p&gt;

&lt;p&gt;The trap is that both sound identical on the call. Your job in that moment is not to push past the objection. It's to find out which one you're facing, in under a minute, without sounding defensive.&lt;/p&gt;

&lt;p&gt;Three things are usually hiding behind "next quarter":&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Real timing.&lt;/strong&gt; Something specific blocks a decision right now.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Low priority.&lt;/strong&gt; The problem you raised isn't painful enough yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Low trust.&lt;/strong&gt; They don't believe you can solve it, and "later" is easier than "no".&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Each one needs a different response. Treating them all as "great, I'll put it in my calendar" is how deals rot.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Agree, then ask what changes
&lt;/h2&gt;

&lt;p&gt;Never argue with timing. Agree with it, then get curious about the gap between now and then.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Totally fair. Can I ask what changes between now and next quarter? I want to make sure that when I call, it's actually useful and not just me chasing you."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is the single most useful line in this whole post. If there's a real reason, they'll tell you: "We renew our current tool in March," or "New head of sales starts in January." If there's no reason, you'll hear a pause and something vague like "things should calm down." That pause is your answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Discovery questions that separate timing from priority
&lt;/h2&gt;

&lt;p&gt;Once you know which way it leans, use one or two of these discovery questions. Don't fire all of them; this isn't an interrogation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If it sounds like real timing:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Who else needs to be involved when that happens?"&lt;/li&gt;
&lt;li&gt;"What would you need to have ready before that decision, so you're not starting from zero?"&lt;/li&gt;
&lt;li&gt;"If the renewal date is in March, when would you realistically need to start evaluating alternatives?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last one matters. Buyers often say "next quarter" when they really mean "the decision happens next quarter," which means the evaluation should start now.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If it sounds like low priority:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Out of curiosity, where does this sit on your list right now, top three or further down?"&lt;/li&gt;
&lt;li&gt;"What would have to happen for this to move up?"&lt;/li&gt;
&lt;li&gt;"What's it costing you to leave it as it is for another three months?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ask the cost question calmly. You're not trying to scare anyone. You're helping them say out loud whether the problem is real.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If it sounds like low trust:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Is it the timing, or is there something about what I showed you that doesn't fit yet?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Giving them permission to be honest is often enough. People would rather tell you the real objection than keep dodging your calls.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Sales scripts for each outcome
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Real timing, decision later, evaluation now:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"That makes sense. Since the renewal is in March and these evaluations usually take a few weeks on your side, would it help to do a short working session in January, so you have a comparison ready instead of a rush?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You're not asking for the deal. You're asking for an earlier, smaller step that serves their timeline.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Low priority:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Sounds like this isn't a top-three problem right now, and that's completely fine. Rather than me calling you in three months to ask the same question, can I send you one short note when [specific trigger] happens? If it's still not a priority then, I'll take that as a no."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is honest, it's easy to say yes to, and it gives you a reason to reach out that isn't "just checking in."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Low trust:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Thanks for being straight with me. What would you need to see to know whether this could work for your team? If I can't show you that, I'd rather know now."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Step 4: Never leave without a dated next step
&lt;/h2&gt;

&lt;p&gt;"Call me next quarter" without a date is a no wearing a nicer jacket. Before you end the call, get one of these:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A specific date and time in the calendar, sent while you're still on the call.&lt;/li&gt;
&lt;li&gt;A named trigger ("when the new head of sales starts") plus permission to follow up when it happens.&lt;/li&gt;
&lt;li&gt;A clear no, which is more valuable than a fake maybe because it frees your pipeline.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A simple follow-up email right after the call locks it in:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Subject: Picking this up in January&lt;/p&gt;

&lt;p&gt;Thanks for the time today. As discussed, the renewal decision is in March, so I've put a 20-minute slot on 14 January to walk through options before then. If anything changes earlier, just reply here.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Short, specific, and it repeats their own reason back to them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist: before you accept "next quarter"
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Did I agree before asking anything? No arguing with timing.&lt;/li&gt;
&lt;li&gt;[ ] Did I ask what changes between now and then?&lt;/li&gt;
&lt;li&gt;[ ] Do I know if it's timing, priority or trust?&lt;/li&gt;
&lt;li&gt;[ ] Do I know who else is involved in the later decision?&lt;/li&gt;
&lt;li&gt;[ ] Is there an earlier, smaller step that fits their timeline?&lt;/li&gt;
&lt;li&gt;[ ] Did I leave with a date, a named trigger or a clear no?&lt;/li&gt;
&lt;li&gt;[ ] Did I send a follow-up email the same day?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The real skill is staying calm in the first five seconds
&lt;/h2&gt;

&lt;p&gt;Everything above is easy to read and hard to do live. When a buyer says "call me next quarter," most people feel relief, because the call is ending politely, and they take it. The reps who keep deals moving are the ones who have heard that line so many times that it doesn't trigger anything. They just ask what changes.&lt;/p&gt;

&lt;p&gt;That only comes from sales practice: saying these sales scripts out loud, against a buyer who stalls, until the response is automatic. Role play with a colleague works. So does recording yourself. The goal is that the first time you use "what changes between now and then?" isn't on a deal you care about.&lt;/p&gt;

&lt;p&gt;If you want to rehearse timing stalls and other objections against realistic virtual customers before your next call, that's what we're building at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>startup</category>
      <category>career</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Handle "We Have No Budget": Objection Handling and Sales Scripts for Founders and SDRs</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Mon, 09 Nov 2026 09:05:06 +0000</pubDate>
      <link>https://dev.to/kulissa/how-to-handle-we-have-no-budget-objection-handling-and-sales-scripts-for-founders-and-sdrs-1dng</link>
      <guid>https://dev.to/kulissa/how-to-handle-we-have-no-budget-objection-handling-and-sales-scripts-for-founders-and-sdrs-1dng</guid>
      <description>&lt;p&gt;"We have no budget" is the objection that ends more sales calls than any other. Good objection handling starts with one idea: it is almost never a statement about money. It is a statement about priority, risk or authority. If you treat it as a fact, you leave. If you treat it as information, you get a next step.&lt;/p&gt;

&lt;p&gt;This post gives you a way to diagnose which "no budget" you are hearing, plus sales scripts you can practise out loud. It works for founder-led sales, SDRs and account executives alike.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four meanings of "no budget"
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;No priority.&lt;/strong&gt; The problem is real but not painful enough to fund this quarter.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No authority.&lt;/strong&gt; The person you talk to cannot move money and does not want to say so.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No proof.&lt;/strong&gt; They can't picture the return, so any price feels too high.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No budget, truly.&lt;/strong&gt; Money is frozen, and nothing you say changes that this cycle.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Your job in the next two minutes of the call is to work out which one it is. The discovery questions you asked earlier decide how easy this is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Don't defend, get curious
&lt;/h2&gt;

&lt;p&gt;The worst reply is a discount or a pitch. Slow down and ask permission to understand.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"That makes sense, and thanks for being direct. Can I ask how budget usually gets set for something like this? I want to make sure I'm not wasting your time."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You are asking about the process, not arguing with the answer. Prospects who have real constraints will explain them. Prospects hiding behind the line will usually reveal it here.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Test priority
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;"If budget wasn't a question, would solving this be something you'd want to do this quarter?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ul&gt;
&lt;li&gt;If yes, it is a budget-timing or authority issue. Continue to step 3.&lt;/li&gt;
&lt;li&gt;If "not really", you have a priority problem. Go back to the cost of the status quo: "What does it cost you each month that this stays as it is?" Use their numbers, never yours.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 3: Test authority
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;"Who else would have a say in funding this? Would it help if I put together a one-page summary you could forward?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Notice the framing. You are not going around them. You are making them look good inside their company. A short summary with their own words from the call (the problem, the cost, the outcome they want) is the best asset you can leave behind.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Build proof
&lt;/h2&gt;

&lt;p&gt;When the real issue is proof, shrink the ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Instead of a full rollout, what if we picked one team and one measurable result for 30 days? Then the budget conversation is about evidence, not a promise."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Small, measurable next steps turn "no budget" into "let's see."&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Handle the true no gracefully
&lt;/h2&gt;

&lt;p&gt;Sometimes it really is a no. Do not push. Set the date instead.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Understood. When does budget planning start for next year? Can I check back two weeks before that and send you the summary now so it's in your files?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then actually follow up. Put the date in your calendar before you hang up.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick checklist for the call
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Did I ask how budget is set before I responded?&lt;/li&gt;
&lt;li&gt;Did I separate priority from authority?&lt;/li&gt;
&lt;li&gt;Did I quote the prospect's own cost of inaction, not mine?&lt;/li&gt;
&lt;li&gt;Did I leave with a dated next step, even if it was small?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why this is hard to do live
&lt;/h2&gt;

&lt;p&gt;Reading the script is easy. Staying calm when a real person says "we have no budget" and the silence gets awkward is the hard part. The fix is repetition: say these lines out loud against a buyer who pushes back, until the curious question comes out before the defensive one. That is the idea behind sales role play, and it is what we are building at Kulissa: a sales coach with virtual customers you can practise against before the real call.&lt;/p&gt;

&lt;p&gt;Try the five-step flow on your next three calls, and note which meaning of "no budget" shows up most. You will probably find it is the first one.&lt;/p&gt;

&lt;p&gt;If you want to practise sales calls like this, take a look at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>career</category>
      <category>startup</category>
      <category>saas</category>
    </item>
    <item>
      <title>BANT vs MEDDIC for Founder-Led Sales: Discovery Questions and a Sales Call Checklist That Qualify Deals</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Sun, 08 Nov 2026 09:05:47 +0000</pubDate>
      <link>https://dev.to/kulissa/bant-vs-meddic-for-founder-led-sales-discovery-questions-and-a-sales-call-checklist-that-qualify-ggc</link>
      <guid>https://dev.to/kulissa/bant-vs-meddic-for-founder-led-sales-discovery-questions-and-a-sales-call-checklist-that-qualify-ggc</guid>
      <description>&lt;p&gt;Most founders doing founder-led sales don't lose deals in the close. They lose them weeks earlier, by spending three calls and a custom demo on someone who was never going to buy. That's a qualification problem, and the fix is a handful of discovery questions you ask on purpose instead of hoping the answers show up.&lt;/p&gt;

&lt;p&gt;This post compares the two sales frameworks people reach for most, BANT and MEDDIC, and turns them into a short qualification checklist you can actually use on a sales call this week.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why qualification is a sales skill, not a form
&lt;/h2&gt;

&lt;p&gt;Qualification sounds like CRM admin. In practice it's a conversation skill: asking a direct question about budget or decision-making without sounding like you're reading a checklist. Engineers and founders who move into sales often skip it because it feels rude. The result is a pipeline full of friendly people who will never sign.&lt;/p&gt;

&lt;p&gt;A good rule: if you can't answer "who signs, why now, and what happens if they do nothing," the deal isn't real yet. It's a conversation.&lt;/p&gt;

&lt;h2&gt;
  
  
  BANT: the fast filter
&lt;/h2&gt;

&lt;p&gt;BANT stands for Budget, Authority, Need, Timeline. It's old, simple, and still useful as a first pass.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Budget:&lt;/strong&gt; Is there money, or a way to get it?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authority:&lt;/strong&gt; Are you talking to the person who decides, or someone who can introduce you?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Need:&lt;/strong&gt; Is there a real problem, in their words?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Timeline:&lt;/strong&gt; Is something forcing a decision soon?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Where BANT works: short sales cycles, smaller deals, SDR tips for a first call where the goal is "is this worth a second meeting?"&lt;/p&gt;

&lt;p&gt;Where it breaks: it treats budget as a yes/no gate. In B2B sales, especially SaaS sales to companies that have never bought a tool like yours, budget often doesn't exist until the need is clear. Asking "do you have budget?" on minute four mostly gets you "not really."&lt;/p&gt;

&lt;h2&gt;
  
  
  MEDDIC: the deal map
&lt;/h2&gt;

&lt;p&gt;MEDDIC stands for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion. It's heavier, and it's built for deals with more than one person involved.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Metrics:&lt;/strong&gt; What number gets better if this works?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Economic buyer:&lt;/strong&gt; Who controls the money?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decision criteria:&lt;/strong&gt; What will they compare options on?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decision process:&lt;/strong&gt; What steps happen between "yes, interesting" and a signature?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Identify pain:&lt;/strong&gt; What hurts today, and what does it cost?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Champion:&lt;/strong&gt; Who inside wants this to happen and will sell it when you're not in the room?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Where MEDDIC works: account executive work on larger deals, anything with procurement, security review, or a committee.&lt;/p&gt;

&lt;p&gt;Where it breaks: run all six letters on a first call and it feels like an interrogation. MEDDIC is something you fill in across calls, not a script for one.&lt;/p&gt;

&lt;h2&gt;
  
  
  The founder version: five discovery questions
&lt;/h2&gt;

&lt;p&gt;If you're a founder or a solutions engineer running your own sales calls, you don't need to pick a camp. Use BANT's speed on call one and MEDDIC's depth as the deal grows. Here are five discovery questions that cover most of both, worded so they sound human:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Pain:&lt;/strong&gt; "What made you take this call now, instead of six months ago?"&lt;br&gt;
This gets need and timeline in one question. If the answer is "just curious," that's useful too.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Cost of doing nothing:&lt;/strong&gt; "If nothing changes, what does that look like by the end of the quarter?"&lt;br&gt;
This is your Metrics and Identify pain. Listen for a number or a consequence.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Decision process:&lt;/strong&gt; "Say you love this. What happens next on your side before you could start?"&lt;br&gt;
Much softer than "who's the decision maker?" and it usually reveals the economic buyer and any review steps.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Decision criteria:&lt;/strong&gt; "If you were comparing a few options, what would make one the obvious pick?"&lt;br&gt;
Now you know what you're being judged on, and whether you can win on it.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Champion check:&lt;/strong&gt; "Who else would care about this, and how would you explain it to them?"&lt;br&gt;
If they can explain it well, you may have a champion. If they hesitate, you have work to do.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Notice there's no budget question. Budget usually comes out of question 3 ("we'd need to get it into next year's plan") or you raise it once the value is clear: "Based on what you've told me, does a price in this range make sense to take forward?"&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick sales call checklist
&lt;/h2&gt;

&lt;p&gt;Before you end any discovery call, check you can answer these. If you can't, ask before you hang up.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] What problem they have, in their words&lt;/li&gt;
&lt;li&gt;[ ] Why it matters now&lt;/li&gt;
&lt;li&gt;[ ] What it costs them to do nothing&lt;/li&gt;
&lt;li&gt;[ ] Who else is involved in the decision&lt;/li&gt;
&lt;li&gt;[ ] The next concrete step, with a date&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last line matters most. "I'll send some info" is not a next step. "Thursday at 2 with you and your head of sales" is.&lt;/p&gt;

&lt;h2&gt;
  
  
  What qualification sounds like when it goes wrong
&lt;/h2&gt;

&lt;p&gt;Two common failure modes:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The interrogation.&lt;/strong&gt; You ask all five questions back to back, the prospect gets shorter answers each time, and you leave with notes but no trust. Fix it by following up on each answer before moving on: "You said the team ramps slowly. Slow how?"&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The polite avoidance.&lt;/strong&gt; You sense a weak deal but don't want to ask the hard question, so you book another demo. Fix it by naming it: "Honest question, it sounds like this isn't a priority until next year. Is that right?" People respect that, and a clean "no" frees your calendar.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to get better at it
&lt;/h2&gt;

&lt;p&gt;Qualification questions feel awkward the first twenty times you ask them out loud. Reading a sales framework won't fix that; saying the words will. Sales role play with a colleague works if you can get the time. Pick one question from the list above and use it on every call this week until it sounds like you.&lt;/p&gt;

&lt;p&gt;That's the kind of sales practice we're building at Kulissa: realistic conversations with virtual customers who push back, go vague, or dodge the budget question, so the hard questions feel normal before a real deal depends on them. If that sounds useful, have a look at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;kulissa.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>startup</category>
      <category>career</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The Name Maya and the Illusion of Easy Sales Practice</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Sat, 07 Nov 2026 15:14:48 +0000</pubDate>
      <link>https://dev.to/kulissa/the-name-maya-and-the-illusion-of-easy-sales-practice-mdm</link>
      <guid>https://dev.to/kulissa/the-name-maya-and-the-illusion-of-easy-sales-practice-mdm</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://kulissa.com/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt; blog: &lt;a href="https://kulissa.com/blog/the-name-maya-and-the-illusion-of-easy-practice?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;The name Maya and the illusion of easy practice&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;This note is about the name. For the role, read &lt;a href="https://kulissa.com/blog/maya-ai-sales-coach?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Maya, sales coach&lt;/a&gt;. For the etymology, read &lt;a href="https://kulissa.com/blog/why-we-named-her-maya?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;why we named her Maya&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Easy practice is a costume
&lt;/h2&gt;

&lt;p&gt;When a practice buyer waits politely for a pitch to finish, the rep feels skilled. When nothing stacks a second objection, the rep feels ready. When fluency wins over recovery, the session leaves people warmer and less prepared. That warmth is the costume. Live buyers tear it off.&lt;/p&gt;

&lt;p&gt;The name Maya is a reminder that the costume exists. Illusion is not a metaphor from a brand workshop. It is the failure mode of most sales training: content that looks complete, practice that never hurts, scores that cannot quote the transcript.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the coach is allowed to do
&lt;/h2&gt;

&lt;p&gt;Interrupt. Change temperature. Bring a competitor into the room after price seems handled. Not humiliate for sport. Hard but fair is the ridge. The public demo on the homepage uses promotional credits as stakes so the conversation has a reason to matter. Team product uses the customer's playbooks so the pressure is theirs, not a generic rubric.&lt;/p&gt;

&lt;p&gt;That is the same nerve whether someone meets Maya as gatekeeper or as coach across channels. One name. One standard. Many surfaces.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the name is not
&lt;/h2&gt;

&lt;p&gt;Not a catchphrase stuck on a cartoon. Not a replacement for managers. The rehearsal partner that shows up when the calendar will not, and the coach face when practice leaves the LMS.&lt;/p&gt;

&lt;p&gt;If that sounds like marketing, try &lt;a href="https://kulissa.com/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;kulissa.com&lt;/a&gt; and see whether a best opener survives the second interruption. Then read what we learned in &lt;a href="https://kulissa.com/blog/what-we-learned-building-maya?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;what we learned building Maya&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://kulissa.com/blog/why-we-named-her-maya?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Why we named her Maya&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://kulissa.com/blog/deliberate-practice-for-sales-teams?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Deliberate practice for sales teams, without turning enablement into a cult&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://kulissa.com/blog/what-we-learned-building-maya?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;What we learned building Maya&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Kulissa is a sales coach with live virtual customers for hiring, onboarding and training sales teams. See how it works at &lt;a href="https://kulissa.com/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;kulissa.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>salestraining</category>
      <category>ai</category>
      <category>career</category>
    </item>
    <item>
      <title>How to Run a Sales Demo That Doesn't Kill the Deal: Sales Tips and Discovery Questions for Founders and Engineers</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Sat, 07 Nov 2026 09:08:48 +0000</pubDate>
      <link>https://dev.to/kulissa/how-to-run-a-sales-demo-that-doesnt-kill-the-deal-sales-tips-and-discovery-questions-for-founders-8ej</link>
      <guid>https://dev.to/kulissa/how-to-run-a-sales-demo-that-doesnt-kill-the-deal-sales-tips-and-discovery-questions-for-founders-8ej</guid>
      <description>&lt;p&gt;If you're a founder, engineer or solutions engineer, the sales demo is where your instinct to show everything quietly kills deals. These sales tips turn a product tour into a demo that moves a buyer forward: shorter, built on discovery questions, and closed with a clear next step.&lt;/p&gt;

&lt;p&gt;The pattern is familiar. You built the thing, you know every screen, and the buyer said "can you show me how it works?" So you share your screen and walk through it, feature by feature, for 40 minutes. The buyer nods, says "this looks great, let me take it to the team", and then nothing happens.&lt;/p&gt;

&lt;p&gt;The product was fine. The demo answered questions the buyer never asked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sales tip 1: no discovery, no demo
&lt;/h2&gt;

&lt;p&gt;A demo without discovery is a guess. Before you share your screen, you need answers to three discovery questions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;"What made you take this call now?"&lt;/strong&gt; You're looking for the trigger: a new hire, a missed target, a painful process that broke last week.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"How do you handle this today, and what's annoying about it?"&lt;/strong&gt; This gives you the current workflow, in their words.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"If this worked, what would be different in three months?"&lt;/strong&gt; This gives you the outcome you'll demo toward.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the buyer wants to jump straight to the screen, say so honestly:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Happy to show you. So I don't waste 30 minutes on screens you don't care about, can I ask two quick questions first?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Almost nobody says no to that. And if the first call has to be a demo, keep it to ten minutes and spend the rest on discovery.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sales tip 2: demo the "after", not the menu
&lt;/h2&gt;

&lt;p&gt;Engineers organise demos the way the product is organised: settings, then dashboard, then reports. Buyers think in their own day.&lt;/p&gt;

&lt;p&gt;Build the demo as a story with three beats:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Their pain, in their words.&lt;/strong&gt; "You said onboarding a new rep takes about two months of shadowing calls."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The one workflow that fixes it.&lt;/strong&gt; Show only the path that solves that pain, start to finish.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The result.&lt;/strong&gt; End on the screen that shows the "after": the report, the finished output, the thing they would send their boss.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Everything else stays hidden unless they ask. A feature the buyer didn't ask about is a new question you just created, and new questions slow deals down.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sales tip 3: the 3-to-1 rule
&lt;/h2&gt;

&lt;p&gt;For every three minutes you click, give the buyer one minute to talk. Build check-ins into the script:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Is this close to how your team would actually do it?"&lt;/li&gt;
&lt;li&gt;"What would break if you rolled this out tomorrow?"&lt;/li&gt;
&lt;li&gt;"Who else would need to see this before it goes anywhere?"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last one is the most important discovery question of the whole demo. If the answer is "my CFO and our security lead", you just learned your real buying process, and you have a reason for the next meeting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sales tip 4: handle objections live, don't defend features
&lt;/h2&gt;

&lt;p&gt;Objections in a demo usually sound technical: "Does it integrate with X?" "What about edge case Y?" Engineers love these questions because they have answers. The trap is answering the literal question and missing the real one.&lt;/p&gt;

&lt;p&gt;Use a simple objection handling loop:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Acknowledge.&lt;/strong&gt; "Good question, a lot of teams ask that."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask why.&lt;/strong&gt; "What happens on your side if it doesn't?"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Answer the real concern.&lt;/strong&gt; Often "does it integrate with X" really means "I don't want another tool my team ignores."&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Example:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Buyer: "Does it export to our CRM?"&lt;br&gt;
You: "Not today, honestly. What would you want in the CRM, the scores or the call notes?"&lt;br&gt;
Buyer: "Mostly so managers see who practised."&lt;br&gt;
You: "Got it. Managers get that in a weekly summary. Would that cover it, or does it have to live in the CRM?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You didn't oversell, you didn't lose the thread, and you learned what actually matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sales tip 5: close the demo, not the deal
&lt;/h2&gt;

&lt;p&gt;Founders often end a demo with "So, any questions?" and then wait. That hands control back to the buyer, and the deal drifts.&lt;/p&gt;

&lt;p&gt;You don't need a hard close. You need a clear next step, booked before you hang up:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Based on what you said, the next step would be a 30-minute session with you and your sales manager, where we run this on one of your real scenarios. Does Tuesday or Thursday work better?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Concrete, small, dated. If they can't commit to a next step, that's information too: ask what's in the way.&lt;/p&gt;

&lt;h2&gt;
  
  
  A sales demo checklist you can copy
&lt;/h2&gt;

&lt;p&gt;Before the call:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] I know why they took the call now (trigger)&lt;/li&gt;
&lt;li&gt;[ ] I know their current workflow and its pain&lt;/li&gt;
&lt;li&gt;[ ] I picked one workflow to show, max two&lt;/li&gt;
&lt;li&gt;[ ] I prepared demo data that looks like their world, not "Test Company 1"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;During the call:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Recap their pain in their words before sharing my screen&lt;/li&gt;
&lt;li&gt;[ ] Check in at least every three minutes&lt;/li&gt;
&lt;li&gt;[ ] Ask "who else needs to see this?"&lt;/li&gt;
&lt;li&gt;[ ] Answer objections by asking why first&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;At the end:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Propose one specific next step with a date&lt;/li&gt;
&lt;li&gt;[ ] Send a three-line recap the same day: their pain, what they saw, the next step&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why demos feel hard for technical people
&lt;/h2&gt;

&lt;p&gt;The hard part of a demo isn't the product knowledge. It's staying calm when the buyer interrupts, asks the question you didn't prepare for, or says "we tried something like this and it didn't work." That's a sales skill, and like cold calling or discovery, it gets better with sales practice, not with reading about it.&lt;/p&gt;

&lt;p&gt;The fastest way to improve is to rehearse the uncomfortable parts out loud: the skeptical buyer, the "can you just show me pricing" interruption, the silence after your close. Run it with a colleague, record yourself, or use sales role play with virtual customers who push back like real ones.&lt;/p&gt;

&lt;p&gt;That's what we're building at Kulissa: a sales coach where you practise these conversations before the real call. If demos are the part of selling you dread, take a look at &lt;a href="https://kulissa.com" rel="noopener noreferrer"&gt;kulissa.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
      <category>startup</category>
      <category>career</category>
      <category>programming</category>
    </item>
    <item>
      <title>How Kulissa Started: Winning the Cursor Track at the RAISE Summit Hackathon With a Sales Role Play Prototype</title>
      <dc:creator>Kulissa</dc:creator>
      <pubDate>Fri, 06 Nov 2026 15:20:56 +0000</pubDate>
      <link>https://dev.to/kulissa/how-kulissa-started-winning-the-cursor-track-at-the-raise-summit-hackathon-with-a-sales-role-play-24i4</link>
      <guid>https://dev.to/kulissa/how-kulissa-started-winning-the-cursor-track-at-the-raise-summit-hackathon-with-a-sales-role-play-24i4</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://kulissa.com/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt; blog: &lt;a href="https://kulissa.com/blog/winning-the-cursor-track-at-raise-summit?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Winning the Cursor Track at RAISE: the walk through Paris that planted Kulissa&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;On 5 July 2026 our team won the Cursor Track at the RAISE Summit Hackathon in Paris. The press has already told the story better than I could at the time: El Español, El Correo Gallego and La Voz de Galicia all wrote about it, and the clippings sit on our &lt;a href="https://kulissa.com/about?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;about page&lt;/a&gt; and in the &lt;a href="https://kulissa.com/press?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;press kit&lt;/a&gt;. This post is the part I could not say in a phone interview. What it felt like, what it started, and who we need to thank.&lt;/p&gt;

&lt;h2&gt;
  
  
  Twenty-four hours, and then the brief changed
&lt;/h2&gt;

&lt;p&gt;The format was simple and unforgiving. Build a working product in 24 hours and demo it live to technical judges. No slides to hide behind. The hackathon was driven by Cursor and co-organized with Cerebral Valley, right before the RAISE Summit opened at the Carrousel du Louvre.&lt;/p&gt;

&lt;p&gt;We came in as five people under the name TN1: Ilias Ismanalijev, Ivan Glushenkov, Yanik Almer, Sergey Novikov and me. The first problem on the table was how to stop AI from hallucinating on design problems. We had a plan for that. Then, late in the event, the organizers changed the challenge. The plan was gone, the clock was not.&lt;/p&gt;

&lt;h2&gt;
  
  
  So we went for a walk
&lt;/h2&gt;

&lt;p&gt;Under pressure I remembered something my mother taught me about the Peripatetic philosophers: they taught and argued while walking. It sounded absurd to leave the room with hours left. We did it anyway and walked the streets of Paris.&lt;/p&gt;

&lt;p&gt;Somewhere on that walk the idea arrived. I studied Fine Arts and trained as an actor before I worked in technology, and acting is role-play: you rehearse, you get feedback, you repeat until it lands. Companies ask their people to perform the hardest conversations of their working lives, a skeptical buyer, a price objection, an angry customer, with almost no rehearsal. What if every team had a stage to rehearse on, with a partner who answers back?&lt;/p&gt;

&lt;p&gt;When we got back, Ilias had a first prototype running in about ten minutes. From there the team split the work the way it still splits today: Yanik on the real-time voice and avatar stack, Sergey on the scenario and evaluation engine, me on design and brand. We put a live demo in front of the judges, a company's own documents turned into a voice practice partner that adapts to what you say. We won the track.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it was empowering
&lt;/h2&gt;

&lt;p&gt;I want to be honest about this part. Winning did not make Kulissa a company. Customers do that, and that work is still ahead of us. But the win did something a pitch deck cannot. It told five people, in public, that the idea was worth our next years.&lt;/p&gt;

&lt;p&gt;For me personally it closed a loop. I left Santiago at 18 to study Fine Arts in Madrid and become an actor. For a long time I felt the theatre half and the technology half of my life did not talk to each other. In Paris they did. The name Kulissa comes from the theatre wings, the place where you prepare before you step on stage. That night the whole team was standing in them.&lt;/p&gt;

&lt;p&gt;It also gave us permission to be ambitious out loud. A jury of builders looked at something made in a day and took it seriously. That is a seed. Everything since has been watering it: the &lt;a href="https://kulissa.com/product?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;product&lt;/a&gt;, &lt;a href="https://kulissa.com/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Kulissa&lt;/a&gt;, the hiring, onboarding and training use cases, and the many rewrites in between.&lt;/p&gt;

&lt;h2&gt;
  
  
  Thank you, Cerebral Valley and Cursor
&lt;/h2&gt;

&lt;p&gt;None of this happens without the people who build the room.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cerebral Valley&lt;/strong&gt; invited us and co-organized the hackathon. Running an event where strangers ship real software in a day, and then changing the brief to see who can adapt, is a craft. It was the right test, and it shaped how we still work: when the plan breaks, go for a walk, then build.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cursor&lt;/strong&gt; drove the hackathon and put its name on our track. We built the first Kulissa prototype with Cursor, and we have kept building with it since. Their support did not stop at the award. The further help we have had from both teams during our product development has meant more to a young company than they probably know.&lt;/p&gt;

&lt;p&gt;We are very thankful to both.&lt;/p&gt;

&lt;h2&gt;
  
  
  What comes next
&lt;/h2&gt;

&lt;p&gt;The seed from Paris has grown, but the idea underneath has not changed. Most people walk into the hardest conversations of their working lives without ever having rehearsed them. Actors would never be asked to do that. We want every team to have the wings of a theatre: a place to prepare, to get it wrong safely, and to step on stage feeling ready. If you want to feel what we demoed that day, grown up a little, &lt;a href="https://kulissa.com/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;see how Kulissa works&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read next
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The press coverage and team photos: &lt;a href="https://kulissa.com/about?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;kulissa.com/about&lt;/a&gt; and &lt;a href="https://kulissa.com/press?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;kulissa.com/press&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Why we named her Maya: &lt;a href="https://kulissa.com/blog/why-we-named-her-maya?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;why we named her Maya&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Field notes from building her: &lt;a href="https://kulissa.com/blog/what-we-learned-building-maya?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;what we learned building Maya&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Related reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://kulissa.com/blog/what-we-learned-building-maya?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;What we learned building Maya&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://kulissa.com/blog/ai-sales-coach-hiring-onboarding-training?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Sales coach for hiring, onboarding, and continuous training&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://kulissa.com/blog/confidence-is-built-before-the-call?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;Confidence is built before the call&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Kulissa is a sales coach with live virtual customers for hiring, onboarding and training sales teams. See how it works at &lt;a href="https://kulissa.com/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=blog-repost" rel="noopener noreferrer"&gt;kulissa.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>startup</category>
      <category>ai</category>
      <category>sales</category>
      <category>salestraining</category>
    </item>
  </channel>
</rss>
