PlastIQ trains professionals in the plastics and polymer industry. Their courses range from short workshops to multi-day programs, often with limited seats and specialized instructors. It's the kind of business where the product is partly the people, and the reputation comes from the work in the room.
The problem was that the work outside the room had grown along with the business. By the time PlastIQ came to us, a lot of every week was going into registration handling, emails back and forth with prospective participants, a spreadsheet for the attendee list, another for invoicing data, a third for the waiting lists. Every individual step made sense; together they added up to a job nobody had time for.
PlastIQ didn't need a better form or a nicer-looking website. They needed one place where the whole flow lived. Registration, attendees, capacities,... instead of having to be the integration layer between half a dozen tools themselves.
We came in alongside Onnest, who had already done the brand and visual work. They handled how the platform looks and feels; we handled how it works.
What we built
Most of PlastIQ's registrations come from HR or training coordinators booking multiple colleagues into a course at once. The platform is built around that flow. A coordinator at one of the participating companies browses the catalogue, picks a session, registers their attendees, and provides their details, all in one go, in a couple of minutes, without anyone at PlastIQ having to be involved.
On the back-office side, the PlastIQ team manages courses, sessions, capacities, attendee lists, waiting lists, and the invoicing data that flows into their accounting workflow, all from one place. The team's role shifted from running the registration process to running the courses, with the system handling the coordination work in between.
The waiting list works the way it should: when a new session of a course is opened, everyone on the waiting list gets notified automatically. That alone has turned waiting lists from a manual reminder process into a real conversion channel, people who originally couldn't get a seat get a fair shot at the next one without anyone having to remember to email them.
After a course wraps, the platform generates the participant certificates automatically, pulling the right names, course details, and dates from the system instead of someone in the back office filling in a Word template forty times. It's a small thing per certificate, but multiplied across a year's worth of sessions it's another full job that no longer needs doing.
How we worked together
Two things worth mentioning, because they probably matter to anyone reading this trying to figure out what working with us is like.
PlastIQ talked directly to the developer writing the code. No project manager in between, no email chain three people deep. When something needed to change in the catalogue logic, the conversation and the change happened the same week.
And we worked alongside Onnest, not around them. They'd been PlastIQ's branding partner for years; we weren't there to redo their work. They gave the platform its character, we gave it its mechanics, and the result is more coherent than either of us would have produced on our own.
What this changed
The platform has been live since 2022 and PlastIQ has been growing into it rather than out of it. New course types, more sessions, new modules, each one extends the system instead of breaking it.
The bigger change is what's no longer manual. Registrations come in cleanly, attendee lists update themselves, invoicing data is ready when the team needs it, waiting lists notify themselves when a new session opens. The work that used to happen between a coordinator wanting to book a course and the team being able to run it has, more or less, gone away.
Adding a session means adding a session, not adding work. That was the whole point.
Thinking about something similar?
If admin around your product has started to cap how fast you can grow, the conversation is usually shorter than people expect. We'll tell you on the first call whether it's something we should build, something you can buy off the shelf, or something that doesn't need software at all.
