Proposal · Confidential

A 12-month RevOps partnership

One version of the truth — built in two months, run for twelve.

Twenty spreadsheets that don't talk to each other, a sign-up journey held together by people remembering to do things, and roughly 6,000 member schools with no single record. This proposal puts all of it into HubSpot inside an intensive two-month sprint — then gives you a dedicated RevOps team to run it, improve it, and train your own people to own it, for the rest of the year.

Little Wandle Letters and Sounds × RevOps Hub
Prepared by
Justin Humphreys
RevOps Hub
Prepared for
Oliver Nichol, Managing Director
Humphrey Gullett, Interim Head of Operations
Introduced by
Colm Raleigh, HubSpot
Date
August 2026
View the recording of our meeting

What we heard

Where Little Wandle is today

A five-year-old organisation that has grown fast and, in your own words, with an "oh, that'll do" approach to systems. The result is a business doing genuinely impressive numbers on infrastructure that can no longer carry it. Everything in this section came directly from our introductory call.

~6,000
Member schools won in five years — with no salesperson
20
Disconnected spreadsheets, none deduplicated against each other
700+
Knowledge base articles already in HubSpot, barely leveraged
100%
Of the sign-up → invoice → provision journey handled manually

The seven things standing in the way

Finding 01

No single version of the truth

Trainers and the ops team both suffer, in different ways, from not being able to log into one place and see a school.
  • Ops master spreadsheet — the closest thing to a customer record
  • A separate trainer spreadsheet of school interactions
  • Separate MAT and international school spreadsheets
  • Overlapping data, no deduplication, widely varying accuracy
Finding 02

The revenue journey is entirely manual

WooCommerce is doing the job of a CRM, and every step after payment depends on a person remembering to act.
  • School self-selects type and size on the website → WooCommerce
  • Finance manually raises the invoice and waits for payment
  • Ops manually provisions and schedules the welcome Zoom
  • No renewal visibility, no forecast, no early warning on churn
Finding 03

Relationships aren't modelled anywhere

"For every 6,000-ish school that is a member, what else are they part of?" — that question can't currently be answered.
  • Schools sit inside multi-academy trusts
  • They also sit inside English Hubs
  • International schools sit inside international school groups
  • A school can be a standalone customer and a group member at once
Finding 04

Product usage data is trapped

The assessment tracker is the thing that makes Little Wandle an EdTech — and none of what it knows reaches the people serving the customer.
  • Teachers capture rich assessment data throughout the year
  • None of it surfaces on the school record
  • No usage signal to drive renewal or at-risk conversations
Finding 05

Service is 100% human, and about to hit a wall

As international schools grow, either someone starts work at 3am or customers wait. Neither is acceptable.
  • Chat, email and calls all answered by people today
  • 700+ knowledge base articles sitting unused as an AI source
  • Target: 70–80% of routine queries answered by AI
  • Team freed for the harder, more interesting questions
Finding 06

A sales motion that doesn't exist yet

6,000 customers with zero salespeople is remarkable. It is not, however, a strategy for entering new verticals.
  • First salesperson being hired for expansion into new verticals
  • No pipeline, no stages, no forecast to hand them
  • Nursery, secondary and international are under-worked segments
Finding 07

Capability, not capacity, is the gap

"We've got a real engine there which just needs to be harnessed." The people are there and they're keen — the direction isn't.
  • Six-person ops team; three named leads keen to own this
  • Bright, fast learners — but no prior HubSpot admin experience
  • Regional trainers will need training on whatever gets built
  • A CRM & Insight Manager job description written, not yet hired against
The near-term commitment: you've told your teams the ops master spreadsheet and the trainer spreadsheet will be integrated by the beginning of September, and flagged that the real hurdle is the collaboration between trainers and ops on what the minimum useful data set actually is. That's the first thing this engagement lands — see "What lands first" below.

One goal, clear ownership

Who does what

This only works if the knowledge in your team's heads makes it into the design. We bring the HubSpot capability and do the heavy lifting; you bring the business knowledge and make the calls only you can make. As discussed on the call — the only real limit on pace is how quickly we can get answers out of your team.

The client · decision owner

Little Wandle

Owns the answers. Decides which fields matter, what a school record must show, and who owns what. Three ops leads work alongside us and progressively take the reins. Trainers feed in requirements and adopt the result.

Build & run

RevOps Hub

Designs the data model, migrates the spreadsheets, automates the revenue journey, switches on AI service, trains your people — and then runs the CRM day to day for twelve months.

Platform

HubSpot

Licensing across Marketing, Sales, Service and Content, plus the ~35,000 AI credits — contracted directly with HubSpot via Colm Raleigh. Not included in, or marked up by, the fees below.

The shared goal
One version of the truth in HubSpot — that Little Wandle's own team can run
Every workstream is judged against two tests: can someone log into one place and see the whole school, and is your team more capable of owning it this month than it was last month?

The team you get

Three people, not one hire

You were about to recruit a single CRM & Insight Manager. This engagement instead gives you a project lead who comes to you in person, a full-time technical resource doing the heavy lifting, and a senior strategic voice on call — for less than that one hire would cost you in year one.

Months 1–2 · Onshore, UK

Implementation Lead

Adoption is always better when someone is in the room. This is the person who gathers requirements, runs the workshops, and is accountable to Oliver and Humphrey for the sprint landing.

What they do

  • On-site workshops with ops, trainers, finance and marketing
  • Owns the data architecture design through to sign-off
  • Weekly progress reporting and risk escalation
  • Picks up the requirements that only surface by the water cooler
Months 1–12 · Offshore, 40 hrs / week

Dedicated RevOps Analyst

A named, full-time person — the same person throughout. In months 1–2 they are the build engine; from month 3 they are effectively your CRM team, running the thing they built.

Sprint phase · months 1–2

  • Field consolidation, data cleansing and migration
  • Object model, associations and property build
  • Workflows, automation and pipeline configuration

Run phase · months 3–12

  • Day-to-day CRM administration and bug fixes
  • Ongoing data hygiene, dedupe and quality alerting
  • Campaign, pipeline and renewal support
  • New-user onboarding and enablement
Months 1–12 · 8 hrs / month

Senior RevOps Specialist

A senior consultant retained for the strategic questions — a second opinion on the decisions that are expensive to get wrong, rather than another pair of hands.

Typical use of the 8 hours

  • Monthly strategic review with Oliver and Humphrey
  • Sales process and pipeline design for the new hire
  • Renewal, forecasting and segmentation strategy
  • Licence optimisation and AI roadmap
  • Hiring support if you still want a CRM admin in year two
💡 Why this shape: the analyst who runs your CRM from month three is the same person who built it. They know why every field exists, how every workflow fires, and who on your team does what — so there is no handover cliff when the sprint ends.

Phase 1 · Months 1–2

The implementation sprint

Enhanced resource, deliberately front-loaded, to get the critical things live fast. Six workstreams run concurrently — the data foundation gates the rest, so it starts on day one.

Workstream 1

Data architecture & migration

The foundation everything else sits on
Design the model once, properly — so a school record answers every question ops, trainers, finance and marketing actually ask.
  • Requirements workshops with ops, trainers, finance & marketing (1–2 hrs each)
  • Field consolidation, starting from the 20-spreadsheet field map you've already built
  • Decide field by field — keep, merge or retire; you own these calls
  • Company hierarchy: school ↔ MAT ↔ English Hub ↔ international group
  • Contact model: head teacher, main contact and secondary contacts per school
  • Data cleansing and deduplication across all sources
  • Staged, validated migration into HubSpot
  • Record ownership assigned — every record has a named owner
Workstream 2

Revenue engine

Sign-up → invoice → provision → renew
Take the manual handoffs out of the subscription journey, and give you renewal visibility you've never had.
  • WooCommerce → HubSpot connection so sign-ups create records automatically
  • Invoice and payment status tracked on the school record, ending the manual chase
  • Subscription and renewal management in Revenue Hub
  • Renewal pipeline with early-warning alerts on untouched renewals
  • 3 / 6 / 12-month renewal forecasting
  • New-business pipeline and stages, ready for your first salesperson
  • Segmentation by school type — primary, nursery, secondary, international
Workstream 3

Automated member onboarding

Tailored by school type, size and location
Every new school gets the onboarding that actually fits it — automatically — instead of ops assembling it by hand each time.
  • Onboarding pipeline with clear stages, so no school stalls unnoticed
  • Branching workflows keyed on school type, size, location and package
  • The right welcome Zoom, resource pack and materials per segment
  • Regional trainer auto-assigned by location, with tasks and calendar prompts
  • Automated welcome sequence and member-site access provisioning
  • Onboarding SLAs with alerts when a step runs overdue
  • Reporting on time-to-onboard and completion rates by segment
  • Built so you can add new rules yourselves as the segments evolve
Workstream 4

Interaction tracker

Calls, emails and in-person visits, one timeline
This is what properly retires the trainer spreadsheet — every conversation with a school, whoever had it and however it happened, on the school record.
  • HubSpot call recording and transcription enabled, with UK consent notifications configured
  • AI call summaries and follow-up tasks generated straight from transcripts
  • In-person visits and course delivery logged as activities against the school
  • HubSpot mobile app set up so trainers can log a visit before they leave the car park
  • Custom activity fields — visit type, attendees, outcome, follow-up needed
  • Email and chat threads auto-associated to the right school and contact
  • One interaction timeline visible to ops, trainers and leadership
  • Engagement reporting — which schools haven't been spoken to in six months
Workstream 5

Service & AI

Using the ~35,000 AI credits in your HubSpot quote
Get to 70–80% AI-answered on routine queries, so international growth doesn't mean somebody starting work at 3am.
  • Chat and email consolidated into the HubSpot inbox
  • 700+ knowledge base articles structured as the AI agent's source
  • Customer agent configured, tested and released in stages
  • Clean escalation path to ops and trainers for the complex 20–30%
  • Deflection rate, CSAT and response-time reporting
  • AI credits also applied to data import and enrichment agents
Workstream 6

HubSpot Admin training & adoption

Your three ops leads, plus the wider trainer community
The real risk isn't the migration — it's people quietly going back to their spreadsheets. This workstream is how we prevent that.
  • Structured HubSpot Admin training programme for the three ops leads
  • Covers properties, workflows, lists, reporting, permissions and troubleshooting
  • Role-based training for regional trainers on what's been built for them
  • Permissions and edit-restriction model so records can't be degraded
  • Written process documentation and an internal "how do I…" guide
  • Data-quality automations that flag bad or stale records before they spread
  • Competency checkpoints at months 2, 6 and 12
📞 On call recording: transcription and AI call summaries depend on your final HubSpot tier and seat allocation. We'll confirm exactly what's covered against Colm's quote at kick-off, before anything is promised to the trainer team.
📌 Assessment tracker integration is scoped as a discovery during the sprint and built in Phase 2. We'll assess what the tracker can expose, agree the handful of fields that genuinely belong on the school record, and schedule the build — rather than guessing at the effort before we've seen it.

Early momentum

What lands first

Big CRM projects lose people when nothing visible happens for three months. These are sequenced so your team sees real change inside the first fortnight.

Weeks 1–2

Visible in the first fortnight

  • Kick-off and requirements workshops, on site, with ops and trainers
  • Ops master and trainer spreadsheets consolidated — your September commitment, met
  • Agreed minimum data set and ownership rules for the merged record
  • Draft company hierarchy model reviewed and signed off
  • Three ops leads set up with admin access; first training session delivered
Weeks 3–8

The build lands

  • Full migration of the remaining spreadsheets, cleansed and deduplicated
  • MAT, English Hub and international group associations live
  • WooCommerce connected; sign-up and provisioning automated
  • Tailored onboarding journeys live for your main school types
  • Call recording, transcription and visit logging live; trainers working from the school record
  • Renewal pipeline built and first forecast produced
  • AI customer agent live on chat, staged release
  • Trainer training delivered; documentation handed over
  • Spreadsheets formally retired, with permissions changed to match

Phase 2 · Months 3–12

Running it, and handing it over

Once the build is done, the same analyst moves into business-as-usual — and the emphasis shifts steadily from us doing it to your team doing it.

Run

Day-to-day CRM management

  • Administration, bug fixes and change requests
  • Continuous data hygiene and deduplication
  • User onboarding — including your new salesperson
  • Assessment tracker integration built and released
Improve

Revenue operations

  • Renewal monitoring, so no conversation starts too late
  • 3 / 6 / 12-month forecasting and at-risk flagging
  • Pipeline management for the new sales motion
  • Onboarding journeys monitored and refined segment by segment
  • Interaction and engagement reporting, feeding renewal risk
  • Marketing campaign build and list management
  • Reporting and dashboards for the leadership team
Hand over

Building your independence

  • Ongoing HubSpot Admin coaching for the three ops leads
  • Progressive transfer of routine admin tasks to your team
  • Documentation kept current as the system evolves
  • Month 9 review: continue, hire, or self-sufficient?

What happens at month 12

Three doors, and you choose

You said you don't want to spend heavily training someone up only to lose them, and that your existing team's knowledge of the business is an asset no external hire can match. Agreed. So this engagement is deliberately built to make you less dependent on us over time, not more — and at month nine we'll have an honest conversation about which of these you want.

Door 1

Keep going

Extend the retainer as it stands. Sensible if the CRM keeps expanding in scope — more automation, more markets, more product lines — and you'd rather buy that capability than build it.

Door 2

Hire, with our help

If you still want someone in the building, we'll write the job description, sit on the interview panel and tell you what to look out for — then hand over to them properly, rather than dropping a system on their desk.

Door 3 · What we're aiming at

Your team owns it

Your three ops leads have been training and taking on tasks all year. If they're ready, we step back to a light advisory retainer and they run it. They already know the business — that's the advantage no external hire can match.

💡 Our incentive is pointed at door three. Every month we transfer more to your team is a month closer to you not needing us at this level. We'd rather be the partner you keep for strategy than the dependency you can't get rid of.

Next steps

How we get moving

This week

Review and shape

  • You review this and mark up anything that's wrong or missing
  • Book a call using the link below — we'll walk through the scope, answer your questions and talk through the commercials together
  • Share the field-mapping spreadsheet covering all 20 files, so we can size the migration properly
On agreement

Kick off — target start date early September

  • Contract and statement of work issued
  • HubSpot licences confirmed with Colm
  • Kick-off and first on-site workshop within two weeks of signature
  • September spreadsheet consolidation as the first deliverable
Book the next conversation
Grab a time that suits you

We'll walk through this together, work through anything you'd like changed, and talk you through the commercials in detail.

Book a call with Justin →
🤝 On flexibility: as discussed on the call, this isn't a fixed scope where stepping slightly outside it triggers extra charges. If priorities shift as we learn more about your data, we shift with them — the resource is yours for the year.