Tithi Mondal

Article6 min readUpdated

CRM Design for Small Businesses: Screens Staff Will Use

CRM design for small teams: the lead tracking screen, sales pipeline view and follow up reminders that a busy owner will actually open every day.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

CRM Design for Small Businesses: Screens Staff Will Use: cover illustration

A coaching centre owner gets 15 enquiries after a newspaper advertisement. Five arrive by phone, six on WhatsApp and four through a web form. By Friday nobody remembers who was promised a call back. This is the problem a CRM solves. CRM stands for customer relationship management. It is a tool that records who enquired, what was said and what must happen next.

Who uses a small business CRM, and in what conditions?

The users are usually the owner, one or two sales staff and sometimes a part time telecaller. They work on mid-range Android phones, between calls, often standing in a shop or travelling.

This changes the design. A CRM for a 3 person team is not a smaller version of a large sales tool. Nobody has time to fill 15 fields. The owner opens it twice a day to ask one question: who should I call now?

Before designing, I ask these questions:

  • Where do enquiries arrive: phone, WhatsApp, walk-in, web form, or all of them?
  • Who talks to the customer, and who closes the sale?
  • Does the team work in English, Hindi, Bengali or a mix?
  • What happens to a lead who says "call me next month"?

The answers decide the fields. If you are unsure how to learn them, my guide on user research for startups shows how to do it in a few conversations.

What should the lead tracking screen show?

The lead tracking screen is the daily home of the CRM. It must show who needs action today, sorted by urgency, before it shows anything else.

Each row needs only five items:

  1. Name and phone number, with a call button and a WhatsApp button on the row itself.
  2. Source: phone, WhatsApp, web form, referral.
  3. Current stage, shown as a short label.
  4. Next action and its date, for example "Send fee details, today".
  5. Last contact, in plain words such as "3 days ago".

The top of the screen holds three tabs: Today, Overdue and All. Overdue has a count in red so it cannot be ignored. Search sits below the tabs. For deeper filter patterns, see search and filter UX design.

One decision matters here. Do not make the owner choose between a list and a form. Tapping a row opens a detail screen with the phone number at the top, a notes timeline in the middle and one large "Log a call" button fixed at the bottom.

How should a sales pipeline view work?

A sales pipeline view shows every open lead as a card inside a column for its stage. It answers the question: where is my money stuck?

Keep the stages few. For most small businesses these 5 work:

StageMeaning
NewEnquiry received, nobody has replied yet
ContactedFirst conversation done
Quote sentPrice or proposal shared
NegotiatingCustomer is asking questions or comparing
Won or LostFinal outcome, with a reason

Cards show the name, value in rupees and days spent in the stage. A card that sits in one stage for many days changes its border colour, so the owner sees the stuck deal without reading.

On a phone, columns do not fit. Show one stage at a time with a horizontal tab strip, and let the user change a stage from a menu on the lead detail screen instead of dragging. Dragging a card across a small screen fails often. A "Move to" button works every time.

Always ask for a reason when a lead is marked Lost. A short list such as "Price", "Chose someone else", "Not ready", "No reply" gives the owner real learning after one month.

How do follow up reminders actually get used?

Follow up reminders work when they are created automatically at the moment a call is logged, and when they arrive where the person already looks. A reminder that needs a separate screen and a separate form will not be created.

Make the date part of the call log. After saving a note, the screen asks: "Next follow up?" with quick choices: Tomorrow, In 3 days, Next week, Pick a date. The default is never "none". If the user wants none, they must tap "No follow up needed". That one extra tap prevents most forgotten leads.

For delivery, an in-app badge is not enough. Small teams live in WhatsApp, so a reminder by WhatsApp or SMS at 9 in the morning with a count, such as "4 follow ups today", works better than many separate alerts. I cover channel choices in notification UX for push, SMS and WhatsApp.

Also design the missed reminder. If a follow up is 2 days late, it moves to Overdue and the owner sees it. A CRM should show gaps, not hide them.

What is the main task, step by step?

The main task is logging a call. If this takes more than 20 seconds, the habit dies. Here is the sequence I design for.

  1. The user opens the lead from Today and taps the call button.
  2. After the call, the app returns to the lead and shows the "Log a call" sheet automatically.
  3. The sheet offers an outcome in one tap: Spoke, No answer, Busy, Wrong number.
  4. If Spoke, a note field opens with the keyboard, plus suggested stage change such as "Move to Quote sent?".
  5. The user chooses the next follow up from the quick dates.
  6. One tap on Save. The lead disappears from Today and reappears on its new date.

Voice notes help here. A staff member walking out of a meeting can speak two sentences instead of typing in Hindi or Bengali on a small keyboard. Check that your fonts and keyboards handle the language, as covered in regional language app design.

What mistakes make a CRM empty after a month?

A CRM becomes empty when entering data feels like a chore with no reward for the person typing. These are the common causes.

  • Too many required fields. Ask for name and phone. Everything else is optional and can be added later.
  • Duplicate leads. The same person enquires by phone and by form. Detect the matching phone number and offer to merge.
  • Reports for the owner only. If staff see no benefit, they stop. Give staff their own Today list and a simple count of what they closed.
  • No import. Most small businesses already have a spreadsheet or phone contacts. Without an import screen, nobody starts.
  • Hidden stage rules. Staff move cards to look good. Keep stage meanings written on the screen.
  • Desktop only design. If the phone version is an afterthought, the team will go back to WhatsApp chats.

The CRM also connects to other screens. Quotes and invoices come from it, so see invoice and quotation screen design for that next step. If the owner needs charts of sales by month, my article on admin dashboard UI UX design covers the overview screen.

If you are planning a CRM or an internal sales tool and want the screens designed around how your team really works, you can see my UI/UX design service or write to me through the contact section.

Frequently asked questions

How many fields should a lead form have in a CRM?

Two required fields are enough: name and phone number. Source, budget and notes can be optional, so staff can save a lead in under 10 seconds and add detail later.

Should a small business CRM be built as a mobile app or a web app?

Design the phone version first if your team works away from a desk. A responsive web app that works well on a mid-range Android phone is often the simplest start.

How many pipeline stages are too many?

More than 6 stages usually means staff will skip stages or guess. Start with 4 or 5 and add one only when the team clearly needs it.

How do I stop staff forgetting to log calls?

Show the log sheet automatically after every call, and make the next follow up date part of the same step. Reducing the task to a few taps works better than reminders to update the CRM.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.