How Leni Health gave every woman her own private agent

Two founders, neither of them an engineer, merged two products and had a live site four weeks later. Every woman who signs up now gets her own always-on agent.

Jocelyn Pepe
Jocelyn PepeCofounder and CEO @ Leni Health, conversational women's health
The best experience with Vishnu and Agent37. Great product with great customer service and support. Would recommend 10/10!
Verified review on Trustpilot

The problem

Jocelyn Pepe has written a book about brain health. She coaches, she speaks, she runs training. All of it is delivered by her, to one person or one room at a time, and every hour of it has to come out of her own week.

“I do a lot of one-to-one coaching and a lot of keynote speaking and training and development, but it’s not scalable. So this is scalable.”
Jocelyn Pepe, cofounder and CEO, Leni Health

Her cofounder, Quinn Simpson, had already started on something next to it. They merged the two into one product and gave it a name. Leni is a private conversation for the days when something feels different and you cannot quite name it. Sleep, mood, energy, hormones, and the life around them. Not another dashboard with a chart on it. One clear next step.

What they tried

They started the way two people usually start, sharing one agent. It did not survive them. Only one model account can attach to an agent, so they could not both bring their own. Credits ran out and got passed across by hand. Two unrelated bodies of work landed in the same stream. And the product itself lived inside that one agent, where neither of them could change anything without writing over the other.

“That’s the whole thing with Leni: each person has their own agent.”
Quinn Simpson, cofounder and director of product experience, Leni Health

What was true for the two of them turned out to be the product. The reason a woman would talk to Leni at all is that it is hers: it holds what she told it, and it acts on that and nothing else. An agent shared across an audience cannot do that, no matter how good the prompt is.

What they run now

A woman signs up on lenihealth.com and Leni’s own app makes one API call. What comes back is an always-on agent stamped with her account and nobody else’s: her conversation, her files, her own hard ceiling on what it can spend. Nothing is shared between two women because nothing is shared at all.

Neither founder is an engineer, and there is no fleet for either of them to run. No server to keep up, no queue, no per-user store of chat history to design, and no seat to buy when someone new arrives. The agents answer on an OpenAI-compatible endpoint from the moment they boot, so wiring one into the product was a base URL.

“I have like one big giant storage facility. With lots of rooms, and this Leni Health is one of the rooms that my Agent can access.”
Quinn Simpson, cofounder and director of product experience, Leni Health

The outcome

  • One agent per woman, not one agent for everyone: Leni's own app makes the call at signup. What comes back carries her account and nobody else's: her conversation, her files, her ceiling on spend.
  • Four weeks from the question to a live site: Two products merged into one and put in front of real users, without a single server between them and it.
  • The founders ship it themselves: Both of them change Leni by asking their own agent for it, and neither has to think about the fleet the product runs on.

The part of Leni worth talking to is theirs. The fleet underneath it is ours.

Give every customer their own agent

One API call provisions an isolated, always-on agent with its own files, its own spend cap, and no servers for you to run.

First instance free, no card required.