journeys
01
Existing services were translated into journeys that customers can follow.
/Cloud Native Enablement/Application Modernisation & Migration/Platform Engineering
How Puzzle moved from strong engineering provider to clearly positioned transformation partner.
Together with The GoGrow Company, Puzzle turned its technical excellence into clearly structured transformation journeys, sharpened its messaging for business and tech decision makers and built a consistent go-to-market narrative.
quick facts
client
Puzzle ITC, Swiss cloud native engineering company
focus
Service structuring, positioning, go-to-market narrative, sales enablement
format
Clarity Sprint workshops, journey development, messaging alignment, sales enablement
result
Clear market position, stronger internal alignment, more structured sales conversations
the challenge
The substance was strong. The positioning was not consistently clear.
Puzzle has stood for exceptional engineering competence for years. Cloud native, platform engineering and application modernisation are established in the market. The real challenge was not technical depth. It was how that depth is perceived in the market.
01
Services had grown historically and were not structured along clear buyer journeys.
02
Messaging differed from team to team.
03
Business decision makers saw technical strength, but not always the strategic value.
04
Sales conversations often started with scope instead of transformation.
the goal
From technical implementation partner to strategic transformation partner.
Puzzle wanted to deliberately evolve how the market perceives it. From a strong technical implementation partner to a strategic partner that accompanies development journeys. We aligned on three goals.
01
Structure the portfolio into clearly defined transformation journeys.
02
Sharpen the ideal customer profiles and personas.
03
Build one consistent go-to-market story across all teams.
Three steps from service list to story.
icp & personas
02
For each journey we defined who the ideal customer is, which business challenges come first, which technical topics are decisive and how BDM and TDM perspectives differ. This aligned the argumentation precisely.
narrative
03
Technical depth was translated into strategic impact.
/Reduced complexity/Higher developer productivity/Faster time to market/Sustainable transformation instead of isolated projects
the turning point
Once journeys and narrative were clear, the effect was noticeable inside and out.
Sales conversations started with outcomes instead of service lists.
Internal discussions got faster, because everyone used the same structure.
Marketing became more consistent and focused.
Differentiation from larger providers became clearly visible.
the results
Puzzle no longer shows up only as an implementer. But as a partner that structures and accompanies transformation.
/Clearer positioning and differentiation in the market/Unified messaging across all teams/Structured sales enablement material
“The collaboration helped us articulate our strength clearly, not only technically but also strategically. The journey structure gives us a shared internal framework and helps us convey our value convincingly at management level.”