Context should travel with the person doing the work.
The useful version of AI is not trapped in one chat window. It moves with the thread of work: the docs, decisions, meetings, tickets, blockers, and people behind the answer.
About Peppermint
Work should not lose its memory.
Every team has the same hidden tax: the time spent reconstructing what already happened. The decision buried in Slack. The context from last week's meeting. The reason a ticket changed. The thing someone knows, but has to explain again.
Peppermint exists to keep that thread intact.
The why
The synchronization tax is eating modern work.
Modern work happens across too many surfaces for any one person, document, or AI tool to hold the whole story. So people become the memory layer themselves.
They repeat context, chase updates, write status summaries, prepare handoffs, and answer the same questions again and again. That is the synchronization tax Peppermint is built to remove.
What Peppermint is
A private memory layer for the thread behind work.
Peppermint is a private AI memory and work-context layer for teams. It keeps the thread of work intact across tools so AI twins can answer, coordinate, and delegate with source-grounded context.
The product is not another chatbot. It is a way for people and teams to give AI twins the context they need to answer safely, carry work forward, and reduce the constant need for synchronous coordination.
What we believe
The app changes. The memory should stay yours.
Memory only works when people trust it.
Peppermint is built around private, permissioned context. The goal is not to watch people. The goal is to stop forcing people to rebuild the same context again and again.
The best AI teammate starts from the source.
A twin should not guess from a blank prompt. It should answer from the work that actually happened, with enough source context for people to trust what comes next.
The founders
Built from years of remote-work scar tissue.
Peppermint comes from Liam Martin and Rob Rawson's long-running work on how remote and async teams actually operate. They co-founded Time Doctor, built Staff.com, co-authored the WSJ-bestselling book Running Remote, and helped turn remote work from a fringe operating model into a global default.
Liam Martin
Liam has spent 15+ years measuring the coordination overhead inside remote teams. Peppermint is the next version of that work: software that helps AI keep the thread of work moving.
Rob Rawson
Rob co-founded Time Doctor with Liam and co-authored Running Remote. His work has focused on building systems that make remote teams more accountable, async, and operationally clear.
15+ years building and studying remote teamsTime Doctor, Staff.com, Running Remote, and PeppermintA WSJ-bestselling operating thesis, now becoming software
Where this is going
You should not need to be in every room for work to keep moving.
Peppermint is for founders, operators, builders, and teams who are tired of starting over. Your tools should remember the thread, respect the source, and help your AI twin answer from real work context.