Setting up a sales pipeline in RapBooster CRM takes about two weeks: define 5–8 stages with exit criteria, connect every lead source, add the fields you'll actually use, automate assignment and follow-ups, set up calling, invoices and dashboards, then pilot and roll out. This guide walks through each step, with example pipelines for services, real estate and B2B.
Step 1: design your stages
Each stage should reflect a buyer decision, with a clear rule for moving forward.
| Stage | Exit criteria (move forward when...) |
|---|---|
| New lead | Contact attempted |
| Contacted | Two-way conversation happened |
| Qualified | Budget, need, timeline and decision-maker confirmed |
| Demo / meeting | Demo or site visit completed |
| Proposal sent | Quote or proposal shared |
| Negotiation | Terms being finalised |
| Won | Payment or signed order received |
| Lost | Reason recorded |
More background: sales pipeline stages for Indian SMBs.
Example pipelines
Services / agency: New → Contacted → Discovery call → Proposal → Negotiation → Won/Lost Real estate: New → Qualified → Site visit booked → Visited → Negotiation → Booked → Lost B2B SaaS: New → MQL → SQL → Demo → Trial → Proposal → Won/Lost
Step 2: connect lead sources
| Source | How to connect |
|---|---|
| Website forms | Form integration or webhook |
| Meta lead ads | Integration or webhook / Zapier / Pabbly |
| WhatsApp enquiries | RapBooster WhatsApp integration |
| Google Sheets | Sheet sync |
| Calls | IVR: missed and inbound calls create leads |
| Walk-ins / manual | Quick-add form or mobile |
| Portals / aggregators | CSV import or API |
Tag source and campaign on every lead so you can measure cost per deal. See integrations.
Step 3: add the right fields (and no more)
Must-haves: name, phone, email, company, source, product interest, budget, timeline, owner, next follow-up date. Industry extras: BHK and location (real estate); course and class (education); vehicle model (auto); policy type (insurance).
Keep required fields minimal: every extra field slows data entry.
Step 4: automate assignment and follow-ups
- Round-robin assignment or rules by product, city or language
- Instant task: "Call new lead within 10 minutes"
- Follow-up reminders by stage (e.g. proposal sent → reminder in 2 days)
- Stale deal alerts: no activity in 7 days → notify the manager
- Stage-change notifications to the team
- WhatsApp templates triggered by stage (e.g. a visit confirmation)
See the 5-touch lead follow-up rule and sales follow-up scripts.
Step 5: set up calling (Voice)
- Add an IVR number in Voice
- Enable click-to-call from the lead record
- Recordings and call history auto-logged on the timeline
- IVR menus route inbound callers to the right team
- Missed-call leads created automatically
Why it matters: CRM with IVR.
Step 6: quotes, invoices and contracts
- Create estimates and proposals from the deal
- Convert to invoices on Won (GST-ready). See how to write a GST invoice
- Contracts with e-sign workflows where supported
- Projects and Gantt for delivery after the sale, and tickets for support
Step 7: dashboards
| Dashboard | Shows |
|---|---|
| Pipeline value | Deals and value by stage |
| Conversion funnel | Stage-to-stage conversion % |
| Source performance | Leads, deals and revenue by source |
| Activity | Calls, messages and meetings per rep |
| Speed-to-lead | Average first-response time |
| Lost reasons | Why deals are lost |
Step 8: import existing data
- Export from spreadsheets or your old CRM.
- Clean duplicates and standardise phone formats (+91, +971).
- Map columns to CRM fields.
- Import a small test batch, then the rest.
- Assign owners and next follow-up dates.
Step 9: roll out in two weeks
| Days | Task |
|---|---|
| 1–3 | Configure stages, fields, sources, users and roles |
| 4–5 | Import data; set up automation |
| 6–8 | Pilot with 2–3 reps; collect feedback |
| 9–10 | Fix gaps; train the whole team (30-minute session + cheat sheet) |
| 11–14 | Go live; start the weekly pipeline review |
Step 10: run a weekly pipeline review (30 minutes)
- Deals stuck more than 7 days: next action and owner
- New leads not contacted: fix now
- Forecast for the month
- Lost reasons: what to change in pitch, pricing or targeting
Worked example: a 12-person agency sets up its pipeline
Illustrative scenario for a digital agency selling websites and retainers.
Stages chosen: New → Contacted → Discovery call → Proposal sent → Negotiation → Won / Lost. Exit criteria are written into each stage's description so everyone uses them the same way.
Sources connected: the website contact form (webhook), Meta lead ads (via Pabbly), WhatsApp enquiries (RapBooster WhatsApp integration), inbound calls (IVR) and referrals (manual quick-add).
Fields: service interest (website, e-commerce, app, SMM, ads), budget band, timeline, decision-maker, source, owner and next follow-up date. Only name, phone and service interest are required.
Automation:
- Round-robin assignment between three sales reps
- A task to call within 10 minutes of a new lead
- A proposal-sent reminder after 2 days, and again after 5
- A stale-deal alert after 7 days without activity
- A WhatsApp template when the stage moves to "Discovery call" (confirmation + calendar link)
Invoices and projects: won deals convert to invoices with GST, and a project with milestones (discovery, design, development, launch) is created automatically for delivery.
Weekly review: every Monday the team walks through stuck deals, the forecast and lost reasons. After a month, "price" dominates the lost reasons for small-business leads, so they add an entry-level package, and the win rate for that segment improves.
Recommended automation recipes
| Trigger | Action |
|---|---|
| New lead created | Assign owner; create "call in 10 min" task; send WhatsApp acknowledgement |
| Stage → Qualified | Notify the owner; schedule the discovery call |
| Stage → Proposal sent | Reminder in 2 days; manager notified if value exceeds a threshold |
| No activity for 7 days | Alert the owner and manager |
| Stage → Won | Create invoice; create project; send welcome message |
| Stage → Lost | Require a lost reason; add to the 90-day nurture list |
| Invoice overdue | Payment reminder on WhatsApp and email |
Data hygiene rules
- One lead per phone number: merge duplicates weekly.
- Standard formats: +91 and +971 prefixes, and city names from a fixed list.
- Mandatory lost reasons so reports stay meaningful.
- Owner on every open deal: no orphaned leads.
- Next follow-up date on every open deal: the single most useful field in any CRM.
Common mistakes
- Copying someone else's pipeline: design stages around your buyers' decisions.
- Too many required fields: reps skip the CRM and go back to spreadsheets.
- No training: a 30-minute session plus a one-page cheat sheet saves weeks of confusion.
- Leaders not using it: if managers run reviews from the CRM, the team keeps it updated.
- Automating before the process is clear: define the steps manually first, then automate.
Questions teams ask us during setup
Should leads and deals be separate? For most SMBs, one pipeline where a lead becomes a deal as it moves through the stages is simpler. Larger teams with separate lead-qualification (SDR) and closing (AE) roles may prefer a lead stage followed by a deal pipeline.
How do we handle multiple products or services? Either use one pipeline with a "product" field (simpler reporting), or separate pipelines when the sales processes differ significantly, e.g. one-time website projects vs monthly retainers.
Can we use the CRM on mobile? Yes. Field teams can log calls, update stages and add notes from their phones. Keep the required fields minimal so updates take seconds.
How do we migrate from spreadsheets without chaos? Clean the sheet first (remove duplicates, standardise phones and cities), import a small test batch, check the field mapping, then import the rest and assign owners and follow-up dates immediately.
Who should own the CRM internally? Assign one admin, usually the sales head or an operations person, who manages fields, automation, users and data hygiene, and runs the weekly review.
How soon will we see value? Most teams see immediate benefits in visibility (no lost leads, clear follow-ups) within the first two weeks. Conversion improvements come as you act on the data: faster responses, better qualification, and fixes for the top lost reasons.
One-page action checklist
- Stages with written exit criteria
- All lead sources connected and tagged
- Minimal required fields; industry fields added
- Assignment, first-response and follow-up automation
- Calling set up (Voice) with recordings
- Estimates, invoices and projects configured
- Dashboards for pipeline, sources, activity and lost reasons
- Team trained; weekly pipeline review on the calendar
Key terms in this guide
- CRM: Customer relationship management software that keeps every lead, call, message and deal in one timeline.
- Sales pipeline: The stages a lead moves through from first contact to won or lost, used to forecast and spot bottlenecks.
- Lead scoring: Ranking leads by fit and intent (budget, timeline, engagement) so the team calls the hottest ones first.
- IVR: Interactive voice response: phone menus that route callers to the right team and log calls against the lead.
- Click-to-call: Dialling a lead straight from the CRM record, with the call logged and optionally recorded.
- GST invoice: A tax invoice with the fields required under India's GST law, including GSTINs, HSN/SAC codes and tax breakup.
Plans and pricing (excl. GST)
RapBooster has one CRM plan: every business app for your team, with 5 users included and a simple price per extra user. WhatsApp, Email and the phone gateway are separate plans per account. Live prices are on the pricing page.
Start with a free trial of RapBooster CRM, or compare it with others on the CRM compare page. New to CRMs? Read what is a CRM.

