Why Most CRM Projects Start Wrong
We receive CRM project enquiries every week. The ones that go well start with a clear brief. The ones that go badly — scope creep, budget overruns, a product that doesn't fit how the team actually works — almost always start with the same brief: "We need a CRM to manage our leads and pipeline. Can you give us a quote?"
That's not a brief. That's a category. A developer who quotes from that will either give you a wildly inaccurate number, or will charge you for extensive discovery to extract the information they need. Neither outcome is good for you.
The business owner who spends two hours documenting their sales process before their first developer conversation saves weeks of back-and-forth, gets dramatically more accurate quotes, and ends up with a product that actually fits. This article is that two-hour exercise, structured as a template you can fill out right now.
Section 1 — Your Sales Process (The Most Important Part)
A CRM is a model of your sales process in software. If the developer doesn't understand your process precisely, they'll build a generic one — and you'll spend the next year fighting your own tool. Answer these questions as specifically as possible:
- How do leads come in? List every source: website form, Facebook/Instagram ads, inbound WhatsApp, cold calls your team makes, referrals, trade shows, email campaigns. Each source may have different data fields and different initial workflows.
- What are your pipeline stages? Don't use generic names like "Prospect, Qualified, Proposal, Closed." Write out your actual stages, in sequence, with a one-sentence description of what moving to each stage means. If different product lines have different pipelines, document them separately.
- Who touches a lead and when? Draw a simple flowchart — who receives a new lead, who qualifies it, who demos, who writes the proposal, who closes. If some leads get escalated, document the escalation triggers.
- What data do you collect at each stage? Be specific. At lead entry: name, phone, city, source, product interest. After qualification: budget range, decision timeline, competitor being evaluated. After demo: feedback, objections, next action. This data model drives the entire CRM architecture.
- What activities does your team log? Calls, emails, meetings, WhatsApp messages, site visits? Which of these need a record in the CRM and which are informal?
Section 2 — Users, Roles, and Permissions
Access control is one of the most underspecified parts of a CRM brief — and one of the most important. A badly designed permission model either exposes confidential pipeline data to the wrong people or creates so many restrictions that users bypass the system entirely.
- Who are your user types? Common roles in Indian CRMs: Sales Rep, Team Lead, Regional Manager, Admin, Finance. Document each role you'll have.
- What can each role see and do? Can a sales rep see other reps' leads? Can a regional manager see leads outside their region? Can anyone delete a record? Who can change a deal's value after it's approved?
- How many users? Both now and your realistic expectation in 12 months. This affects both the architecture and the hosting cost estimate.
Section 3 — Integrations (Often the Most Complex Part)
Write down every system your CRM will need to talk to. Be as specific as possible — "connects to our accounts software" is not enough; "needs to push closed-won deals to Zoho Books and create an invoice draft" is a requirement a developer can scope.
- Lead sources that need auto-import: Facebook/Instagram Lead Ads, IndiaMART, JustDial, website contact form, WhatsApp Business API?
- Communication tools: Does the CRM need a built-in call dialler? Click-to-call? WhatsApp message logging? Email tracking?
- Accounting/ERP: Tally, Zoho Books, QuickBooks, a custom ERP? What events should trigger a sync — just closed deals, or also invoices, payments received, credit notes?
- Courier/logistics: (Relevant for D2C brands) Delhivery, Shiprocket, XpressBees? Do you need shipment tracking inside the CRM, or just AWB number storage?
- Marketing: Mailchimp, Brevo, WhatsApp broadcast tools? Should CRM lead data sync to marketing lists automatically?
Section 4 — Reporting Requirements
This section is worth spending real time on. The reports you need from your CRM determine the data model — and data models are expensive to change after launch. List the specific reports your sales leadership needs to run the business:
- Daily/weekly/monthly lead count by source
- Pipeline value by stage and by rep
- Lead-to-demo conversion rate by source
- Average deal size and days-to-close by product
- Rep activity report — calls made, demos done, proposals sent
- Won/lost ratio with lost reasons breakdown
- Revenue forecast based on weighted pipeline
For each report, note whether you need it in real time, daily, or weekly. Note whether it needs to be exportable to Excel or emailed automatically. Note if any reports need to be visible to clients or external stakeholders.
Section 5 — Data You Already Have
Almost every CRM project involves migrating data from whatever the team is currently using — spreadsheets, a previous CRM, paper registers. This affects timeline and cost significantly, and developers need to know about it upfront.
- Where is your current data? (Excel/Google Sheets, Salesforce, Zoho, old custom software, physical registers)
- How much data? (Approximate number of contacts, deals, and historical activity records)
- How clean is it? (Duplicate records? Inconsistent formats? Missing fields?)
- What must come across? (Active leads definitely, historical deals probably, old activity logs maybe)
The One-Page Brief Template
Once you've answered the questions above, structure your brief like this — one page, eight sections:
- Business overview: What you sell, who you sell to, your team size, your current GMV/revenue scale
- The problem: What specifically isn't working with your current setup
- Pipeline stages: Listed in order with one-line descriptions
- User roles & permissions: Table format — role, what they see, what they can do
- Required integrations: Bulleted list, as specific as possible
- Key reports needed: The 5–7 most important, described concretely
- Data migration: Source, volume, quality, what needs to come across
- Timeline & budget: Your target go-live date and your realistic budget range
A client sent us a 4-page brief before our first call last year. Our discovery took 45 minutes instead of the usual 3–4 hours. The project started 3 weeks earlier, came in exactly on budget, and the team adopted it in week one because it matched how they actually worked. The brief was the project's most valuable deliverable.
If you'd like a Word document template you can fill in directly, or if you want help thinking through your brief before you send it to developers, get in touch — it's a 30-minute conversation and it'll save you months.