Designing for the wrong market

Bizbox, a free app, was losing almost every U.S. user after the first day. The research I led into why pointed the company to Brazil, and to a new product.

Brazilian barber managing Pix payments, receipts and handwritten accounts at his worktable
Pix payments, receipts and handwritten records on one worktable, the routine the product had to fit.

The product launched in the United States as Bizbox, a free, multi-language scheduling tool with embedded payments, built for Latino home service workers. It never found product-market fit there. In 2021, most people who downloaded it stopped using it after the first day.

I joined as the founding Product Designer while the company was struggling with retention, and led the research into why. Discovery was mine to run: planning, interviews, synthesis, the principles that came out of it, the MVP scope and the interface itself.

A good part of it was facilitation rather than design. I got the founders to agree on what the first release had to prove, then worked with Product, Engineering and QA to build it mobile-first.

The Bizbox app in June 2021, with a team card for inviting professionals and a form for booking an animal care and training appointment
Export 01 · 4:3
The Bizbox app Slide 08 · crop the phone mockups out of the blue panel. No slide title, no “a.” mark.
Bizbox in the United States, with team invites and appointment booking.
Google Analytics user retention chart for the 42 days ending 31 August, dropping from 100% on day zero to under 10% the next day and close to zero after that
Export 02 · 4:3
The retention cliff Slide 09 · crop the two Google Analytics cards side by side. Drop the slide title and the footnote.
Retention collapsed after day one · Google Analytics, 42 days ending 31 August 2021.
The challenge

Wrong people, or the wrong promise?

The first question was why people stopped using an app that cost them nothing. We split it in two: were we reaching the wrong segment, or offering the wrong value proposition? The promise at the time was to save time and impress customers. Each quadrant got its own hypotheses and the tests that could rule them out.

A two by two matrix crossing wrong and right segment with wrong and right value proposition. Each filled quadrant lists hypotheses and possible tests, such as trying other segments, testing the app as is in Brazil, and redefining a value proposition stronger than saving time and impressing customers
Export 09 · 4:3
The challenge matrix Segment against value proposition, with hypotheses and tests in each quadrant.
Segment against value proposition · the first map of why a free app was losing its users.
The unknowns

We started with uncertainty, not features

The segment side of the matrix led us to solo entrepreneurs in Brazil. Before making product decisions there, we listed the questions that could change the direction of the company.

  1. 01Who are Brazilian micro-entrepreneurs?
  2. 02How do they manage their business today?
  3. 03Which assumptions from the U.S. product no longer hold?
  4. 04What would users need on day one?
  5. 05What should we intentionally leave out?
No interface would have saved a product aimed at the wrong problem.
A CSD matrix with three columns of sticky notes: green certainties, yellow suppositions and red doubts
Export 03 · 21:9
The CSD matrix Slide 12 · crop the three sticky columns. Keep the Certainties, Suppositions and Doubts headings, drop the slide title.
Certainties, suppositions and doubts · separating what we knew from what we assumed, before the first interview.
Research

What the interviews found

Rather than validate the existing product, we used interviews and observation sessions to learn how Brazilian entrepreneurs worked day to day.

The entrepreneurs we met were not using CRMs, managing detailed spreadsheets or looking for advanced business software. They ran their businesses on tools they already trusted and connected the steps by hand.

In Brazil, far more of a solo entrepreneur's routine was still done by hand than in the U.S. Digitizing it would give back the hours spent on admin, so people could focus on the work their clients paid them for.

The research plan in Notion for interviews with Brazilian professionals: 30 minute in-depth interviews, with sections for objective, hypothesis, recruitment, target users, interview guide, answers and analysis
Export 04 · 4:3
The research plan Slide 14 · crop the Notion window. Keep the “32 · 30min in-depth interviews” card if it crops cleanly beside it.
Thirty-two interviews of thirty minutes each, planned around daily routines rather than product features.
Two Brazilian personas, Carol, a beautician, and Tabatha, a personal trainer, each with demographics, pains and needs, and potential solutions
Export 05 · 4:3
The personas Slide 16 · crop the four persona cards. Check the body text is legible at export scale, it reads greyed out on the slide.
Carol and Tabatha, two of the four personas the interviews kept returning to.
The existing business stack, three familiar tools connected by hand.

People wanted a product shaped around the way they already worked, not another set of features to learn.

Strategy

Five assumptions became five product decisions

The research changed the product strategy, and that strategy became the MVP scope.

Previous assumptionWhat we learnedProduct decision
Entrepreneurs want business softwareThey want simple workflowsPrioritise essential tasks over feature depth
More features create more valueSimplicity increases confidenceRemove unnecessary complexity
Desktop-first workflows are acceptableBusiness happens on the phoneDesign mobile-first
Users will adapt to the productThe product must adapt to usersMirror familiar behaviours instead of creating new ones
Onboarding should explain everythingUsers learn by doingFocus on immediate value instead of education
An atomic research database in Notion, with each finding tagged by status, confidence, relevance, profession and source
Export 06 · 21:9
Atomic research Slide 15 · crop the Notion nuggets table. Export at 2x so the column headings stay readable.
Every finding tagged and traceable · the evidence the founders and I argued the strategy from.
The MVP

The smallest product that could validate the direction

The MVP had to take work off people already overloaded by running a business. It covered fast invoicing, Pix-ready payments, simple customer management, clear language and enough restraint to stay quick on lower-end Android devices.

It followed three principles. Fast: immediate value before explanation. Familiar: existing behaviours before new mental models. Light: essential workflows before feature depth.

Three Quaddro app screens for professionals: an empty September agenda, creating a service plan, and a finances list of Pix and manual payments
Export 07 · 21:9
The app for pros Slide 23 is empty and slide 22 is the Figma canvas. Best source is the real screens: export them from the “App for pros” file directly, or crop the prototype canvas as a fallback.
The app for professionals · agenda, service plans and finances.
A professional's Quaddro booking page in the browser, with opening hours, location, plans and packages, single services with prices and a button to book
Export 08 · 21:9
Quaddro in Brazil Slides 24 and 25 · crop the web booking screens. Pick whichever shows the client-facing flow most clearly.
The client side · a professional's booking page, with plans, packages and single services.
Business impact

From adapting a product to rebuilding it

Bizbox did not cross the border. It was rebuilt around Brazilian entrepreneurs and relaunched under a new name, Quaddro. The research led the pivot, and the company kept building on that product through to a R$16M funding round.

U.S. → BR
the research that led the company to Brazil
MVP
built around how Brazilian entrepreneurs worked
R$16M
funding round, raised as the product kept evolving
Before

“Why are people not using a free app?”

After

“What product should exist for this market?”

Reflection

Question assumptions before proposing solutions

When a product enters a new market, the assumptions behind it carry more risk than its interface.

Since Quaddro I start with the assumptions, and that still holds at a marketplace serving millions of users.