StorePlus.AI: Designing 0-1 warehouse management B2B SaaS product for faster operations

B2B SaaS

Supply Chain

0-1 Shipped

Role

Solo UX Designer

0-1 Design: UX research, design, wireframes, prototyping, quality assurance. developer handoff

0-1 Design: UX research, ideation, design, prototyping, quality assurance. developer handoff

Duration

12 weeks;
worked full-time:

(Jul' 23- Jul' 24)

Stack

Figma, PowerBi

Team

1 Designer

2 Founders

3 Engineers

Here’s a 1 min TL;DR version

THE PROBLEM

Small retailers and wholesalers across India had no shared system for supply chain operations; everything ran on WhatsApp, Excel, and memory

3 core systematic problems:

Fragmented communication

Manual inventory tracking

Zero order visibility

SOLUTION PREVIEW

StorePlus.AI- a B2B commerce platform that replaced informal tools with a unified operational system

Designed from 0-1 with 3 main features: 1. Modular Dashboard 2. Order Tracking 3. Chatbot

IMPACT

User adoption shot up within 3 months of launch 🚀

Diving deeper into the project

Let’s start from the beginning

MY ROLE

HOW I SOLVED THE PROBLEM

I built the platform from 0-1, driving end-to-end product design from research through developer handoff, collaborating directly with the founders and engineers across 12 weeks for MVP launch.

RESEARCH

I conducted mixed-method research to understand how users operated before any platform existed

56

Response to

Open-Ended Surveys

8

User interviews

(4 retailers, 4 wholesalers)

4

Contextual Inquiry

8

Competitive Analysis

In-depth Research Plan

Surveys & Interviews

🧑‍💼 4 wholesaler interviews; 4 retailer interviews
📋 56 surveys

Goal: Uncover how users currently manage orders, what triggers a check-in, and what makes them feel confident vs. anxious in their workflow.

Findings: Users weren't struggling to use tools, they were surviving without the right ones. Every process was manual, every update required a person, and every decision was made on memory alone.

Contextual Inquiry

Goal: Observe naturalistic behavior and identify the informal systems users had built to compensate.

Findings: Every workaround told us what the platform needed to replace: sticky notes for order references, group chats for status updates, handwritten ledgers alongside digital records. None of these were habits. They were infrastructure.

Competitive Analysis

KEY INSIGHTS

Using Affinity Mapping, I analyzed the research data to find 3 key insights

1

Adoption depended on system credibility. Users needed to trust the platform before they would use it.

Adoption depended on system credibility. Users needed to trust the platform before they would use it.

2

Both user groups had opposing cognitive models that had to coexist in one interface.

Both user groups had opposing cognitive models that had to coexist in one interface.

3

Every behavioral workaround pointed directly at a gap the platform needed to fill.

Every behavioral workaround pointed directly at a gap the platform needed to fill.

Clustering 30+ user insights into themes that shaped the redesign

Detailed User Personas

FINDING OPPORTUNITY IN USER JOURNEY

Two workflows. One Interface.

Wholesalers

Manage 50+ orders daily. They need to scan quickly, spot problems at a glance, and take bulk actions. Dense information and fast scanning are priorities.

Retailers

Track 2-3 orders. They want deep detail about each order like, timeline, messages, proof. They need to investigate, not scan.

WHOLESALER JOURNEY MAP

RETAILER JOURNEY MAP

The Problem Statement

🧠 How might we design a supply chain platform that users trust enough to replace the tools they already rely on?

REFINING THE PROBLEM STATEMENT

IDEATION

Two workflows. One Interface.

Wholesalers

Manage 50+ orders daily. They need to scan quickly, spot problems at a glance, and take bulk actions. Dense information and fast scanning are priorities.

Retailers

Track 2-3 orders. They want deep detail about each order like, timeline, messages, proof. They need to investigate, not scan.

Marking opportunities in the user journey, creating information architecture and ideating features

IDEATION

Ideating features and creating information architecture

WHOLESALER JOURNEY MAP

RETAILER JOURNEY MAP

BRAINSTORMING

INFORMATION ARCHITECTURE

EXPLORING DIFFERENT IDEAS WITH LOW-FIDELITY WIREFRAMES

Choosing Concept A: Despite its rigidity, it prioritized speed, scalability, and familiarity which was the foundations of trust in a B2B environment. So, I decided to further explore Concept A.

Why Not Other Concepts?

SCOPING THE MVP

The founders wanted to ship everything at once; I used effort and impact to protect the sprint and define V2

⚠️ Challenge: The founders wanted to push the entire platform in one sprint. With 12 weeks and 3 engineers, that wasn't feasible without compromising quality on every feature.

  1. Dashboard
Medium dev effort
Medium time
High impact
✅ V1
  1. Order tracking visibility
Low dev effort
Less time
High impact
✅ V1
  1. AI supply chain assistant
High dev effort
More time
High impact
→ Prototyped in parallel · V2

Decision: Prioritized #1 and #2 because together they addressed the root credibility gap with manageable technical risk and within the V1 release window. The AI assistant was prototyped in parallel to validate the concept without blocking the sprint.

DEFINING SUCCESS METRICS

Before writing a single wireframe, I defined what success looked like across three levels: trust restoration, behavioral adoption, and operational efficiency

Order Completion Rate: 90%+

Why: For a 0→1 product, completion rate is the purest signal of trust. If users trust the platform enough to complete orders on it instead of reverting to their old methods, the core problem is solved.

Impact: Higher adoption rate

Supporting Metrics

Key Features Designed

FEATURE #1: MODULAR DASHBOARD

Designed Storeplus.AI which is a B2B product that connects small wholesalers and retailers operations across India

I built the platform from 0-1, driving end-to-end product design from user research, information architecture, interaction design, usability testing to developer handoff. As the solo Designer, I collaborated directly with the founders and engineers over the span of 12 weeks.