If you work
for anyone,
nobody looks.
For dev shops and IT service firms where the answer to “who do you sell to?” is still “anyone who needs software”.
- market
- Hungary
- firms measured
- 647
- company size
- 11-50 people
- live in
- 30 days
The problem isn't quality.
It's namability.
source: our own measurement of the Hungarian IT services market, 2026. n=227.
we read one by one across the Hungarian IT services market
how many could name the industry or platform they actually serve
We read two hundred and twenty-seven Hungarian IT service firms one by one. Nineteen could name who they work for: SAP Business One, ServiceNow, Dynamics, Odoo - or manufacturing, telecom, pharma. For the rest the answer was “any company that needs software”.
This is not about the quality of the work. It's that with no nameable customer there is nothing to target - not for us, not for you. A customer who could be anyone is, in practice, nobody.
First you have to say who you work for. After that the outreach can be automated - but only after.
It doesn't grind lists.
It hunts signals.
Once the specialism exists, the signals appear with it. The machine watches for movement inside the circle where you are credible.
hiring developers
They've been advertising for in-house developers for months. Whoever can't hire eventually outsources.
a platform rollout
They're rolling out a platform you work on. Customisation and operations follow the rollout.
rapid growth
The team grew fast in months. Processes break here, and outside capacity is what fixes them.
stack change
Moving to cloud, replacing an ERP, commissioning a security audit. Squarely your table.
fresh funding
Budget and a deadline. Building the internal team is slower than the roadmap they committed to.
a compliance deadline
NIS2, ISO, a data-protection audit. A dated obligation somebody has to solve.
↳ these are examples - your machine gets tuned to the specialism we name in week one
Thirty days,
step by step.
↯This is a scenario, not a case study from an existing client. We are looking for our first client now - the moment there are measured results, they go here instead of an invented number.
We name who you work for.
This is the most important step on the page, and for you it's the hard one. We don't start from your capabilities but from your best twenty projects: which industry, around which platform, at what company size the margin was best and the sale shortest.
Your GTM knowledge base gets built.
From your references we pull out where you are demonstrably better than a larger integrator - and what you answer to “we already have a partner”. That knowledge base stays yours.
The machine goes live.
It finds the companies inside the named circle where something is moving, reads up, and writes about what is happening at their company. Not about your service list.
Sharper every month.
It becomes clear which industry and which argument gets replies, and the machine weights toward it. If the focus narrows further, that's good news: it gets more accurate.
Hi Tamás,
I saw you rolled out the new warehouse system in the spring, and that you've been hiring a developer alongside it.
At logistics firms this is the usual point: the rollout is done, but customisation and integration eat capacity for months. That's the part we take over.
Do you have 20 minutes next week? I'll show you how that stage looks elsewhere.
Three things,
with dates attached.
We don't promise project counts - we don't control them. What we promise depends on us, and it carries a date.
The GTM knowledge base
Everything worth knowing about your buyers, your arguments and your market - written down, structured, on your own infrastructure. It stays yours.
The live machine
A system that finds, researches, writes, sends and follows up. On your domains, into your CRM. Not software you rent - an engine you own.
The learning loop
What got replies, what didn't, what we changed. One page, with numbers. Not a dashboard login - a readable answer to what is happening.
What an IT firm's owner
usually asks.
“We don't want to narrow down and lose other clients.”
You're not turning anyone away. Narrowing is about who you actively approach, not who you serve. Referrals keep coming as before. Outbound only works when there is something to aim at.
“Our projects come from referrals.”
Good - while it lasts. Referrals can't be turned up: you can't ask for more the month two big projects end. The machine covers the stretch when none arrive.
“We could build this ourselves.”
Obviously. You build software. The question is whether there's capacity left for your own client acquisition after you've delivered your clients'. So far there hasn't been.
“Who actually does the work?”
The two of us. No account manager, no junior we hand it off to. The person on your first call is the person building the system.
If it doesn't bring clients,
it doesn't cost much.
The most common objection isn't “I don't believe it.” It's “what if it doesn't pay off?”. So it's built like this:
Most of the money is a success fee.
A low monthly retainer, with the larger part due when you win a client. The setup fee covers building the machine - not a deposit against results.
Do the math, don't take our word.
Take your average project value or monthly retainer and divide by our fee. In IT services one new framework agreement usually covers the year.
Built once, runs long.
The machine keeps running past six months without a rebuild. The setup fee spreads across that whole period, not one month.
If it doesn't add up against your numbers, we'll tell you that too.
We'll say so on the first call if we're not a fit. Cheaper to hear it now than in six months.
Let's start with
who you sell to.
Thirty minutes, free. We go through your best projects and see whether a nameable customer emerges from them. If none emerges, we'll say so - that's a useful answer too.