## Client Meeting Notes

**Project Name:** [Your Project Name]
**Date:** [MM/DD/YYYY]
**Client Name:** [Client’s Name]
**Interviewed By:** [Your Name(s)]

---

### **Client Overview**
- **Brief description of the client and their background:**
  (Example: Kevin is a Dungeon Master who wants a tool to help manage his D&D campaigns.)

- **Client’s main goal for the software:**
  (Example: The tool should help track player turns, roll dice automatically, and send notifications.)

---

### **Interview Questions & Responses**

#### **1. What are the costs vs. budget?**
**Client’s Response:**
(Example: "I don’t want to spend much, ideally free, but I’d consider paying a one-time fee.")

**Clarification & Notes:**
(Example: The client is looking for a free tool but may accept optional paid features.)

---

#### **2. What is the timeframe for this project?**
**Client’s Response:**
(Example: "I need this ready before my next campaign starts in three months.")

**Clarification & Notes:**
(Example: A strict deadline, must focus on core features first.)

---

#### **3. What problem are you trying to solve?**
**Client’s Response:**
(Example: "Managing initiative order and tracking actions is too slow.")

**Clarification & Notes:**
- The real problem is **speed and efficiency** during gameplay, not just "initiative tracking."
- Consider features like **automation** and **UI improvements** to streamline this.

---

#### **4. What is the most important feature?**
**Client’s Response:**
(Example: "Initiative tracking needs to be easy and automatic.")

**Clarification & Notes:**
- This feature should be the **core focus** of the software.
- Other features (e.g., dice rolling) are secondary.

---

#### **5. Is there a similar product on the market?**
**Client’s Response:**
(Example: "Yes, but they are either too complex or too expensive.")

**Clarification & Notes:**
- Competitor analysis needed.
- Find a way to differentiate: **Simpler UI? Free version? Customizable?**

---

#### **6. Are there any existing products or technologies that will need to be integrated?**
**Client’s Response:**
(Example: "It would be nice if it worked with Roll20 or D&D Beyond.")

**Clarification & Notes:**
- Check for **APIs** for possible integrations.
- Consider a **manual import/export** feature if full integration isn’t feasible.

---

#### **7. What does success look like for this project?**
**Client’s Response:**
(Example: "If my players can see whose turn it is without me saying anything, that’s a win.")

**Clarification & Notes:**
- Focus on **visual clarity and notifications**.

---

#### **8. What risks are associated with a malicious user?**
**Client’s Response:**
(Example: "Not much, unless players try to cheat dice rolls.")

**Clarification & Notes:**
- Consider **server-side dice validation** to prevent cheating.

---

#### **9. What is the expected lifetime of this software?**
**Client’s Response:**
(Example: "I want to use it for many campaigns, so it should last for years.")

**Clarification & Notes:**
- Future **maintenance and updates** should be considered.

---

#### **10. What additional features would you like?**
**Client’s Response:**
(Example: "A way to send private messages to players would be cool.")

**Clarification & Notes:**
- Nice-to-have, but **not essential** for version 1.

---

## **Key Takeaways & Next Steps**
- **Most important feature:** Initiative tracking
- **Secondary features:** Dice rolling, notifications, private messaging
- **Deadline:** 3 months
- **Risks:** Potential cheating in dice rolls

### **Next Steps:**
✅ Prioritize initiative tracking
✅ Research existing products for inspiration
✅ Explore integration options with Roll20/D&D Beyond

---

### **Signatures**
(Client) **[Client’s Name]** – *Reviewed & Approved*
(Developer) **[Your Name]** – *Re
