zLinq
Project Overview
Ongoing UX/UI for zLinq's telecom lifecycle platform. A Lead Designer works with the CTO in Figma on the customer dashboard — assets, savings, feed, and navigation — so the product team can ship it.
Late May 2025: NDA and MSA, then a short UI proof of concept on the customer dashboard — feed concept, widget containers, and a design language zLinq's product team could implement. The CTO wrote that the initial UI POC was very well received.
Mid-June 2025 zLinq approved a full UX/UI engagement. The first working session was 24 June 2025. First phase, from the CTO's brief: a complete Main Page redesign in a new design language — metrics, summary, and data widgets (assets, savings, add/delete columns); the feed in expanded and collapsed states; a new left nav, collapsed and expanded. Customer-facing workflows first; as little internal UI as possible for the first release.
The Lead Designer works in Figma with the CTO and a Senior Business Analyst. Weekly review, comments in the file. Designs are consumed by zLinq's product and engineering team. More than a year later the same partnership is on the next design phase of the same product.
Talk to a senior designer about a product dashboard
This is weekly Figma review with a CTO who ships — not a deck that dies at handoff. If that is the engagement you want, start at /contact-us/.
Project inquiry
Tell us what you are trying to ship
Response within 1 business day
The Challenge
zLinq sells telecom lifecycle management — software and services for voice and data connectivity, unified communications, and contact center. The customer dashboard had to show assets, savings, and vendor work without reading like a spreadsheet. The CTO needed a designer who could take operational workflows (personas on real scenarios) and turn them into a design language engineers would actually build.
Our Solution
May 2025 started as a short UI proof of concept on the customer dashboard. After that landed, zLinq approved a full engagement. The Lead Designer works in Figma with the CTO and a Senior Business Analyst: weekly review, comments in the file. First phase was a complete Main Page redesign — metrics, summary, and data widgets; assets and savings views; a feed in expanded and collapsed states; a new left nav. Customer-facing workflows first.
Technologies Used
Results & Impact
Still the design partner more than a year later, now on the next phase of the same product — not a one-off mock.
Client Testimonial
“The initial UI POC was very well received.”
Services Provided
- UI/UX Design
- Creative Design
Why Maxiom?
- Inc. 5000 listed company
- Top 5% senior engineers
- 98% client satisfaction rate
- Agile/Scrum methodology
Frequently asked questions
What did Maxiom design for zLinq?
UX/UI for zLinq's customer-facing telecom lifecycle dashboard. First phase was a complete Main Page redesign: metrics, summary, and data widgets; assets and savings views; a feed in expanded and collapsed states; and a new left navigation. Internal UI was kept as small as possible for the first release.
Who designed the zLinq work?
A Maxiom Lead Designer. The work is reviewed weekly with the CTO and a Senior Business Analyst. Comments live in the Figma file.
How does the engagement run day to day?
Figma is the working file. The CTO reviews weekly. zLinq's product and engineering team consumes the designs and ships them. Maxiom is the design partner, not the build team on this engagement.
Is the zLinq engagement still active?
Yes. The proof of concept landed in May 2025, the full engagement started in June 2025, and the same partnership is still on the product more than a year later — now a new 2026 design phase, not a one-off mock.
What was the proof of concept?
A short UI POC on the customer dashboard: feed concept, widget containers, and the new design language. The CTO wrote that the initial UI POC was very well received. That is why the full engagement was approved.
Do you hand designs off to the client's engineers?
On this engagement, yes. Designs live in Figma and are consumed by zLinq's product and engineering team. The test is whether they can build from the file, not whether the deck looks finished.
How do UX/UI engagements like this start?
Usually a short, bounded proof of concept on the riskiest surface — here, the customer dashboard — then a written engagement if it lands. Start at /contact-us/ with the product, the constraint, and who has to ship from the file.
Is this staff augmentation or a design engagement?
A Lead Designer UX/UI engagement. If you need extra developers inside your org rather than a design partner, that is a different conversation — say so on the contact form.