Freelance project - Marketplace stabilisation

Stabilising Makwa so laundry orders, vendors, and admin operations could run smoothly.

In our early freelance days, Makwa came to us with a mobile marketplace and admin-panel stack that needed fixes, stability work, and operational support across customer orders, vendor flows, and internal management tools.

Client Makwa
Public funding context Reported six-figure US dollar round in 2020
Product model On-demand laundry pickup, delivery, vendors, and tracking
Scope Mobile app fixes, admin panels, and operational stability
Makwa laundry marketplace screens with mobile app views and an adapted admin operations panel.
Makwa web and mobile product screens, adapted for the Codtronix case study.

System delivered

A marketplace support layer across mobile, vendors, orders, and admin tools.

The work was less about a new visual redesign and more about making the existing product dependable enough for real operations: customers booking laundry, partners processing orders, and admins keeping the service moving.

01

Mobile app stabilisation

Fixed issues in the customer-facing app so booking, preferences, pickup timing, and service flows behaved more reliably.

02

Admin panel support

Supported internal tools used to manage orders, customers, vendors, service states, and operational exceptions.

03

Vendor operations

Improved the software layer around laundry partners, order handling, status movement, and fulfilment visibility.

04

Order lifecycle

Helped tighten the flow from customer request through pickup, vendor processing, delivery, payment, and review.

05

Preference and service flows

Supported laundry-specific product details such as garment preferences, detergents, service options, and clear customer instructions.

06

Support workflows

Worked around the practical support needs of an on-demand operation where delays, changes, and customer communication affect trust.

Customer books Pickup scheduled Vendor assigned Preferences captured Order tracked Admin resolves Delivery completed Review collected

The challenge

Why the obvious build path was too risky.

Makwa was operating in a demanding on-demand service model with public startup momentum behind it. Customers expected scheduled pickup and delivery, vendors needed clear order information, and internal teams needed admin tools that did not slow them down. When marketplace, mobile, and admin-panel issues stack up, operations feel the pain immediately.

The approach

How the work was made smaller, clearer, and more accountable.

  1. Worked through mobile-app issues affecting the core customer journey: booking, service selection, preferences, timing, support, and order visibility.
  2. Supported the admin-panel side so internal teams could manage customers, orders, vendors, exceptions, and operational state with fewer blockers.
  3. Focused on stability, bug fixing, and practical operational fixes rather than cosmetic change, because the product already had real marketplace and investor-pressure context.

The outcome

What the team gained beyond shipped code.

  • Booking, pickup, and service flows stopped breaking mid-order, so the team spent less time firefighting the app and more time running the operation.
  • Admin and vendor teams got a panel that reflected the real state of an order, cutting the back-and-forth needed to resolve exceptions and customer complaints.
  • A stronger technical foundation for a funded, publicly-positioned startup to keep expanding pickup, delivery, tracking, payments, and vendor quality without the app itself becoming the bottleneck.

Discuss your context

Need to stabilise a product that is already in the market?

We can help identify the flows costing you orders, support time, or trust, then stabilise the app and admin tools your operation depends on.

  • See what should be built, simplified, or avoided
  • Leave with risks, constraints, and a credible next step
  • Talk to senior product and engineering people, not a script
It could be yours Show us the workflow, product idea, or system constraint you want to turn into an advantage.

We will help you decide what to build first, what to avoid, and how to move from messy context to usable software.