Topic 1 — What is Tech Sales?

Goal: Understand what tech sales is and why it's a powerful career entry point.

Lesson 1.1 — The call that doesn't sound like selling

Dario Vance has a regional trucking company on the line. The Operations Director, Marcus Thorne, runs forty trucks across three states and he is tired — you can hear it. Dario could launch into the pitch. Instead he asks: "When a driver's route gets re-planned mid-day, who eats the cost — you, the customer, or the driver's overtime?"

There's a pause. Then Marcus starts talking, and he doesn't stop for four minutes.

Dario sells for Brightwheel Freight, a B2B software company whose product helps mid-size trucking and logistics firms plan routes and cut fuel costs. What he just did is the whole job in miniature. He didn't describe a feature. He found the place where Marcus's day hurts and let Marcus describe it out loud.

That approach has a name. Consultative selling means understanding a customer's real problem and helping them decide whether your product actually fits — rather than pushing them toward a "yes." The salesperson acts more like a guide than a closer-of-doors.

Old-style selling talks. Consultative selling asks, then listens for where it hurts.

This is the part that surprises career-changers most. The pushy, fast-talking stereotype is not what good tech sales looks like in 2026. The best reps sound like a smart colleague who happens to know one product extremely well. If the product won't help Marcus, a good rep says so, because a bad-fit customer churns in three months and torches your reputation. Helping is the strategy, not the soft option.

Lesson 1.2 — Why it's sold through conversations, not a "buy" button

You buy headphones with one click. Nobody calls you first.

So why does Brightwheel need Dario, and Renske, and a sales engineer, and weeks of conversation to sell a piece of software?

Because of what kind of software it is. Most tech sales is B2B — business-to-business — meaning Brightwheel sells to other companies, not to individual consumers. And most of what gets sold is SaaS: Software as a Service, software you rent by subscription (usually billed monthly or yearly) instead of buying once on a disc.

Put those together and the reason for the conversation becomes obvious. Marcus isn't spending $40 of his own money. He's signing his company up for a tool that ten dispatchers will use every day, that has to plug into systems they already run, and that might cost tens of thousands of dollars a year. He can't evaluate that from a product page, and he has a boss he'll have to justify the decision to.

So the software gets sold the way expensive, high-stakes things get sold: through conversations, live demonstrations, and trust built up over several touches. A "buy now" button works for headphones, not for a decision a whole operations team has to live with. That gap is exactly why the salesperson exists — someone has to help a real, busy human figure out if it's the right tool.

Lesson 1.3 — The role you'd actually start in

Here's the part that trips people up. They picture "sales" and imagine themselves closing the big deal, shaking hands, signing the contract. That's a real job. It is almost never the first one.

Watch who does what on Marcus's deal. Dario found Marcus, started the conversation, and booked the first meeting. Then he handed Marcus to Renske Bauer, a Senior Account Executive, who runs the actual sales meetings and closes the contract. Two different jobs.

Dario is an SDR — Sales Development Representative. SDRs find and start conversations and book qualified meetings for closers. They do not close deals themselves. There's a sibling title, BDR — Business Development Representative, that means almost the same thing; the rough convention is that SDRs often handle inbound leads (people who already raised a hand — downloaded a guide, asked for a demo) while BDRs often handle outbound (cold prospects who've never heard of you). Many companies use the two words interchangeably, so read the job description, not the acronym.

	SDR / BDR (entry)	Account Executive (AE)
Main job	find and start conversations	run meetings and close deals
Owns	booked qualified meetings	signed revenue
On Marcus's deal	Dario	Renske

The AE is who an SDR usually becomes after a year or two of hitting target. So the entry role is the on-ramp, not a consolation prize: the skills that make you good at it — research, outreach, qualifying — are the same ones the AE job is built on. You learn the product, the customers, and the craft while someone more senior carries the close.

Lesson 1.4 — How the money actually works

Owen Driscoll, the sales manager who runs Brightwheel's SDR team, says one number to every nervous candidate in the final interview: "Your base is yours no matter what. The rest, you build."

That sentence is the entire pay model. Tech sales runs on base salary plus commission. The base is fixed money that lands every paycheck. The commission is extra money you earn by hitting targets — for an SDR, usually by booking enough qualified meetings. Add them together at full performance and you get the number job ads advertise: OTE, on-target earnings — what you make if you hit 100% of quota.

For US SDRs in 2025, the rough benchmarks look like this:

• Base: around $60k — money you get regardless.
• OTE: around $85k — base plus commission, if you hit target.

The gap between those two numbers — roughly $25k — is the part your results control. Sell more, earn more. That's the appeal and the pressure in the same sentence.

Two honest caveats Owen always adds. OTE is the target, not a guarantee; in any given year only about half of reps fully hit quota, so plan around the base and treat commission as upside you're chasing. And these are US tech-market figures — they shift with city, industry, and company.

Still, line it up against other ways into tech with no degree and no coding, and the math is striking: a real shot at mid-five-figures in year one, climbing fast for people who perform.

Lesson 1.5 — Hired for who you are, paid for what you can take

Dario doesn't have a computer science degree. He doesn't have a business degree either. He managed a coffee shop for three years. Owen hired him anyway — and if you ask Owen why, he won't mention a résumé line.

Tech sales is one of the few tech-adjacent jobs hired for traits over credentials. The four that matter most:

• Drive — you set your own pace, and the targets don't chase themselves.
• Communication — you'll talk and write to strangers all day.
• Coachability — you'll get feedback constantly and have to use it fast.
• Resilience — and this one is the job.

That last word deserves a hard look, because it's where the romance meets reality. Sales is a numbers game, and the numbers are humbling. The benchmarks aren't a secret:

• Cold emails get a reply roughly 3–6% of the time.
• Cold calls connect with a live human roughly 8–12% of the time.

Read that again. The overwhelming majority of Dario's outreach gets ignored. That is not Dario failing — that is the normal, expected baseline that every quota is built on top of. The job assumes most doors don't open, and is designed around volume so that the ones that do open add up to a great month.

Rejection isn't the exception in this job. It's the raw material. You're paid to keep going after the ninth "no" because the tenth contact books the meeting.

This is why coachability and resilience beat a polished degree. The product, the script, the industry are all teachable in weeks. The ability to dial a stranger right after one hung up on you, and sound just as warm, is the rare thing — and why a former barista with grit out-earns a credentialed candidate who wilts at "no."

Worked example — A Tuesday with Dario

It's 8:50 a.m. Dario opens his list of target accounts: mid-size carriers in the Midwest with aging route-planning systems. This is prospecting — researching who to contact and finding the right human inside each company. By 9:15 he has fifteen names, one of them Marcus Thorne at a regional carrier.

Morning is outreach. He sends a batch of personalized emails, then starts dialing. He runs about forty-five dials today. Most go to voicemail or nowhere — that 8–12% connect rate, live and in person. Between calls he fires off LinkedIn notes. Around 11:00 a phone actually picks up, and it's a quick, sharp qualifying conversation: does this company even have the problem Brightwheel solves, and is this person involved in fixing it? Two of today's calls are a genuine fit.

Marcus replies to the email in the afternoon — curious, a little skeptical. Dario doesn't pitch. He asks the route-replanning question from Lesson 1.1, listens, and books a meeting for Thursday with Renske, the AE who'll run it. One meeting booked. He needs roughly twenty qualified meetings this month to hit quota, so he logs it and keeps moving.

Late afternoon is follow-up — the unglamorous engine of the whole job. He pings six people who went quiet last week, because most deals start only after several touches, not the first. He ends the day having been ignored far more than answered, with one solid meeting on the board and a pipeline that's a little fuller than this morning. That is a good day. String enough of them together and you hit OTE.