A training course booking system that onboards learners for you
Training providers spend too long on the steps between a booking and the first session: confirming places, taking payment or raising employer invoices, sending joining instructions, enrolling learners in the LMS and collecting pre-course forms. We build a workflow that handles those steps from your booking form or system through to Moodle, Canvas or your LMS, with reminders and a class list for the trainer. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why course admin goes wrong on the first day
A single course date can involve individual learners paying online, employers booking several staff on one invoice, joining instructions, LMS accounts, pre-course questionnaires and reminders. Much of it is copied between a booking form, a spreadsheet, the LMS and email.
Mistakes show up on the day: a learner without an LMS login, a trainer without an up-to-date list, an employer booking with no purchase order number, a learner who never got the venue details.
What we build
What our training course booking automation includes
Online booking
Course dates with places available, booked through your form or booking tool, with waiting lists when full.
Payment or invoice
Stripe Payment Links for individuals, or employer invoices with purchase order numbers.
Joining instructions
Venue or online joining details, timings and what to bring, sent on booking with reminders before the date.
LMS enrollment
Learners created and enrolled in the right course in Moodle, Canvas or your LMS.
Pre-course forms
Questionnaires, prior learning and access needs collected and passed to the trainer.
Class list
A list per course date for the trainer with attendance status and notes.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Booking made
A learner or employer books a course date.
-
02
Automated
Payment or invoice
Payment is taken or an employer invoice is prepared.
-
03
Automated
Onboarding sent
Joining instructions, LMS access and pre-course forms go out.
-
04
Staff review
Team checks
Staff check access needs, invoices and waiting lists.
-
05
Head of school or programme lead decides
Course decisions
Running, moving or cancelling a course date is decided by the programme lead.
How it behaves
How course booking and onboarding behave
What learners and employers see
- Instant booking confirmation and payment or invoice
- Joining instructions and reminders before the date
- LMS access ready for the first session
What the course team sees
- Class lists per date with access needs
- Employer invoices to check
- Waiting lists when courses fill
What the automation does
- Enrolls learners in the LMS
- Sends joining instructions and forms
- Never cancels or moves a course by itself
Edge cases and fallbacks
- Course is full
- The learner joins the waiting list and staff are told.
- Payment fails
- No place is confirmed; the learner gets a retry link.
- Learner already has an LMS account
- Matched by email instead of creating a duplicate.
- LMS or Stripe outage
- Bookings are queued and retried, and the course team is alerted.
Architecture
Course booking and onboarding at a glance.
- Input
- Logic and services
- Output
- Data
- People
How it flows
- 1 A learner or employer books a course date through your form or booking tool.
- 2 Payment is taken or an employer invoice is prepared, and the learner is enrolled in the LMS.
- 3 Joining instructions, reminders and pre-course forms go out.
- 4 The course team checks access needs and gets a class list for the trainer.
Project planner
How the project runs, phase by phase.
Course booking, payments & learner onboarding project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Courses, booking routes, payment and invoicing rules, LMS and joining instructions.
-
02
Design
2 to 3 days
Booking flow, payment rules, LMS mapping, forms and reminders.
-
03
Build
1 to 2 weeks
Booking, payment, LMS enrollment, messages, forms and class lists.
-
04
Shadow run
About 1 week
Bookings for one course run through the workflow while staff check each step.
-
05
Launch
1 to 2 days
Switch on for all courses.
-
06
Support
Ongoing
New courses, venues and form changes.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Courses, booking routes, payment and LMS mapping.
$200 – $400
-
Build
Booking flow, payments, enrollment, messages and lists.
$500 – $1,300
-
Integrations
Stripe, LMS and email.
$150 – $400
-
Testing and shadow run
One course run end to end.
$100 – $250
-
Launch and training
Switch-on and course team walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Stripe, LMS and n8n are billed to you directly. Accounting integration for employer invoices may need a second workflow.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Stripe: Stripe's published processing fees for your country.
- LMS: Your LMS hosting or plan.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
EU and UK: learner data
When you collect learners' details directly, GDPR Article 13 (and UK GDPR) requires telling them the purposes, legal basis, recipients and retention.
Source: gdpr-info.euAccess needs are sensitive
Disability and health details given as access needs can be special category data under Article 9, so only the trainer and course team see them.
Source: gdpr-info.euUK: marketing emails
Course newsletters run separately from booking emails and only go to people who agreed, under PECR regulation 22.
Source: www.legislation.gov.ukFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Course booking, payments & learner onboarding questions, answered.
Software that lists course dates, takes bookings and payment and manages places. Our workflow connects your booking route to payment, the LMS, joining instructions and trainer lists, so the steps after booking happen by themselves.
Not always. We can work with a simple form, your website or an existing booking tool, and add the onboarding steps it lacks.
Yes. Employer bookings collect a purchase order number and learner list, and an invoice is prepared for your accounts team.
Moodle through its web services (creating users, enrolling them and reading completion), Canvas through its REST API and Google Classroom through its API. TalentLMS and others are confirmed per project.
Yes. Joining links and time zone details go out on booking and in reminders.
Bookings to attendance, learners without LMS access on day one, pre-course forms returned and time staff spend per booking.
Free 20-minute call
Want this for your schools & training?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for schools & training
All servicesEducation CRM & enquiry pipeline
Every family or learner enquiry from web, phone, open days and social in one education CRM, with tour bookings, polite follow-ups and a weekly view of enquiries, visits and applications by source.
From $1,000 · About 4 weeks Details
Admissions documents, offers & enrollment
Applications checked for missing documents, reminders sent to families, assessment and interview slots booked, offer and acceptance steps tracked and enrollment forms collected before the first day.
From $1,000 · About 4 to 5 weeks Details
AI assistant for parents & learners
An AI assistant on your website and help inbox that answers term dates, fees, uniform, transport, course and policy questions from your approved information, in several languages, and passes anything personal or sensitive to staff.
From $2,500 · About 5 to 8 weeks Details