HealthTech SaaS · India · Creware Technologies
A practice-management web app for Indian nutritionists and dietitians.

Role
UX, UI, IA, visual design
Company
Creware Technologies, in-house
Research
15 interviews, 38-person survey, 25h shadowing
Output
8 core modules, full web app, dev handoff
Status
I kept meeting dietitians who spent more time on spreadsheets than with clients. The tools weren’t bad. They just didn’t talk, so she became the glue.
50 to 150 clients. Five or six apps. Nothing shared between them.
From the survey of 38 practitioners
25 of 38
lose track of who has paid, who hasn’t, and when to renew
23 of 38
struggle to track clients and appointments across tools
20 of 38
find client management manual and time-consuming
27 of 38
have no single place to see how the business is doing
The reconstruction tax
No single task is the villain. The switching is: every hop between apps means rebuilding context from scratch.
15 interviews, a 38-person survey, 25 hours of shadowing. I expected “the tools are too complex”. They had mastered their tools. The exhaustion was being the glue between them.
A practice, before Fitify
Seven stages, the same pattern: familiar tools, joined together by hand.
Composite personas built from the interviews.
I used each tool for real tasks and looked for where the workflow broke, not for feature counts.
Assessed against publicly documented features.
“A better tool” meant a feature race. “The system that connects what they already do” didn’t exist yet. Scope, architecture and positioning shifted in week one.
How might we make clients, billing and diet plans see each other, so a dietitian never has to copy information between tools again?
Principles
Connect first, polish second
Build for the practitioner, not the patient
Modular, so it scales without bloat
Design rules
One source of truth
Automate the maths, not the judgement
Familiar, not clever
Deliberately not
Clinical records and insurance
A client-side food tracker
Heavy document authoring
Forecasting
I built the information architecture before any visual design. Version one didn’t survive contact with the personas.
The final structure: 8 core modules, plus five calculators and an FAQ.
Every module answers a pain from the research, and the dashboard ties them together.
Before: five or six apps that share nothing. After: one dashboard that sees all of it.
Why every list screen looks the same
Filters stay on the page
Not behind a “Filter” button. Excel people expect to see what they can sort by.
Ten rows, then pagination
Every table. Short enough to scan.
One breadcrumb, one title
The same place on every screen.
Same layout, module to module
Learn Clients and you know Leads, Billing and Offerings.
Status is never colour alone
A tick or a cross beside the word.
Dashboard
Active clients, sales, balance to collect, today’s appointments and birthdays, and upcoming renewals.
Answers: “no single place to see how the business is doing.”
Four numbers on top
Active clients, sales and balance to collect: the business at a glance.
Today’s birthdays
A reason to message a client that isn’t about money.
Today’s appointments
Who is coming in, without opening a calendar.
Today’s lead follow-ups
Leads stop dying in message threads.
Upcoming renewals
Renewals get chased before they lapse, not after.
Balance receivable
Who still owes, and how much.
Diet chart reminder
Which plans are due today.
Offerings
A dietitian sells three things: products, services and consultations. So Offerings has three tabs, one for each, with stock, pricing and tax in the same place.
Answers: in walkthroughs, “Offerings” alone confused people, so I kept the umbrella and made everything inside it plain.
Clients
Not every client is the same kind of client. Three tabs: service plans, products, consultations. Same table in each, so nothing has to be relearned.
Answers: records scattered across Excel sheets.
Food and Recipe
Create a recipe once, with its calories, and reuse it in any diet chart.
Answers: rebuilding meals from scratch for every plan.
Billing and Expenses
Money comes in three ways and goes out one. Three tabs for service, product and consultation billing, and a fourth for expenses, with totals, discounts and balances added up for her.
Answers: “I lose track of who has paid.”
Diet Chart
The heart of the product. Pick a client, build the week from saved recipes, then mail it, download it or send it for approval.
Answers: plans lost in WhatsApp chats.
Still the weakest screen. Building the week deserves a proper planner view. Next on my list.
Leads and Appointments
A lead is a conversation that hasn’t become a client yet. The Leads tab follows each one from New to Converted or Dropped. The Appointments tab keeps the day’s bookings right beside it.
Answers: leads forgotten in message threads.
Employees
Only clinics see this one. The Attendance tab marks who is in today, and Employee List holds roles and details. Solo dietitians never see it.
Answers: Karthik’s “I can’t see what’s happening across the clinic.”
Calculators
Calorie, body fat, BMR, 1RM and macro calculators, one click away in the sidebar, so the numbers behind a plan don’t need another app.
The system underneath
Roboto for dense, readable data, seven colours with clear jobs, a 12-column grid and a 16 to 48px spacing scale.
Live at fitify.co.in. Five or six daily tools now have one home. Usage hasn’t been measured yet, so I’m not claiming impact I can’t show.
What’s next
A client progress loop
Feeds plan-following back to the dietitian, closing the “once I assign a plan, I have no idea how they follow it” gap.
Diet-plan templates
Reusable plans across clients, the daily time-saver practitioners asked for most.
Operational analytics
Trends and forecasts, once there’s real usage history to learn from.
Fragmentation is a design problem, not a feature gap. The most valuable thing I built was connective tissue.




