Hakim
Product Manager
Hakim is an AI product manager built by ZainaBot.AI to help founders, PMs, and designers turn rough ideas into clear, shippable specs. He pressure-tests assumptions before writing a single line, so every document is grounded in real user needs and measurable outcomes. Hakim writes for two audiences at once: engineers who need precision and execs who need confidence. Whether you need a full PRD or a fast one-pager, he brings structure to the chaos.
How Hakim helps you
Turn your vague product idea into a structured, ready-to-build PRD
Write user stories that give engineers exactly what they need to ship
Build a quarterly roadmap with effort and impact estimates attached
Run RICE, ICE, or MoSCoW scoring to defend your prioritization calls
Define your North Star metric and map the KPI tree beneath it
Spot scope creep early by naming non-goals before work begins
Capabilities
- Full PRDs with goals, non-goals, and acceptance criteria
- Lite one-pagers for fast-moving teams
- User stories in standard As a / I want / So that format
- Quarterly and theme-based roadmap creation
- RICE, ICE, Kano, and MoSCoW prioritization frameworks
- North Star metric definitions with supporting KPI trees
- Discovery questioning to pressure-test assumptions first
- Open questions sections to surface unknowns before build
Live Coaching with Hakim
Hakim plays the other person in a tough conversation while coaching you in real time, whispering tactical suggestions as you go. Practice as many times as you like, then get a scored performance breakdown at the end.
5 practice scenarios
Getting a Distracted Founder to Commit to a Roadmap
easyWho you face: Priya Anand, 34, co-founder of an 18-person B2B SaaS startup. She has strong opinions but changes her mind weekly based on the last customer call she took.
Get Priya to formally approve the Q3 roadmap without letting scope creep in at the last minute.
Pushing Back on a Feature Request from a Key Account
mediumWho you face: Carlos Vega, 41, VP of Operations at a logistics company that represents 20% of your ARR. He's polite but used to getting his way and frames everything as urgent.
Decline the custom build diplomatically while keeping Carlos satisfied and the relationship intact.
Aligning with a Skeptical Engineering Lead on Scope
mediumWho you face: Jin-ho Seo, 38, senior engineering manager at a mid-size fintech. He's technically brilliant, deeply protective of his team's bandwidth, and distrusts PMs who he thinks underestimate complexity.
Reach a shared, realistic scope agreement with Jin-ho that both sides can commit to.
Defending Deprioritization to an Angry Internal Stakeholder
hardWho you face: Fatima Al-Rashid, 45, Head of Sales at a 200-person enterprise software company. She is results-driven, politically savvy, and not afraid to escalate to the CEO.
Own the communication failure, explain the reprioritization clearly, and rebuild enough trust to avoid escalation.
Running a Prioritization Session When Everyone Disagrees
hardWho you face: Marcus Webb, 51, Chief Revenue Officer at a growth-stage healthtech company. He's a former salesperson who dominates rooms, dismisses frameworks as 'theory,' and only trusts revenue numbers.
Facilitate a defensible prioritization decision that the group owns, without letting Marcus hijack the process.
Success stories
Illustrative examples of how Hakim is used.
From Fuzzy Brief to Approved Spec in One Session
A startup founder came in with a rough idea for a B2B onboarding feature but no clear user definition, no success metric, and a list of wants that kept growing.
Hakim ran a discovery sequence, locked the Job-To-Be-Done, trimmed scope using MoSCoW, and produced a one-page PRD with testable acceptance criteria that the engineering lead approved the same week.
Roadmap That Survived the Executive Review
A product team had a backlog of 40 plus items, competing stakeholder priorities, and a quarterly planning meeting in three days with no clear framework for what to cut.
Hakim applied RICE scoring to the top candidates, grouped survivors by theme, and built a quarter-by-quarter roadmap with effort estimates that gave leadership a defensible plan they could actually commit to.
Turning a Feature Request into a Measurable Outcome
A designer brought a request from sales to add a dashboard feature, but the ask had no user story, no definition of done, and no connection to any product metric.
Hakim separated the problem from the proposed solution, defined the target user precisely, tied the feature to a retention KPI, and wrote acceptance criteria that made the project testable rather than open-ended.
Ready to work with Hakim?
Start a conversation now, or browse the full team of coaches.