kevin.
kevin.
When the product can’t tell the whole story
It’s no secret that startups move fast. They build the product, find product–market fit, raise money, win customers, hire people and enter new markets, often all at once. When you’re racing against time, the product naturally becomes the centre of the story. It’s the thing you’re building, investors are backing and customers need to understand.
That works particularly well when the product is genuinely extraordinary.
When I joined payments startup kevin., it was building technology many people in the industry didn’t believe was possible. Its founder, Pavel, had raised $65 million around a powerful proposition: kevin. was building a unique payment infrastructure capable of replacing multiple players in the payment chain and significantly reducing fees.
The technology could allow account-to-account payments to work on existing point-of-sale terminals, giving businesses an alternative to payment infrastructure dominated for decades by card schemes. Pavel would walk into meetings with major banks, explain what kevin. was building, be met with disbelief, and then demonstrate a transaction. The room would go quiet.
In those rooms, the product could speak for itself.
Outside them, things were less clear.
Was kevin. an account-to-account payments company? An open banking company? A payment gateway? Payment infrastructure? Depending on where you looked or who you asked, you could reasonably arrive at any of those answers.
None was entirely wrong. They described the technology, the category closest to it, or one of the things it could do. But kevin. didn’t yet have a compelling answer that travelled beyond the product.
A founder cannot be in every sales meeting. A product demonstration cannot explain the business to every candidate considering joining. Marketing cannot reveal technology the company needs to protect. As a business grows, more people have to explain what it is, why it matters and where it is going without having lived inside the founder’s head.
Without a shared idea, people reach for what they have: features, categories, competitors and familiar language that makes something unfamiliar easier to understand.
A company can have breakthrough technology and still end up describing itself using the language of everyone around it.
If you define yourself through the system you want to replace, that system continues to set the terms of the conversation.
The difference between what drives you and why you matter
When I arrived at kevin., the company was already working on a new brand. At the centre of the thinking was a purpose that captured the founder’s mentality perfectly:
Fuck legacy.
I understood why it resonated.
Pavel had spent years challenging assumptions built into the payments industry. He was the founder of a relatively small company attempting to rethink infrastructure dominated by some of the largest and most established players in the world. He had been told what he was building couldn’t be done, then demonstrated that it could.
“Fuck legacy” captured that energy. It was provocative, defiant and emotionally true.
But what drives a founder to build something isn’t always the same as the difference the business exists to make.
Being against legacy explained the fight kevin. was in. It didn’t explain what winning that fight would make possible. If you define yourself through the system you want to replace, that system continues to set the terms of the conversation.
The more interesting question was much simpler:
What does this product actually make possible?
I knew very little about the intricacies of payment infrastructure when I first met Pavel. But listening to him describe the technology, and particularly those moments when people saw something they had assumed was impossible actually happen, made its significance feel bigger than the category being used to describe it.
kevin. wasn’t interesting simply because it could make payments cheaper.
It was rebuilding payment infrastructure from the ground up. The technology could remove unnecessary intermediaries, work silently behind businesses and give partners sole control over their payments. Rather than forcing companies to operate within someone else’s scheme, the infrastructure could allow them to build a payment experience around their own business.
The breakthrough wasn’t simply another way to move money. It was what businesses might be able to do once the old constraints were removed.
That became the foundation for a different idea:
Build a world of payment possibilities.
The most dangerous thing about a breakthrough product is believing it can tell the whole story.
An idea big enough for the business
A strategic idea only becomes useful when it clarifies the business underneath it.
“Building a world of payment possibilities” gave kevin. a way to connect things that had previously been explained separately. Its clean-slate infrastructure was how it did things differently. Its mission was to free partners from the pains of legacy payments. Its promise became “Payments you can build business on.”
A2A still mattered. Lower fees still mattered. POS payments, security, direct bank connections and removing unnecessary intermediaries still mattered. The strategy didn’t replace any of those things.
It gave them somewhere to belong.
Instead of leading primarily with the mechanics of account-to-account payments, kevin. could start with what the infrastructure enabled: greater control, new services, better conversion, stronger customer relationships and the freedom to build on top of the payment infrastructure itself.
One of the simplest expressions became:
Your brand. Your scheme. Your rules.
The product had not changed. What had changed was the significance of it.
The story could now adapt for investors, payment service providers and merchants without turning kevin. into a different company for each audience.
This mattered particularly for technology the company could not, or should not, explain in full. Without a bigger idea, secrecy leaves a vacuum and people fill it with the nearest understandable category.
People need to know what they’re joining
The same problem existed inside the company.
kevin. had grown quickly and needed to attract talent beyond its home market in Lithuania. But most candidates cannot fully evaluate the significance of proprietary infrastructure before joining a company, and even highly technical people rarely choose their next employer by comparing product architecture alone.
They need to understand what they are helping to build.
kevin.’s old visual identity was playful, irreverent and impossible to ignore.