We thought we were building training software. A few hundred conversations with frontline teams taught us what we were really building — and for whom.
When we started building this, I thought we were building training software. It took a few hundred conversations with the people we actually build for to understand we were building something else — and that most of what I assumed on day one was wrong.
This is a reflection on that: what we got wrong, what our customers taught us, and what we ended up building because of it. I'm writing it partly because I think the lessons are useful to anyone trying to train a frontline team, and partly because the people who taught us these things deserve the credit for it.
Like a lot of software people, we started with a tidy picture in our heads. Courses. Modules. A learner sitting down with a bit of quiet time to work through material, click "complete," and come out the other side trained. It's a clean picture, and it's roughly how corporate training has looked for twenty years.
It has almost nothing to do with how a technician, an installer, a cleaner, or a line cook actually learns their job. That gap between the picture in our heads and the reality of the work is where our real education started.
The first thing we heard, over and over, was that the day doesn't have a quiet hour in it. The people our customers were trying to train were in trucks, on roofs, on floors, between calls — often on a phone with one bar of signal, often not in their first language. A beautiful desktop course was, to them, invisible. It might as well not have existed.
The second thing was subtler, and it changed how we thought about the whole problem. One operations manager mentioned, almost in passing, that his best technician was quietly burning out — not from the work, but from being the de facto trainer for every new hire. "Teaching the new guy" had become a second full-time job nobody had planned for. We heard versions of that from company after company: the knowledge was there, locked in the heads of a few good people, and the only way it moved was by wearing those people down. It's a big part of why so much frontline training quietly fails, and it was the moment we realized this wasn't really a content problem.
The third lesson took the longest to actually hear: our customers didn't have a learning problem. They had an access problem. As one of them put it to us bluntly, the information already exists — it's just never where the work happens, when the work happens. They didn't need us to invent more training. They needed the training they already had to reach people.
Once we accepted all of that, what to build got a lot clearer — and honestly, a lot less glamorous than the product we'd first imagined.
We stopped asking people to create training from scratch. Almost every company we talked to already had the raw material — SOPs, PDFs, safety docs, recorded walkthroughs, years of hard-won knowledge sitting in binders and in people's heads. So we built the thing that turns what you already have into training people can actually use, in minutes, without needing an instructional designer or a blank screen. If your "training" is a shelf of binders, the job is getting that onto the phone in people's pockets, not rewriting it.
We built for the phone first, because that's where our people are. Short pieces that fit between jobs, not hour-long courses. Delivery that meets someone where they already are instead of asking them to stop and come find it.
And we built the boring, essential part: a way for an operations leader to actually see who's ready — not who clicked "complete," but who is genuinely prepared to do the work. The managers we talked to were flying blind, and "I'm pretty sure they were trained" is not a sentence you want to say after an incident. For the teams where that matters most, it also means a complete, timestamped record you can hand an auditor in minutes instead of reconstructing one in a panic.
The feedback that has meant the most to us isn't about features. It's about relief.
A customer telling us the binder nobody opened is now something their crew actually pulls up on a Tuesday afternoon. An operations manager saying onboarding stopped being the thing that burned out his best people. A safety lead who can produce a training record on demand instead of dreading the request. A founder who told us the knowledge that used to walk out the door every time a veteran retired now stays in the business.
None of that is dramatic. It's not the language of a product demo. But it's the language our customers actually use, and every time we hear it, it tells us we're pointed at the right problem. The wins we're proudest of are quiet ones — a new hire who's genuinely useful in weeks instead of months, a manager who sleeps a little better because the answer to "are they ready?" is finally something they can see.
The biggest shift was less about the product and more about us. We came in thinking of ourselves as a software company that happened to serve the trades. We've come to think of ourselves as something more like careful listeners — people whose real job is to pay very close attention to how skilled work actually gets done, and then get out of the way of the people who are already good at it.
We build for people who fix, install, maintain, clean, cook, and keep things running — the work that doesn't happen at a desk and doesn't get nearly enough credit. It turns out that if you take that work seriously, and take the people doing it seriously, a lot of the product decisions make themselves. Our customers have been the real designers all along. We've mostly been listening closely and trying to keep up. It's also why we spend so much time thinking about how field and service teams are actually trained in the real world, not the ideal one.
We're still learning, and we expect we always will be. But the direction has never felt clearer: build for the reality of the job, not the fantasy of the classroom.
If you're trying to turn what your team already knows into training they'll actually use — and finally see who's ready — that's exactly what we built Quinn to do. Book a quick demo and we'll walk through it against your reality, not a slide deck.