Building CredoStar: From Internal Tool to Product
Where it started
CredoStar did not start as a product idea. It started as a problem we ran into ourselves.
We needed to issue certificates for a training program. The options were: use a generic PDF template and manually fill in names, or pay for a credentialing platform that required recipients to create accounts just to view their own certificates.
Neither option was acceptable. So we built a tool that could generate, issue, and verify certificates using the OpenBadges standard. It took a few weeks. It worked well enough for our use case.
Then we showed it to a few educational institutes. They had the same problem. They wanted verifiable credentials but the existing solutions were either too expensive, too complicated, or too locked down.
That was the signal. We turned the internal tool into a product.
The decisions that shaped it
Early on we made three decisions that defined what CredoStar became:
Standards-first. We built on the OpenBadges specification rather than inventing a proprietary format. This means certificates issued through CredoStar are interoperable with any system that supports the standard. Recipients are never locked into our platform.
Verification without accounts. Recipients should be able to share and verify their credentials without creating an account on our platform. The certificate carries its own verification data. Anyone with the link can check if it is real.
Simple issuance. The issuing organization should not need a technical team to set up and manage credentialing. Upload criteria, add recipients, issue certificates. That is the entire workflow.
What we got wrong
We overbuilt the admin dashboard in the first version. We added analytics, reporting views, and batch management features before we had enough users to validate whether any of it mattered.
Most of it did not matter. Issuers wanted to create a badge, send it to recipients, and move on. The elaborate dashboard was a distraction. We stripped it back to the core workflow and usage went up.
The lesson is one we keep relearning: ship the smallest useful thing, then watch what people actually do with it.
Where it is now
CredoStar is live and serving organizations that issue certificates. It handles the full lifecycle: badge definition, credential generation, delivery to recipients, and public verification.
The roadmap is driven by what issuers actually ask for, not by what we think would be impressive. Right now that means better bulk issuance tools, more customization options for certificate templates, and integrations with learning management systems.
What we learned about product development
The biggest takeaway from building CredoStar is that the best products do not start from market research. They start from encountering a problem firsthand, building the minimum thing that solves it, and then discovering that other people have the same problem.
That is the approach we use for everything we build at Thinqzo. Not because it is a methodology we read about, but because it is literally how our first product happened.