You're working with seven clients simultaneously. You know each one intimately: the political dynamics inside their leadership team, the half-formed strategy they keep circling back to, the decision that got reversed last quarter and why, the stakeholder who's the real veto point even though they're not the most senior.
You use Claude constantly. It helps you draft recommendations, structure thinking, write proposals, prepare for difficult conversations. You get good results — but only after you spend five minutes re-briefing Claude on the client, every single time.
That five minutes adds up. Across seven clients, multiple sessions a day: you're spending an hour a week just reloading context that Claude immediately forgets.
Custom instructions aren't enough. You can tell Claude who you are and how you like to work, but you can't keep seven clients' worth of context in there. It's not designed for that.
Claude Projects help with static reference documents — the contract, the org chart, the RFP. But consulting engagement knowledge is different. It's the stuff that isn't written down anywhere:
This is the information that makes you effective. And currently you're carrying it in your head, in scattered notes, and in emails — re-briefing Claude every time you need it.
Stash is a store that Claude can query directly via a connector. You add records — short, structured facts — and Claude can retrieve them in any conversation. Not by attaching files or pasting context, but by calling a tool that searches your store and surfaces what's relevant.
The typical setup for a consultant looks like this: one Stash collection per client engagement, with records for each significant fact, stakeholder note, recommendation status, and open question.
| Record category | Example |
|---|---|
| Stakeholder dynamics | "CFO holds real budget approval, not project sponsor. Get CFO buy-in before any formal submission." |
| Engagement history | "Ops efficiency recommendation rejected in Mar — conflicts with COO's existing vendor contract. Revisit in Q4." |
| Open decisions | "Phased vs. big-bang implementation still undecided. Client wants a risk model before committing." |
| Key commitments | "Agreed: interim report 15 July, final deliverable 30 August." |
| Preferred framing | "Client prefers ROI framing over risk reduction. Use financial outcomes language in all outputs." |
When you open Claude for a working session, you don't re-brief. You say: "Pull my context for Acme Corp" — and Claude loads what's relevant in seconds.
That's not a carefully constructed demo. It's what a real working session looks like when Claude has your context already loaded. The steering group prep that used to take 15 minutes of briefing takes 2.
Stash organises records by collection, so each client engagement stays completely separate. When you switch from Meridian Finance to Northern Logistics, you query a different collection. Claude doesn't conflate them.
You can also keep a "principals" collection — a lightweight CRM of the people you work with across engagements: their roles, their positions on things, their communication preferences. Queryable from any conversation.
If you bill by the hour, context overhead is a real cost. But there's a bigger issue: the time you spend re-briefing Claude is time you're not billing, and it produces outputs that are worse than they'd be if Claude actually understood the situation.
Consultants who use Claude with full client context get better recommendations faster. That's not a vague benefit — it's the difference between Claude suggesting a generic approach and Claude knowing that the CFO will reject any proposal that adds capex in H1.
The workflow that works for most consultants:
Records you add today are available in any future conversation. The engagement knowledge that currently lives in your head accumulates in a store Claude can actually use.
The free tier covers 2,500 records and 50 queries a month — roughly one active client engagement's worth. Consultants with multiple active clients typically reach the limit within a few weeks. The paid tier (£8/month) removes the caps. Pricing may change; cancel anytime.
Claude → Settings → Connectors → Add custom → paste this URL:
https://app.stashlite.com/mcp
Sign in with Google. Your account is created automatically. No setup, no code.
Get your connector URL →Stash works best for the information that isn't formally documented anywhere else. If it's already in the contract or the SOW, Claude Projects can handle it. If it's the tacit knowledge from client calls — the political reality, the stated vs. actual priorities, the commitments that weren't written down — that's what Stash is for.
You don't need to capture everything. Even 10 records per client engagement dramatically changes what Claude can do for you. Start with the stakeholder dynamics and the open decisions. Everything else follows naturally.