Product thinking
Three notes based on work in Apex and Vibe.
A product lesson from cutting Apex model cost by roughly 95%.
The first version gave an expensive model too much responsibility. It received broad market context, performed much of the reasoning, and generated the explanation. The result could look intelligent while remaining expensive and difficult to reproduce.
A review platform cannot outsource credibility to a verified badge.
Vibe was designed to help people make better local decisions through real experiences. That requires operational work: reports need triage, evidence needs privacy, businesses need a fair challenge path, and users need protection from retaliation.
How I sequence core value, safety, operations, and monetization.
A roadmap becomes useful when it expresses dependency and value, not when it contains every good idea. For Vibe, reviews and business profiles were the core layer because no other feature mattered without credible local information.
Contact
Send me a short message on WhatsApp about what you are building, what already exists, and where you need help.