This tool finds where users struggle on our platform and helps you turn that into
finished designs for engineering — no design software or technical skills needed.
🎨 Studio — make designs by describing them
Just type what you want, like you'd explain it to a designer — one sentence
is enough. For anything that exists on the platform today, the assistant gathers the
evidence itself (current screen, usage numbers, session recordings) before designing:
"Design a version of the appointment card where rescheduling is one tap." "Show me the current doula dashboard and design a simpler version." "Make the booking flow feel less overwhelming on a phone."
The design appears in the preview on the right. Keep talking to change it —
every change is saved as a version (the v1v2 pills), so you can
always go back. The assistant knows our real screens and brand, can pull usage
numbers from PostHog, and will look at the current design before changing it.
Paste screenshots straight into the message box (or click 📎) — sketches, competitor apps, anything.
Paste a Figma link (use "Copy link to selection" in Figma) and it designs from that
frame. First connect your Figma account once via Connect Figma in the top bar —
links then open with your Figma file access.
📱 Phone previews it on a phone · Open ↗ full tab · Download saves an HTML file.
Copy for Figma → in Figma run the html.to.design plugin and paste → editable Figma layers.
Send to engineering creates the Asana task with the design attached. That's the handoff — done.
Conversations are shared — open a teammate's design from the sidebar and build on it.
🔍 Findings — real problems, found automatically
Every night the tool reviews session recordings from care.findraya.com and picks out
the moments users actually got stuck (rage-clicks, dead ends). Each finding shows
what happened, screenshot evidence, and a ▶ link to watch the real session.
Approve → it goes to engineering in Asana. Deny with a reason → the
analyzer learns and stops suggesting that pattern. Your denials genuinely make it smarter.
You can also ask the Studio chat things like "what did the scans find?",
"show me the videos from yesterday", or "scan the doula dashboard sessions".
💡 Tips
Talk outcomes, not pixels: "make it obvious how to reschedule" beats "move the button 20px".
Ask for options: "give me a variation" or use the preset buttons under the chat.
Not sure how something works? Ask the chat — it knows this tool.
Sessions log you out after 15 minutes of inactivity (patient-privacy rule) — just sign back in.
What this platform is
An internal tool that watches where users actually struggle on care.findraya.com,
turns those moments into evidence, and helps you produce finished, on-brand designs
for engineering — all by typing plain English.
How it works, in one breath: PostHog records anonymized sessions of the
platform → the system picks out the ones where users demonstrably struggled (rage clicks,
dead ends) → replays them, screenshots the key moments, and has AI analyze them → findings
land in the Findings inbox with evidence → you approve or deny → the same AI
designs the fix in our design system → engineering gets a pixel-accurate spec in Asana.
Example things to type
Design — the assistant gathers evidence itself, then draws:
"Redesign the availability page" — it checks the current screen, pulls sessions,
verifies which controls are actually used, starts a deep scan, and gives you a v1 with
what's verified vs. assumed
"Design a version of the appointment card where rescheduling is one tap"
"Make the booking flow less overwhelming on a phone"
Paste a screenshot or Figma link + "build this in our design system"
Investigate — real numbers, across all sessions:
"How do doulas use their dashboard?"
"How many people clicked 'Select Entire Month' in the last 30 days?" — settles
"is this feature used?" definitively
"Show me the videos of the availability page from the last two weeks" — full
list with watch links
"What did the scans find? Show me the top finding"
Act:
"Scan the 15 worst doula sessions on the dashboard" — findings in ~20 min
"Fold in the new findings and refine the design"
"Try a variation" · "Simplify" · "Before and after"
"Send v3 to engineering"
The one habit that makes it all work: when it proposes something, push
back — "what's your evidence for that?" It will separate verified from assumed and
go get the data. The tool is built to be challenged; your pushback makes it smarter.
Accounts, access, or anything broken: Al (CTO).
Technical documentation lives in Confluence → Engineering → "Raya Design Studio".