Product Strategy · 0→1 · AI · SaaS

I like problems that don’t have an obvious answer.

I’ve spent my career moving closer to the problem — from engineering, to teaching, to delivery, and now product. I like understanding how people actually use something, finding the friction they don’t always say out loud, and turning an idea into something real enough to challenge.

6+ years product & delivery0→1 ownershipB2B · B2C · SaaSAI product experience
Himanshu Barsaiyan
Product Manager · B2B SaaS · AI
01 — The path behind the products

Engineering roots. Delivery discipline. Product curiosity.

I didn’t arrive at product through a single career switch. I kept moving closer to the part of the work I enjoyed most: understanding people, solving problems and deciding what should exist.

2020 → Present
A Logic Data

Product Manager & Project Delivery Head

Built and owned products from discovery through delivery across SaaS, EdTech and AI — while learning what changes when an idea has to survive real users, real constraints and real delivery.

Product discoveryRoadmapsPrioritization0→1AI products
2017 → 2020
Engineering → Training → Delivery

Moved closer to people using the system

Started in core engineering, then trained engineers and students to build ATVs, go-karts and automotive systems. That experience taught me something product still reinforces: observing the journey often reveals what a specification never will.

01
Start with the problemObserve the customer journey, frame the right problem and turn it into a clear product direction.
02
Turn ideas into productsShape 0→1 concepts into focused MVPs, requirements and practical ways to validate them.
03
Build with reality in mindConnect priorities to delivery plans, product requirements and engineering constraints.
04
Connect product domainsApply the same product thinking across SaaS, EdTech, AI and B2C experiences.
02 — What pulled me toward product

I kept moving closer to the problem.

Core engineering taught me systems and constraints. Training taught me to watch how people learn and work. Delivery taught me that the journey matters more than the plan. Product gave me the space to connect those things and decide what is worth building.

01Engineer

Learned to think in systems, constraints, process and failure points.

02Trainer

Worked directly with learners and teams building real engineering projects.

03Builder

Helped build a company from scratch — from pipeline and ideas to delivery and products.

04Product

Started asking the question I now return to first: “What problem are we actually solving?”

My instinctObserve the journey before deciding what to build.
My fearFinding out we were wrong after too much time has already gone.
My use of AITurn an idea into something tangible quickly enough to challenge it.
03 — Impact at a glance

Numbers from products I have actually shipped.

45%Course-upload timeline reduction
30%Order-processing speed improvement
8–10 hrsWeekly operational leakage reduced
40+Worktracker users
0→1Product ownership across SaaS & B2C
07 — How I think

Start with the journey. Find the problem. Learn early.

01

Discover

Research, interviews, product signals, JTBD.

02

Define

Problem framing, constraints, MVP boundaries.

03

Prioritize

RICE, impact, confidence, effort and sequencing.

04

Build

PRDs, stories, prototypes and engineering alignment.

05

Measure

North Star, KPI tree, funnel and experiments.

06

Learn

Feedback, guardrails and scale/kill decisions.

08 — Core skills

Product depth with technical range.

01

Strategy & Discovery

Product discovery, user research, JTBD, personas, problem framing, MVP definition, roadmaps.

02

Execution

Backlog ownership, PRDs, user stories, RICE, Agile/Scrum, stakeholder and cross-functional leadership.

03

Data & Growth

SQL, Excel, KPI/North Star metrics, A/B testing, hypothesis testing, funnel analysis, AARRR.

04

Technical & AI

SaaS architecture, API integration, AI product development, rapid prototyping, Lovable, Mindsmith, Gemini, n8n.

09 — About

Still learning how to build things that matter.

I started as a mechanical engineer because I liked understanding how things work. Somewhere along the way, I realised I was equally interested in the people using those things — what confused them, what slowed them down, and what made a solution genuinely useful.

That took me through engineering, technical training, EdTech and delivery before product became the natural place for me. Today I enjoy the space between people, technology and messy problems where the answer isn't obvious.

I don't think a product person needs to know everything. I think you need to know what you can be very good at, recognise where someone else is better, and bring those strengths together. A great product, like a great car, is rarely made from one person's expertise.

Outside work, I like capturing moments. It started with photographs, moved into videos and reels, and one day I'd like to make a good movie. I also want to stay grounded enough to care about the world around me — not just use it, but nurture it.

What I’m working towardBuilding something iconic that solves a problem people have learned to live with.
10 — Outside the product

I like capturing moments too.

It started with photographs, moved into videos and reels, and somewhere along the way became a love for experiences, travel and storytelling. One day, I’d like to make a good movie.

Himanshu on a motorcycle surrounded by hills
Somewhere on the road.
Himanshu scuba diving
Curiosity takes me places.
Himanshu skiing with his partner
Collecting stories along the way.
11 — Contact

Let's talk about the problem.

For Product Manager, Senior Product Manager or AI Product opportunities, I’d be happy to walk through the decisions behind the work.