CodesClue started as a software consultancy: a team that gets handed someone else's hardest problem and ships working code against it. Client work like that teaches you a specific kind of discipline — you don't get to hide behind "it's still in beta," and you don't get to ship something you can't explain to the person who has to trust it.
Somewhere in the middle of that client work, our own sales process quietly became a mess. Every new engagement started the same way — a spreadsheet of prospects, a rep skimming it for anyone who looked promising, and a set of judgement calls that lived in someone's head and nowhere else. We were building ranking systems, scoring engines and outreach automation for other companies during the day, and doing none of it for ourselves.
So we built the tool we actually needed: something that would take a raw list, score every row against who we were actually trying to reach, rank it, hand each name to the right person, and draft the first message. It was internal for a long time. It didn't have a name that mattered outside the company, and it didn't need one — it just needed to work every morning.
It kept working. Once the internal version was reliable enough that we trusted it with our own pipeline, the obvious next question was whether anyone else needed the same thing. LeadClue is that answer — the internal tool, rebuilt as a product, with the same standard we held it to when only we were using it.
2019
the year CodesClue started building software for other companies
40+
client engagements before we scored our own first lead
9 mo
from internal spreadsheet to a working scoring engine
1
internal tool that turned out to be the actual product
Illustrative figures — CodesClue's founding date and project history are being finalised for publication.