I will write you a product requirements document

I will turn your startup idea into an investor and engineering ready PRD

Most startups do not fail because of bad ideas. They fail because of vague execution-

• Engineers build the wrong thing.
• Features creep.
• Roadmaps drift.
• Investors lose confidence.
• If you feel like your product idea is clear in your head but messy on paper I can help.
• I turn early-stage product ideas into structured, engineering-ready, investor-ready Product Requirements Documents that reduce ambiguity and accelerate build velocity.

Before writing a single line of code (or starting to build), you should be able to answer:

• What exact problem are we solving?
• Who is the first real user?
• What is MVP vs noise?
• What must work on Day 1?
• What are the performance, scalability, and security constraints?
• How will we measure success?
• 
  

If these are not written clearly, you are gambling.

Your structured PRD may include:

• Clear problem and business case definition
• Defined target users and workflows
• Prioritized MVP scope
• Functional requirements
• Non-functional requirements (performance, latency, uptime)
• Data and system architecture considerations
• AI or ML constraints
• KPI's
• Risks and assumptions