Intura a reflection journal for the people who lead.
- Shipped
- Mar 2026
- Platforms
- iOS and web
- Kind
- Consumer app, leadership
- Team
- One person
A journal for people who lead, and a coach that has read all of it.
You answer the same three questions each evening: what mattered, who mattered, what is still on your mind. Over months that becomes a record, and the coach reads it back and tells you what you keep doing. It is for managers, so it is built for the one thing a manager cannot risk: there is no database and no journal text on any server. Every note lives on your device and syncs through your own iCloud.
- In numbers
- 454commits0database rows, by design1person
Everyone who leads carries the same load in their head.
Who is stuck, who said what three weeks ago, which conversation has been avoided twice. It never gets written down, because writing it down means keeping a file on your colleagues, and nobody wants that file sitting on a company server.
Intura is that file, built so it can only ever live with you. You write a few lines after a one to one. The coach reads them, remembers across weeks, and asks the question you were avoiding.
Four things it does, and the decision behind the app.
Reflection is an important leadership muscle. Also love the focus on privacy and clarity over noise.
There is no database. Not a small one. None.
The server is completely stateless. No Postgres, no Redis, nothing that persists between requests. Every coaching note lives on your device and syncs through your own iCloud. The app sends its notes up with each request and gets the updated version back, and the server keeps no copy of what it was given.
What that does not mean is that the words evaporate. The request reaches a model provider, which holds it under its own retention terms, and the app reports usage to an analytics service. Statelessness removes my copy, not every copy. A privacy claim that overstates itself is worth less than one that does not, so this one is drawn where it actually falls.
It makes some features harder and a few of them impossible. For an app where you write honestly about the people you work with, that was the right trade.
Not one prompt. Assembled at request time.
A persona, the instructions for this particular endpoint, and a shared block of voice rules whose main job is stopping the model from writing like a model. Managers get ten leadership frameworks, among them Radical Candor, Nonviolent Communication and The Coaching Habit. Individual contributors get ten of their own. The coach answers in whatever language you wrote in.
- App
- Next.js on Vercel, stateless
- Memory
- On device, synced via iCloud
- Model
- Claude Sonnet, via Vercel AI Gateway
- Chat
- Server sent events, token by token
- Prompts
- Composed from markdown at request time
- Tracks
- Manager and IC, ten frameworks each
Comments from leaders when Intura launched.
Posted publicly on LinkedIn, by people who lead teams for a living, which is exactly who the app was built for.
“Despite considering myself a very reflective person I rarely had the diligence to write these things down. A lightweight tool like this — especially one that helps surface patterns over time without creating more admin overhead — feels intuitively useful. Reflection is an important leadership muscle. Also love the focus on privacy and clarity over noise.”
“This is fantastic, and valuable for busy leaders. I can't wait to get in there and try this out — have no doubt this will be a game changer for organization, prioritization and pattern spotting.”
“Love this! I've always found journaling and reflection to be incredibly helpful. But it requires consistency so having this as a coach would be amazing.”
“Having an app to help me remember journaling would be great. Even better if it has some useful insights. I'm also more likely to try an app with privacy awareness.”
James LunanProduct Management“This is such a great idea, and I know the UI design will be spot on too!”
“Very cool and so valuable for people managers.”
Journalling is a habit, and a habit is the hardest thing to ship.
The product does what it says. The problem is the writing. It is a new habit, it lands at the end of a working day when there is least of you left, and the phone is the hardest place to do it. Quality was never the question; staying with it is.
Measuring it is harder than it sounds. The signal is keyed to an install rather than a person, so a new phone reads as somebody new, and the server keeps nothing that could tell me otherwise. I can see that people stop. I cannot see which of them came back on a different device, and I cannot see why any of them left.
- What it is not
- Not a quality problem. The people who keep it going say in public that they learn something about how they lead, which is the whole promise.
- Being tried
- Shorter prompts, a weekly summary worth coming back for, and meeting people at a moment they already reflect instead of asking them to invent a new one.
Everything on this page was designed, built and shipped end to end.
The design, the code, the App Store listing, the support replies and the marketing that got anyone to look. If you have an idea and the means to back it, that is the whole offer: I can carry it from a conversation to a thing people use.
Smaller doors too: coaching someone building their own product, or taking yours apart with you and handing over how I solved the part you are stuck on.
- What that covered here
- 01The constraint that decided the architecture02A stateless server, with the notes on the device03The coach, assembled per request rather than one prompt04The iOS app and the web app05The launch, and the people who replied to it