Skip to content
All projects
Case 03 of 06

Wieldy

A B2B SaaS for dental insurance billing, with an AI layer for the questions practices ask every day. The challenge was designing across three regulated domains without the interface becoming confidently incorrect where an error has a financial cost.

Services
Product design, AI UX, Immersion through handoff
Year
2023
Wieldy marketing page above the payments dashboard
Wieldy claims table with posting status per claim

Reporting is a primary surface.

Practice owners evaluate a billing tool by how quickly it answers questions about outstanding revenue. In B2B the operator and the purchaser are frequently different people, and the purchaser evaluates the product through the reporting screens.

Three domains, one interface.

Wieldy operates at the intersection of dental practice operations, insurance claims processing and applied AI. Each domain carries its own vocabulary, regulatory surface and failure modes. Combined in one product, the design risk is producing an interface that is confidently incorrect in a context where incorrect has a financial cost to the practice.

A complete product

From registration to the AI layer, designed as one system.

Registration and onboarding

Sign-up, identity verification and a guided first run.

Patient records

The people each claim is built on.

Insurer records

What each insurer accepts, and in what format.

Invoices and submission

Invoice construction and submission to insurance companies.

Reporting

How much revenue is outstanding, and where.

AI layer

Answers to the recurring questions practices ask.

An AI answer carries the weight of a validation rule.

The recurring questions occur at decision points where the user is uncertain whether a submission is correct. An AI response in that position sets a higher accuracy requirement than conversational features usually carry.

Grid of Wieldy screens: reports, documents, claims and patient views
Product screens
Home dashboard on a laptop surrounded by payments, credentials, admin and identity screens
Dashboard, credentials, admin and identity check
Laptop with the sign up screen and floating claims tables
Sign up and claims
Insurance payments table with a date range picker open

The difficult elements were the rules.

Domain risk translates directly into design risk, and immersion ahead of interface work was the only viable sequence. Scheduling the reporting screens last, when the purchaser evaluates the product through them, is a common and costly sequencing error.

Next projectScaelifeThe brief named the wrong user.