Education software development for training providers who copy enrolments by hand
Most of a training provider’s admin happens between “I want to enrol” and the first session. The education software we build covers that stretch: enrolment and payment in one step, a course catalogue that follows the real timetable, seat tracking for corporate clients, and certificates generated as PDFs. Session booking and PDF certificates borrow from systems we run: slot booking on the car-service site and PDF reports on XRay, our own product. Where your current LMS works, we connect to it rather than replace it.
What slows a training provider down, and what we build for it
Enrolments are copied into the LMS
They arrive by form, email and invoice request, and staff key in each learner.
What we buildOne enrolment form that takes payment and creates the learner’s access, so nobody copies anything.
Payment, invoice and access are three jobs
Someone checks the payment, sends the invoice and then opens the course, one learner at a time.
What we buildCheckout through a card provider such as Stripe, an invoice by email, and course access opened when the payment clears.
Booking a session date takes three emails
Learners and trainers agree a date by email, and someone copies it into the calendar by hand.
What we buildSessions with fixed slots and seats, booked online and written to your calendar with a message to your team. The car-service site books 45-minute slots this way.
The website shows last term’s timetable
The course catalogue is edited separately from the real schedule, so dates and seats drift apart.
What we buildA catalogue generated from the timetable you keep, with the seats left shown on each session.
Corporate seats are a spreadsheet job
A company buys twenty places, and working out who used them takes an afternoon.
What we buildA page per corporate client where their manager assigns seats and sees who attended and passed.
Certificates are made one by one
Each one is a Word file with a name typed in and a date that is sometimes wrong.
What we buildCertificates generated as PDFs from attendance and results, with a link anyone can use to check one is genuine.
The off-the-shelf LMS doesn’t fit
Your course structure, branding or language doesn’t match what the platform allows.
What we buildEither the missing parts built around your LMS through its API, or a smaller system that does what your courses need. See Product development.
Course pages don’t answer questions
People compare providers on dates, format, prerequisites and what the certificate is worth. Thin pages lose them.
What we buildCourse and topic pages with that detail, structured so search engines and AI assistants can read them, and articles published on a schedule.
A company books eight seats
The HR contact books seats
They reserve eight places on a course and pay or get one invoice, before they know every name.
Names come later
They add learners from a link as people sign up. Seats left are always visible to them.
Learners get access
Each learner gets a joining link or an LMS account, without anyone copying names across.
Certificates go out
When a learner completes, a PDF certificate is generated, and the HR contact gets one summary for the group.
An example of how it would work, not a client story.
Enrolment to certificate
What we build
What we build for a training provider
Two pieces come from systems we have built: slot booking written to Google Calendar with a message to the team, as on the car-service site, and PDF reports generated by XRay, our own product, which is how certificates would be made.
- Enrolment with payment through a card provider such as Stripe, and access opened on payment.
- Session booking in fixed slots, written to your calendar.
- A course catalogue built from the timetable, with seats left.
- Corporate seat management for the client’s manager.
- Certificates as PDFs that can be checked by link.
Copying enrolments into the LMS?
Tell us what happens between “I want to enrol” and the first session.
How we work with you
Tell us what happens today
Tell us how enrolments, payments and certificates are handled now, and which LMS you use, if any. We reply within one business day, usually within a few hours.
A free first look
An online call, and an outside check of your site with XRay, our own audit tool. A deeper audit is scoped after the call.
Build, or take over
We build the missing parts, or take over a system someone else built. One team covers analysis, build, testing and DevOps.
Keep it running
Fixes, security updates and new features. Hourly billing, one rate for the whole team, a report every week.
You own the code, the data and every account. More on how we work and the systems we have built.
What this doesn’t do
No course content or teaching. We build the system. Writing and teaching the courses stays with you.
No accreditation advice. What a certificate has to say is up to your awarding body. We build what they require.
No promises about Google rankings. We build course pages search engines and AI assistants can read. Positions are not ours to promise.
No prices before we talk. Billing is hourly with weekly reports, scoped after the call.
Questions we get from training providers
Can you connect to the LMS we already use?
Often, yes, if it has an API. Then enrolment and payment can open access in your LMS without anyone copying details across. If it has none, we look at what can be done safely before suggesting a replacement.
Can learners pay when they enrol?
Yes. Payment is taken in the enrolment form, and course access opens when it clears. We connect Stripe or Paddle, in an account in your company’s name.
Can companies buy seats for their staff?
Yes. The client’s manager gets a page to assign seats and see attendance and results, and the invoice goes to the company instead of each learner.
Each learner and each corporate client needs their own login, and our staff sign in with company accounts.
Each learner sees only their own courses and certificates, and each corporate manager sees only their own company’s seats, enforced in the database, not just on the screen. Sign-in through your company identity provider is agreed in the scope, and we check what it supports on the first call.
Who owns the system and the learner data?
You do. You own the code, the data and every account. If learner data includes minors or other sensitive details, here is what we check first.
Where to go from here
Still making certificates one by one?
Tell us which LMS and payment tools you use, and where the copying happens.
We reply within one business day, Tallinn time (EET), usually within a few hours. No obligation.