# Notes/Thoughts/Ideas

This file is ignored by Claude (see .clauignore).
Use this for personal thoughts, todos, and reminders.

## 📝 Quick Thoughts

- Read CLAUDE-SETUP.md, CURRENT-STATE.md, and LESSONS-LEARNED.md before starting work on [your task].
- Update CURRENT-STATE.md with what was completed and update LESSONS-LEARNED.md if we encountered any new issues.
- 

## ✅ Personal TODO

- [ ] Answer the 5 key questions in docs/05-QUESTIONS-AND-ACTION-ITEMS.md
- [ ] Decide on app name (TroubleTree? DecisionPath? MSP Navigator?)
- [ ] Set up Render account for free tier testing
- [ ] Add patherly.com to my namecheap account for dynamic dns

## 💡 Feature Ideas (Future)

- Voice-guided troubleshooting for hands-free operation
- Integration with Teams/Slack for notifications
- AI suggestions based on past sessions
- Mobile app for on-site work
- Make an import plan function. Something where it can be written in text or formatted in such a way, and then imported as a plan.

## 🐛 Bugs to Track

- Sessions are not picking up where they left off. You get put back to the beginning of the tree you're working on.

## 🎯 This Week's Focus

**Goal:**

**Tasks:**
-

## 💬 Questions for the Team

- 
- 

## 📊 Metrics to Watch

- How many tickets am I using this on?
- Time saved per ticket?
- Are exports actually useful?

## 🔧 Technical Debt

- 

## 🎨 Design Ideas

**1. Custom note formatting**
- Add a feature that allows the formatting of the ticket notes when they've been finished. For instance, if we have a 'send notes as email' feature, it would be a good idea to allow the customization of the ticket notes to include the ticket number, the client, the engineer who worked on it, and any other fields that are chosen to be added to the notes template.

**2. Options on the go**
- I think another valuable idea would be to allow users to select a troubleshooting step while in the midst of their tree. For instance, if they're in the middle of troubleshooting and they decide to try something outside of the current available options, allow them to select a pre-made troubleshooting technique and then take them to a point in the tree that makes sense. If more context is needed, I can provide it when we decide to work on this.
- 

## 💰 Budget Tracking

**Current Hosting Cost:** $0 (Render free tier)
**Expected Cost in Production:** ~$25-35/month (Railway Pro)

## 📅 Timeline Tracking

**Week 1:** Project planning ✅
**Week 2:** Backend development
**Week 3:** Frontend + testing
**Week 4:** Deploy and dogfood

## 🎓 Things I'm Learning

- 
- 

## 🔗 Useful Links

- Render Dashboard: https://dashboard.render.com
- Railway Dashboard: https://railway.app
- Project Repo: [add when created]

---
