Every Irish EdTech sale passes through three filters, and only one of them is written down. The first is the RFP (Request for Proposal, the formal document a buyer publishes listing what they need) or formal evaluation, if there is one. The second is a compliance checklist that the school's DPO (Data Protection Officer, the person responsible for ensuring the school meets its data protection obligations) or IT lead runs through before a contract is signed. The third is an unwritten set of expectations around support, pricing, references, and cultural fit that decides most deals and appears in no document.
Founders who enter the Irish market with a strong product and clean compliance often stall at the third filter. They do not know it exists until a deal they expected to close simply goes quiet. The school does not send a rejection. It stops replying.
This guide covers all three filters: who is making the decision and how many of them there are, what compliance has to be true before you are in the room, what kills deals that passed the formal evaluation, how Irish pricing models work, when schools actually buy, and what to have ready before your first serious pitch.
Key takeaways
Irish buyers are not one market. Primary schools, post-primary schools, ETBs (Education and Training Boards, the 16 regional statutory bodies running further education, adult education, and apprenticeships across Ireland), and universities differ in decision-makers, budgets, procurement rules, and sales cycles. A strategy that works for primary schools will not work for ETBs, and neither will transfer directly to universities.
Compliance is the price of entry, not a differentiator. Seven items, from GDPR (General Data Protection Regulation, the EU's data privacy law) with the Irish DPC (Data Protection Commission, Ireland's data protection authority) as regulator to EU data residency and safeguarding for under-18 users, must be in place before a buyer will look at the product itself. Getting them right does not win the deal. Not having them loses it.
The unwritten list decides most deals. Support hours that overlap the Irish school day, a named Irish reference, training included in the price, twelve-month contracts, and Irish terminology are not in any RFP. They are the reasons a school stops replying after a promising demo.
Procurement follows the academic calendar, not yours. Schools decide between February and June for a September deployment. Pitching in November means January at the earliest or an eight-month wait. ETBs run quarterly cycles. Universities measure in twelve-to-eighteen-month procurement cycles with their own financial year-end.
The first Irish customer is the hardest. Once you have one named Irish reference in the same segment, the next ten conversations are different. Everything in this guide points toward getting that first reference as quickly and cleanly as possible.
What does "expects" actually mean in an Irish EdTech sale?
It means three separate lists, and the list that matters most is the one nobody writes down.
The first list is the formal RFP or evaluation criteria, if the buyer uses one. ETBs and universities almost always do. Schools sometimes do, sometimes do not. Where it exists, it is the easiest to satisfy because it tells you exactly what it wants.
The second list is the compliance checklist. The school's DPO, IT lead, or principal runs through it, sometimes formally and sometimes as a series of questions over email, about three weeks after the demo. If you cannot produce a DPIA (Data Protection Impact Assessment, the document assessing privacy risks before a new system is deployed) template on request, the conversation ends at this point. You may not hear that it ended. The school simply does not follow up.
The third list is the unwritten set of expectations that Irish buyers carry into every evaluation. These cover support hours, Irish references, pricing structure, contract terms, training, and whether the product feels like it was built for the Irish market or adapted from a UK or US version with a search-and-replace. This list decides more deals than the other two combined, because it is the one founders do not know to prepare for.

Who is actually making the decision?
The answer depends entirely on which buyer segment you are selling to, and each segment operates differently.
Primary and post-primary schools. The buying committee is typically the principal, the deputy principal, and a nominated teacher, though the composition varies. The board of management approves any material spend. Budgets are small and the decision cycle is short, usually within the February-to-June buying window described later in this guide. Peer recommendation is the strongest channel. A principal who hears from another principal that a product works in their school carries more weight than any demo. The sales conversation is human, direct, and usually decided by one or two people in the room.
ETBs. Ireland's 16 ETBs are regional statutory bodies managing post-primary, further education, adult education, and apprenticeship centres. A single ETB may cover dozens of centres and thousands of learners. Procurement runs through OGP (Office of Government Procurement, the central body that manages public sector purchasing frameworks in Ireland) frameworks where applicable, otherwise through above-threshold public tenders. Cycles are measured in quarters, not weeks. An ETB procurement decision can cover a dozen schools in one contract, which makes it the highest-leverage buyer segment in the Irish market, but the slowest to close.
Universities and institutes of technology. Several Irish institutes of technology have been reorganised into Technological Universities, which changes their procurement structures. Universities have dedicated IT procurement teams, security review processes, and their own financial year (many set year-end at 30 September). The cycle from first contact to signed contract is typically twelve to eighteen months. Expect a formal security review, a pilot, and a committee decision.
Department-level buying. Rare, slow, and usually reserved for national infrastructure. Not a realistic channel for early-stage EdTech products.

The compliance baseline: what has to be true before you are in the room
Seven items must be in place before an Irish buyer will evaluate the product itself. These are not differentiators. They are the minimum. Missing any one of them will end the evaluation, usually silently.
1. GDPR compliance with an Irish-relevant data protection notice. Your privacy notice must name the DPC as the relevant supervisory authority, not the UK's ICO (Information Commissioner's Office, the UK's data protection authority). Irish schools and universities operate under the DPC. A notice that references only the ICO signals that the product was built for a different market and has not been localised for Ireland.
2. EU or EEA data residency. Student data must be stored within the EU or EEA (European Economic Area, the EU member states plus Iceland, Liechtenstein, and Norway). If data transits through or is processed in the US, UK, or elsewhere outside the EEA, you need Standard Contractual Clauses (SCCs, the legal mechanism allowing data transfers outside the EEA while maintaining GDPR protections) in place and documented.
3. A completed DPIA template. The buyer needs to run a data protection impact assessment before deploying your product. You should provide a pre-completed DPIA template for a representative deployment, not a blank form. Schools do not have the resources to write one from scratch, and expecting them to do so slows the procurement by weeks.
4. A published sub-processor list. Buyers expect a current, dated list of every third-party service that processes their data, published on your website. It must include a change-notification process so the school knows before a new sub-processor is added, not after.
5. Cyber insurance. At a level appropriate to the contract value. Buyers rarely specify an amount, but they ask whether it exists.
6. A recognised security certification. ISO 27001 (the international standard for information security management) or Cyber Essentials Plus (the UK government-backed certification for basic cybersecurity) for larger deals. For smaller deals, a completed security questionnaire with named controls is usually sufficient.
7. Safeguarding-aware handling for under-18 users. Age-appropriate design, no third-party advertising, a clear parental consent position, and data handling that reflects the fact that your users are children. Irish schools will not deploy a product that has not addressed this explicitly.
What kills deals that passed the RFP?
Nine things that appear on no formal evaluation but stop deals from closing. Each one has ended at least one deal that Square Root Solutions has seen in the Irish market.
1. Support hours that do not overlap the Irish school day. A ticket submitted at 9am Dublin time that receives its first reply at 4pm Pacific time is a 9am ticket that sat unanswered for the entire school day. Schools need answers during their working hours, not yours.
2. No named Irish reference. Not a UK reference, not a European reference, not a testimonial on a website. A named school or institution in Ireland that the buyer can contact directly. The first Irish reference is the hardest to get and the most valuable asset in your sales operation.
3. A free tier that changes without warning. Schools that adopted a product on a free plan and then faced an unannounced change to pricing or features do not trust the next free tier they are offered. If you offer a free plan, the terms need to be stable and the transition to paid needs to be predictable.
4. Data leaving the EU. Even with SCCs in place, Irish buyers are increasingly reluctant to send student data outside the EEA. Data residency within the EU is becoming a practical requirement, not just a legal one.
5. Sub-processor list not disclosed on request. If a DPO asks for your sub-processor list and you cannot produce one immediately, the evaluation stops. This is a compliance item, but it appears here because the failure mode is usually a response delay, not a missing document.
6. Contracts that auto-renew with a long notice period. Irish schools operate on annual budgets. A contract that auto-renews for twelve months with a ninety-day notice window creates a financial commitment that may span two budget years. Twelve-month terms with a clear renewal decision point are the standard.
7. Training treated as a paid add-on. If the first cohort of teachers needs training to use the product, that training needs to be included in the price. Charging separately for onboarding signals that the product is not ready for a school environment, where the teacher is the user and the teacher's time is the constraint.
8. Sales handled entirely remotely, with no Irish-based commercial contact. A named person who understands the Irish market and can answer questions in Irish business hours is expected. Fully remote sales from a different time zone closes fewer deals than it should given the product quality.
9. UK terminology in the product or sales materials. "Year 7" instead of "First Year." "SIMS" instead of "the school MIS." "KS2" (Key Stage 2, the English curriculum stage for ages 7 to 11) instead of "third to sixth class." These are small signals that accumulate into a perception that the product was not built for this market, and they are easy to fix if you know to look for them.
What pricing model do Irish buyers actually pay?
Five pricing models work in the Irish market, and the tolerance for each varies by buyer segment.
Per-pupil pricing. The most common model for primary and post-primary schools. Irish price tolerance is well below UK equivalents: an English academy trust with 8,000 pupils operates in a different budget world from an Irish primary school with 240 pupils. Price per head for the same product must reflect that difference, or the school will not engage.
Per-institution pricing. A flat annual fee regardless of school size. Often easier to sell to smaller schools than per-pupil models, because the cost is predictable and does not require board approval for a formula the board cannot verify.
Per-user pricing. For staff-facing tools: curriculum planning, school administration, professional development. Well understood by buyers and rarely resisted, because the school knows exactly how many staff accounts it needs.
Consumption-based pricing. Usage-based models are a hard sell in Irish education. Schools need predictable annual costs for budget planning. If you use consumption pricing, offer an annual cap so the school can budget with certainty.
Free pilots. Expected in higher education. Common in ETB procurement. Acceptable in schools if the paid contract that follows allows exit. A pilot is not a favour. It is the buyer's way of testing whether the product works in their environment before committing budget.
Pricing mistakes take roughly eighteen months to surface. The wrong model signed at the wrong price does not fail immediately. It fails when the school's budget renews and the next year's allocation goes to something else.
Procurement calendars: why they set your sales calendar
The Irish education procurement calendar is not a suggestion. It is a hard constraint that determines when your sales conversations can happen and when they are wasted effort. For a deeper look at how the academic calendar shapes product releases and go-live windows specifically, see Shipping to the Academic Calendar: Why September Doesn't Move.
Schools (primary and post-primary). Decisions happen between February and June for a September deployment. Pitching in November means a January decision at the earliest, which often means an eight-month wait until the following September. Pitching in July means September at the earliest, often the following February. The campaign window is February to April, targeting a September go-live.
ETBs. First contact in October for a spring decision is a reasonable rule of thumb. ETB procurement moves in quarterly rhythms, and the evaluation process includes OGP framework checks, board approval, and sometimes a formal tender.
Universities. Many set their financial year-end at 30 September. Budget planning happens in spring and summer. The twelve-to-eighteen-month procurement cycle means that a conversation started in September may not close until the following winter.
Timing to avoid. October outreach targeting December pilots is the most common timing mistake. Schools are deep in first-term delivery, budgets for the current year are committed, and nobody is evaluating new products. Late August and early September are peak stress periods: schools are onboarding, administrators are processing returns, and your outreach competes with everything that needs to happen before the first day of term.
Not sure how many of these items your product actually has covered?
A Discovery Sprint with Square Root Solutions maps where your product and commercial model sit against every item on all three lists, and identifies what to fix before a buyer sees the deal. Two weeks, one clear picture.
What should you have ready before your first serious Irish pitch?
Nine items. If you are within six months of your first paid Irish deployment, every one of these should be in place or in progress.
1. A DPIA template, filled in for a representative deployment. Not a blank form. A completed assessment that the school's DPO can review and adapt, not write from scratch.
2. A current, public, dated sub-processor list on your website. With a change-notification process. Buyers check this before they reply to your follow-up email.
3. Data residency evidence. The region, the provider, and the certification. A page on your website stating where data is stored and linking to the hosting provider's compliance documentation.
4. At least one named Irish reference from the same segment, willing to take a call. This is the single most important item on this list. Everything else can be prepared in weeks. The first Irish reference takes months and changes every conversation that follows.
EduSmart Planner, the AI-powered curriculum planning platform built by Square Root Solutions for CJ Fallon, is an example of how the first reference compounds. CJ Fallon brought roughly thirty years of relationships with Irish schools. The platform had GDPR compliance in place from day one, sub-processors clearly named, and pricing fitted to an existing budget line. It now runs across more than 100 Irish schools. That first deployment, built on CJ Fallon's existing trust, made every subsequent conversation shorter and more productive.
5. A pricing option that fits an existing buyer budget line. Do not ask the school to create a new budget category for your product. Find out what they already budget for and price accordingly.
6. A stated support window overlapping Irish business hours. With a named channel (email, phone, or in-app) and a defensible response time. "Within two business days" is acceptable. "We will get back to you" is not.
7. A training plan included in the price. Delivered by a person, at least for the first cohort. Self-serve documentation is fine as a supplement. It is not a replacement for the first onboarding.
8. A twelve-month contract as default. With a clear renewal decision point. Not an auto-renewal with a long notice window.
9. A localisation pass. Irish year names (First Year, not Year 7), Irish institution types (DEIS, Gaelscoileanna, ETB), the correct regulator (DPC, not ICO), and the correct qualifications framework. This takes a day of work and signals that the product was built for this market.
Frequently asked questions
Do Irish schools actually check GDPR compliance in detail?
Yes. DPC awareness is high following sector enforcement actions across Europe, and Irish schools have been directly reminded of their obligations through the DPC's Data Protection Toolkit for Schools (published December 2024). A vendor who cannot produce a DPIA template on request is not shortlisted. The check is not always formal, but it always happens.
Does Irish-language support matter?
For English-medium schools, generally not. For Gaelscoileanna (all-Irish primary schools) and Gaelcholaisti (all-Irish post-primary schools), it does. Elsewhere, Irish-language support is a nice-to-have that signals market awareness but does not determine the deal.
Is a UK reference useful in Ireland?
Useful, but not sufficient. A UK reference demonstrates that the product works in a school environment, but Irish buyers want an Irish reference for procurement fit, support alignment, and cultural fit. The regulator is different, the terminology is different, and the budget context is different. A UK reference plus an Irish reference is strong. A UK reference alone leaves a gap.
How much should I budget for compliance and localisation?
For UK or EU vendors entering Ireland, a few weeks of engineering work and a legal review of data protection documentation. For US vendors, significantly more, because of data residency infrastructure, DPIA preparation, and the gap between US and EU data protection expectations.
Do universities and ETBs follow central government procurement rules?
They use OGP frameworks where applicable and the same public procurement thresholds (currently €25,000 for services), plus their own institution-specific procedures, security reviews, and timelines. A product that passes one university's review does not automatically pass another's.
Can you sell to Irish universities without a local presence?
Yes, but it is harder and slower. A named Irish commercial contact, an Irish support number, and existing Irish deployments shorten cycles. Fully remote sales from another time zone is possible for a strong product, but expect the procurement cycle to stretch.
What is the biggest mistake companies make entering the Irish market?
Assuming Ireland is a smaller version of the UK. The regulator is different (DPC, not ICO). The procurement landscape is different (boards of management, not academy trusts). The reference expectations are different (Irish references, not UK ones). The pricing tolerance is different (smaller budgets, more price-sensitive). The terminology is different (First Year, not Year 7). Companies that treat Ireland as a UK localisation project spend months discovering all the ways it is not.
Square Root Solutions builds EdTech platforms for the Irish and UK market, where getting compliance, commercial model, and cultural fit right in month three is cheaper than discovering what was missing in month eighteen. If you are preparing for your first Irish pitch or your tenth, a Discovery Sprint maps where you stand against everything in this guide before a buyer does it for you.
Read next: How to Choose an EdTech Software Development Company