Contact
Contact Nico van Zyl
The best way to start a conversation is to share the product problem, who it affects and what must become possible. Public contact routes are listed below.
Good reasons to get in touch
I am a strong fit when a startup, scale-up or enterprise team needs senior product-design judgment and production-minded execution in the same engagement. Typical work includes clarifying a technically complex product, designing an interface or workflow, building a design system, improving an existing product, or carrying a validated direction into frontend code.
I am less useful for requests that only need high-volume visual production, speculative work without access to the real problem, or delivery that separates interface decisions from user and technical constraints.
What to include
A useful first message names the product and audience, the current problem, the outcome you need, the stage of the work, important technical or business constraints, the people involved and any real deadline. Links to a working product, brief or repository are helpful when they are safe to share. Please do not send credentials, private customer data or confidential material through a public channel.
No availability, response time or engagement is implied by this page. A conversation is the place to confirm fit, scope, timing, commercial terms and the appropriate private channel for further material.
Public channels
LinkedIn is the clearest public route for professional enquiries. GitHub is appropriate for public technical context, and X is available for a shorter introduction. These links identify Nico’s public profiles; they are not automated booking or support systems.