UI is what they see; UX is whether they finish
UI: hierarchy, colour, type, cards, icons, spacing. UX: the sequence, the default, the error, the time to WhatsApp. A gorgeous card that hides the price until step four is a UI win and a UX loss.
Owners should judge UX with a stopwatch and a cheap Android, not with “my cousin liked the Dribbble shot.”
Why owners mix the two on invoices
Agencies sell one SKU because clients buy one SKU. That is fine if the SOW names both. It is not fine if “UX” meant a colour pass. Ask which frames are wireframes and which are visual.
What UI work looks like in Figma
Components, states (hover, disabled, error), a type scale, and spacing that a developer can copy. Brand tokens belong here if you have a kit. If you do not, you are inventing a brand: buy branding first.
UI without states is a poster. Buttons that only exist in “default” fail the first invalid GSTIN.
What UX work looks like in bookings and ops
Task flows: find → choose → confirm → pay → proof. Empty states when the calendar has no slots. A path when UPI bounces. Ops dashboards: the next action on the first screen, not a chart nobody uses. See SaaS dashboard UX.
UX also includes words. “Submit” is not a CTA. “Send on WhatsApp” is. Writing: microcopy.
When pretty UI hides a broken journey
A Chennai clinic site with a cinematic hero and a contact form that emails a Gmail nobody checks is a lead killer. So is a D2C checkout that forces an account before UPI. Catalogue of failures: website UX mistakes.
If paid traffic lands on that hero, you are buying UI for Google and Meta to admire. Fix the path: landing UX.
Dribbble shots vs a clinic that cannot book
Awards do not ring the reception phone. If the primary job is a booking, the first fold must start that job. Visual craft still matters for trust — after the path is obvious.
Who should own which in an SME
Founder owns the job and the constraint (COD, Tamil, GST). Designer owns structure and UI. Developer owns what the file did not specify. Marketing owns claims that must match the screen. When everyone “has an eye,” you get seven heroes.
Decision rights belong in the brief: how to brief.
How to brief so you are not paying twice
Write the user, the job, the device, and what happens after success. Attach brand files. Circle three competitor sites you like *for a reason* (“clear fees,” not “modern”). Anti-references matter more than inspiration dumps.
If you cannot write that page, you are not ready for visual UI. Start with a prototype conversation: prototype vs finished UI.
How Brevia splits UI and UX in the ₹50,000 pack
UX structure in wireframes, UI in high-fidelity Figma, proof in a clickable prototype, then specs for website or Next.js build. Chennai HQ; India-wide delivery.
Map your job on a consultation or contact thread.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.