Constructing
WRK.01Case study
SaaS & productTurning emotional support into an intelligent digital product
Built end to end by Matter — product strategy, brand, the public site, the employer offering and the web app behind them, for an AI-powered, non-clinical companion that gets to know a person over time and helps them see what's underneath.
- Client
- Talk to Kaya
- Category
- AI consumer product
- Status
- Live product
- Started as
- An idea, a founder and a voice note
- Duration
- Ongoing — live at talktokaya.com
- Scope
- Product strategy · Brand & identity · Marketing website · UX & interface design · Web application · AI product design · B2B offering · Launch infrastructure
The problem
Support is usually available exactly when it is hardest to ask for: late, alone, and below the threshold that would justify calling anyone. The products that fill that gap tend to be either a clinical service with a waiting list or a journal app with a chat box bolted on — and the workplace versions ask people to trust that their employer cannot see what they wrote, without ever showing why.
Objectives
- 01Make support available at the moment it is needed, not at the next appointment
- 02Present the tools as one place to put things, not a feature list
- 03Give employers a signal about their people without a route back to a person
- 04Be explicit about what the product is and is not
Work delivered
One project. Every layer.
01
Product and experience strategy
The shape of the thing: which modes of support belong in one product, how Kaya moves between just listening and helping someone move — regulate, release, reflect, reframe, recalibrate — and where the line sits between a companion and a clinical service.
02
Brand and the public site
Two registers of one brand. talktokaya.com is calm and cinematic — a glowing orb over still water, conversation fragments surfacing beside it, and one line up front: hey, let's talk. Inside the web app, the octopus mark and wordmark carry the brand.
03
The product and its memory
Weekly recap, journal, unsent letters, glow notes, hold space and take me there — held in one place, with conversational support that connects conversations, entries, check-ins and letters across weeks. The site shows that memory as a twelve-week heatmap rather than describing it.
04
Kaya for Teams
The employer offering and its own page: a dashboard preview covering wellbeing signal, adoption and retention, department breakdowns behind a hard anonymity floor, campaigns, SSO and SCIM, and data residency — with book-a-demo as the route in.
05
Privacy, answered in public
The question a team will actually ask — can my employer see what I wrote? — answered on the page with a plain "No." and the storage-layer reasons behind it: content bound to its owner, administrators limited to functions that return figures, and an anonymity floor applied after every filter.
06
Launch foundation
The web app at app.talktokaya.com with account sign-up and explicit consent for what Kaya stores, a try-the-demo route from the homepage, a stay-in-the-loop list, and the contact and demo-booking paths for employers.
StackNext.jsVercelConversational AIPostgres row-level security
Before
- Support available at the next appointment, not at 2am
- A feature list where a companion should be
- Workplace tools that ask for trust without showing why
- Nothing that remembers you between the hard moments
After
- Six tools, one place to put things
- A companion that remembers patterns across weeks
- An employer signal with no route back to a person
- What it is and is not, said before it is asked
Talk to Kaya is a non-clinical support product and not therapy, medical treatment or a crisis service. No usage figures or outcomes are published for it; dashboard figures shown on its site are sample data.
Live at talktokaya.com
