PreSales FAQ

A presales consultant helps sales win deals. You find out what the customer really needs and show how the product solves it. The job covers discovery, demos, proofs of concept, RFP answers and the technical side of the business case. You are the bridge between the customer's problem and the product.

Link to this question

Both. You need enough technical depth to earn the trust of the customer's experts. You also need enough business sense to talk value with their managers. Most people come from consulting, support, engineering or the business domain itself.

Link to this question

Listening comes first. Then clear storytelling, solid product knowledge and the courage to say no to a bad deal. Writing matters more than most people think. Your summaries get read by people who never met you.

Link to this question

Help the customer decide well, even if the answer is not your product. Stay curious, stay honest and put the customer's problem before your feature list.

Link to this question

Build on what you already know, such as a product, an industry or a technical field. Practise presenting, learn discovery and ask to shadow presales colleagues on real deals.

Link to this question

Many paths. Some people lead a presales team. Others move into product management, sales, customer success or consulting. Presales teaches you the product, the market and the customer at once. That makes you useful in almost any of these roles.

Link to this question

SaaS customers can leave at every renewal. So the deal has to fit from day one, not only look good in the demo. Presales makes sure the promise matches what the product really does.

Link to this question

The buying journey is how the customer decides, from first doubt to renewal. The selling journey is what your team does in each of those steps. Good presales starts from the buying journey and fits the selling steps to it.

Link to this question

Early, but only once the deal is qualified. Join too late and you demo against requirements someone else shaped. Join too early and you spend your time on deals that never close.

Link to this question

Sales owns the relationship, the forecast and the commercial terms. Presales owns the solution fit, the demo and the technical answers. Write it down in a simple RACI matrix, so nobody drops a task or does it twice.

Link to this question

Each persona buys for a different reason. The CFO wants numbers, the IT lead wants low risk and the user wants an easier day. Find out who is in the room before the meeting. Then show each of them the part they care about.

Link to this question

The customer's goals, current processes, systems, pains and how they will decide. Listen more than you talk. Write down what you learn in an Opportunity Scoping Document.

Link to this question

Sales discovery asks why the customer wants to change and whether the deal is real. Functional and technical discovery asks how they work today and what the solution must do. Sales usually leads the first. Presales leads the second.

Link to this question

All three are qualification frameworks. BANT is a quick first check of budget, authority, need and timeline. CHAMP starts with the customer's challenges. MEDDIC adds metrics, decision criteria, the decision process and a champion for complex deals.

Link to this question

The OSD is your discovery summary. It lists the customer's goals, pains, processes, systems and open questions in one place. Sales, presales and later the delivery team all work from it. Send it to the customer too, so they can correct you early.

Link to this question

FTQ stands for functional and technical qualification. It checks whether your solution truly fits the customer's requirements before you invest in a demo. Check this first, because a strong business case does not help if the product cannot do the job.

Link to this question

A short meeting where sales, presales, services, product management and development look at one open deal together. You use it when the fit is unclear and one team cannot decide alone. Record the decision and the actions, and check them in the next call.

Link to this question

When the product cannot solve the core problem, when nobody can decide or when there is no budget or reason to act. Walk away early, and you free your time for deals you can win.

Link to this question

It finds the services a customer needs to make your SaaS work for them. Think of setup, data migration, integrations and training. Skip it and the deal looks cheaper than it is, until the project starts.

Link to this question

Start with the customer's pains, not your menu. Show a few scenes that each solve one pain. Run every scene as Tell-Show-Tell.

Link to this question

A simple loop for every demo scene. Tell what you will show and why it matters. Show it live. Then tell what it means for them, tied back to their pain. People remember the two tells more than the click path.

Link to this question

Try not to. A demo without discovery turns into a feature tour, and feature tours rarely win. If the customer insists, give a short overview demo. Use it to ask the discovery questions you missed.

Link to this question

Most fail before they start. There was no real discovery, the wrong people are in the room or the demo shows everything instead of three things that matter. So start with the preparation.

Link to this question

Remote, you lose body language. Keep the camera on, check in more often and cut the demo into shorter scenes. On site, you can read the room. Use the whiteboard, walk around and watch who leans in.

Link to this question

Send a short thank-you note with the recording and slides. Answer the questions you could not answer live. Then agree on the next step and confirm it in writing.

Link to this question

Click-through demos and short personal videos let buyers see the product on their own time. They are worth it early in the deal and for simple questions. Keep the live demo for the people who decide.

Link to this question

One slide deck that holds every scene, story and screenshot your team uses. For each demo you copy the master and keep only what fits this customer. It saves hours and keeps the story consistent.

Link to this question

Take the yearly gain from the solution, subtract the cost and divide by the cost. Use the customer's own numbers wherever you can. Finance trusts their own data more than yours.

Link to this question

A proof of concept tests whether the solution can do something in the customer's world. A proof of value tests whether it delivers the value they need, measured against agreed numbers. A pilot runs the solution with real users and data before the full rollout.

Link to this question

No. A POC costs both sides weeks. Agree only when there are written success criteria, a decision date and a clear next step if it works. Often a focused demo or a reference call answers the same question faster.

Link to this question

No. Answer only the ones you can win. If you were not involved before the RFP was written, a competitor often shaped it. Check fit, competition and effort before you commit the team.

Link to this question

An RFI collects information to build a shortlist. An RFP asks for a full proposal against the customer's requirements. An RFQ asks for a price when the customer already knows what to buy.

Link to this question

Listen to the whole concern first. Then ask a question to find the real worry behind it. Answer that worry, not the surface wording, and check that your answer landed.

Link to this question

Often it is doing nothing. The customer decides the problem is not painful enough to fix now. Build a clear case for why they should act now, not only why they should pick you.

Link to this question

Stay close. Answer the late technical questions fast, back up your AE in negotiation and make sure nothing promised is missing from the contract. Then hand over cleanly to the delivery team.

Link to this question

Do it soon after the decision, while memories are fresh. Ask the customer why they decided, if you can. Look for one or two changes the team will make next time, and write them down where people will find them.

Link to this question

Win rate on qualified deals, time spent per deal and the number of technical wins are a good start. Add customer-facing numbers such as demo-to-next-step rates. Pick a few and track them honestly.

Link to this question

Listen first. Talk to every team member, to sales and to the customers before you change anything. Then fix one thing that hurts everyone, such as deal intake or a shared playbook. Small early wins buy you trust.

Link to this question

Write the answer down once and put it where people look. A shared knowledge page, a standard slide or a short recorded video all work. Link to it the next time the question comes. After a few rounds, people look there first.

Link to this question

It helps more than most people expect. Customers look you up before the first call. Share what you learn in deals, without customer names. A few honest posts a month are enough to start.

Link to this question

No, but presales people who use AI will replace those who do not. AI takes over the first draft of RFP answers, research and summaries. You keep the part customers pay for: judgement, trust and a story that fits them.

Link to this question

Pick a few sources and make them a habit. One podcast on the commute, one book a quarter and your own product release notes go a long way. Share one thing you learned with your team each week.

Link to this question

A camera at eye level, light from the front and a decent microphone. Those three matter more than any expensive gear. Add a second screen so you can see the customer while you present.

Link to this question

Beyond CRM and slides, most teams use a screen capture tool, a recording tool, a whiteboard and some form of click-through or interactive demo. Start with one tool that saves you time every week. Add more later.

Link to this question

Use it as an assistant. Let it prepare account research, draft RFP answers, summarise calls and suggest discovery questions. Always check the output, because your name goes on it.

Link to this question

Start with one book on demos and one on negotiation or listening. The books page lists the ones that shaped this handbook, with a short note on each.

Link to this question

Yes. Every chapter, tip and blog post on this site is free to read, without sign-up. The video course and the printed book are the paid parts. They go deeper, but you do not need them to use the handbook.

Link to this question

A video course built on this handbook. It takes you from discovery and qualification to demos, POCs, RFx and closing. You pay once, and templates plus a certificate come with it.

Link to this question

Yes. Some lessons are free previews. Look for the Preview label in the curriculum on the course page.

Link to this question

Unlimited, and at least 24 months after purchase. You pay once, and lessons added later are included.

Link to this question

Write within 30 days and you get a full refund. Only the payment provider's fee is deducted.

Link to this question

Yes. Pass the final exam and you get a certificate you can share on LinkedIn.

Link to this question

The video lessons are in English. The course pages and the lesson texts are available in English and German.

Link to this question

Yes, for free. Send a short message through the contact page and tell me about your situation.

Link to this question

Enter the email address you used when you enrolled. You get a sign-in link by email. No password needed. The link works for 30 minutes.

Link to this question

Yes, in the course. The FAQ lesson holds more than ten hours of video answers on mindset, career, discovery, demos and more.

Link to this question

On the templates page. It lists every template with a short description and a preview. The free newsletter toolkit puts templates in one zip, and the course comes with the full library.

Link to this question

Try the site search at the top of the page. It covers every chapter, blog post and lesson. Still stuck? Write me through the contact page. Good questions end up in this FAQ.

Link to this question