Software

The screens people
sit inside all day.

Soluxain does enterprise software design and UX audits — the kind of application work where people use your tool every day and it fights them. Claims queues, dashboards, admin tools, configuration screens. Dense, unglamorous, high-consequence software where a confusing layout is not an annoyance — it is a denied claim, a missed deadline, or three hours a day lost across a team. We work in Figma and Figma AI, in LLM tooling, or in both, depending on what your team already runs.

Request an audit See the work

Placeholder — swap for a real screenshot

Enterprise healthcare

Claims workflow redesign

A pharmacy claims review process spread across three disconnected applications. Auditors lost their place constantly, training took months, and throughput sat flat at thirty reviews a day.

What we did. Contextual inquiry with four users across two roles. A heuristic read of every screen in the existing flow. Current-state and target-state flow models. Iterative wireframes, then an interactive prototype taken through two rounds of moderated usability testing before a line of production code was written. Three applications collapsed into one wizard-driven screen.

This redesign has exceeded our team’s expectations. The ease at which the users can now complete tasks is very impressive, and onboarding new trainees will be much easier with this new process.
Supervisor, claims audit team

30 → 45: quality claim reviews completed per day, per auditor
12 → 7: minutes to complete a single claim review
2.5 hrs: returned to each auditor every working day
3 → 1: applications needed to finish one review
−50%: time required to train a new employee

Enterprise healthcare

Second case study

Placeholder. Same shape as the one above: the situation, the constraint, the method, the measured outcome, and a line from somebody who had to live with the result.

Numbers beat adjectives, and one sentence from the person doing the work beats both.

To fill in

What this section needs

The situation before, in one sentence a stranger would understand
Who the users were and what their day looked like
Research method and how many people you talked to
What you made: flows, wireframes, prototype, design system
Five measured outcomes, before and after
One quote from a user or a stakeholder

How we approach software design

Most engagements start with an audit, because the expensive mistake is redesigning the wrong thing beautifully.

Heuristic analysis and UX review

Every screen measured against established usability principles, with findings ranked by how much they cost you rather than how much they bother us.

Severity-rated and actionable.

Competitive landscape

What your competitors solved, what they got wrong, and which conventions your users already carry in their heads from using someone else’s tool.

Two to three rivals, torn down.

Figma, Figma AI, or LLMs

Flows, wireframes, and interactive prototypes real users test before engineering commits, built in Figma with a component library your developers build against — variants and states documented. Where an LLM workflow gets there faster, or where your team already lives in one, we work that way instead. You pick, or we recommend and you decide.

AI compresses the iteration, not the thinking.

Start here

The audit

The cheapest way to find out whether the problem is the interface, the workflow, or the assumption underneath both. Fixed scope, fixed price, no obligation to continue.

We walk what you have the way your users actually move through it, benchmark it against your competitors, and measure it against usability principles settled long before anyone called this a discipline. You get findings ranked by impact and effort, and a roadmap any development team can act on — ours or yours.

What you get

Heuristic review of the current experience
Competitive teardown of two to three rivals
Findings prioritized by impact and effort
A redesign roadmap you own outright

Request an audit

Common questions

What does a UX audit actually produce?

A findings report ranked by impact and effort, a competitive teardown of two or three rivals, and a redesign roadmap any development team can act on. Fixed scope, fixed price, no obligation to continue.

How long does an audit take?

Two to three weeks for most applications. Larger platforms with several user roles take longer, and we tell you which before starting.

Do you work with our existing developers?

Usually, yes. Most software engagements end in a documented handoff — flows, prototypes, and a component library with variants and states — so your team builds against something real rather than a picture.

Do you use Figma or AI tools?

Both, and which one depends on your team. Figma and Figma AI where you need a component library engineers can work from. LLM tooling where it gets to a tested answer faster. We recommend, you decide.

Have something that needs fixing

Tell us what you have and who uses it. We come back with what is wrong, what it is costing you, and what fixing it would take. If nothing needs fixing, we say that too.