How to Prepare for Your First Sales Meeting with a School

Your first sales meeting with a school is not primarily a chance to tell the buyer everything about your business.

It is a chance to understand whether there is a genuine problem, whether your offer is a credible fit and what would need to happen before the school could make a decision.

That distinction matters because school suppliers often prepare for the wrong kind of meeting.

They build a polished presentation, rehearse a detailed product demonstration and collect every case study they have. They then spend most of the meeting speaking while the school provides very little information about its current situation, budget, decision-makers or timetable.

The supplier may leave feeling that the meeting went well because the contact was polite and appeared interested. Yet no one has established:

• how important the problem is;
• who owns it internally;
• whether money is available;
• whether the school can choose the supplier;
• which colleagues need to be involved;
• what the school would need to see before proceeding;
• whether there is a realistic decision date.

A successful first meeting should produce clarity, not merely enthusiasm.

Sometimes that clarity leads to a demonstration, site visit, formal quotation or technical review. Sometimes it reveals that the school is not ready, the decision belongs to a central trust team or the offer is not a good fit. Both outcomes are valuable.

This guide explains how to prepare for your first sales meeting with a school, who should attend, which questions to ask, what information to bring and how to end with a useful next step.

Understand the purpose of the first meeting

The purpose of the first meeting is usually to determine whether a worthwhile opportunity exists.

It is not necessarily to close the sale.

For a small and straightforward product, the school may be ready to request a quotation or place an order quickly. More complex purchases normally require several stages, including internal discussion, budget confirmation, procurement, due diligence and approval.

Your first meeting should help both parties answer five broad questions.

Is there a defined problem?

The school should be able to explain what it wants to improve, replace, reduce, introduce or manage differently.

A vague interest in “seeing what is available” can still lead somewhere, but it should not be treated as a qualified purchasing opportunity yet.

Is the problem sufficiently important?

Schools encounter many problems that they would like to solve. Only some receive funding and leadership attention.

You need to understand what happens if the school does nothing.

Is your offer relevant?

The meeting should reveal whether the product fits the school’s phase, size, systems, pupils, staff capacity and delivery requirements.

Can the school buy it?

This includes budget, delegated authority, procurement, contract arrangements and whether the purchase is controlled by the school or its trust.

Is there a sensible next step?

Examples include:

• a tailored demonstration;
• a site survey;
• a technical review;
• a meeting with the budget holder;
• a written proposal;
• a formal quotation;
• a defined pilot;
• reconnecting during the next budget cycle.

Approach the meeting as a joint assessment.

You are not trying to persuade every school to buy. You are trying to establish whether the school has a problem you can solve in a way it can realistically approve, implement and sustain.

This mindset makes it easier to ask direct but professional questions about budget, authority and timing.

It also helps you recognise when the correct outcome is to stop pursuing the opportunity.

Research the school, trust and people attending

The school should not need to spend the first ten minutes explaining facts you could have found publicly.

Before the meeting, confirm:

• the school’s official name;
• phase and age range;
• approximate pupil numbers;
• school type;
• location;
• whether it belongs to a MAT;
• the trust’s name and size;
• the likely purchasing level;
• the roles of the people attending;
• the reason the meeting was arranged.

The guide to researching a school before contacting it explains how to use school websites, trust information, official records and public strategies without turning public data into awkward personalisation.

Review the correspondence that led to the meeting.

Record:

• who initiated contact;
• what problem or interest they mentioned;
• which product they viewed;
• which questions they asked;
• whether a price has already been discussed;
• whether another colleague was copied;
• whether a deadline or project was mentioned.

Do not make the school repeat information it has already provided.

Research the attendees

Understand what each person is likely to care about.

A teacher or end user may focus on:

• practical use;
• pupil suitability;
• preparation time;
• training;
• day-to-day workload.

A senior leader may focus on:

• strategic relevance;
• whole-school effect;
• implementation capacity;
• evidence;
• accountability.

A school business manager may focus on:

• complete cost;
• budget;
• procurement;
• contract terms;
• supplier assurance;
• value for money.

An IT manager may focus on:

• compatibility;
• security;
• data;
• integrations;
• support;
• technical workload.

Do not assume that the most senior attendee is the main decision-maker.

The person who arranged the meeting may be an end user or internal champion. They may need help involving finance, IT, safeguarding or trust colleagues later.

Research the organisation without overdiagnosing it

Use public information to prepare useful questions, not to announce that you understand the school better than its own staff.

For example:

“I understand the trust has six academies and a central operations team. Is this service normally reviewed centrally, or would each academy decide separately?”

This is appropriate.

Avoid:

“We noticed your results have declined, so clearly your current system is not working.”

Public information rarely explains the complete operational context.

Confirm who should attend the meeting

A meeting can fail before it begins because the people needed for a useful discussion are absent.

If the meeting concerns a classroom product, an end user may be enough for an initial exploration. If it concerns a whole-school platform, the school may need educational, operational and technical perspectives.

Before the meeting, ask:

“Who would be most useful to include at this stage?”

Or:

“Because the platform involves pupil data and staff accounts, would it be helpful to include someone from IT or data protection in the first discussion, or should that review happen later?”

The answer should reflect the meeting’s purpose.

Do not invite everyone too early

A first conversation with eight participants can become difficult to manage when the basic problem has not been defined.

For early discovery, one or two relevant contacts may be sufficient.

Additional stakeholders can join when there is enough information for them to assess.

Do not proceed too far with only an end user

An enthusiastic teacher, department leader or administrator can be a strong internal champion. However, the opportunity may stall if the budget holder and approver remain unaware of it.

During the meeting, ask:

“Who else would normally need to review or approve something like this?”

This identifies the wider buying group without undermining the original contact.

Bring the right supplier colleagues

Do not bring several colleagues merely to make the meeting appear important.

Each supplier attendee should have a clear role.

You may need:

• a salesperson to lead discovery and commercial discussion;
• a product specialist for detailed use cases;
• a technical colleague for complex integrations or security;
• an implementation lead for large projects;
• a subject specialist for educational or professional services.

For many first meetings, one well-prepared person is enough.

If several supplier colleagues attend, agree beforehand:

• who leads;
• who asks questions;
• who takes notes;
• which topics each person handles;
• who confirms the next step.

A school should not have to watch supplier colleagues interrupt or contradict one another.

Set a clear agenda and define the meeting length

Schools operate to tight timetables. A meeting that begins without an agenda can quickly consume more time than expected.

Confirm the duration in advance.

A useful first meeting may take:

• 20 to 30 minutes for an initial qualification call;
• 30 to 45 minutes for a more detailed discovery meeting;
• 45 to 60 minutes where a short demonstration or several stakeholders are involved.

Longer is not automatically better.

A practical agenda might be:

1. Introductions and meeting purpose — 5 minutes
2. Current situation and priorities — 15 minutes
3. Relevant overview of the supplier’s approach — 10 minutes
4. Questions, buying process and next steps — 10 minutes

Send a short agenda with the calendar invitation or confirmation email.

For example:

To make the meeting useful, I suggest we cover:

• how the school currently manages the process;
• the main difficulties or priorities;
• whether our service appears relevant;
• who else would need to review it;
• the most useful next step.

I have allowed 30 minutes.

This reassures the school that the supplier will not deliver an uncontrolled hour-long pitch.

Ask whether the school wants a demonstration

Do not assume that a first meeting and a demonstration are the same thing.

A demonstration is more useful after you understand:

• the user group;
• the current process;
• the main problem;
• the required functionality;
• the people evaluating the product.

Where the school specifically requests a demonstration, keep discovery at the beginning so you can focus on relevant features.

A generic demonstration of everything the product can do is rarely persuasive.

Prepare questions that uncover the real requirement

The quality of the first meeting depends heavily on the questions asked.

A supplier that asks only:

“What are you looking for?”

may receive a list of requested features without understanding the underlying problem.

Prepare questions in several groups.

Current situation

• How is the school currently handling this?
• Which staff members or departments are involved?
• Which systems, suppliers or internal processes are currently used?
• How long has the current arrangement been in place?
• What is working well and should be retained?

Asking what works well is important. It prevents the conversation from becoming a simplistic criticism of the current provider or process.

Problem and impact

• What is creating the greatest difficulty?
• Who is most affected?
• How often does the problem occur?
• What workarounds are staff using?
• What happens if nothing changes?
• Why is the school considering this now?

Ask for examples.

Instead of accepting:

“Reporting takes too long.”

ask:

“Which report creates the most work, and what does the team currently need to do to produce it?”

Desired outcome

• What would a successful result look like?
• Which changes would staff notice?
• What would pupils, parents or leaders experience differently?
• How would the school assess whether the purchase was worthwhile?
• Which outcomes are essential and which would be desirable?

Requirements and constraints

• How many pupils, users, rooms or sites are involved?
• Which existing systems must the offer work with?
• Are there accessibility requirements?
• What staff time can the school commit?
• Are there safeguarding, data or site constraints?
• Does delivery need to happen during a particular term or holiday?
• Which requirements are non-negotiable?

Buying process

• Who owns the relevant budget?
• Is the decision made by the school or centrally by the trust?
• Who else needs to review the offer?
• Will quotations, a framework or a formal competition be required?
• Who has final approval?
• Who can sign the contract?
• Is there a target decision or implementation date?

Department for Education buying guidance advises schools to identify everyone affected, confirm approval and check their procurement rules before buying. Suppliers should therefore expect useful school meetings to involve questions about stakeholders, specification and the correct buying route.

Alternatives

• Is the school reviewing other suppliers?
• Could the school improve the current process without buying a new product?
• Is an existing trust or local-authority service available?
• What would make the school retain the current approach?

Do not react defensively when alternatives are mentioned. Understanding them helps you explain genuine differences rather than repeating generic benefits.

Prepare the right evidence and materials

You should be ready to support the discussion without turning the meeting into a document recital.

Useful materials may include:

• a concise school-specific overview;
• a relevant case study;
• initial pricing or package information;
• a simple implementation outline;
• sample reporting;
• product screenshots or physical samples;
• a technical summary;
• an assurance-document index;
• a formal sales pack available after the meeting.

The guide to what to include in a school supplier sales pack explains how to organise pricing, evidence, implementation and assurance information so it can be forwarded internally.

Choose one relevant case study

A case study should resemble the buyer where possible.

Match by:

• school phase;
• size;
• problem;
• trust structure;
• implementation complexity;
• geography where relevant.

A small primary school may not learn much from a highly resourced 30-academy MAT implementation. A MAT central team may need stronger evidence of scalability than a single-school testimonial provides.

Be ready to explain:

• the original problem;
• what was delivered;
• what the school contributed;
• how long implementation took;
• what result was observed;
• what the evidence does not prove.

Know your pricing

Do not enter the meeting unable to give any indication of cost.

Even when a tailored quotation is necessary, prepare:

• starting prices;
• typical ranges;
• standard packages;
• the variables that affect cost;
• setup, training, travel and support charges;
• renewal pricing;
• minimum contract value.

The school may not expect a final price during the meeting, but it should be able to establish whether the offer is broadly affordable.

Prepare for compliance questions

You do not need to send every policy before the meeting. You should know which documents are available and who can answer specialist questions.

Depending on the service, be prepared to discuss:

• insurance;
• safeguarding;
• DBS arrangements;
• health and safety;
• data protection;
• cybersecurity;
• accessibility;
• subcontractors;
• business continuity.

The guide to what documents a school supplier should have ready provides a document-by-document checklist.

Test the meeting technology

For online meetings, check:

• meeting link;
• microphone;
• camera;
• screen sharing;
• presentation permissions;
• demonstration account;
• internet connection;
• backup screenshots or video.

Do not use real pupil data in a demonstration.

For onsite meetings, confirm:

• school address and site;
• arrival time;
• parking or public transport;
• visitor sign-in;
• identification requirements;
• room and equipment;
• who will meet you;
• whether samples or equipment are permitted.

Plan how to explain your offer without taking over the meeting

Your product explanation should respond to what the school has told you.

A useful structure is:

1. Restate the problem.
2. Confirm the desired outcome.
3. Explain the relevant part of your offer.
4. Show how implementation would work.
5. Provide appropriate evidence.
6. Check whether the explanation fits.

For example:

“You have explained that staff currently export information from three systems and manually combine it for the monthly trust report. The relevant part of our platform is the central reporting module, which connects academy-level accounts and produces the agreed report structure. A typical rollout would require one trust project lead, a technical review and administrator training at each academy.”

This is stronger than beginning with:

“Let me show you all 27 features in our platform.”

Use a short company introduction

The school needs enough information to understand who you are and why you are credible.

A concise introduction might cover:

• what the company provides;
• which schools it serves;
• relevant experience;
• who will deliver the work.

Avoid a long company history unless it has direct relevance.

Connect features to the school’s situation

Do not merely say:

“The platform has automated notifications.”

Explain:

“Because you currently rely on staff checking the spreadsheet each morning, the notification can alert the attendance team when an agreed threshold is reached.”

Be honest about limitations

If the product cannot meet a requirement, say so.

You may be able to offer:

• a workaround;
• an integration;
• a future development;
• a different package;
• a recommendation that another supplier is more suitable.

Do not promise functionality during the meeting merely to preserve momentum.

Pause and check understanding

Use questions such as:

• Does that reflect the problem accurately?
• Would this fit your current process?
• Which part would be most useful?
• What concern would you still have?
• Who else would need to see this?

The school’s response is more valuable than uninterrupted presentation time.

Discuss budget, procurement and timing professionally

Some suppliers avoid budget questions because they fear appearing too commercial.

That can result in months of work on an opportunity that has no credible funding route.

You do not need to demand a precise budget immediately. You should establish whether the school has considered affordability.

Useful questions include:

• Has a budget been identified for this project?
• Which budget would normally fund it?
• Is the school considering this for the current or next financial period?
• Is there an approximate range the proposal needs to fit?
• Would the decision depend on additional funding or approval?
• Would a phased approach be useful?

If the school says it has no budget, clarify what that means.

It may mean:

• the current budget has been spent;
• the purchase was not planned;
• the buyer has not spoken to finance;
• the price exceeds expectations;
• the problem is not a sufficient priority;
• the purchase belongs in the next budget cycle.

Do not offer a discount before understanding the issue.

Ask about the purchasing route

Questions may include:

• Does the school need comparison quotations?
• Is an approved framework available or required?
• Would the trust run the procurement centrally?
• Is an existing contract in place?
• Will a formal specification be issued?
• Which person or committee approves the purchase?

Current DfE guidance tells schools to check their own procurement policy and use the route appropriate to the value and nature of the purchase. Framework agreements also specify how a school can select a supplier and place an order.

Do not tell a school that no procurement is necessary unless you understand its rules and the applicable route.

Understand the timetable

Ask what is driving the date.

A credible timetable may be linked to:

• contract expiry;
• budget approval;
• a governing-body or trust meeting;
• summer installation;
• a September launch;
• staff training;
• a statutory deadline;
• a tender timetable.

A vague desire to “have something in place for September” is not enough if the school has not considered procurement, data, training or implementation.

The guide to how long it takes to sell to a school explains why approval and implementation are separate stages.

Listen carefully, take useful notes and manage the conversation

Listening is not simply remaining silent while waiting to present the next slide.

Useful listening involves:

• asking follow-up questions;
• clarifying vague statements;
• checking assumptions;
• noticing disagreement between participants;
• distinguishing essential requirements from preferences;
• summarising what you have heard.

Take structured notes

Your notes should cover:

• current process;
• problem;
• impact;
• desired outcome;
• users;
• requirements;
• constraints;
• budget;
• stakeholders;
• procurement;
• timing;
• concerns;
• agreed actions.

Tell the school that you are taking notes so you can send an accurate recap.

Do not record the meeting without obtaining appropriate agreement and considering data-protection requirements.

Clarify ambiguous language

If the school says:

“We need something easy to use.”

ask:

“Which users are you most concerned about, and what has made the current process difficult?”

If it says:

“The price needs to be reasonable.”

ask:

“Is there an existing budget or comparison point we should understand before proposing a scope?”

Notice differences between attendees

A teacher may want flexibility while the trust wants standardisation. The IT team may prefer strong central control while academy staff want local autonomy. Finance may want a lower initial cost while operational colleagues want complete implementation support.

Do not ignore these differences.

Summarise them:

“It sounds as though the trust needs consistent reporting, while academies still need control over their own users. We should make sure the next demonstration addresses both requirements.”

Keep the meeting on time

When one topic begins consuming the whole meeting, say:

“That technical point deserves a fuller answer. I suggest we record it and arrange a separate review with the appropriate colleagues rather than use the remaining time now.”

This respects the school’s time and prevents rushed next steps.

End with an agreed and proportionate next step

Do not end the meeting with:

“We will send some information and you can let us know.”

That creates no ownership or timetable.

Use the final minutes to summarise:

• the problem;
• the school’s desired outcome;
• the apparent fit;
• the unresolved questions;
• the people who still need to be involved;
• the agreed next action.

For example:

“You are looking for a replacement before the current contract ends in December. The priority is reducing manual reporting across four academies while allowing each school to retain local access. The next step is a technical demonstration for the trust IT manager and two academy administrators. I will send possible dates and indicative trust pricing by Thursday.”

Good next steps

• Schedule a tailored demonstration.
• Arrange a site visit.
• Provide an itemised quotation.
• Send a technical questionnaire.
• Introduce the supplier to the budget holder.
• Review data and safeguarding documents.
• Define a pilot with success criteria.
• Reconnect before a named budget meeting.

Weak next steps

• Send more information.
• Keep in touch.
• Think about it.
• Follow up sometime next month.
• See whether anyone else is interested.

Where possible, give each action:

• an owner;
• a date;
• a clear output.

Action	Owner	Date
Send indicative pricing and implementation outline	Supplier	Thursday
Confirm whether IT review is required centrally	School contact	Friday
Hold tailored demonstration	Both parties	Proposed dates next week

It is also acceptable to agree that there should be no immediate next step.

For example:

“The school has no available budget this year and will not begin planning until January. We will close the active opportunity and reconnect during the first week of January with updated pricing.”

This is better than six months of vague follow-up.

Follow up promptly and assess the opportunity honestly

Send a written recap soon after the meeting, usually on the same or next working day.

The follow-up should include:

• thanks;
• a concise summary of the current situation;
• the desired outcome;
• the proposed scope or relevant solution;
• important unanswered questions;
• the agreed actions and dates;
• only the documents that are currently useful.

For example:

Thank you for meeting today. My understanding is that the school wants to replace its current visitor-management process before the start of the next academic year. The main requirements are faster reception check-in, central contractor records and a clear process for visitors working with pupils.

We agreed that I will send indicative pricing, implementation requirements and our data and safeguarding overview by Thursday. You will confirm whether the trust IT team needs to join the demonstration.

Once that is confirmed, we will arrange a 45-minute demonstration focused on reception workflow, reporting and trust-level administration.

Do not send every available document

Send what supports the next stage.

After an initial discovery meeting, that may be:

• one-page summary;
• relevant case study;
• indicative pricing;
• implementation outline;
• answers to specific questions.

Detailed contracts and assurance files can follow when the school begins formal evaluation.

Update your opportunity record

Record:

• problem;
• priority;
• stakeholders;
• budget status;
• procurement route;
• decision process;
• target date;
• competition;
• risks;
• next action.

Qualify honestly

A friendly meeting is not automatically a strong opportunity.

A stronger opportunity has:

• a defined problem;
• a credible internal champion;
• a possible funding route;
• access to relevant decision-makers;
• a known buying process;
• a realistic timetable;
• a scheduled next step.

A weaker opportunity may have:

• general curiosity;
• no budget discussion;
• no reason to act;
• no authority;
• no agreed next step;
• requirements outside the product’s fit.

Do not inflate the sales forecast because the school was complimentary.

Common first school sales meeting mistakes

Talking for most of the meeting

The supplier leaves with little understanding of the school’s problem or buying process.

Beginning with a long company presentation

The school needs relevance before history.

Demonstrating every feature

Show only what connects to the school’s stated needs.

Failing to discuss budget

The opportunity may remain active for months without a realistic funding route.

Asking for the budget too abruptly

Build context first and explain why the information is needed to recommend an appropriate scope.

Ignoring trust structure

The academy may not control the decision.

Accepting vague problems

Ask for examples, frequency and impact.

Promising unsupported outcomes

Explain the mechanism and evidence rather than claiming the product will automatically transform attainment, attendance or workload.

Agreeing to features or contract changes immediately

Record the request and confirm it after checking internally.

Bringing too many supplier colleagues

The meeting can feel intimidating or inefficient.

Failing to invite a necessary school stakeholder

Technical, financial or safeguarding questions then appear much later.

Leaving without a dated next step

The opportunity drifts into repeated “just checking in” emails.

Sending an enormous follow-up pack

Relevant information becomes difficult to find.

Treating politeness as buying intent

School staff may be interested and courteous without having authority, budget or urgency.

Criticising the current supplier

You rarely understand the full history or contractual situation. Focus on the school’s requirements and the strengths of your own approach.

Frequently asked questions

How long should a first school sales meeting be?

Thirty minutes is often enough for an initial discovery conversation. More complex meetings involving demonstrations or several stakeholders may take 45 to 60 minutes. Confirm the duration and agenda in advance.

Should I demonstrate the product in the first meeting?

Only when the school has requested it or enough is known to make the demonstration relevant. A short discovery discussion should normally happen first so you can focus on the right use cases.

Who should attend from the school?

The person who owns the problem should normally attend. Depending on the purchase, the school may also need an end user, business manager, senior leader, IT colleague, safeguarding lead or trust representative.

How many people should the supplier bring?

Bring only the people needed to make the meeting useful. One well-prepared representative is often enough. Add technical, implementation or subject specialists where their expertise is genuinely required.

Should I send an agenda?

Yes. A short agenda helps the school prepare and shows that you will respect the agreed time. Include the current situation, requirements, relevant overview and next steps.

Should I ask about budget in the first meeting?

For a serious commercial discussion, yes. You do not always need an exact figure, but you should understand whether a budget exists, which budget is relevant and whether the likely price is realistic.

How do I ask about budget without sounding aggressive?

Explain that you need to recommend an appropriate scope. Ask whether the school has identified a funding source or approximate range and whether the purchase is planned for the current or next budget period.

Should I discuss competitors?

You can ask which alternatives the school is considering and what matters in the comparison. Do not criticise named competitors or make unsupported claims about them.

What documents should I bring?

Prepare a concise overview, relevant case study, pricing guidance, implementation outline and answers to likely technical or compliance questions. Do not overwhelm the school with every policy and certificate.

Should I provide an exact price in the meeting?

Provide one where the scope is standard and understood. For complex work, give a realistic range and explain what information is needed to produce a formal quotation.

What if the school says it has no budget?

Clarify whether the issue is current timing, total cost, lack of an approved budget line or low priority. Agree a realistic future date where appropriate rather than automatically discounting.

What if the person attending cannot make the decision?

They may still be a useful internal champion. Ask who else needs to be involved and provide a concise summary they can share. Avoid bypassing them without agreement.

What should I do if the offer is not a good fit?

Say so honestly. Explain which requirement you cannot meet and, where appropriate, suggest a more suitable route. A poor-fit sale is likely to create implementation and renewal problems later.

Should I record the meeting?

Only with appropriate agreement and after considering privacy and data-protection requirements. Written notes are usually sufficient for an initial meeting.

How quickly should I follow up?

Send a concise recap on the same or next working day. Confirm the problem, agreed actions, owners and dates while the discussion is still fresh.

What is the best way to end the meeting?

Summarise what you heard, confirm whether the offer appears relevant and agree one proportionate next step with an owner and date.

How do I know whether the meeting was successful?

A successful meeting produces useful information and a clear decision. That may be a scheduled next step, a future reconnection date or an honest conclusion that the opportunity is not suitable. Polite interest alone is not enough.