Selling IT Solutions Backwards: How to Lose a Deal in 40 Hours (or Win It in 45 Minutes)

Here is the play I watched for years inside a big copier dealer, and still watch every week from the other side of the table. A rep gets a sniff of an IT opportunity. Maybe it started as a copier call and the customer mentioned the server closet that sounds like a hair dryer. The rep gets excited, runs a decent discovery, and then does the thing every one of us was taught to do. They bring in the engineer. The engineer does a site survey, counts switch ports, opens Visio, which is an engineer’s love language, builds a beautiful three-layer diagram, prices out the cloud migration and the document management licenses, and forty engineering hours later the rep emails a forty-two-page proposal, because nothing says “we listened” like forty-two pages. Then nothing. Then, two weeks after that, the email that makes your engineer want to quit: “Thanks for this. Can you send over the design so we can get a second opinion?”

If that made you wince, you already understand the problem with selling IT solutions. It is not that your reps cannot sell. It is not that your engineers cannot design. It is that the order is backwards. We do the most expensive work in the deal, the engineering, before the customer has committed to anything, and then we “present” a finished design and hope they like it, which is also how I approach gift giving, with similar results. I want to make the case that the presentation belongs before the engineer, not after. Get the order right and you can win the deal in a forty-five-minute meeting. Get it wrong and you can lose it over forty hours, slowly, with diagrams. Flip the sequence and almost everything else about selling IT solutions gets easier, cheaper, and a lot less heartbreaking for the person holding the Visio license.

The Way Most of Us Are Selling IT Solutions (and Why Your Engineer Is Quietly Furious)

Pull up almost any MSP sales process guide and you will find the same five steps in the same order. Erick Simpson’s widely shared sales engineering process lays it out: discovery, design, proposal creation, review, and then, in fifth place, presentation. The presales software crowd agrees, and their pitch is that you should scope and quote faster. Nobody in the category is asking whether you should scope later.

I have watched this deal play out more times than I can count, and the details barely change. A growing professional services firm. A server older than the iPhone. A managing partner who says “we need to modernize” without being prompted. So we do what you do. The best engineer gets pulled in and spends the better part of a work week on it. Site survey, switch counts, a migration plan, document management mapped to every department, a diagram you could have framed. The proposal lands somewhere north of forty pages and everybody is proud of it. Then, three weeks later, the thank-you call. It was incredibly thorough. Their current IT guy looked it over and can do “basically the same thing” for less. Our design. Their guy. If you have been in this channel for any length of time you have lived some version of that, and you remember exactly how your engineer looked at you afterward.

Let me put a number on those forty hours. Consensus’ 2025 presales workload report found that 70% of deals require presales support and 35% of demos are unqualified or underqualified. Loopio’s 2026 benchmark says teams now spend 33 hours per RFP and win 39% of them. Now do the dealer math. Kaseya’s MSP benchmark puts the dominant break-fix rate at $101 to $200 an hour. Forty hours of unpaid design on a deal that was never really a deal is four to eight thousand dollars of billable capacity you just donated, and nobody even sent you a tote bag. Do that twice a month and you have a half-time engineer whose real job title is “free consultant to the competition.” They do not put that on LinkedIn, but they should.

This is hitting both halves of my audience at once. On the dealer side, The Cannata Report’s 2025 survey found that 47% of office technology dealers now offer managed IT, but it was only 7.6% of dealer revenue, and the same report quotes dealers saying the difficulties of launching it outweigh the gains, which is the office technology industry’s polite way of saying “ouch.” That is a small base and a hard start, but look at the other number in the same survey: among dealers who have it, 73% reported a 28.8% average revenue increase. It is growing, just painfully. On the MSP and VAR side, Kaseya’s 2026 State of the MSP report has 71% naming new customer acquisition as their biggest challenge, and the share struggling to quickly demonstrate value nearly doubled year over year, from 10% to 19%. Read that last one again. Demonstrating value quickly is a presentation problem. It is not an engineering problem. You cannot Visio your way out of it.

And here is the 2026 wrinkle that makes all of this urgent. Your buyer now shows up with a design. Gartner’s March 2026 survey found 45% of B2B buyers used AI during a recent purchase and 67% would prefer a rep-free experience. Two months later Gartner found that 69% of buyers want a sales rep to validate the AI-generated insights they brought with them. Everybody asked ChatGPT to design their network this year the same way everybody asked it to turn their dog into a Pixar character. So your engineer’s free design is now competing with a free robot design, and the robot does not bill hourly, does not take lunch, and has never once asked for a second opinion on itself. You will not win that by out-diagramming the robot. It has read every design guide ever written. You have read the ones with pictures. You win by being the human who gets the room to agree on what the outcome actually is.

Why the Bowtie Funnel Puts Presenting Before Proposing

When we built the Bowtie Funnel at revenueify, we did not have to debate where the presentation goes. We had spent years inside the industry watching the other order fail and paying for it by the hour, so the sequence was settled before the first whiteboard marker came out. It still looks odd to anyone trained the traditional way. Stage three is qualifying and interviewing the opportunity. Stage four is presenting solutions and gaining commitment. Stage five, only after that, is overcoming objections, negotiating, and closing, which is where the proposal lives. The knot in the middle of the bowtie is the moment of commitment, and the presentation is how you tie it, in about forty-five minutes. The proposal is what you hand someone who has already said yes. Handing it to someone who has not said yes is not a proposal. It is a brochure with your margins in it.

I need you to accept that a presentation and a proposal are two different things, because most of the channel uses the words interchangeably. A proposal is a document. It has part numbers, quantities, labor hours, a lease rate, and terms, and it is roughly as persuasive as a phone bill. It is the output of engineering. A presentation is a conversation, and in our world it fits on one slide: the customer’s business objectives in their own words, the roadblocks standing in the way, a picture of what their world looks like after, and how they will know it worked. There is no network diagram on it. There is no pricing grid on it. If there is a pricing grid on it, you have made a proposal with fewer pages, and I appreciate the effort, but no. It exists to get agreement, not to describe a product.

If you need proof that the decision happens before the document, look at Proposify’s 2026 data across 742,000 proposals. Buyers close an average of 2.5 days after first opening a winning proposal, and winning proposals are shorter than losing ones, eleven pages versus thirteen. Nobody reads forty pages and changes their mind in two and a half days. Nobody reads forty pages, period. They made the decision in the room with you, or they did not, and the document just confirmed it. That is why we put it last, and it is the whole argument for selling IT solutions in the order Customer Focused Selling® sequences it.

Selling IT Solutions Starts With Discovery, and Discovery Is Not Where You Sell

I have to say this plainly because copier reps, and I was one, are physically incapable of hearing a problem without quoting a fix for it. Tell a copier rep your back hurts and you will get a quote for a chair. Discovery is not where you sell. Discovery is where you listen. We teach it as the F.I.N.D. Interview System®, but forget the acronym for a minute, because the heart of it is one question: what business issues is this customer actually living with? Not what hardware is old. Not how many users they have. Every rep already asks how many users they have. It is the “how about this weather” of IT discovery. What is broken in the business, what is it costing them, and what happens if nothing changes?

Here is what that sounds like across the five things a dealer or a VAR actually sells. For networking: “When the network slows down, what stops in the building?” For cloud: “What would it mean for the business if that server closet was no longer a single point of failure?” For servers: “What did the last outage cost you in hours, and who had to stay late?” For document management: “How much of your team’s week goes to hunting for documents across email, the share drive, and the filing cabinets?” For workflow: “Walk me through what happens to an invoice from the moment it hits the mailbox to the moment it gets paid.” If that last answer takes more than four minutes and involves a physical inbox, congratulations, you have found a business issue. Every one of those questions is open-ended on purpose. You are handing the customer a microphone and a blank canvas, and then, this is the hard part, you are shutting up.

The discipline is in how you finish. Open broad, dig in, and then close every business issue with a yes-or-no confirmation: “So if your team got back five hours a week that they currently spend chasing documents, that would be worth solving this year. Is that fair?” Miranda Priestly, back on screens this year, would simply say “That’s all.” A close-ended question at the end of a business issue does two jobs. It confirms you heard it right, and it gets the customer to say out loud that the problem matters. A business issue the customer has confirmed out loud is the raw material of your presentation. A business issue you assumed is a guess with a part number on it.

This is also where most “no decision” losses are born. Dixon and McKenna’s study of 2.5 million sales conversations found 40% to 60% of deals are lost to customers who intended to buy and never acted, and Ebsta’s benchmark has reps blaming indecision for 61% of lost deals. Indecision is almost never about the switch model. Nobody has ever lain awake at night torn between two access points. It is the business issue that never got confirmed, so nobody inside the account felt enough urgency to move. Gartner found that 74% of buying teams show unhealthy conflict during the decision, and teams that reach consensus are two and a half times more likely to call it a high-quality deal. You build that consensus in discovery and you cash it at the presentation.

The Presentation Stage Is Where Selling IT Solutions Actually Happens

Now you sell. This is the stage I wish I could go back and teach my younger self, because I spent years thinking the presentation was where you showed the customer your stuff. It is not. The presentation is where you tell the customer their own story back to them, and then invite them to finish it with you. We call the tool OBJECTIVELens®. You can call it one slide. One. Not one slide plus an appendix. It has four boxes: what they are trying to achieve, what is standing in their way, what the solution looks like from where they sit, and how we will both know it worked. Every word in the first two boxes came out of their mouth during discovery. If you cannot fill those boxes in the customer’s language, you are not ready to present, and you are definitely not ready to engineer.

The magic is that the customer paints with you. You put up the outcome and say, “Here is what I heard. Here is what I think it looks like when it is fixed. What did I get wrong?” They correct it. They add the branch office you did not know about. They tell you the CFO will never approve a capital purchase this year, which is a conversation I covered in the IT financing playbook and will not repeat here, because I only get to write that one once. Every correction is a gift, because it is happening on a slide you can change in thirty seconds instead of in a design your engineer would need a week to rework. You are co-authoring the ideal solution before it exists. People defend what they helped build. Nobody has ever gone to bat for a diagram they were handed.

Then you ask for the commitment, out loud, before anyone opens Visio: “If we can deliver this, inside this budget range, by this date, are you ready to move forward with us?” Three things can happen and all of them are good. They say yes, and now your engineer designs against an agreed outcome for a customer who is already emotionally signed. They say “yes, but,” and you change the picture right there. Or they say no, and you just lost a deal in forty-five minutes instead of forty hours. That is the whole title of this article, and it is the best trade in the channel. Losing early is a win. Ask any engineer who has built a full design for a customer that was always going to buy from the incumbent. Actually, do not ask them. They are still upset. This is also what the 6sense data is really about. Their 2025 buyer study found 94% of buying groups had ranked their preferred vendor before first contact, and that early favorite still wins 80% of the time. The presentation is how you become the favorite before a proposal exists. A proposal cannot make you the favorite. It can only confirm that you already were.

One more thing, and I will keep it short because we have a whole page on it: this is where the engineer finally walks in, and their job in the room is to validate the fit, not to run the meeting. You will know if your engineer is running the meeting, because it will be forty minutes in and someone will have said “VLAN” to a CFO. A rep who owns the outcome slide can sell an IT roadmap they did not personally engineer. That sentence is the entire reason a copier rep can sell managed IT at all.

The Proposal Stage Is a Formality, If You Did the Work

Now the engineer designs, and they design against four boxes the customer already agreed to, which is a completely different assignment than “go figure out what they might want.” The proposal that comes out of that is a confirmation. Its job is to prove that the pieces and parts we are proposing, the switches and access points, the migration plan, the server or the cloud tenant, the document management licenses, the workflow build, actually deliver the success criteria on the slide. It is an engineering document checking itself against a business agreement. It is not a persuasion document. The persuading is over. If the proposal has to do the persuading, it is not a proposal. It is a Hail Mary with a signature line.

Which is why I will say the thing that makes sales managers nervous: if you are doing this right, your proposal win rate should be high, and you should almost never have to modify a proposal. Spain did not win the World Cup by redrawing the formation at halftime of the final. They ground out a 1-0 in extra time on a plan they had been running the whole tournament, and the final only confirmed what was already true. If you find yourself on revision three of a proposal, that is not a pricing problem. That is a presentation you skipped. Revision three is where margin goes to die. The customer is using your proposal to do the thinking you should have done together in a forty-five-minute meeting, and every revision is another block of hours your engineer is paying for. Loopio’s data says only 75% of teams even run a go/no-go process on RFPs, and that number dropped this year. The presentation, done right, is the best go/no-go process in the business, because the customer runs it for you, for free, which is the only free thing in this article I am in favor of.

Selling IT Solutions Is the Same Play for Copier Dealers and IT VARs

I wrote this for two readers who think they have different problems. The copier dealer is trying to grow an IT business and keeps watching reps who can close an MFP deal in their sleep freeze the moment the word “server” comes up, like a deer that has just been asked about subnet masks. The IT VAR or MSP already sells this stuff and wants a better win rate and a lower cost of sales, which in practice means fewer engineering hours on deals that never close. Same play for both of you. Lead with the business issue. Present the outcome before you engineer it. Gain the commitment. Then, and only then, let the engineer do what they do.

That is the exact order we teach in copier sales training for dealers selling past the box, and in IT VAR sales training for resellers who are tired of quoting first and praying second. Same method. Same one slide. Different room. If you take one thing from this, take the sequence: discover, present, commit, engineer, propose. Forty-five minutes before the forty hours, never the other way around. You have been selling IT solutions backwards, and the fix does not require a new engineer, a new quoting tool, or a new vendor. It requires moving one meeting. I realize that is a less satisfying answer than buying software. It is also cheaper.