Pratyus Saha
I build digital products that solve real problems and create real impact.
Operating Model
Talk directly to the people using your product. Find out exactly what they want to achieve and where they get stuck. Base your decisions on these conversations instead of guessing what they need.
Identify the exact problem you have to solve. Review the long list of feature requests, then set it aside. Focus on fixing the single issue that actually improves the business and helps your users.
Shape your work around actual user needs and your team's technical limits. Keep the interface simple to use. Ensure the product works today while leaving room for future updates.
Test your idea quickly. Build the smallest possible version of your product that still gets the job done. This approach lets you confirm the concept works before your team spends six months writing code.
Release your work to the public early. Look at your daily active user numbers and read the direct feedback. Make your next round of changes based entirely on how people actually interact with the software.
Artifacts
A founder-written product document defining the trust problem in online astrology and the AI architecture needed to counter fear-based manipulation.
Decision proof
Frames fraud as an incentive-system problem and responds with transparent calculation, citations, and subscription-aligned incentives.
A product requirements document covering user pain, competitive gaps, technical architecture, tradeoffs, and validation for a dual-mode AI comprehension product.
Decision proof
Makes traceability the product center: every output must link back to the source document so users can verify claims.
