Bumpa

Helping small businesses manage their businesses effectively.

August 2021 - October 2021

View app
Project Header Image

Background

Bumpa is an inventory management system that helps small businesses manage their inventory, drive sales from multiple channels (offline and online), provide enough data to grow their business, and engage with their customers.

Problem

Initially, Bumpa was originally known a side project by the two founders founded in 2018 and were looking to revamp the entire platform to scale the business. The founders had also received feedback from its existing subscribers about the usability of the entire system. The app had only grown to a little over 1k subscribers while being more developed than other inventory management system in the current market and wasn't used in full capacity.

Contributions

  • User Research
  • Information Architecture
  • Interface Design
  • Product Strategy
  • Brand Design

Collaborators

  • Kelvin Umechukwu - Product Owner
  • Adetunji Opaleye - Engineering Lead
  • Stephen Ojo- Mobile Engineer

Goal

To design an improved mobile application with an updated brand, with a better user experience.

Outcome

Over 29k signups after the redesign process completed, compared to the initial 1k subscribers, over $3m GMV compared to the initial $8k GMV, >38k orders monthly orders completed compared to the initial 283 monthly orders , 250k pre-seed raised

My role

I collaborated with the Product Owner to define the product strategy, conduct user research and usability testing. I also led the visual design efforts, from branding to UI Design and collaborated with the developers to ensure it was adequately implemented.

Banner Image

Research

To kick off the new application, I started with a couple of brainstorming sessions with the founders to help understand the goal of the product. The initial product (Salescabal) focused heavily on its online store offering and less on its inventory management. We realized that while there is an increase in the number of internet users in Africa year on year, most transactions were still happening offline vs. online. Small businesses were transacting on multiple ends: offline, Instagram, facebook, twitter and weren't properly tracking their sales. There was still a big deficit in the market for proper bookkeeping for small businesses. It was, therefore, important to shift the goal of the product to inventory management and provide users with the flexibility to record from multiple channels. We also evaluated the existing application and spoke to existing customers to discover pain-points and important improvements to be made to the existing application.

  • The brand was not reflective of the scale the business was looking to go.
  • Onboarding users was problematic. New users didn’t know the next task to complete after signing up.
  • Adding a product to the application was a Herculean task, which dissuaded new users from using the app. New users with multiple products hated adding the products one by one before actively using the application because the product page required too many details to be filled.
  • There was no comprehensive data analytics to help the users make more informed decisions. Therefore, users had little or no incentive to record their orders.
  • Order statuses were confusing to understand, as there were too many labels, which made filtering confusing.

Learning from existing products in the market

We evaluated existing products and looked into other markets essential towards learning from them.

  • Flutterwavelogo
    Strengths
    • Easy integration with existing platforms through its API

    • Simple and clean user interface

    • Focused on online orders

    Weaknesses
    • No means to record offline sales or sales from order sources

    • No detailed analytics

    • Users cannot add own domain

    • No mobile app

  • Paystacklogo
    Strengths
    • Easy integration with existing platforms through its API

    • Simple and clean user interface

    • Focused on online orders

    Weaknesses
    • No means to record offline sales or sales from order sources

    • No detailed analytics

    • No ability to add multiple variations

    • Users cannot add own domain

    • No mobile app

  • Selarlogo
    Strengths
    • Clear offering

    • Multiple currencies available

    • Connection to various payment methods

    • Users can add thier own domain

    Weaknesses
    • Solely focused on digital products

    • No mobile app

Simple Brand Identity System

We decided that a name change was the right way to go because it helps set the course for where the product was looking to go. After settling on a name, I had to come up with a logo, and a simple brand system to build upon. This helps us refine the product going forward.

Bumpa Brand

Community-Driven Iterative Design Process

We wanted to move fast and break things, so we can learn more from our customers. We created a community of beta-testers of ideas we had in ways the product could evolve. We wanted to leave an open line of communication for our customers to reach us so we can learn what they require the most for the product, and how the product can evolve. I constantly tested the ideas of the product either by conducting user interviews with them, demoing what we were currently working on, and received valuable feedback. Some of the important sections improved on the app are:

Improved onboarding experience

The initial onboarding was a simple sign-up process, and users were left confused about what to do after setting up their accounts. Our first iteration had a to-do list on the homepage. Our initial assumption that users can easily find the to-do list and know what to do proved untrue. Users wanted everything spelled out step by step.

Before
After

Ease of adding a product

The initial flow for adding a product was a long-form which users found overwhelming to fill when they had more products. They also found that some details weren’t particularly relevant to their type of business, e.g., adding product options, which dissuaded them from adding the products. The goal for this section was to reduce the time needed to add a new product, providing flexibility for adding products. First, we introduced a quick method that allows users to add the product when they are recording an order. This way, they don’t need to add the products before using the app. Also, we introduced a minified version of the add product page, and users can add more details if they need to add more information about the products.

Simplifying order status

We modeled our initial order status after existing products in other markets, showing paid, unpaid, fulfilled, unfulfilled. Users found it hard to group each of the orders. Users wanted a more straightforward way to know the orders that required more actions. So while we kept the vocabulary, we changed the filters to enable users to get a quick result on orders they need to complete. We introduced “All,” “Pending - unfulfilled or unpaid orders,” “completed - paid & delivered” orders.

Before
Bumpa User flow
After
Bumpa User flow

Introducing a comprehensive data analytics

We tested an iteration of the design of the analytics page to see what details were important to users. Users offered new details they would like to see, enabling us to introduce improved analytics.

Key Takeaways

It was an amazing experience working on the product with the founders, seeing the traction they are on at the moment makes me happy. As with every experience, here are my major takewaways

Prioritize Experience Over Features

A startup means you have to make hard calls. You have to decide what to cut out to ship on time. I learned this balance— while still sticking to quality. It worked well because people responded to our difference in quality.

Don't be too precious over an idea.

The product has gone through many versions, some of them made public. It’s important not to hesitate to kill your babies. I debate with the product owner and mobile engineer for the best ideas. When we see a good idea, we take it; it's best for the product.