Who this is for
Businesses whose customer data lives in a sales person’s phone, three spreadsheets and an inbox. The moment a second person starts handling enquiries, or the owner wants to know which campaign produced which customer, a CRM stops being optional. This service also fits companies that bought a CRM, use it as an address book, and want it to actually run the pipeline.
Choosing the CRM
| CRM | Fits best | Watch out for |
|---|---|---|
| HubSpot | Marketing-led businesses that want forms, email, pipeline and reporting in one place; strong free tier | Paid tiers rise steeply once you need automation and multiple pipelines |
| Zoho CRM | Nepal businesses that want a full suite (Books, Desk, Campaigns) at a lower price and are comfortable configuring | Setup depth; easy to over-customize |
| GoHighLevel | Local service businesses and agencies wanting CRM, WhatsApp/SMS inbox, funnels and booking under one login | Less suited to complex B2B pipelines; agency-style pricing |
| ActiveCampaign | Email-first businesses where the CRM mainly supports sequences and deals | Lighter pipeline features than the others |
I do not resell licences and I recommend the one whose free or lowest tier covers your next twelve months. Each platform has its own page with a shipped example: HubSpot automation and setup and GoHighLevel setup.
What gets connected
- Website forms and chat: every submission creates or updates a contact with source and page.
- Meta lead ads and Google Ads: leads arrive in real time with campaign and ad set; closed deals are sent back as offline conversions. The intake side is lead generation automation.
- WhatsApp: conversations logged on the contact, templates triggered from pipeline stages; see WhatsApp Business automation.
- Email: two-way sync so a reply from Gmail or Outlook appears on the record, and marketing sequences run from CRM segments; flows are built under email automation.
- Calendar and booking: meetings and appointments create activities and move deals.
- Quotes and invoicing: deal stage triggers a quote or invoice from a template; see sales and quotation automation.
- Sheets and reporting: a scheduled export feeds the owner’s Looker Studio dashboard.
- eCommerce: WooCommerce orders and customers synced for stores.
What the service includes
- Data model: contact, company and deal fields, pipelines and stages agreed with the people who will use them.
- Migration of existing contacts from sheets, phones and inboxes, with de-duplication and a mapping document.
- User roles, permissions and ownership rules.
- Integrations built natively where the CRM supports them and in n8n, Make or Zapier where it does not.
- Automations inside the CRM: assignment, stage-based tasks, follow-up reminders, stale-deal alerts.
- Reports and dashboards for pipeline, source performance and activity per person.
- Testing with real records, duplicates and partial data.
- Training for each role, documentation and an optional monthly maintenance plan.
How a CRM project runs
- Process interviews (week one): how a lead becomes a customer today, step by step, for each service line.
- Design (week one to two): fields, pipelines, ownership rules and the integration list, approved on one page.
- Build and migrate (weeks two to four): the CRM configured in your account, historical data imported into a sandbox first.
- Integrate (weeks three to five): forms, ads, WhatsApp, email and invoicing connected and tested.
- Train and go live (week five to six): role-based training, a two-week period where I review data quality daily.
What to decide before a CRM integration
- The system of record. The CRM owns the customer; the accounting tool owns the money; the sheet is a view. Deciding this first prevents two-way syncs that overwrite each other.
- Field discipline. The fewest fields that still answer the reports you want. Every extra required field lowers the chance the team fills anything in.
- Pipeline stages by evidence, not by feeling. “Proposal sent” is a stage; “warm” is not.
- Ownership and reassignment rules, written down, so the automation can enforce them.
- What happens to the old sheet. It becomes read-only on the go-live date. Running both in parallel is how migrations fail.
What breaks, and how I prevent it
- Duplicate contacts from different phone formats; normalization on every entry point and merge rules in the CRM.
- Sync loops between CRM and email tool; one direction per field, documented.
- Integrations dying when a staff member whose login was used leaves; integrations run under a dedicated service account owned by the business.
- Reports nobody trusts because stages are skipped; required fields on stage change and a weekly data-quality check.
- Vendor lock-in; a scheduled full export to your own storage so you can leave any platform.
Pricing pointer
Setup is quoted on request; a CRM setup with migration and two or three integrations sits in the middle of the range, and a full build with WhatsApp, ads, email, invoicing and reporting sits at the top. Maintenance is quoted on request, and the CRM subscription is paid by you. Broader multi-tool builds are scoped under workflow automation.
Next step
Tell me where customer data lives today and how many people touch it, and I will recommend a platform and send a fixed quote. The full set of automation services is on the automation hub.
