Services
Product design first. Brand and web when you need them.
Software designed for the staff and patients who use it every day, with the healthtech teams who build it. Every engagement starts with a day alongside your users.
What gets designed
Designed for efficiency.
Product design
Apps and platforms for the people giving and receiving care.
What changes: staff adopt it, and the renewal has a case.
Often includes
- Workflow maps
- Prototypes tested with real users
- Screens your engineers build from
Research
Time with your users, wherever the work happens.
What changes: requirements come from the floor, not the RFP.
Often includes
- Shift shadowing
- Ride-alongs
- Interviews with staff and patients
- A written handoff
Design systems
A library your engineers build from.
What changes: designs your engineers build once, not twice.
Often includes
- Components matched to your codebase
- Usage notes
Brand and web
When the company needs to look as strong as the product.
What changes: buyers and investors see the quality before the demo.
Often includes
- Brand identity
- Marketing site
- Sales collateral
- Investor decks
How pricing works
Scoped and priced after the calls.
A first call on what’s happening with your users, then a few more on what fixing it is worth to the business. After that, a written proposal with options, each with a goal and a price.
How it starts
Every engagement starts with a day alongside your users.
A sample day shift · 07:00 Huddle · 08:00 Shadow the shift · 12:00 Lunch · 13:00 Walk the workflow · 15:00 Sort the notes · 17:00 Debrief · 18:00 Handoff
1 Meet the people
A day with the staff or patients who use the product, from the morning huddle to the end of the shift.2 Agree on the path
A written handoff: what the day showed, what to fix first, and which way of working fits.3 Stay through the build
Design reviews with your engineers until it ships, so what gets built is what was designed.
Questions founders ask
The short answers.
Anything else, bring it to the call.
What does it cost?
Price follows the problem. After the first few calls comes a written proposal with options, each with a goal and a price.
Do you work with our engineers, or hand off files?
With them. Design reviews run alongside the build until it ships, and designs use the components your engineers already have.
Do you need access to our users?
Yes, for at least a day. Every engagement starts alongside the people who use the product, on site or over video.
We don’t have a designer yet. Is that a fit?
Yes. Medtel and TribeHealth both had no designer when the work started.
Do you design for patients, or only for staff?
Both. Past work includes TribeHealth’s patient and provider platforms, Wellen’s exercise program for women 50+, and SuperAwesome’s mobile allergy card.
Get your week back.
Thirty minutes on one workflow your users work around, and whether the fit is right.