The need
A new Claude user created a Project, cannot put other chats into it, and doesn't understand how Projects differ from the old chat model — paying-adjacent onboarding friction with no Thai answer.
Original post — verbatim Thai
จะเอาแชทอื่นไปใส่ในโปรเจคก็ไม่ได้ สร้างมาเป็นแบบนี้ตลอดผมก็เลยงงว่าผมทำถูกหรือผิดแล้วแบบนี้มันต่างกับแบบเก่ายังไง
Three business opportunities
OPPORTUNITY 01
Thai Claude onboarding course ('0 → Project')
- What
- Short paid workshop covering Projects, knowledge files, chat migration and how the model differs from plain chat.
- Who pays
- New subscribers pay a small fee to stop guessing at a feature they pay for.
- Price
- ฿390–990 — hypothesis
- Why now
- Repeated beginner UX questions in the group; no Thai-first guide exists.
- Effort
- S
- Moat
- Thai-first depth kept current with Anthropic UI changes.
- Risk
- Anthropic improves in-product onboarding, dissolving the gap.
OPPORTUNITY 02
Chat→Project migration toolkit
- What
- Script and service that exports Claude chats and reformats them into Project knowledge/custom-instructions; done-for-you option.
- Who pays
- Professionals with years of chat history pay for continuity.
- Price
- ฿990–2,900 — hypothesis
- Why now
- Native import doesn't exist; the post shows users hitting exactly that wall.
- Effort
- S
- Moat
- None long-term — use as lead-gen wedge for the course/service.
- Risk
- Anthropic ships native chat-to-project import; kill the product fast if so.
OPPORTUNITY 03
Managed Claude workspace for teams
- What
- For Thai SMEs: configured Projects (per role), knowledge bases, prompt library, plus staff training and monthly refresh.
- Who pays
- SMEs pay setup plus a monthly care retainer.
- Price
- ฿5,000–20,000 setup + ฿2,000/mo — hypothesis
- Why now
- As teams adopt Claude, the configuration burden lands on non-experts.
- Effort
- M
- Moat
- Workflow templates and training brand within the Thai ecosystem.
- Risk
- Drifts into a services treadmill without product leverage.