AssetIQ: 264% revenue growth
Scoped to inventory accuracy first — revenue followed when stockouts stopped killing sales.
Read case study →Frameworks
Frameworks you can cite
These aren't slide-deck fluff — they're how I actually scope, ship, and measure products. Each framework links to real case studies with numbers leadership can trust.
Framework 01
Outcome-first product thinking
Start with the number, work backward. Before a feature ships, I can name the metric it's meant to move — revenue, cost, accuracy, or adoption.
Visual flow
Outcome → Bet → Scope → Ship → Measure
Principles
- Define the outcome before the output
- Tie every roadmap item to a measurable delta
- Kill scope that doesn't move the number
Real examples
Kaizen: 2× core retention
Narrowed launch to brand-voice AI founders could trust — retention doubled vs. broader feature set.
Read case study →Framework 02
Find the money
Size the opportunity before a line of code. I locate where growth is trapped: manual processes bleeding cost, stockouts bleeding sales, markets nobody serves.
Visual flow
Pain → Prize → Wedge → Validation
Principles
- Map the cost of the status quo in dollars
- Validate the prize with operators, not slides
- Prioritize wedges with the highest ROI per sprint
Real examples
Toyota systems: $40M saved
Automated vehicle tracking and service-queue workflows at distributor scale.
Read case study →AssetIQ: stockouts → revenue
Two-day stock counts and 85% accuracy hid the real cost: empty shelves.
Read case study →Framework 03
Build the machine
AI where it earns its keep, automation where work repeats, ruthless scope where it doesn't. Shipped fast, measured honestly.
Visual flow
Automate → Instrument → Expand
Principles
- Deploy AI only where it beats manual reliably
- Automate repeatable workflows before adding features
- Scope to the smallest proof that earns trust
Real examples
Sumo: ~90% fewer billing errors
POS, cameras, scales, and conveyors wired into one IoT nervous system.
Read case study →Navbot: 85% inquiry automation
Conversational AI for social queries and appointment scheduling.
Read case study →Framework 04
Compound the gains
Toyota taught me growth isn't one big launch — it's a hundred one-percent improvements that stack. Build systems that keep paying off after the release note.
Visual flow
Ship → Measure → Improve → Repeat
Principles
- Kaizen over hero launches
- Instrument for continuous improvement loops
- Design for operability, not just launch day
Real examples
Neoshift: 1,000+ restaurants
Scaled from pilot sites to nationwide footprint through incremental adoption wins.
Read case study →Mave LMS: 40% completion ↑
AI-assisted course flows improved engagement through iterative refinement.
Read case study →Framework 05
Builder-PM advantage
I can read the code, ship faster, and earn engineering trust. The best PMs bring the problem, not a dictated solution.
Visual flow
Problem → Prototype → Trust → Velocity
Principles
- Prototype to de-risk before full build
- Speak engineering fluently in reviews
- Earn trust by understanding constraints firsthand
Real examples
TechCare: 863K+ downloads
Started as a frontend developer shipping templates at global scale.
Read case study →Luca: Cloudinary-class CDN
Infrastructure product built with deep technical narrative for investors.
Read case study →Framework 06
Emerging markets lens
Constraints become product advantage: offline-first flows, POS for busy lines, inventory truth when connectivity fails. Ship for real conditions, not defaults.
Visual flow
Constraint → Wedge → Adoption → Scale
Principles
- Design for flaky connectivity and high-touch operations
- Optimize for adoption on the floor, not in a demo
- Turn local constraints into defensible product wedges
Real examples
Gloria Jean's: offline-first ordering
BD + AU apps with 65% digital-order adoption on unreliable networks.
Read case study →Neoshift: POS for busy lines
Built for restaurant floors where seconds matter more than feature count.
Read case study →FAQ
Framework questions
- What is outcome-first product management?
- Starting with the business number a feature must move — revenue, cost savings, accuracy, or adoption — and working backward to scope, ship, and measure honestly.
- How does Atiq apply Toyota kaizen to product?
- Through compound gains: ship, measure, improve, repeat. Growth stacks from many small wins rather than one hero launch — a mindset learned saving $40M at Navana/Toyota.
- What is the builder-PM advantage?
- A PM who can read code, prototype, and earn engineering trust ships faster and scopes smarter. Atiq's journey began as a frontend developer with 863K+ template downloads.
- Why does emerging-markets context matter for product?
- Real constraints — offline connectivity, high-touch operations, cost sensitivity — force sharper product wedges. Designs that work in Dhaka often outperform Silicon Valley defaults globally.