The same story, every time
Why we're doing it, who's involved, what happened last week. Typed in again.
HomlaMemory
Stop explaining your business to AI. Again.
Your team saves decisions, client details and lessons from any AI chat. Next time anyone asks, their AI checks this memory first.
NorthwindMemory
- Policy
Refunds over $200 go to a person, never to an agent.
Lea · 3 dGiven to the AI when a refund tool is about to be used - Knowledge
Petit Atelier wants invoices on the 1st, with the PO number.
Nora · 2 hReplaced an older fact - Insight
Shopify order notes are visible to the customer. Use tags for internal notes.
Sam · 1 dSaved from Claude - Signal
The spring lookbook moves to the new Figma file. Jonas owns it.
Jonas · 5 dSaved from ChatGPT
Remember: Petit Atelier wants invoices on the 1st, with the PO number.SavedThe problem
Every new chat starts from zero.
What the AI needs to know is in email, calls and people's heads. So your people paste it in by hand. Skip it and the answer is generic.
Copy, paste, paste, paste
The brand voice, the email they're replying to, the process. Then, at last, the question.
It forgets by tomorrow
It's like a new hire who forgets everything overnight. Your people start over every morning.
How memory works
Save it once. Every AI on the team finds it.
Saved from the chat
Ask your AI to remember a decision, a fact or a fix. It is saved for the whole team. A new fact replaces the old one.
Linked for you
People, clients, projects and tools are picked out for you. Open one and see all the team knows.
- Nothing to fill in
- Search by type and topic
Every change on the record
Each save and each removal is logged. You can see where a fact came from. Nothing is deleted.
- Freelancers only read memory if you let them
Company rules
Your rules come along on every request.
Write a business rule once, like “refunds over $200 go to a person”. Every AI on the team gets it right before it acts.
- Only where it applies. A rule about changing things never shows up when the AI only looks.
- Never a flood. At most two rules are added to a request.
ClaudeSupport chat
Refund order #4498 in full, it's $340.
shopify · write
policy attached: Refunds over $200 go to a person, never to an agent.
policy attached: Refunds over $200 go to a person, never to an agent.
This refund is over $200, so your team's policy says a person handles it. I have drafted a note for Lea instead.
Also in Homla
The rest of Homla.
What does it remember?
Only what your team asks it to save. Decisions, client details, fixes and rules.
What if a fact goes out of date?
Save the new one. It replaces the old fact. The change is logged.
Can freelancers see our client notes?
Only if you let them. You choose what each freelancer's AI can read.
Which AI apps can use it?
Every app your team connects. Claude, ChatGPT, Cursor and more.
Tell it once. Your whole team's AI knows.
Start free. Save one client detail. Ask about it from any AI.
- Playbooks the whole team can use
- One memory every AI reads
- Each person gets only their access
- Works in Claude, ChatGPT and Cursor