The need
Opening a fresh Claude Code session means retelling the job every time, so a memory plugin is attractive - but the free core quietly consumes the paid plan's quota and the Pro tier costs extra, which is an unresolved cost question.
Original post — verbatim Thai
เปิด Claude Code ใหม่ทีไรต้องเล่างานซ้ำ?
Same pain, other posts
Every week, I have to type the same long AI orders.
เบื่อไหมครับ เมื่อเปิดแชทใหม่ต้ิองอธิบายงานใหม่ทุกรอบ
ต้องอธิบายบริบทเดิมซ้ํา ๆ เมื่อเปิด Session ใหม่
Three business opportunities
OPPORTUNITY 01
Team memory server for Claude Code (self-hosted, Thai docs)
- What
- A shared context store - decisions, tasks, gotchas, conventions - that Claude Code reads and writes across a team's repos, with admin controls, an audit log and a Thai setup guide.
- Who pays
- 3-15 person dev teams paying to delete the daily re-explanation tax, and consultants who context-switch across client repos.
- Price
- hypothesis: free core, ฿290/dev/mo for hosted/self-host support
- Why now
- His post proves demand (over 100k stars on the plugin he covers) while local teams still need audit, admin and Thai-language setup that foreign guides don't give.
- Effort
- M
- Moat
- Accumulated project memory becomes a switching cost the longer a team runs it.
- Risk
- Anthropic's native memory and skills are improving fast and may absorb the plugin category.
OPPORTUNITY 02
Context-cost meter: what your memory plugin actually charges you
- What
- A usage-analytics layer that shows how much quota each memory injection consumes per repo, then auto-tunes it - summarise, prune, budget caps, 'cold start only' modes.
- Who pays
- Pro/Max users alarmed that a 'free' plugin spends the quota they pay for - the exact caveat flagged in this post.
- Price
- hypothesis: ฿99/mo
- Why now
- Memory plugins became mainstream this year and their hidden cost on paid quota is new, unaddressed and measurable.
- Effort
- S
- Moat
- Benchmark data on memory volume versus task success that nobody else is collecting.
- Risk
- Very narrow niche inside one ecosystem, and providers may surface the same telemetry natively.
OPPORTUNITY 03
Repo context onboarding-as-a-service ('first session already knows your code')
- What
- For a flat fee, run an extraction pass over a client repo - architecture notes, past decisions, runbook, gotchas - and hand back a curated memory bundle plus a working first-session brief.
- Who pays
- Agencies inheriting legacy Thai codebases and CTOs onboarding new developers, who pay for time-to-productivity.
- Price
- hypothesis: ฿9,900 per repo
- Why now
- Context reconstruction is now automatable with Claude Code itself, so the margin comes from curation rather than reading code by hand.
- Effort
- S
- Moat
- A reusable extraction pipeline that becomes the import path for the team memory server.
- Risk
- One-off revenue and highly variable results on messy or undocumented repos.