Become an SDR/BDR · Beginner · ~8 hours
Technology Sales Fundamentals
Learn how technology is bought and sold, the roles involved and the language used by modern B2B sales teams.
Status: Catalogue ready. This lesson version is available in review mode while subject-matter, accessibility and assessment checks are completed.
How a B2B technology sale works
The people and motion in a B2B sales team
By the end of this lesson
- Describe the difference between an SDR or BDR, an Account Executive and a customer-facing specialist.
- Explain why a B2B technology purchase involves several people and several decisions.
- Use accurate, non-promissory sales language when describing a potential opportunity.
A sale is a process of helping someone decide
Technology sales is often described as moving a prospect through a funnel, but that picture can hide the human work involved. A business is not buying a feature in isolation. People are trying to understand a problem, compare options, estimate risk, secure internal agreement and decide whether a change is worth the cost and effort. A responsible sales professional helps make that decision clearer. They do not create certainty where evidence is missing. In a business-to-business, or B2B, sale, the first person who responds may not be the person who owns the budget. The person who feels the problem may not control procurement. A technical colleague may need to check whether the product can integrate with existing systems. A finance or security reviewer may need to approve the commercial and operational risk. This is why good sales work is less about delivering one perfect pitch and more about finding out who is affected, what they need to decide and what evidence would help. An SDR or BDR usually creates and qualifies early conversations. The titles overlap between employers, but the broad work can include researching accounts, writing relevant outreach, listening for a possible fit and arranging a useful next conversation. An Account Executive often owns the wider opportunity, including discovery, demonstrations, proposals, commercial discussion and coordination with other teams. A sales engineer or solutions consultant may explore technical requirements and explain how a solution could work. Customer success, implementation, legal, finance and support may become important as the conversation continues. None of these roles should imply that a prospect is guaranteed to buy or that a learner is guaranteed to succeed in the role. A useful handover records what was actually heard, what was inferred and what still needs confirmation. This distinction protects the buyer and makes the next conversation more effective. For example, “the operations lead said reporting takes two days each month” is evidence from a conversation. “The company needs our dashboard” is an interpretation that still needs testing. The quality of a sales process is therefore visible in the questions it asks and the decisions it makes. A team may decide not to pursue an opportunity because the problem is not urgent, the product is not a fit or the buyer cannot access the required information. That is not automatically failure. It may save everyone time and prevent an unsuitable purchase. Ethical selling treats a clear no, a later review and a referral to a better option as legitimate outcomes.
Roles are connected by evidence
A sales process becomes easier to understand when each handoff has a purpose. Early outreach should earn a conversation, not force a buying decision. Discovery should improve understanding, not collect impressive-sounding phrases. A demonstration should make a relevant workflow tangible, not show every button in a product. A proposal should state assumptions and next steps, not disguise uncertainty in polished language. This evidence-led approach also explains why CRM hygiene matters. A CRM record is not simply an administrative task; it is a shared memory of the relationship. A colleague reading it should be able to tell who was involved, what problem was discussed, what timing was mentioned, what has been agreed and what remains unverified. Personal opinions or sensitive details that are irrelevant to the business process do not belong there. A beginner can practise this by writing a short “known, assumed, next” note after a fictional conversation. Known facts are statements the buyer made or information from an approved source. Assumptions are interpretations that may be useful but need confirmation. Next steps are actions that someone has agreed to take, with an owner and a date where appropriate. The format is simple, but it makes sales thinking visible and reduces the temptation to treat enthusiasm as qualification.
Workplace example
Northstar Analytics sells a reporting platform to mid-sized professional-services firms. An operations manager says monthly reporting takes two days and that the finance director is concerned about inconsistent figures. An SDR should record those statements, ask who else needs to be involved and agree whether a discovery meeting would be useful. They should not record that Northstar is definitely buying or that the finance director supports the project before either is confirmed.
Try this walkthrough
- 1.Write the buyer's stated problem in their own terms, without adding a product claim.
- 2.List the people who may experience, approve, implement or fund a change.
- 3.Separate direct evidence from assumptions and identify one question that would test the most important assumption.
- 4.Write one low-pressure next step that the buyer can accept, decline or amend.
Watch for these traps
- Treating a job title as proof that someone is the final decision-maker.
- Writing a handover from memory and presenting interpretation as fact.
- Measuring a good conversation only by whether it produced a meeting.
- Using urgency, scarcity or certainty that has not been supported by evidence.
Knowledge check
Choose the response you think is strongest. These checks are practice until the course version has passed subject-matter review; graded attempts will be handled server-side.
For the reviewed pilot, answers are checked on the server. This draft result is not yet added to your official learning record.
Practice studio
Make a decision. Test a response. Leave evidence.
Use the case from this lesson to practise judgement without creating a score or changing your course record.
Scenario decision
Northstar Analytics sells a reporting platform to mid-sized professional-services firms. An operations manager says monthly reporting takes two days and that the finance directo…
Choose a response
Branching roleplay
A colleague asks you to move this situation forward. What do you say next?
Evidence workspace
Draft a short known / assumed / next note from the fictional case. Use fictional details only.
This is a session-only practice draft. It is not saved, graded or added to your learning record. Never enter real personal or confidential information.
Practical assignment
Create a one-page role map for the Northstar Analytics case. Include the buyer problem, four possible stakeholders, three known facts, three assumptions and a proposed next step. Label every inference clearly.
Pass this lesson's knowledge check before recording it as complete.
Final assessment
Show what you can apply
Complete the final knowledge check after the lessons. Your answers are graded on the server and a certificate is issued only when the course requirements are verified.
Start this course before taking the final assessment.
Portfolio evidence
Practical portfolio project
Work through a simulated B2B technology sale from account research and first contact to discovery, qualification and next steps.
Turn the practical project into a bounded evidence record. Save a draft while you work, then submit it for human review when it is ready.
Sign in to save practical evidence. Sign in