Business diagnostics
Strong traffic can hide a weak business for longer than you'd think
DOMIK UA had the visitor numbers a real estate platform is supposed to want. The developers paying for leads weren't renewing, and the traffic dashboard had no way to say why.
The traffic was strong. The renewals were not.
DOMIK UA came to me in 2018 with a real estate listings platform in Ukraine and a problem that did not look like a problem. Visitors were arriving in the numbers a platform like theirs is supposed to want.
I asked what happened to a visitor after they landed, not how many arrived. Nobody had a real answer, because nobody had needed one before. The traffic number had always been enough to point to, and the money that mattered didn't come from a visitor at all. It came from property developers paying for leads worth following up.
Two leaks, not one
Consumers arrived and left without ever becoming a lead a developer could act on. Separately, the developers who did get leads had no structured reason to stay, renew, or spend more once they'd tried the platform once.
Fix only the consumer side and you send more leads into a relationship that already leaks. Fix only the developer offer and you're packaging leads that were never good enough to sell in the first place. Both problems had to move together, or neither one would.
The same form for a browser and a buyer
A visitor three weeks from a purchase and a visitor browsing on a lunch break landed on the identical lead form. Every developer received one undifferentiated stream and had no way to act on any of it differently — the platform's own data couldn't tell them which lead was which.
Over about four months, I rebuilt the lead magnets and the forms around two things a browser doesn't have and a buyer does: urgency, and a budget.
What changed, in order
The forms came first, because nothing after them would matter if the input stayed the same. Then real onboarding for developers — an actual path into the platform, not a login and an invoice. Then packaged offers that gave a developer a specific reason to renew rather than a generic invitation to buy more. Then campaigns run against real, localised demand instead of national spend that reached everyone equally and nobody in particular.
The groundwork for a subscription model came last, once the relationship with a developer was worth making recurring at all.
The traffic number was never the one that mattered
Paid traffic converting into leads improved 2.5 times. Business-to-business renewals rose 40% quarter over quarter — the number that actually said something, because it meant developers had decided the leads were worth paying for a second time, not just a first. Revenue per developer account roughly followed, modelled from the new packaging and the renewal change rather than measured on its own.
Both sides of the marketplace already existed before any of this started. What changed was how short the path was between a visitor and a lead a developer would actually pay for twice.