1. What you're building. A web app, a mobile app, an internal tool, an AI-assisted workflow, whatever it is, describe it the way you'd explain it to a friend, not a spec sheet.
  2. Who it's for. Your own team, paying customers, or both. This changes how we think about auth, scale and support.
  3. What exists today. Nothing yet, a prototype, an old system you're replacing, tell us where you're starting from.
  4. Rough timeline. "Yesterday," "this quarter," or "no fixed date" all work. It tells us how to scope the first version.
  5. Any constraints. Budget range, must-use technology, compliance requirements, anything that would change how we'd approach it.