Skillfit.io had a strong market, but outbound was too manual to scale.
The team had early traction, but new customer acquisition still depended heavily on Lukas and a working student manually building lists in Apollo and LinkedIn Sales Navigator.
The process was slow and painful. Skillfit.io was sending standard copy to manually qualified leads, but response rates and conversion rates were low, lead relevance was inconsistent, and outbound created only about one meeting every two weeks.
At the same time, the category was competitive. Paid acquisition was expensive because Skillfit.io was competing with much larger companies, so outbound was not just another channel. It was one of the most important paths to new pipeline.
"We booked around one meeting in two weeks. And it was quite painful."
We helped Skillfit.io build the outbound system themselves.
Skillfit.io did not want an agency to simply hand over booked meetings. Outbound was a core part of the company's value creation, so Lukas wanted the team to understand the system and stay close to how it worked.
Enablement helped Skillfit.io set up the foundations: secondary domains, email infrastructure, the outbound toolset, Clay templates, bilingual copywriting support, and a structured process for building and testing campaigns.
The work also forced strategic clarity. Skillfit.io used the setup process to think more deeply about its value proposition, buyer personas, use cases, trigger events, and the segments most likely to respond.
Skillfit.io reached 4-5 outbound meetings per week.
Before the collaboration, Skillfit.io was booking around one meeting every two weeks. After the collaboration, Lukas reported that the team was booking 4-5 meetings per week, which matched the initial goal.
The team could likely book more, but Skillfit.io was intentionally limiting outbound volume based on team size and capacity.
The process also gave the team more than meetings. Lukas said the collaboration helped Skillfit.io learn a lot about itself, especially around value proposition, buyer personas, and how to position a complex product with multiple use cases.
Skillfit.io left with outbound capability, not dependency.
The collaboration worked because Skillfit.io wanted to learn the system, not outsource the problem. Enablement provided structure, templates, coaching, and expertise, while the Skillfit.io team stayed close to the implementation.
For an early-stage SaaS company in a competitive market, that mattered. Skillfit.io needed more pipeline, but it also needed market learning: which segments respond, which trigger events matter, and which messages create real conversations.