Key takeaways
- Coaching gets better with more context; adoption collapses when people feel watched.
- Lucy resolves it by design: she never changes your systems, managers see team-level data and never your prompts or mistakes, coaching stays private, and contracts prohibit surveillance.
- Lucy works for the person, even though the company pays, and that is not a setting an employer can flip.
The privacy paradox
Personalized coaching gets better the more context it has. Adoption collapses the moment people feel watched. Every observation-shaped product has to answer for that tension. Most monitoring tools answered by collecting more and explaining less, which is why they read as surveillance, and why people hide their real work from them.
The distrust is rational. Most workplace technology has served the company at the worker’s expense, so people reasonably assume the next deployment is being done to them. That assumption has to be answered with architecture and evidence, not reassurance.
Trust is the first link
- Trust
- Value
- Adoption
- Capability
- Scale
Nobody adopts what they don’t trust. Break the first link and everything downstream fails, which makes trust the load-bearing wall of the company rather than a compliance posture. An AI investment your people don’t trust is an AI investment that doesn’t land.
Visibility, confidence, control
What Lucy can capture
- Text from the apps you work in
- Application and window context
- Interactions with AI tools
- Behavior signals like tool switching
What Lucy never captures
- Passwords
- Camera or webcam
- Anything outside configured hours
- Files on your disk that aren’t part of your coaching
Visibility: every capture is explainable. Confidence: Lucy is read-only by design and never writes to your systems, you control screen content retention, and processing runs on Lucy Labs’ secure infrastructure and the trusted AI providers we use. We are vendor-, cloud- and model-agnostic and name the providers and regions for your deployment. Control: you can pause anytime and search, filter, redact or delete your captured content yourself, with more user controls planned.
Whose side is Lucy on?
Lucy works for the person, even though the company pays for her. Coaching is private. Managers see team-level patterns gated by a minimum team size, never prompts, struggles or mistakes; small teams show managers no team totals. The one exception is the person’s to grant: they can choose to share their own progress. The skills they build go with them; what they build for work stays with the company.
One architecture clears every gate
For a business, the same posture that earns employees’ buy-in also clears IT, security, legal, procurement and the works council in one pass. IT keeps the keys: the tool policy is the boundary Lucy coaches within. The organization is the data controller for its coaching; Lucy Labs is the processor. Works councils get commitments in writing.
What we will not sell
We sometimes get asked for exactly how much time each employee spends on every task, for staffing decisions. Our answer is no, even when it costs us the deal. Our terms prohibit using Lucy for employee surveillance, ranking or disciplinary action. The same boundary that disqualifies surveillance buyers earns adoption from everyone else. The full architecture is on the Trust page.
Next: How Lucy learns what works.
Sources and notes
- Based on Lucy Labs’ internal product design (draft, October 2026).
Founder & CEO of Lucy Labs. Twenty years running enterprise transformation by hand in big tech and Global 2000 companies, now building it into software.
