WhatsApp CRM · IT & Software Companies
The demo went well. Then the deal died in a room you weren't in.
Written for how it & software companies actually work
For small teams selling software: product and SaaS vendors with a POS, ERP module, HRIS or school system, custom development shops where the founder still handles sales, and resellers implementing someone else's platform with local support.
The cycle is set by the buyer, not by you. An SME can go from demo to signed deal in a few weeks, so follow-ups a few days apart are fine. A corporate buyer commonly takes one to three months through internal approvals, and check-ins should be paced to their calendar rather than your impatience. A government tender runs to its own published dates; there, the thing to track is submission and clarification deadlines, not persuasion.
Enquiries follow institutional budget cycles more than festivals: bursts around corporate and government budget planning, and school system enquiries clustering before a new academic year. Decision-makers are often unavailable for meetings around April and December even when message volume does not drop.
A normal day in your inbox
- hi, can we see a demo of this? POS system
- we want to use your software, is the price monthly or one-time?
- we'd have about 5,000 users, what's the per-user price?
- can you migrate data from our existing system? we don't want to lose it
- can you email the quotation, we need to discuss internally before a meeting
- demo was good, but our IT person needs to look before we decide
- is support/AMC included in that price or charged separately?
- the specification is for a government tender, we need a sealed quotation
- another vendor quoted cheaper, what's the difference with yours?
Where the deals leak
- Demo requested
- Demo delivered
- Internal discussion
- Quotation sent
- PO or contract
- Implementation
- Go-live
- AMC renewal
The internal discussion after the demo. The person who liked what they saw now has to re-explain it, from memory, to people whose job is to be sceptical, and you gave them nothing to carry in.
Most sellers treat "we'll discuss internally" as the buyer's problem to come back about, so no date gets set and no summary gets sent. The objections that decide it, cost, migration risk, the IT person's workload, are raised in a room where nobody can answer them. The second leak sits after go-live, where the relationship goes quiet until a support ticket or an AMC invoice, and early dissatisfaction turns into "we're evaluating other vendors" before anyone hears it.
A board that matches your job
Read the Internal discussion column first each week. Few deals sit there at once, but each one is worth weeks of unpaid pre-sales work you have already spent.
Stage 1
Demo requested
Qualify here. Ask what they are trying to solve and who decides, before booking anything.
Stage 2
Demo done
Walkthrough delivered. A summary they can forward should go out the same day.
Stage 3
Internal discussion
The real drop point. Every card here needs a dated check-in, not a hope.
Stage 4
Quotation sent
Price, support and scope are out and comparable line by line.
Stage 5
PO / contract
Signed, or moving through a procurement chain.
Stage 6
Live
Implemented and running. From here it is check-ins, added seats and AMC.
Tags worth having
- SME buyer
- Corporate buyer
- Tender / RFQ
- Trial running
- Migration concern
- IT gatekeeper involved
- AMC due
- Reseller lead
Set it up once
Everything below happens inside WhatsApp Web, on the number you already use. No API, no new inbox.
Add InboxCRM to Chrome- 1
Qualify before you demo
Save a quick reply that asks what problem they want solved and roughly how many people would use the system, before a date is set. Demos are free and comparison is normal, so a share of requests were never going to convert. Two questions separate a real buyer from a research exercise without turning anyone away.
- 2
Send something they can forward
Keep a post-demo quick reply with a short summary of the three points that came up, as a document or message, plus the answers to the cost and migration questions that always surface internally. Quick replies carry files, so the one-pager goes out in one keystroke while the demo is fresh.
- 3
Never leave "internal discussion" undated
When a card moves to that stage, set the next check-in there and then in the appointment centre, and say the date out loud in the chat. A follow-up rule on the stage catches anything that drifts past it. This one habit addresses the primary drop point directly.
- 4
Treat the IT person as a second buyer
Tag the deal when a technical gatekeeper is involved, and offer to answer their questions directly rather than selling only to the owner. Someone whose reputation is on the line if the migration goes badly will become an obstacle if routed around, and an ally if consulted.
- 5
Pace follow-ups to the buyer, not to you
An SME can decide in weeks; a corporate approval chain commonly runs one to three months; a tender runs on its own published timeline and is not moved by persistence at all. Use separate tags or boards, and schedule check-ins to match. For a tender, what you track is submission and clarification dates, not persuasion.
- 6
Put the AMC renewal on the calendar before the invoice
Schedule a check-in a few weeks after go-live and another ahead of each renewal date. An AMC that arrives only as an invoice is a renewal you might lose; a conversation a month earlier is where added seats, a second department and a referral actually come from.
The messages that stall a sale
“Looks good, we'll discuss internally and let you know.”
Usually means
The demo worked on them personally, but now they have to defend it to people who were not in the room.What works
Give them something concrete to carry into that conversation, a short summary and answers to the two or three questions that always come up, and agree a date to check back. Treating this as a private matter you have no role in gives up exactly where you are most needed.“Our IT person has to look at it first.”
Usually means
There is a technical gatekeeper whose approval matters, and who may reasonably worry about migration effort or being blamed later.What works
Offer to answer their specific technical questions directly, and send documentation aimed at them. Dismissing that person as an obstacle to route around is usually what turns them into one.“Another vendor quoted cheaper.”
Usually means
On paper the quotations look interchangeable, so price is the only visible difference.What works
Ask what the other quotation includes, implementation, training, support hours, customisation scope, and offer a line-by-line comparison. Discounting on the spot without knowing what you are matching teaches every future buyer to open with a discount request.“Can you migrate our data? We're afraid of losing it.”
Usually means
Switching systems is a genuine business risk to them, not a preference.What works
Walk through what the migration actually involves, step by step, and what their team needs to prepare. Never promise a flawless, effortless changeover; that is a support relationship starting with a broken promise.“Is there a free trial?”
Usually means
Free-demo culture has trained buyers to expect a long evaluation runway before committing anything.What works
Be clear and consistent about what is genuinely free, the demo and walkthrough, and what has a boundary, such as a trial period or a scoped pilot. Refusing every trial loses serious buyers; open-ended access invites indefinite evaluation.
Quick replies to save first
Copy these, swap the details in [brackets], and save them as quick replies so you stop retyping them.
Demo request, qualifying
Thanks for the interest. Before we set up a demo, could you tell me the main thing you're hoping to solve, and roughly how many people would actually use the system? I'll build the demo around that.
Booking the demo
Does [Wednesday] at [3.00pm] work for a demo? It takes about [30 minutes]. Send me whichever link or location suits you.
After the demo
Thanks for your time. I'll send a short summary of the three main points we covered as a [PDF] so it's easy to share with anyone who wasn't on the call.
"We'll discuss internally"
Understood, take the time you need. If anything comes up about [cost, migration or support] while you're discussing, ask me right here. I'll check back on [date].
Cheaper competing quote
Happy to look at it. If you can tell me what their quotation covers for support, training and customisation scope, I'll compare it line by line and show you where the difference actually sits.
Free tools that help here: WhatsApp Link Generator, WhatsApp QR Code Generator.
The parts of InboxCRM you'll use most
Pipeline stages
Few deals in flight, each one meaningful. Stages make it obvious which ones have gone quiet since the demo.
Appointment centre and scheduling
Turn demos, post-demo check-ins and implementation reviews into dated events with reminders.
Quick replies
Send the qualifying questions, the post-demo summary file and the technical doc without retyping them.
Follow-up rules
Catch any deal sitting too long in Internal discussion, which is where this trade loses most of its work.
Contact notes and custom fields
Record user counts, buyer type, who the gatekeeper is and when the AMC falls due.
Questions from it & software companies
We already have a CRM. Why another one?
Most CRMs do not see WhatsApp, which is where the demo requests, the post-demo silence and the support questions actually happen. InboxCRM adds a board and notes on top of WhatsApp Web itself. It has webhooks, so events can be pushed to your own systems rather than kept in a second island of data.
Can several people on the team work the same pipeline?
InboxCRM runs inside the WhatsApp Web session on a given browser profile, and CRM data is stored locally there. So a shared sales number on one machine gives one shared board, while a BD executive on their own number gets their own. Decide who holds which WhatsApp account before you design your stages.
Should we use campaigns to message our client list about a new module?
Campaigns exist, for lists that opted in, with sending caps, quiet hours and per-contact cooldown. We would be careful here. A corporate or government contact tends to read broadcast-style messaging as a red flag rather than a convenience. An individually written note from the person who ran their implementation lands very differently.
Does it help with tender work?
Only as a tracker. You can hold submission and clarification dates in custom fields and schedule your own reminders against them. It does not run a tender, does not produce your technical response, and nothing about it improves your odds in a formal evaluation, which is decided on criteria outside any tool.
What are the honest limits?
It does not perform data migration, does not replace a technical proposal or a service agreement, and does not make the internal argument for your champion inside their own organisation. It only tracks what you enter. It runs in desktop Chrome on WhatsApp Web with no WhatsApp Business API, and scheduled messages need Chrome open with WhatsApp Web loaded when they are due.