Selling B2B Software to the Buyers Who Actually Decide

    Short answer

    How to pick a sales model by price, find who to contact first, choose trial or demo, and get through security review

    Artem Smirnov
    Artem Smirnov

    Last updated · 12 min read

    Artem Smirnov in a dark suit against a charcoal studio backdrop, next to the line 'SELLING B2B SOFTWARE. Price picks the model, not you'

    Selling B2B software comes down to four decisions, made in this order:

    1. Pick the sales model your price forces. That means self-serve, a sales-assisted demo, or an enterprise deal that goes through procurement.
    2. Contact the person who owns the problem first. You find that person in your own closed deals, before you reach anyone else in the buying group.
    3. Choose a free trial or a demo. Use a trial when one user can see the value alone. Use a demo when the value depends on the buyer's data, their roles or their context.
    4. Open with relevant outbound on LinkedIn and email. Ask for a meeting. Leave the purchase for later.

    Behind all four sits a gate. Once your software touches company data, IT and security review the deal. If your answers are not ready, the deal waits.

    How is B2B software sales different from selling to consumers?

    B2B software sales is one company selling software to another. In B2C, one person spends their own money, often in minutes. In B2B, a group spends a company budget, and every person in that group can slow the decision down.

    The group is bigger than most founders expect. According to Forrester's 2024 State of Business Buying report, a typical buying decision involves 13 people inside the organization. The same report says 89% of purchases bring in at least two departments and 86% stall somewhere in the buying process (Forrester).

    That last number matters most. If 86% of purchases stall, a stall is normal, so plan your follow-up for it from the start.

    The stages are similar across most software companies, whatever the price:

    1. Prospecting. You find companies and people who match your past buyers.
    2. First conversation. A reply turns into a booked meeting.
    3. Discovery, then a demo or trial. The buyer checks whether the product fits their situation.
    4. Technical and security review. IT checks how your software handles their data.
    5. Proposal and procurement. Budget, terms and paperwork get settled.
    6. Close. The contract is signed.

    How long each stage takes, and who sits in it, depends mostly on one thing: your price. The wider plan around these stages is a B2B sales strategy.

    Which sales model fits your software's price?

    Price decides how much selling a buyer will put up with, and how many signatures the purchase needs. That makes it the first decision.

    No published study puts dollar lines between the bands in this table. SaaS Capital supports the direction only. It notes that product-led growth tends to have lower annual contract value than growth driven by a salesperson.

    Price levelSales motionWho you contact firstMain gateRole of outbound
    Low: one person can pay by card without asking anyoneSelf-serve or trial-ledThe end user who has the problemDoes that user reach value alone during the trial?Small. It can seed the first users in a niche, but sign-up flows carry the volume
    Mid: a monthly or annual plan that needs a budget owner's approvalSales-assisted, demo-ledThe head of the team that owns the problemThe budget owner's sign-offThe main source of first meetings
    High: an annual contract that goes through procurementEnterprise, several meetings and reviewsThe senior head of the function that owns the problemSecurity review, then procurementOpens the account. Relationship work carries it from there
    Services-heavy software work: custom development, implementation, IT consultingConsultative, proposal-ledThe executive who signed off on your last similar projectTrust in your team and agreement on scopeThe primary channel. Past projects carry the message

    The rows are defined by who has to approve the purchase, on purpose. A card limit at a 20-person startup is not the same as one at a bank. So find your row by asking who signed your last three deals. The number on your pricing page tells you less.

    Three decision rules fall out of the table:

    • If one person can buy on a card, do not build a sales team to sell it. Put the effort into the trial instead.
    • If the purchase needs a budget owner's sign-off, build a demo motion, and treat outbound as your main source of first meetings.
    • If it goes through procurement, plan for the security review from the first meeting.

    The clients my team works with usually sell deals from USD 10,000 upward, often reaching six or seven figures. That describes my client base only. The whole software market looks different.

    One old assumption needs to go: that a high price means in-person selling only. McKinsey's B2B Pulse Survey asked 3,942 decision makers in 13 countries in April 2024. Buyers split into roughly equal thirds. One third prefers in-person contact, one third prefers remote contact, and one third prefers digital self-serve. Buyers used an average of 10 interaction channels (McKinsey).

    69% of respondents said they would make a purchase of $500,000 or more remotely.

    So a large software contract can start with a LinkedIn message and close over video calls. What matters is getting the right person into the first meeting.

    Who in the buying group should you contact first?

    A software buying group usually holds five kinds of people:

    • The problem owner. The person whose team feels the pain your software removes.
    • The economic buyer. The person who controls the budget. In a smaller company this is often the problem owner too.
    • The technical evaluator. IT and security, who check how your software connects to their systems and handles their data.
    • Procurement. The team that handles contracts, terms and vendor onboarding at larger companies.
    • End users. The people who will open your product every day.

    How many of these show up, and how that number changes with company size, depends on how big a buying committee really is. This section covers one narrower thing, the first message.

    My answer always starts in the past. I start from the client's closed deals and ask one question about each: who approved it? Then I look at the companies already paying them and find lookalikes, and those lookalikes become the first target list.

    After that, I search by the titles that niche really uses, never a generic "manager" title. When the buyer is a software or IT company, that usually means CTO, Head of IT or Director of IT.

    If your software serves finance, HR or sales teams, the first contact is the head of that function instead, under whatever title it carries at that company size. Your own deal history tells you more than any template does.

    I also take Assistant, Manager and Associate out of the first list entirely. A bare "Manager" title tells you nothing about what that person decides. Those contacts eat sends and rarely move a deal. A weak list stays weak whatever the email says.

    The first-contact rules, in short:

    1. Problem owner first. They have the reason to take a meeting.
    2. Economic buyer next, or at the same time. Do this when your deals show the same person signs.
    3. Technical evaluator after the problem owner invites them in. A cold message to IT about a tool nobody asked for goes nowhere.
    4. Procurement never as the opener. They process a decision someone else has already made.

    One test settles every name on the list. If you cannot say what this person decides about your software, they come off.

    Should you offer a free trial or a demo?

    Buyers want different things at different moments. Gartner polled 632 B2B buyers over August and September 2024. It found that buyers prefer self-service tools when they are searching for general information and learning. When the task is judging whether a product fits their company's needs, they prefer input from a seller (Gartner).

    That gives you the trial-or-demo rule:

    • Use a free trial when a single user can see the value alone, in their first sessions, with no data integration and no one else's approval.
    • Use a demo when the value depends on the buyer's own data, workflows or several roles working together. In that case the fit question is the whole sale, and buyers want a person for that.
    • Use a demo first, then a scoped trial when the product needs integration but the buyer insists on testing. Agree in the demo what the trial must prove, and who will judge it.

    If you choose demos, the hard part is filling the calendar with the right people. That is a separate topic: booking more qualified SaaS demos.

    Then comes the gate. Once your software reads, stores or moves company data, IT and security get a say, as the technical evaluator in the buying group above.

    The list below is preparation advice. It is not campaign data. On the first call, ask the problem owner who reviews new vendors on the security side, and write that name down.

    To see what reviewers ask, look at a published template. The Cloud Security Alliance's CAIQ is a set of Yes/No questions a buyer can ask a cloud provider to check it against the Cloud Controls Matrix. CSA says the full version has 261 questions and the Lite version has 124. Have these ready before your first call with a large company:

    1. A one-page data handling summary. What data you collect, where it goes, how long you keep it, and how it is deleted.
    2. An access control description. Who on your side can see customer data, and how that access is granted and removed.
    3. Your hosting location. Where the data physically sits, in plain words.
    4. Answers to the standard questions. Write them once, keep them current, and reuse them on every questionnaire.
    5. A named owner on your side. One person who answers security questions within days, so they do not bounce around your team for weeks.

    Only describe controls you actually have, and never claim a certification you do not hold.

    If buyers prefer no rep, why does outbound still start software deals?

    The headline number looks like bad news for anyone selling by outreach. Two thirds of business buyers now say they would rather buy without a salesperson: 67% in Gartner's survey of 646 B2B buyers, which ran from August to September 2025 (Gartner). The previous year's survey put that figure at 61%.

    That earlier survey also holds the second half of the story: 73% of B2B buyers steer clear of vendors whose outreach is irrelevant to them (Gartner). Buyers reject irrelevant outreach. Relevant outreach still gets through.

    My clearest evidence is one month of outreach my team ran for a UK firm in software development and IT consulting. Between 17 April and 17 May 2023, it signed 6 contracts totaling GBP 928,800. The firm sells software services rather than a product, so it sits in the bottom row of the model table. Here is how email and LinkedIn contributed:

    ChannelPositive repliesMeetings bookedSales
    Cold email41132
    LinkedIn outreach62183

    Between them, the two channels booked 31 meetings and closed 5 of the 6 contracts.

    Read the split before you copy it. LinkedIn produced more replies, more meetings and more sales than cold email that month, though the case data does not show how many messages each channel sent. And both channels produced signed contracts within the same month. It is one firm and one month, so read it as one example.

    A technology client of ours went from zero qualified calls to 40+ a month inside 90 days. A German IT company booked 84 sales meetings in one month. That was 3 to 5 a day.

    What should the first outbound touch to a software buyer look like?

    Start on LinkedIn. Send the email after a LinkedIn touch, so the buyer has already seen a name and a face when it lands.

    Plan for 5 or 6 touches at minimum, across more than one channel where you can. One or two messages rarely start a conversation with a senior buyer. Usually the third follow-up performs best, provided you leave real gaps of time between touches.

    Ask for a meeting in the first message. Nobody buys software from a stranger's email. They buy after they audit you, and a busy department head might still give 20 minutes to someone who clearly understands their problem.

    Here is a made-up example of a first email to a VP Engineering, sent after a LinkedIn connection. Every name and result in it is invented, so do not copy the proof line:

    Subject: Regression testing on your mobile releases

    Hi Marta, I saw your team ships the mobile app every two weeks. We build test automation for engineering teams of 30 to 80 people, and one team that size now runs its regression suite overnight instead of over two days. If regression time is on your list this quarter, would a 20-minute call next Tuesday or Wednesday be useful? If someone else owns QA tooling, who should I talk to?

    It names one problem and asks for one small meeting. Its last question gives a wrong-person reply somewhere to go: the real owner. The proof in your version must be your own: a real customer, a real result.

    Then set the right goal. I tell founders to stop aiming for "10 booked demos this month" and start 50+ conversations. Conversations come first. Demos come out of conversations. A target that only counts demos pushes people to pitch too early.

    Content has a place here too, behind the outreach. Posts and case studies give a buyer something to find while looking into you once your message has landed. Content gets attention. Direct messages get deals.

    What happens after the demo is booked?

    Booking a meeting and closing a deal are two different jobs, and I say this to every software founder. A full calendar proves the targeting and the message work. It says nothing about whether your team can turn a demo into a signed contract.

    Look back at the UK firm above: 31 meetings, 5 contracts. My team controls the booking. The demo and the follow-up decide everything after it.

    With a weak close rate today, extra meetings will only make it worse. New volume brings colder buyers and more skeptics, and a demo process that already leaks with your warmest leads will leak faster with them. Fix the demo and the follow-up first. Then add meetings.

    A booked call counts for little before a deal closes, and the numbers behind that show why.

    I book the meetings over email and LinkedIn and then hand over: the demo and the close belong to your people.

    If you do one thing this week, open your CRM and write down who signed each software deal you closed in the past year, with their title and the deal value. That list decides your sales model, your first contact and your first message.

    If you sell software and cannot tell which sales model your deal size supports, book a call and bring your last closed deals.

    Questions founders ask about selling B2B software

    How risky is B2B sales for a small software company?

    The risk sits in concentration. A few large deals carry the year, and each one can stall for reasons outside your control. Outbound lowers that risk only when the offer already sells to a few paying customers. Without that proof, more outreach spreads an unclear offer faster, so sharpen the offer before you add volume.

    Can a small software team sell without hiring SDRs?

    Yes, if someone owns two jobs. Someone must read and answer every reply quickly, because a missed reply wastes everything it cost to produce. We put one person in charge of the reply inbox so nothing gets missed. Every lead also needs to live in a CRM, and which CRM you use matters far less than using one.

    How long until an enterprise software deal closes?

    Much longer than the booking does. Meetings can start within weeks of a campaign launching, while contracts from those meetings often arrive months later. In high-ticket B2B, I expect some meetings that produce nothing at the time to become signed work 9 to 12 months later. Judge a campaign on pipeline and conversations first, and on signed contracts over the full cycle.

    Do buyers look up whoever runs the demo?

    Whoever runs the demo gets checked online between the booking and the meeting. A buyer who finds an empty profile starts doubting before the call even begins. A good message cannot rescue an empty profile, so optimize the LinkedIn profile of everyone involved in your sales process, not only the founder's.

    Want to see what we would build for your company?

    I am Artem Smirnov. I help established B2B companies build and run the go-to-market system behind their pipeline, from outbound to AI search visibility. Book a call and we will see what fits yours.

    Artem Smirnov
    Artem Smirnov

    I help established B2B companies build and run their go-to-market systems. 9 years in outbound, 10,000+ campaigns.