zLinq
Project Overview
UX/UI design 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.
Maxiom is the UX/UI design partner on zLinq's telecom lifecycle platform: SaaS dashboard design in Figma for the customer-facing product, handed to zLinq's engineers to ship. Enterprise product design: information architecture, interaction design, and a design language the product team can implement.
First phase was a complete Main Page redesign of the customer dashboard. Metrics, summary, and data widgets (assets, savings, add/delete columns). An activity feed in expanded and collapsed states. A new left navigation, collapsed and expanded. Customer-facing workflows first; as little internal UI as possible for the first release. Widget containers and the feed concept were proven in a short UI proof of concept before the full dashboard redesign.
A Lead Designer works in Figma with the CTO and a Senior Business Analyst. Weekly review, comments in the file. More than a year later the same UI/UX design engagement is on the next design phase of the same SaaS dashboard product.
Talk to a senior designer about SaaS dashboard UX/UI
This is weekly Figma review with a CTO who ships — UI/UX design, not a deck that dies at handoff. If that is the engagement you want, start at contact us.
Related
Project inquiry
Tell us what you are trying to ship
Response within 1 business day
The Challenge
Our Solution
Technologies Used
Results & Impact
Impact
Client Testimonial
The initial UI POC was very well received.
Services Provided
Why Maxiom?
- Software since 2002
- $100M+ in contract value
- 221+ clients
- Top-rated on Clutch
Frequently asked questions
What did Maxiom design for zLinq?
UX/UI for the customer-facing telecom lifecycle dashboard. First phase was a complete Main Page redesign: high-fidelity UI for metrics, summary, and data widgets; assets and savings views; an activity 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. Weekly review 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 same UX/UI partnership is still on the product more than a year later — now a new design phase, not a one-off mock.
What was the proof of concept?
A short UI proof of concept 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.
Do you hand designs off to the client's engineers?
On this engagement, yes. Product design handoff is the Figma file: zLinq's product and engineering team consumes it and ships. 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 UI proof of concept on the riskiest surface — here, the customer dashboard — then a written UX/UI 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. Extra developers inside your org is a different conversation — say so on the contact form.