An AI memory people can trust.
An AI memory for freelancers and small teams. It detects decisions — scope, dates, prices — inside email and Slack threads, then asks a human before updating anything.

In 60 seconds
Problem
Scope, date and price decisions get lost in email and Slack threads; nobody can say later who agreed to what.
What I did
Built an AI loop that detects changes, then asks a human before updating anything — with the source for every claim.
Result
22
sign-ups and 15 workspaces in the last 90 days
Admin dashboard · 4 Nov 2026
My call
I ruled out auto-applying AI-detected changes: nothing changes without one deliberate click, until real accept rates earn automation category by category.
01
The problem
Freelancers and small teams agree scope, dates and prices in threads. When something changes, nobody can find what was decided — or prove who agreed to it.
02
My contribution
Led product strategy, research and design from concept to launch.
Designed human-in-the-loop AI workflows: every AI claim shows its source and confidence.
Built a tokenised design system (53 components) and 173 screens with clickable prototypes for handoff.
03
Key decision
Decision 01
No auto-apply.
The AI can detect a changed price or date in a thread. The question was whether to apply it automatically.
Rejected
✕ Auto-apply detected changes
One silently wrong price poisons every answer that depends on it.
Chosen
✓ One deliberate click per change
Source on the left, AI interpretation on the right, confidence on every claim — nothing changes until a person accepts.
Trade-off we accepted
More clicks today. The plan is to earn automation category by category, using real accept rates.

Change review screen
Highlight 02
Only decisions get your attention.
The overview splits “needs you” from “just happened”, so nothing urgent hides in a feed.

Overview: needs you vs just happened
04
Complexity handled
19 scenario areas, 8 principles
“Humans control change” and “Every claim has evidence” were used to test every layout.
Platform, not template
A polo manufacturer’s orders ran through the same screens to prove the model generalises.
05
Outcome
Live since 2026 · v0.4
22sign-ups in 90 daysAdmin dashboard · 90 days
15workspaces createdAdmin dashboard · 90 days
6trials startedAdmin dashboard · 90 days
90%review items acceptedAdmin dashboard · 30 days
Method and source
Bracket’s admin dashboard, 90 days to 4 Nov 2026, including my own test account. Honest read: the dashboard counts 1 of the 15 workspaces as active, and no trial has converted to paid yet — onboarding is the next problem to solve.
What I suspect · Hypothesis, not a finding
15 workspaces were created, but only 4 Gmail accounts were connected and nobody finished the tour. My suspicion — not yet verified — is that Bracket asks for setup before it shows any value: people have to connect a source before they see a single detected decision.
How I’d investigate, then test · Planned
First, find out where people stop: replay the 14 sandbox sessions to see where the tour is abandoned, and talk to five people who created a workspace but never connected a source. If setup is the blocker, test a Gmail-first start that surfaces one real decision in the first session. Measure: share of new workspaces that review one decision in their first week.
0 likes · 2 views · Nov 16, 2026
Designing an AI Memory SaaS That Detects Scope, Price and Date Changes in Freelancers' Email and Slack, #9 Product of the Day on Product Hunt