Frappe CRM implementation
We set up a pipeline that follows how you actually sell, including leads that go cold and come back. Every enquiry comes in with its source attached, so you can see which campaigns are working.
Systems
What you get.
- Pipeline, stages and SLAs worked out from your real calls and spreadsheets
- Web and event forms that record UTM, gclid and fbclid on the server
- WhatsApp Business API on the record timeline
- Management dashboards in Frappe Insights, built on SQL your team can read
Proof
Who it's for
Teams whose enquiries come in by phone, walk-in, form, event and ad, then sit in spreadsheets before anyone follows up. Admissions offices and sales teams are the usual fit.
More on who this suits
Teams whose enquiries come in by phone, walk-in, web form, events and ads, and get typed into spreadsheets before anyone follows up. That includes admissions offices, sales teams in trading and services businesses, and anyone paying per user for a CRM their team doesn't keep up to date.
What's included
Pipeline and stage designStages and SLAs taken from your real calls, with leads allowed to move back.
We work out stages, statuses and service level agreements from your real calls and spreadsheets instead of starting from a template. Leads can move back a stage, because a lead that goes cold often needs nurturing again.
Capture with attributionUTM, gclid and fbclid stored on every lead, plus Facebook lead forms.
Web and event forms record UTM, gclid and fbclid on the server, so every lead's source is stored on the record and nobody has to guess. Frappe CRM can also pull in leads from Facebook lead forms directly.
Calls and messages on the recordExotel or Twilio calls and WhatsApp messages on the lead's timeline.
Frappe CRM works with Exotel and Twilio for calling, and call logs show up on the lead. WhatsApp Business API messages appear on the same timeline.
Dashboards and the ERP linkInsights dashboards, and an ERPNext customer created at the status you pick.
Management dashboards in Frappe Insights, built on SQL your team can read. If you use ERPNext, Frappe CRM can create the customer there automatically once a deal reaches the status you choose.
Common mistakes we help you avoid
A deals-and-organisations setup you don't need
Forcing a B2B deals-and-organisations setup onto a process that doesn't have either.
One field for call outcome and stage
Using one field for both the call outcome and the pipeline stage, when they record different things.
Forms that lose the campaign
Forms that lose the campaign details, so nobody can tell whether the ad spend worked.
Routing rules hidden in code
Assignment rules hidden in code that nobody can see or change. We put routing rules where your team can edit them.
QR codes that break on a rename
Printed QR codes that stop working when someone renames a form. We fix each form's link when it's created so it never changes.
How we work
Every build runs through the same six steps, from a free call to go-live.
01
A call
30 minutes, no charge
02
Discovery
1 to 2 weeks, paid
03
Blueprint
Included in discovery
04
Build
3 to 8 weeks
05
Acceptance
1 to 2 weeks
06
Go-live and run
Ongoing
How it's priced and run
Every build follows our process. We start with a free call, then paid discovery and blueprint, then the build. Your team tests it on a separate site that gets wiped afterwards, and we go live with a runbook.
We run it as an Implementation. The scope is fixed against a signed blueprint and we bill across four milestones instead of by the hour, so you'll know the price before work starts.
After go-live, a Managed run covers support, small changes, framework upgrades (tested on a UAT site first) and regular checks that your backups actually restore.
Questions buyers actually ask.
A focused CRM build runs four to eight weeks. One recent admissions CRM went from signature to go-live across nine campuses in four weeks.
No. Frappe CRM is open source. You pay for hosting and for our work, so your twentieth user costs nothing extra.
Frappe CRM syncs Facebook lead forms on its own. For web and Google traffic, we record UTM, gclid and fbclid on the enquiry on the server, so the campaign is saved with the lead.
Yes. It can run on the same site as ERPNext or a separate one, and it can create the ERPNext customer when a deal reaches a status you choose.
Often that's the right call. In our admissions CRM case study, the CRM ran alongside the client's existing ERP instead of replacing it.
Let's start with a call.
Thirty minutes, free of charge, and you won't sit through a sales deck.