Product build · Business growth

Building EzyMitra: a WhatsApp-first platform for small businesses

A write-up of why we built EzyMitra, the decisions we made about scope and simplicity, and how the platform is structured. Described qualitatively — we do not publish figures we cannot verify.

  • Product
  • WhatsApp Business API
  • Lead management

In this case study

  1. Business context
  2. The problem
  3. The existing process
  4. The challenge
  5. The solution
  6. What we deliberately left out
  7. Technology
  8. Implementation
  9. Workflow
  10. Outcome

TypeOur own product

FocusLead management, WhatsApp automation, follow-ups

Primary usersOwner-run and small-team businesses

ChannelOfficial WhatsApp Business API

Business context

EzyMitra was built for a category of business that conventional CRM software serves poorly: owner-run and small-team businesses where customers message instead of emailing, where the owner is closely involved in every sale, and where nobody has time to maintain a complicated system.

These businesses are often good at what they do. Their weakness is not service quality — it is that the sales side runs on a personal phone. This is a write-up of how we approached that problem as a product.

The problem

Enquiries arrive through WhatsApp, calls, website forms and social messages, and all of them end up on somebody’s device. There is no shared record of who has been contacted, no reminder for a follow-up, and no way to see what a colleague already promised a customer.

The consequences are specific: slow first responses, duplicated or contradictory replies, forgotten follow-ups and a customer history that leaves when a staff member does.

  • Conversations trapped on individual phones
  • No follow-up discipline beyond memory
  • No visibility of enquiry volume or response time
  • No ownership of a lead once it arrived

The existing process

In a typical setup, a customer messages the owner’s or a salesperson’s number. The reply happens when that person is free. Details are remembered or scribbled. If the customer goes quiet, nothing happens — the enquiry simply drops out of view.

When these businesses tried a conventional CRM, adoption failed for a consistent reason: it added data entry without removing any of the phone-based work. The conversation stayed on WhatsApp, and the CRM became a place to re-type it.

The challenge

The design problem was restraint. The platform had to add enough structure to stop leads being lost, while adding so little friction that a two-person team could adopt it in a day.

The technical problem was the channel itself. WhatsApp automation is tightly governed: it requires the official Business API, approved message templates, respect for the 24-hour service window and explicit opt-in. Unofficial automation of a personal number risks a permanent ban, which for most of these businesses would mean losing their main sales channel.

The solution

We built the platform on the official WhatsApp Business API so a business keeps one verified number while a team works from a shared inbox. Conversations are assigned, tagged and logged against a customer record.

Every enquiry, whatever its source, becomes a lead with a source, an owner and a next action. An automated first reply acknowledges it within seconds and asks the qualifying questions that save a phone call. Follow-ups are scheduled rather than remembered.

Around that core we added only what a small business genuinely uses: review requests after a completed job, consented broadcasts, catalogue and quotation sharing, and a small set of dashboards.

  • Shared inbox on a single business number
  • Automatic first response and qualifying questions
  • Assignment rules so ownership is never ambiguous
  • Follow-up scheduling with respectful automated nurture
  • Review requests and simple insights

What we deliberately left out

A large part of the design work was deciding what not to build. We left out deep pipeline customisation, elaborate custom-field builders, complex forecasting and anything that required a training programme.

Every feature was tested against a single question: would a busy owner use this on a Tuesday afternoon? If not, it stayed out of the first version.

Technology

The platform is a web application with a mobile-first interface, because the people using it are usually on their phones. The backend handles WhatsApp webhooks, message queueing, template management and scheduled follow-ups.

  • PHP and Laravel-style architecture with a relational database (MySQL)
  • WhatsApp Business API integration via webhooks, with queued outbound messages
  • Scheduled jobs for follow-ups and reminders
  • Role-based access, audit logging and data export
  • n8n workflows for optional integrations with other tools

Implementation

We built in stages, starting with the smallest loop that proved the idea: a message arrives, it becomes a lead, the right person is notified, and a follow-up is scheduled. Only when that loop was dependable did we add automation, then broadcasts, then reviews and insights.

Onboarding a new business follows a similar sequence: provision the API number, get the first templates approved, import existing contacts, configure assignment and follow-up rules, and train the team on a short set of daily screens.

Workflow

A typical enquiry moves through the same six steps: it arrives; an automatic reply goes out; it is assigned to an owner; the team replies from the shared inbox; a follow-up is scheduled; and an outcome is recorded, followed by a review request for completed work.

Because each step is recorded, the business can finally answer questions it could not before: how many enquiries arrived, how quickly they were answered, and how many were never followed up.

Outcome

Businesses using this approach move from conversations scattered across personal phones to a single shared record with clear ownership and scheduled follow-ups. The change is primarily one of visibility and discipline rather than of technology.

We deliberately do not quote conversion or revenue figures here. Results vary widely by business and category, and we would rather describe what changes structurally than attach a number we cannot support.

Related

Services and products involved

WhatsApp-first business growth platform

EzyMitra

WhatsApp-first platform for lead management, customer communication, automated follow-ups, reviews and business insights.

  • WhatsApp automation
  • Lead management
  • Follow-ups
  • Reviews

WhatsApp Automation

WhatsApp Business API workflows: instant replies, notifications, reminders, nurture sequences and conversations logged in your CRM.

  • WhatsApp Business API
  • Notifications
  • Lead nurturing
  • CRM logging

CRM Development

Custom CRM systems with lead capture, assignment rules, pipelines, follow-ups, WhatsApp integration and reporting that reflects reality.

  • Lead management
  • Sales pipeline
  • Assignment rules
  • Follow-ups

SMEs

CRM, WhatsApp automation, websites and custom software for growing businesses replacing spreadsheets and manual coordination.

  • CRM
  • WhatsApp
  • Websites
  • Automation

Next step

Have a similar problem to solve?

Every build starts with the same question: where is time and revenue actually leaking? Tell us about your process and we will suggest where to start.

Start Your Project WhatsApp