AI-powered client request tracker that our team can use from Claude & ChatGPT

About us We're a small creative agency (2-9 people). Client requests arrive by email, WhatsApp and calls, and they get lost. Nobody knows what's open, who's on it, or what we promised. What we want A simple request tracker our team can talk to. Instead of opening another dashboard, we want to ask Claude or ChatGPT things like: - "What's open for client X, and what's overdue?" - "Have we had a request like this before? How did we handle it?" - "Draft a reply to the latest request from client Y." (A person always approves before anything is sent.) Scope - Clients, requests and messages stored in a real database - "Similar past requests" search (by meaning, not just keywords) - AI-drafted replies, approved by a person - A simple login-protected web page for the team - An MCP endpoint so each of us can connect Claude.ai or ChatGPT and sign in as ourselves, seeing only what we should see - A short README so we can change it later Milestones 1. $40 (2-3 hours): first deploy. A tiny version live with one AI call, plus 5 honest lines on how the setup went. 2. $160: the tracker. Data, similar-request search, drafted replies, team login. 3. $150: the AI connection and handover. MCP endpoint connected to Claude and ChatGPT, plus the README. We'll start a few people on Milestone 1 and continue with one. Platform: Dodil Cloud We'd like this built on Dodil (dodil.io). We looked around and it seems to do everything in one place (database, AI, logins, hosting), and it says it's made for connecting apps to Claude and ChatGPT, which is exactly what we want. You can sign up there yourself. We're not technical, but from what we read, they have a command-line tool and an MCP connection, so you can build with Claude, ChatGPT or Cursor helping you directly on the platform. That sounded like it would make the work much faster, so feel free to use it. Their docs and guides are on their site. In your proposal, tell us: - which AI coding assistant you'd use, and why - one question you have about the sign-in part