Use Case
The scope call. The prioritisation trade-off. The "let's not do that" that saves two weeks of work. It all happens — then vanishes into a Slack thread, a meeting that wasn't recorded, or the gap between someone's brain and their keyboard. Flints catches it before it's gone.
The problem
You know the question. It comes on Slack at 4pm. It comes in a PR review. It comes from the engineer who wasn't in the meeting. It comes from you, three weeks later, trying to remember why you chose approach A over approach B.
The decision was made. The reasoning was sound. But it lived in a meeting, and meetings are where context goes to die.
You don't have a decision problem. You have a capture problem — and it's not just yours.
It's not only PMs making decisions. Your designer just chose a pattern in a stakeholder review. Your engineer made an architecture call during a pairing session. Your team lead resolved a scope conflict over lunch. All of it matters. None of it lands anywhere the rest of the team — or your AI tools — can reach. So decisions get re-litigated, context gets repeated, and everyone spends their energy re-explaining instead of moving forward.
How Flints fixes it
After any meeting or conversation — anyone on the team: Option+Space, type the decision and the reasoning, pick "Decision" as the type, hit save. Three seconds. The whole team can see it. No one has to ask.
It's not just your captures — it's your designer's, your engineer's, your team lead's. When anyone on the team logs a decision, feedback, or learning, it lands in the shared project instantly. Everyone's context becomes everyone else's context.
Writing a PRD? Prepping a stakeholder update? Your AI already has every decision, constraint, and trade-off from the project — including the ones your teammates captured. No pasting, no re-explaining. Just ask for what you need.
A day with Flints
Sprint planning — you descope the admin dashboard
You capture: "Decision: Pushing admin dashboard to next sprint. Users need the export feature more urgently — 3 enterprise accounts waiting on it."
Customer call — they request bulk import
You capture: "Feedback: Acme Corp needs CSV bulk import for onboarding — they have 2,000 records to migrate. Third customer to ask for this in 2 weeks."
Your designer captures a UX decision you didn't know about
You see a notification: "Decision: Going with inline editing instead of a modal for settings — tested both in the prototype, inline had way less friction." You didn't need to be in the room. The context is already shared.
You ask your AI to draft the Q2 roadmap
Your AI already knows which features got descoped and why, what customers are asking for, the UX decisions your designer made, and every trade-off the team has captured. The draft it produces actually reflects reality — not a hallucinated version of your product strategy.
Engineer asks "why aren't we building the dashboard?"
They find the decision in Flints — the reasoning, the trade-off, and the customer data that drove it. No Slack thread archaeology. No "let me find the doc." The answer is right there.
Built for your workflow
"We're going with Stripe over Paddle because of multi-currency support and our existing integration."
"What if we let users create templates from their most common entry patterns? Could reduce capture time for power users."
"Should we charge per-seat or per-workspace? Need to model both before pricing review on Friday."
"3 customers this week asked for bulk export. Moving from nice-to-have to must-have for Q2."
"Enterprise pilot converted to annual contract. The export feature was the deciding factor — good call prioritising it."
"Users don't read onboarding emails. The in-app tooltip had 4x more engagement. Shifting all onboarding to contextual UI."
Free 14-day trial for your whole team. No credit card. Set up in under a minute.