Personas
Three personas built from 21 sourced observations across operator, owner, and employee groups. Every claim cites its source. Mood quotes are synthesis only - labeled clearly throughout.
People Observations from Research
Drawn from research/docs/research.md, research/strategy.md, research/docs/competitors.md, research/docs/ux-patterns.md, and research/docs/benchmark.md. Personas grow directly from these observations.
No competitor explicitly designs for the operator who has no HR training. Wellable, Woliba, and Nivati all use language ("dedicated account manager," "wellness coordinator," "program administrator") that assumes an HR professional on the buyer side. The no-HR operator is tolerated, not designed for.
Operators who cannot see a price or try a product without scheduling a sales call do not buy. Nivati, Woliba, and Wellable all require demos. Headspace Core and Gusto prove that the SMB buyer self-activates when friction is removed.
They need the product to tell them what to do next, confirm they did it correctly, and show them it mattered. They do not have the HR background to contextualize a 67% participation rate or a 7.2/10 team score.
They engage in short purposeful sessions: a Monday morning check of last week's results, a 5-minute program setup once a month, a quick invite after a new hire joins. They do not "use" the product daily - they rely on it to work in the background and alert them when something needs attention.
The operator must believe the product is worth launching AND employees must respond. If zero employees respond after 14 days, the operator's belief breaks immediately. Both must succeed in session one.
Seeing a number alone does not create a habit. The Officevibe AI-recommended-action model confirms: operators who understand what to do next stay engaged. A score without context produces no action.
The owner dashboard (aggregate team signal) is the paid feature. The emotional driver for upgrade is "I want to show the owner this is working" - not a feature checklist or team-size wall.
No competitive data confirms or contradicts this. Consistent with the role profile (office manager, EA, ops coordinator, founder in a small company) but unvalidated.
The owner sees Brio when the operator shares it or when they receive a monthly digest. Their attention span for the dashboard is under 2 minutes. They want one number, a trend, and a plain-language interpretation.
They approve budget, want proof the investment is worthwhile, and want an early warning before someone resigns. They are not curious about product mechanics.
In an SMB with no HR layer, the owner is the boss. If they could see individual data, they would be the surveillance threat. The aggregate-only model protects the product from this structural problem.
No research data on age range. Consistent with "founder or CEO" but unvalidated.
Owners who see ROI mention it in peer groups (EO, YPO, investor circles). They share to look like caring leaders, not for financial incentives. This is year-1 secondary, not primary.
Without employee participation, there is no aggregate signal. Without signal, the owner has nothing to see. Without owner value, there is no renewal. The value chain starts with employee trust.
They were enrolled by their employer. This is a fundamentally different trust context than a product someone chose to use personally. In an employer-funded tool, employees are not in a free consent context.
Before answering the first check-in, employees ask themselves: "Can my manager see my answer?" If uncertain, they do not respond honestly, or do not respond at all. This doubt must be resolved before Question 1 appears.
If the first experience feels invasive (too many questions, unclear who sees what), employees opt out mentally and never engage honestly again. If it feels safe and fast (under 30 seconds, clear privacy statement), a participation habit forms over 3 to 4 weeks.
"Your answer joins the team's anonymous score - [company name] sees only the team total, never your response." One sentence. Plain language. Before Question 1. Repeated at the same moment in every subsequent check-in, not just at onboarding. The repetition is the trust.
Limeade (11/40 benchmark score) and Typeform (14/40) show that privacy claimed but not architecturally designed erodes trust. Culture Amp (33/40) and Apple Health (35/40) earn trust through structural guarantees.
Employees in an employer-funded product are not making free choices about consent. Opt-out framing in this context is not meaningful consent. It also corrupts the aggregate signal because employees who suspect monitoring respond dishonestly.
MVP decision: N=5 flat, non-configurable by employer. No live count is shown to anyone (operator or employee) during an open cycle. The score appears only after the cycle closes and the minimum-N is met. Closed by founder decision, June 2026 - not by re-research. The legally defensible US threshold (ADA, GINA, EEOC) still requires legal counsel before launch and is deferred.
Priya - The Handed-It Operator
Chosen by diverge-then-converge. The daily driver of the product. Every V1 design decision serves her first.
Priya is 31. She has been at the consultancy three years. When the founder decided the team needed "someone to own the people stuff," Priya got the ask - without asking for it. Her actual job is office logistics, vendor management, and onboarding new hires. She now also runs the monthly all-hands, manages the holiday party, and - as of two months ago - is supposed to "run wellbeing programs." She has no HR background. She looked at a few tools and either hit a demo wall or found products that assumed she had a team of HR professionals. Her fear is not the work - it is the uncertainty. She does not know if what she is doing is making a real difference.
Context she arrives from: She Googled "how to run employee wellbeing programs for small businesses." She tried signing up for one competitor and was asked to schedule a demo. She did not schedule it. She is looking for something she can start in an afternoon without having to justify it to anyone first.
- Run structured wellbeing programs without HR knowledge (primary)
- Know if the team is struggling before someone resigns
- Feel competent and confident in a role she was given, not trained for
- Prove to the founder that the people investment is paying off
- No self-serve path: every tool requires a demo call or assumes an HR team
- No plain-language feedback: she cannot interpret 67% participation as good or bad
- She suspects employees are not filling in surveys honestly
- No "recommended next action" when the score is low
- Sees a price on the page without having to talk to anyone
- Can try it before committing (free tier, no credit card)
- Product tells her what to do next, not just what happened
- Gets a confirmation moment: "you launched a program correctly"
- Another demo-required product
- A product that assumes she knows HR terminology
- A dashboard full of numbers without interpretation
- Having to explain to employees why their responses are not private
"I don't have time to become an HR expert. I just need to know what to do and that it's actually working."
Marcus - The Checking-In Owner
The budget approver and renewal decision-maker. Not a daily driver - he checks in occasionally for a high-level read.
Marcus is 43. He founded the consultancy Priya works at. He cares deeply about his team - three people left in the past 18 months and each time he was caught off guard. He approved the wellbeing budget because he wants to know if people are happy before they hand in notice. He is not going to learn a new product for this. He wants a number and a trend, once a month, via email.
Context he arrives from: Priya showed him the product, or he received a monthly digest email with the team score. He is not discovering Brio himself in most scenarios. [?] Whether the owner or operator discovers Brio first is an open question. This persona assumes operator-led discovery, which is the primary hypothesis. See Open Question Q2 in research/docs/research.md.
- Know at a glance if the team is doing well or if something is off
- Make a confident budget decision: is the wellbeing investment worth renewing?
- See team health without accessing individual employee data
- No simple, credible team-level view without asking the operator directly
- Woliba's burnout signals by manager feel invasive and legally uncomfortable
- Officevibe was the closest analog but is now $4,999/year flat, pricing him out
- He does not want a dashboard - he wants the answer to "is the team OK?" in one read
- One number, a trend, and a plain-language interpretation
- The product explicitly tells him what he cannot see and why
- The monthly digest lands in his email and takes under 2 minutes to absorb
- Individual employee data surfacing anywhere in the product
- A complex dashboard that requires training to interpret
- Privacy language that sounds like marketing copy rather than a structural guarantee
"I don't need to know who's unhappy. I need to know if the team is doing OK as a whole before I lose another good person."
Yemi - The Skeptical Employee
The critical engine of the product. Without her honest participation, there is no aggregate signal - and without signal, neither the operator nor the owner has anything worth paying for.
Yemi is 27. She has seen "wellness theater" at her previous job: company surveys that appeared in the all-hands with "we heard you" but nothing changed. She is not hostile to Brio, but she is not enthusiastic either. Before she fills in the first check-in, she will ask herself: "Who sees this? What happens with it?" If she gets a clear, specific answer to that question before she has to respond, she will answer honestly. If she does not, she will either skip it or put in a non-answer.
Context she arrives from: She received an invite from Priya. The invite said it is anonymous. She has heard that before.
- Know with certainty that her response is private before she responds
- Spend under 30 seconds on the check-in or she will feel it is not worth the interruption
- Feel that the company is acting on what she says (otherwise the check-ins are performative)
- Has been told surveys are "anonymous" before but in a small team she was probably identifiable anyway
- Does not trust "anonymous" if the employer controls the platform and the data
- Feels that wellbeing programs often track performance, not wellbeing
- One specific sentence before Question 1: exactly what is shown to the manager, exactly what is not
- The format protects against inference: her response only appears as part of a team aggregate
- The company does something visible in response to aggregate feedback over time
- Questions that feel like performance review disguised as wellbeing
- Survey invitation that leads with company branding, not the privacy guarantee
- Check-ins that take more than 30 seconds
- Any moment that feels like data collection rather than genuine support
"I'll participate if I actually believe no one can see my answer. But I've been told that before. Show me exactly how it works, not just a promise."
Primary Persona Selection
Three options were considered. The choice traces directly to the product's value chain.
She is the buyer, the daily driver, the activation bottleneck, and the person whose behavior most directly determines whether the product has any data to show. Every V1 design decision serves her first.
He approves the budget and decides on renewal. Without his conviction, there is no subscription.
Without their participation, there is no aggregate signal, which means neither the operator nor the owner sees anything worth paying for.
Chosen: Option A - Operator. The operator decides to try, activates the product, invites the team, and is the first to experience value (or not). The owner is downstream: they see value only after the operator has set things up. The employee does not choose the product at all. Every design decision that serves the operator's competence and clarity also, indirectly, serves the owner's need for signal - because a competent operator runs programs that generate employee responses.
Source: research/docs/research.md Key Conclusion 3, research/docs/aarrr.md Activation section.
What We Do Not Know About People
Open unknowns that affect design and product decisions. Some are closed by founder decision; most remain open.
| Unknown | Why It Matters | Status |
|---|---|---|
| Does the operator or the owner discover Brio first? | Determines primary acquisition channel and landing page message | Closed - founder decision Default established: operator-first. Landing page hero speaks operator language; owner-trust block on same page. Reversible by paid A/B acquisition test. See research/strategy.md D3. |
| What percentage of SMB employees honestly participate in anonymous employer surveys? | If the answer is low even with privacy architecture, H1 is broken and the product premise needs revision | [?] |
| Does a structural privacy argument (subscription model = no incentive to monetize data) outperform a policy-based one in driving participation? | Affects which message is primary on the product page and in employee onboarding | [?] |
| What is the operator's actual daily schedule and digital context when they engage with a wellbeing tool? | Affects notification timing, digest cadence, and whether the product needs a native app | [?] |
| How do SMB employees perceive wellbeing programs differently from large-enterprise employees? | Large-company research may not apply: in a 15-person team, everyone knows each other, which changes the inference risk and trust calculus | [?] |
| At what point does participation drop naturally (novelty wearing off), and what reverses it? | Affects retention design: when to prompt operators, when to refresh program options | [?] |
| Owner age range and digital behavior | Affects dashboard design (mobile vs. desktop) and the format of the owner digest | [?] |
Why three personas, not four: a fourth persona (HR professional at a slightly larger SMB) was considered and discarded. The research confirms that designing for an HR professional shifts the product into the territory of all current competitors. Brio's differentiation is precisely that it does not assume an HR layer. Source: research/docs/competitors.md, "What Is Missing Across All" - gap 1.