Let's start with the honest version of why we did this. We didn't wake up one day and decide to chase a quality certification because it felt like the right thing to do. We did it because there was a tender we wanted to bid for, and ISO 9001 was a mandatory requirement to even be considered. That's the origin story.
If you're not familiar with it, ISO 9001 is an international standard for quality management. Essentially, proof that a company has consistent, documented processes for how it delivers work, not just good intentions and talented people.
Here's what I expected going in: an outside consultant pokes around, finds a list of things we're doing wrong, and we spend months fixing them. That's the story most certification posts tell. It's not quite what happened to us.
We already believed this, before anyone told us to
One thing we've said internally for a long time is that a Craftsman who builds in a way that only they understand isn't protecting their position — they're creating a fragility that the whole team eventually pays for. If someone is the only person who knows how a piece of work actually functions, the project doesn't just depend on them. It's vulnerable because of them. We'd felt what happens when that goes wrong, and we'd already built habits around avoiding it.
Some of those habits are just how we work by now. A feature gets planned before anyone jumps to code, and that plan gets approved by another Craftsman — not as a formality, but so at least one other person understands what's being built. Documentation gets written where it actually helps. Bugs have somewhere to go — clients have a way to report them, and internally there's an expectation of resolving them in a reasonable time. And we talk to each other constantly.
So when the findings started coming in, the consultant didn't find a company that didn't care about this. He found a company that mostly already lived it. There weren't many flags. The process was, honestly, a fairly smooth one.
The one thing that kept coming up
But it wasn't flag-free either. And the pattern in what did come up was consistent enough that it became the actual lesson of the whole thing: we were doing the work. We just weren't always proving we'd done it.
A few honest examples. Internal meetings happened, decisions got made, direction got set but we weren't strict about logging the date or who was actually in the meeting. A client would confirm a design decision, and that confirmation was real whether it was a quick call, a "yes, go ahead" but we didn't always keep a written record of it before moving to the next step. And system architecture — the kind of thing that is second nature to us and often just stays in our heads. Not because we hadn't thought it through, but because it didn't occur to us that it needed to be written down for someone else to see.
Why this matters more than the certificate itself
This is really the same fragility problem again, just from a different angle. It's not enough for a Craftsman to build in a way that doesn't depend on them. The rest of the team and the client also need a way to see that. A track record isn't bureaucracy for its own sake. It's what lets someone else step into a project without the person who built it in the room to explain it. It's what lets a client trust a company they've never worked with before. It's what lets you actually trace a problem back to its source when something goes wrong.
That's also, we think, the real reason clients ask for a certification like this in the first place. Not because they doubt the work but because when there's a disagreement about what was agreed, someone needs a record to point to, not just two people's word against each other.
What we do differently now
So what actually changed? A few concrete things.
Meetings now happen over Google Meet, with Gemini transcribing as we go — and we still take our own notes in parallel, because a transcript isn't the same as someone's read on what mattered. When it's needed, a follow-up email goes out afterwards, so there's something short and clear to point back to later.
Client confirmations on decisions now go through ClickUp as much as possible. If a client confirms by email or another channel instead, we log it back in ClickUp so there's one place it lives and for some cases, a digital signature is used too. This is now written into our client agreements, so it's not just our habit, it's something clients agree to upfront. We don't move to the next step until that confirmation is in writing, somewhere we can find it again.
The habits didn't need reinventing — they needed a place to live that wasn't just us.
Where we've landed
We got ISO 9001 because a tender needed us to. But what it actually gave us wasn't a new set of values — it was a mirror. It confirmed the instincts we already had, and it pushed us to close the one real gap between them: turning "we do this well" into "here's how you'd know."
Certified by the European Certification Institute Ltd. (EuCI).