Product Strategy
Turn business goals, customer needs, and operating constraints into clear product priorities and roadmap decisions.
Hi, I'm Tarun Product Leader.
I work with founders and leadership teams on the product and technology decisions that shape growth, execution, and scale.
About
Product, technology, and operations in the same conversation.
I work best when business priorities and technology decisions are in the same conversation — across product direction, architecture choices, AI use cases, team capacity, and day-to-day operations.
- Most useful when direction is unclear, execution has stalled, or scale is creating new problems.
- I've worked across SaaS workflows, marketplace systems, payments, AI use cases, and platform architecture.
- I focus on decisions that affect customers, costs, teams, and the next stage of growth.
How I Help
Clearer decisions. Stronger execution.
The decisions that affect how teams grow, deliver, and serve customers.
Discuss a challengeTechnology Strategy
Shape architecture, platforms, integrations, and delivery choices around the business model, not just the tech stack.
SaaS & Platform Design
Design workflows for onboarding, roles, permissions, payments, reporting, and reliability.
AI & Automation
Identify practical AI and automation opportunities that improve speed, decision quality, data visibility, and team efficiency.
Execution & Delivery
Connect roadmap, team capacity, vendors, tradeoffs, and release priorities so work moves with more clarity.
Cost, Risk & Security
Bring visibility to costs, reduce technical risk, strengthen security posture, and make platforms easier to trust.
When I'm Most Useful
When the next decision is not obvious.
These are the moments where product, technology, operations, cost, and customer experience need to be understood together.
- The roadmap is unclear or disconnected from business goals.
- Technology decisions are slowing growth.
- Product, engineering, and operations are not aligned.
- Systems are becoming harder to scale, maintain, or explain.
- There are AI ideas, but no clear practical use case.
- Costs are rising without enough visibility.
- Customer workflows feel fragmented, manual, or hard to trust.
How I Work
Start with the business pressure, not the feature list.
I start with what needs to improve and follow how the work actually moves.
Understand the business pressure
Clarify what needs to improve: growth, cost, delivery, customer experience, risk, or efficiency.
Map the real workflow
Follow users, teams, data flows, decisions, exceptions, and handoffs.
Separate signal from noise
Identify what should be built, simplified, automated, measured, secured, or avoided.
Design what needs to be built
Connect flows, roles, data, permissions, and architecture into something a team can build and trust.
Add practical AI where it helps
Use AI where it improves judgment, speed, visibility, or customer experience.
Build for adoption and scale
Make the next action clear, owned, and easier to execute.
Credibility
Where I've built real depth.
SaaS Workflows
Built and shaped workflows for onboarding, permissions, status movement, reporting, and support.
Marketplace Systems
Worked across seller onboarding, catalog quality, payments, and fulfillment visibility.
Payments & Business Workflows
Covered wallets, subscriptions, commissions, payouts, reconciliation, and financial controls.
AI Use Cases & Automation
Focused on retrieval, triage, decision support, workflow automation, and clear ownership.
Platform Architecture & Execution
Connected product strategy, architecture, team capacity, customer behavior, and delivery tradeoffs.
Thinking
A few principles I work from.
Strategy is useful only when it changes how people work.
A good plan eventually becomes product behavior, process clarity, and team adoption.
AI should improve judgment, speed, and visibility.
Useful AI reduces ambiguity, speeds up retrieval, and keeps ownership visible.
Most SaaS problems are also workflow problems.
Adoption, ownership, and operating habits often matter as much as the technical design.
Operational clarity creates business scale.
When roles, workflows, data, and decisions are visible, teams move faster with fewer hidden dependencies.