I will review your prd, product requirements, and mvp before development
Senior Technical Product Manager, PRD and Requirements Review
About this Gig
I review PRDs, product requirements, MVP plans, and technical product documents before they get handed to engineering. No external links, pdf or attachment only.
The point is simple: find the problems while they are still cheap to fix.
I look for contradictory or ambiguous requirements, missing flows and edge cases, unclear acceptance criteria, hidden dependencies, sequencing problems, scope creep, and things being called MVP that really are not.
I also look at the gaps between business intent and what engineering is actually likely to build, along with operational, security, trust, and governance issues where they matter.
You will get a structured review with prioritized findings and practical recommendations.
This is a review service, not PRD ghostwriting or open-ended fractional product management. If the review identifies larger work that needs to be done, we can discuss that separately.
Product stage:
Ideation
•
Prototype
•
MVP
Product type:
Digital Products
Industry:
Business
•
Insurance
•
Technology & internet
Target country:
Worldwide
My Portfolio
FAQ
What documents can you review?
PRDs, product requirements, MVP plans, technical product specs, feature requirements, user flows, and similar product documents intended for engineering or implementation.
Do you rewrite the PRD?
Not as part of the standard review. I identify problems, explain why they matter, and recommend what should change. If you want me to rewrite or rebuild sections afterward, that can be scoped separately.
Can I send more than one document?
Each package covers one primary document. You can include supporting material for context, but additional documents that need their own review should be scoped separately.
What if my document is longer than the package limit?
Message me before ordering. I can either recommend the right package or create a custom offer based on the document length and complexity.
What do I receive at the end of the review?
A structured written review with prioritized findings, explanations of why each issue matters, and practical recommendations for what to clarify, change, remove, or investigate further. Question: What exactly are you looking for?
What exactly are you looking for?
Contradictions, ambiguity, missing flows, edge cases, weak acceptance criteria, hidden dependencies, sequencing problems, scope creep, MVP problems, and gaps between business intent and likely implementation.
Is this a technical code review?
No. I review product requirements and implementation intent, not source code. I can flag technical risks, integration concerns, API issues, or architectural assumptions where they affect the product requirements.
What are the consulting minutes for?
They are for discussing the product, clarifying context, or walking through findings. They are not ongoing product management or additional document work.
Do you use AI in the review?
I may use tools to assist with analysis, but the review, prioritization, conclusions, and recommendations are mine. If you require a human-only review, tell me before ordering.
Can I send confidential or proprietary material?
Only send material you are authorized to share. If your organization requires an NDA or has specific handling requirements, message me before ordering so we can determine whether the engagement is a fit.

