CEO
Runs the studio and personally handles the first call, the scope and the proposal for every project.
Nine people.no middlemen.
Nine people in Madrid, plus three advisors who help us decide when the decision is a big one. The person you speak to on the first call is the one who will be on your project.
Team
9 people on staff
Advisors
Network of advisors and specialists
Based in
Madrid, projects across Spain and abroad
The team:
Every project has a named technical lead from day one until the final handover.
Cristian Wisultschew
CTO
Responsible for the architecture of every project and for reviewing all code that leaves the studio.
CMO
Positioning, content and acquisition. Translates what we build into language clients recognize.
Arturo Pozuelo
Blockchain expert
Designs contracts and prepares them for audit, and defines custody so end users never see a wallet.
Head of Events
Coordinates event operations and Eventnode field testing, with the system running at the door.
Héctor de la Fuente
Developer
Patri Huarte
Developer
Natalia Marshall
Graphic designer
Juan Gil
Videographer
Missing someone here?
It might be you. Send us your CV and tell us why you want to build at Nakalabs: we read everything we receive, even when there's no open role with your name on it.
Advisors:
We don't work in a closed circuit. Behind every project there's a network of advisors and specialists who advise us before we commit to an architecture, enter a new industry or sign a large contract.
A network, not an org chart
Senior profiles in security, scaling, business and investment whom we consult depending on what each project needs.
Consult before deciding
Big decisions go through someone who has already lived that problem in production before us.
Contacts that open doors
A large, highly professional network in Spain and abroad: suppliers, funds, manufacturers and technical teams.
How we work:
Four rules we apply on every project, including when they're uncomfortable.
A named lead
You know who runs your project and you talk to that person, not to an account manager.
Small team by choice
We'd rather turn down a project than accept it and staff it with people we don't know.
Written decisions
Every architecture choice is documented with its rationale, so your team can continue without us.
Bad news, early
If something slips or doesn't hold up technically, we say so in the meeting, not in next month's invoice.
Where you may have seen us:
Industry forums and events where we've taken part or been recognized.
Talk directly to the team.
No sales filter: the person who will lead your project technically will be on the first call.