Bengaluru, India · Open to PM roles, available immediately

Najeebul Hannan

Product Manager, ex-Founder at Naav Cartographic Arts

I'm the PM who turns undocumented, messy operations into systems a team can run without me — enterprise WMS, ERP platforms, and a company I scaled to 8-figure (INR) revenue.

Najeebul Hannan

About

I build products in messy operational environments — warehouses, healthcare ERPs, land surveys, school rollouts. I go in where nothing's written down, figure out how the work actually happens, and turn it into something a team can run without me in the room.

Most recently I co-founded a GIS survey company, scaled it from zero to 8-figure (INR) revenue in two years, and exited in 2026. Two degrees shape how I work — counselling psychology for discovery and cross-functional alignment, mechanical engineering for systems thinking.

Product Strategy

Turn a founder's gut call or a stakeholder's wishlist into a sequenced bet — service portfolio at Naav, WMS roadmap at Huckleberry.

Discovery & Research

Sit with the people doing the work — warehouse floor staff, field crews, therapists — before writing a single requirement.

Roadmapping

Prioritise against what actually blocks revenue or accuracy, not what's loudest in the room.

Stakeholder Alignment

Hold a client's real problem steady while translating it into something engineering can build — and defend the trade-off when it's unpopular.

The work, and the thinking behind it.

Every one of these opens into the full story — research, the framework I prioritised with, the trade-off I had to defend, and what I’d do differently.

1M+ DAILY ORDERS

Huckleberry Enterprise WMS

The tools on the market broke down long before Amazon/Flipkart-scale order volume, and warehouse staff couldn’t use them.

  • B2B
  • ENTERPRISE
  • 0→1
8-FIGURE REVENUE

Naav QA/SOP Decentralisation

Delivery quality depended on me personally checking every job — that doesn’t scale past a few clients.

  • GIS
  • OPERATIONS
  • FOUNDER-LED
200+ CLIENTS IN 90 DAYS

Online Counselling Platform

People in emotional distress abandoned signup because it asked too much of them, too soon.

  • HEALTHCARE
  • 0→1
7 Years in product & ops
5 Industries
10 Products launched
50+ Stakeholder interviews

Where I’ve done it.

Naav Cartographic Arts Mar 2022 – Jun 2026

Founding Partner, Product Manager

  • Scoped and prioritised service offerings across 80+ clients — scaled revenue to 8-figures (INR) within 2 years.
  • Rebuilt the QA/SOP framework — enabled an 8–10 person team to operate independently across every account.
  • Delivered 50+ projects and 100+ spatial reports — held under 10cm RMS accuracy throughout.
Huckleberry Nov 2020 – Jan 2022

Product Manager

  • Redesigned the database schema pre-launch — avoided a costly post-launch rebuild.
  • Authored the PRD/BRD and order flow — enabled a 7-person team to build in parallel without conflicting assumptions.
EdTech & counselling company Jul 2020 – Oct 2020

Operations & Scrum Executive

  • Built and launched an online counselling platform — scaled to 200+ active clients in 3 months.
  • Directed onboarding across 15+ institutions, 50,000+ students — held 100% year-on-year retention.

Tools

  • Jira
  • Confluence
  • Figma
  • Notion
  • Postman
  • QGIS

Methodologies

  • Agile & Scrum
  • MVP Scoping
  • A/B Testing
  • SOP Development

Domain Expertise

  • B2B SaaS platforms
  • Warehouse Management Systems
  • ERP Systems
  • GIS & Geospatial Analytics

Contact

If you’re building something in a messy operational space, I’d like to hear about it.

Open to PM roles in B2B SaaS, warehouse and ERP systems, and ops-heavy products. GIS and geospatial too.

I reply within three working days.

This opens your email client with the message pre-filled. If nothing happens, write to najeebul.hannan@gmail.com.

Case Study 01

Huckleberry Enterprise WMS

Problem
Client's warehouse ops couldn't run at Amazon/Flipkart-scale order volume on tools available in the market.
My role
Sole PM, 7-person cross-functional team
Outcome
Scaled to 1M+ daily orders, zero post-launch schema rework

The why

Client leadership needed the WMS to hold up at marketplace scale before signing further contracts. A schema mistake caught after launch would have meant a rebuild mid-contract.

Situation

Huckleberry was building an enterprise WMS for a client processing Amazon/Flipkart-scale volumes. Tools already on the market were slow for operators and broke down well before 1M+ orders a day.

Task

Owned the full product lifecycle — discovery, PRD/BRD, information architecture, sprint delivery — for a 7-person interdisciplinary team, from storefront intake to courier handoff.

Discovery

Interviews with warehouse operations staff and client leadership, including users of competing WMS platforms.

  • Inventory was tracked in a way that didn’t map to how pickers actually moved through the warehouse.
  • Competing tools broke down past a few hundred thousand daily orders — the client needed headroom to 1M+.
  • The database schema as originally briefed would have needed a rebuild after launch.
“I don’t need another dashboard, I need to know which bin has stock without walking there.” Warehouse operations staff, anonymised

Prioritisation

No formal framework — the call was made on cost of being wrong. Fixing the schema pre-launch was cheap; fixing it post-launch meant a rebuild during a live contract. Schema and information architecture came before any UI work.

Action

Authored the PRD and BRD, redefined the database schema and the end-to-end order flow — storefront intake, picking logic by bin/category/sector, courier handoff — then ran delivery across design, engineering and QA through Jira, Confluence and Figma.

Storefrontintake Orderservice Pick planbin / category / sector Pack& verify Courierhandoff Schema and information architecture redefined here — in week two, before build, not after launch Order lifecycle, as rebuilt Cost of being wrong: a pre-launch schema change is a sprint. The same change post-launch is a rebuild during a live contract.
The order lifecycle as rebuilt, with the two stages whose data model was redefined before build marked. Redrawn from the PRD — no client system, screen or data is shown.

The conflict

I set go/no-go criteria around A/B test results and QA cycles rather than the release-date pressure client leadership wanted — that meant pushing one release back a sprint. It gave leadership data-backed reasoning to reschedule instead of shipping known defects.

Result

  • Order volume — handled 1M+ daily orders within 12 months of launch, architected for that scale from day one.
  • Post-launch defects — reduced, since go/no-go was tied to QA and A/B results, not the calendar.
  • CEO and CTO recognised the contribution to client revenue growth in the post-project outcome review.
  • Avoided a schema rebuild mid-contract, which would have put the client relationship at risk.

So what

I’d push for the warehouse-floor interviews even earlier — the schema fix landed before build only because I caught it in week two. A week later and it ships broken.

Working on something shaped like this — undocumented, operational, and running on people rather than systems?

Tell me about your problem
Case Study 02

Naav QA/SOP Decentralisation

Problem
Delivery quality depended entirely on me personally checking every job — that doesn’t scale past a few clients.
My role
Founder & Product Lead, team of 8–10
Outcome
8–10 person team operating independently at <10cm RMS accuracy across 80+ clients

The why

Every new client meant more founder hours on QA, capping how many accounts the company could take on — the business couldn’t grow past what I could personally check.

Situation

Naav had scaled past 50 projects and 80 clients across agriculture, government, ecology and infrastructure. Accuracy and turnaround gaps kept surfacing across engagements, and every fix ran through me.

Task

Owned the QA/SOP framework rebuild — from founder-led spot checks to a documented, decentralised system the field and analysis team could run without me.

Discovery

Methods: reviewing recurring accuracy and turnaround issues across client engagements to find where the QA process actually broke down.

  • Most errors weren’t skill gaps — they were the same step done differently by different people because nothing was written down.
  • The team could hold a standard if given a checklist, not if given a founder-in-the-loop review.
  • Turnaround gaps clustered around a handful of survey types, not evenly across the business.

Prioritisation

Fixed the highest-frequency, highest-cost gaps first. SOPs went to the survey types with the most recurring errors before covering edge cases.

Action

Documented SOPs and built a decentralised QA/QC system by survey type, so the 8–10 person field and analysis team could self-check against a standard instead of routing through me.

Before Job Job Job Job Founder checks each Client Throughput capped at one person’s hours. Every new account tightened the cap. After Job Job Job Job SOP for that survey type + lead sign-off Client Standard held by the document, not the founder. Accuracy bar unchanged; the bottleneck gone.
QA routing before and after decentralisation. The change is where the standard lives, not how high it is set. No client work or client data is shown.

The conflict

The team wanted me to keep doing final sign-off — it felt safer. I pushed sign-off down to team leads instead, because keeping it with me meant the business couldn’t grow past what I could personally review — that meant trusting leads with client-facing accuracy calls before they’d fully proven themselves.

Result

  • Accuracy — held under 10cm RMS error across 50+ projects and 100+ reports, without founder sign-off.
  • Team autonomy — 8–10 member team operating independently across all 80+ client accounts.
  • Freed founder time to focus on service-line strategy instead of QA.
  • Company scaled to 8-figure (INR) revenue within two years on this delivery model.

So what

I’d build the SOPs from month one, not after the recurring-error pattern was already costing client trust.

Working on something shaped like this — undocumented, operational, and running on people rather than systems?

Tell me about your problem
Case Study 03

Online Counselling Platform

Problem
People seeking mental health support during COVID were abandoning signup because it asked too much of them while they were already struggling.
My role
Product lead, working directly with the CTO
Outcome
200+ active clients within 3 months of launch

The why

The company needed to validate a 0→1 counselling product fast, during COVID, without a large team — a high-friction signup would have meant no data to validate anything.

Situation

Built from scratch during COVID-19. No existing onboarding pattern for people in emotional distress signing up for therapy online, and every day of delay meant lost demand.

Task

Led product definition and delivery — PRD, product spec, user flows, onboarding strategy, competitive USP analysis — working directly with the CTO to translate requirements into features.

Discovery

Methods: competitive analysis, and framing the onboarding problem around emotional state rather than conversion-funnel logic.

  • Standard signup forms assumed users had the bandwidth to fill in a lot of detail up front — people in distress don’t.
  • The therapist-matching step was where users dropped off, not account creation.
  • A short, low-friction first step got people to the next step even if the full profile came later.
“I almost didn’t sign up. It felt like applying for a job.” Early user, anonymised

Prioritisation

Cut the signup flow down to the minimum needed to get someone to a therapist, and deferred everything else — preferences, history — to after the first session was booked.

Action

Built a low-friction onboarding flow and managed cross-functional development, including therapist integration and full platform rollout.

Before Create account Full profileand history Preferences Therapist match First session drop-off concentrated here After Email + whatyou need Therapist match First session Profile and history,after the booking The trade: a less precise first match, in exchange for the person arriving at all.
Signup sequence before and after. The decision was to defer everything that was not needed to reach a therapist. Redrawn from the spec — no product screen or user data is shown.

The conflict

Internally there was pressure to collect more profile data up front, to make therapist-matching more precise from session one. I chose to defer it, because a perfect match on session one mattered less than getting people through the door at all — losing someone at signup meant losing them completely.

Result

  • Active clients — 0 → 200+ within 3 months of launch.
  • Signup completion improved — not instrumented precisely at the time.
  • Therapists could onboard clients same-day instead of over multiple back-and-forth steps.
  • Proved the product fast enough to keep scaling through COVID demand.

So what

I’d instrument the funnel from day one — we knew qualitatively where people dropped off, but I never had the exact numbers to prove the fix worked.

Working on something shaped like this — undocumented, operational, and running on people rather than systems?

Tell me about your problem
Naav Cartographic Arts

Founding Partner, Product Manager — Naav Cartographic Arts

Dates
Mar 2022 – Jun 2026
Reported to
Co-founders (self-directed)
Scope
80+ clients, 8–10 person delivery team

Context

Co-founded a GIS mapping and survey company from zero. Built the service line, the delivery team, and the QA process from scratch across agriculture, government, ecology, education, fisheries and infrastructure clients.

What I owned

  • Service portfolio scoping and prioritisation against evolving client demand.
  • Technical delivery — field survey, drone/aerial data acquisition, spatial analysis.
  • QA/SOP framework, client relationships from scoping through handover.

What changed

  • Scoped and prioritised service offerings across 80+ clients — scaled revenue to 8-figures (INR) within 2 years.
  • Rebuilt the QA/SOP framework — enabled an 8–10 person team to operate independently across every account.
  • Delivered 50+ projects and 100+ spatial reports — held under 10cm RMS accuracy throughout.

How I worked

Ran delivery through documented SOPs rather than founder-led review, with client and project tracking in Jira, Confluence, Notion and Trello. Designed and deployed a web/Android estate operations app to 15+ estates for real-time visibility into field activity.

Want to talk about what this would look like on your team?

Start a conversation
Huckleberry

Product Manager — Huckleberry

Dates
Nov 2020 – Jan 2022
Reported to
Client CEO/CTO and Huckleberry leadership
Scope
Enterprise WMS + healthcare ERP, 1M+ orders/day, 1M+ users

Context

Technology and product consulting firm. Led the full product lifecycle on two enterprise builds: a healthcare ERP serving 1 million+ registered users, and a warehouse management system architected for 1M+ orders a day.

What I owned

  • PRD/BRD authorship and end-to-end order flow, storefront intake through courier handoff.
  • Sprint planning, backlog grooming and retrospectives for a 7-person cross-functional team.

What changed

  • Redesigned the database schema pre-launch — avoided a costly post-launch rebuild.
  • Set go/no-go criteria around A/B and QA results — reduced post-launch defects.

How I worked

Ran delivery across design, engineering and QA in Jira, Confluence and Figma, with structured stakeholder presentations at each build stage to keep client and Huckleberry leadership aligned from discovery through MVP launch.

Want to talk about what this would look like on your team?

Start a conversation
EdTech & counselling company

Operations & Scrum Executive — EdTech & counselling company

Dates
Jul 2020 – Oct 2020 (also Oct 2018–Jul 2019, Aug 2016–Jul 2017)
Reported to
CTO
Scope
Online counselling platform, student ERP onboarding, CRM/PM tool

Context

Software product and technology company spanning EdTech, counselling, and enterprise SaaS. Worked across four product streams over three stints, starting as an Associate Data Analyst and ending as Operations and Scrum Executive.

What I owned

  • Product definition and delivery for a 0→1 online counselling platform, working directly with the CTO.
  • Onboarding, training and implementation for a student ERP, across Tier-1 and Tier-2 institutions.

What changed

  • Built and launched an online counselling platform — scaled to 200+ active clients in 3 months.
  • Directed onboarding across 15+ institutions, 50,000+ students — held 100% year-on-year retention.

How I worked

Also contributed to a CRM/project-management tool (scoped its MVP down against stakeholder pressure for a broader build) and an internal learning platform — defining user flows, audience and content structure.

Want to talk about what this would look like on your team?

Start a conversation