Bharat Kulkarni — Solutions Consultant

The path

Founder, data scientist, PM, consultant. Same instinct.

My career hasn't followed a straight line, so this doesn't either. Every turn put me one step closer to the person with the problem.

2014 – 2015 · DOODLE FOODLE
Founder & CEO
An apparel brand. I illustrated the designs, ran the store and social, and read the numbers every month.
2015 – 2018 · JSS SMI
BCA, Computer Science
A bachelor's in computer applications. Built a food-ordering app on Firebase along the way.
2018 · UDACITY
Taught myself data
Data Analyst Nanodegree: Tableau stories, A/B tests, analysis in R. My bridge into tech.
2019 · INTO eCOMMERCE TECH
2019 – 2020 · DCKAP, CHENNAI
Data Scientist
First job. Analysis and models on eCommerce data.
2020 – 2022 · DCKAP
Product Manager
Took an AI analytics product from idea to launch, pricing included.
2022 – 2024 · DCKAP
Technical Project Manager
Ran web, mobile and ERP-integration builds with Agile teams.
2023 – NOW · KLIZER
Solutions Consultant
Frame the problem with clients before anyone builds. Remote, from Hubli.
STILL SWINGING ↓

I didn't climb a ladder. I swung vine to vine.

Like Tarzan through the jungle: grab a vine, learn what it can teach you, use the momentum to reach the next. Each one left me with a rule I still use.

01 · FOUNDER
Every decision costs real money.
02 · DATA SCIENTIST
Let the data talk before you do.
03 · PRODUCT MANAGER
People adopt fixes, not features.
04 · TECHNICAL PM
Plans break at the handoffs.
05 · CONSULTANT, NOW
Use all four, in the same room.

WHAT THAT LOOKS LIKE · A TYPICAL FIRST CALL

"We need a new B2B portal."

One ask. Each vine hears a different question, and each one changes what we build.

THE FOUNDER ASKS
What is a slow quote costing them every month?
THE DATA SCIENTIST ASKS
Where do orders drop off today, and how do we know?
THE PM ASKS
Will buyers really stop phoning and emailing their rep?
THE DELIVERY LEAD ASKS
Which ERP sync breaks first on launch day?
THE CONSULTANT ASKS
Is a portal the answer, or is it a faster way to quote?

Problems I get called in for

Client work stays under contract, so here are the patterns instead. Happy to walk through real examples in conversation.

"We need AI."

USUALLY: A slow manual step nobody has mapped yet.
I START BY: Mapping the workflow, then using AI only where it removes real effort.

"Our ERP and store don't talk."

USUALLY: Nobody owns the data. It's rarely a missing connector.
I START BY: Agreeing on one source of truth before anyone picks a tool.

"Nobody uses the new system."

USUALLY: It was built for the buyer, not the people using it every day.
I START BY: Sitting with daily users, then rolling out in small, visible wins.

"We have data but no answers."

USUALLY: Plenty of reports, no decision attached to any of them.
I START BY: Naming the decision, then finding the few numbers that drive it.

I fall into rabbit holes. On purpose.

It's the same loop whether I'm choosing a black T-shirt or framing a client's problem. Reviews come late. First I want to know how the thing is made, and why.

↓ 01

Get fixated

IN LIFE One thing at a time: a tee, a pizza, a perfume.

AT WORK One real problem, not a wish list of features.

↓ 02

Learn how it's made

IN LIFE The materials, the process, and who it was really built for.

AT WORK How the business actually runs, before what the software does.

↓ 03

Hear from people who live with it

IN LIFE Long-term owners and makers, not launch-day hype.

AT WORK The team using the system daily, not just the buyer.

↓ 04

Test it myself

IN LIFE Use it until the novelty wears off and only the truth is left.

AT WORK Prototype it before I propose it.

↓ 05

Make it simple, then share it

IN LIFE A newsletter issue or a reel.

AT WORK A recommendation anyone can read in a minute.

What came out of the holes

HOLE	TRIED	KEPT
Black tees	Six or seven, over a year	Two stayed black
Earphones	Wireless, over-ear, the fancy stuff	Wired EarPods
Fragrance	A lot of perfumes	Le Sel d'Issey
Pizza	One Neapolitan pie	Sourdough, baked at home