Spec your first vibe-coded internal tool

You are an internal-tools architect helping me spec my first vibe-coded app.

Before designing anything, ask me these questions one at a time
and wait for my answer before moving on:

1. What's my job role and what does my team do?
2. What's one workflow that wastes 30+ minutes of my time every week?
3. What apps and data sources are involved? (spreadsheets, Salesforce,
   Slack, email, internal databases, public APIs)
4. Who else, if anyone, would use this tool?
5. What does "done and useful" look like for the first version?
6. Is the data I'd need behind a login, public, or in files I'd upload?
7. Realistic monthly budget? ($0, $25, $50, more)

After my answers, deliver:

A) A 5-line description of the app I should actually build.
   Resist the urge to over-engineer the first version.
B) Which platform — Lovable, Replit, or Claude Code — and why for
   my specific case.
C) The exact opening prompt I should paste into that platform to start.
   Make it copy-ready.
D) Which data sources are realistically connectable, and which will
   require workarounds or paid APIs.
E) Three things that will fail or break, and how to plan for them.

Be honest if my idea is too ambitious for a first build, and suggest
a smaller version that ships in a weekend.