Your CRM should match the way your business actually sells.
Gully Sales configures your chosen CRM around your real sales process: your stages, your fields, your permissions, your automations and the systems it has to talk to. Then we take it live with your team working inside it.
A pipeline built from your stages, not from a vendor's default template.
Every enquiry captured, owned and followed up inside one system.
Reports leadership can read without exporting anything to a spreadsheet.
Gully Sales Private Limited serves businesses across India, with sales, marketing and revenue operations specialists under one roof.
In one paragraph
What is CRM Implementation and Customisation Services?
CRM implementation and customisation is the work of turning a CRM licence into a working sales system. Gully Sales documents how your business actually sells, then configures the data model, pipeline stages, fields, permissions, automations, integrations and reports to match it, tests the build on your own records, and takes it live with an owner named for every enquiry.
The problem
A CRM nobody trusts is more expensive than no CRM at all.
Most Indian SMBs buy a CRM with good intentions. Someone signs up, a few users are created, the default stages are accepted, and within a few months the real work has drifted back to WhatsApp, Excel and memory. The system is not wrong so much as unfinished: it was switched on, never built. Your team is simply working the way the software was left, and the software was left the way the vendor shipped it.
You will recognise it as
Your pipeline stages are the ones the software came with, and nobody can say what moves a deal from one to the next.
Salespeople keep their real pipeline in a personal spreadsheet and update the CRM before the review meeting.
Enquiries arrive on the website, on WhatsApp and by phone, and only some of them ever reach the system.
Half the fields on the opportunity screen are empty, and nobody is sure which of them matter.
Everyone can see and edit everything, so no one is confident the data is correct.
Management reports are still built by exporting the CRM into Excel and cleaning it up by hand.
What it costs the business
Forecasts are guesses, because stages mean different things to different salespeople and close dates are moved rather than reviewed.
Enquiries are lost between the channel that produced them and the person who was meant to call, with no record that it happened.
Managers coach on opinion instead of evidence, because the record of what was said and promised is incomplete.
The licence is paid for every month while the actual selling happens outside it, so the spend buys nothing.
When a salesperson leaves, their accounts, conversations and commitments leave with them.
Why it persists. Configuring a CRM properly is not a software job or a sales job; it sits between the two. It needs someone who can sit with a sales team, write down how they really sell, argue about what a stage means, and then build that agreement into fields, rules and permissions. Vendors sell licences and demonstrate features. IT teams set up users. Salespeople have targets to hit. So the middle work never gets an owner, and the default template quietly becomes the process.
If it stays unresolved. The business keeps growing on personal relationships and individual memory. Every new salesperson invents their own method, every review starts with an argument about the numbers, and the day comes when leadership wants to know what the pipeline is really worth and there is no honest answer. Replacing the CRM does not fix it, because the next one is switched on the same way.
What changes
You get a system your team uses because it fits how they work.
In the first weeks
A written map of how your business sells today, agreed by the people who actually sell.
A CRM configured to that map: your stages, your fields, your record types, your screens.
Every live enquiry and open deal in one place, each with a named owner and a next step.
Standard reports for owner, manager and salesperson, running on the day you go live.
In how the work runs
Enquiries from your website, phone, email and WhatsApp landing in the system with a source recorded.
Follow-ups created by the system on the day they are due, instead of remembered by the salesperson.
Stage movement that means something, because each stage has entry criteria and required fields.
Permissions that let managers see the whole picture and salespeople see their own work clearly.
In sales and marketing
Fewer enquiries going quiet, because every one has an owner and a due follow-up from the moment it arrives.
Review meetings that examine deals rather than argue about whose numbers are right.
Faster onboarding for new salespeople, who inherit a documented process instead of a folklore.
A licence you are paying for that is finally doing the work it was bought to do.
In what management can see
A pipeline view leadership can open at any time and understand without an explanation.
Reporting on source, stage, ageing and win rate produced by the system, not by an analyst.
A record of every conversation, quote and commitment that stays with the business.
Over the longer term
A configuration that can absorb new products, regions and teams without a rebuild.
Documented settings and a change log, so the system is maintainable by whoever owns it next.
A clean base for automation, scoring and analytics later, because the data model is sound.
Gully Sales controls the quality of the process capture, the configuration, the testing and the documentation you receive. Pipeline value, win rate and revenue depend on your market, your offer and your team's discipline, so we report them against a baseline as outcomes, never as promises.
Who it is for
This is for businesses ready to build the CRM properly, once.
The businesses it suits
Businesses that have bought a CRM licence and never configured it beyond creating user accounts.
Growing sales teams where each person tracks their pipeline differently and reviews start with reconciliation.
Companies whose enquiries arrive across website, phone, WhatsApp and referrals with no single record.
Businesses adding salespeople, regions or products where the current setup will not hold the extra complexity.
Firms that have chosen a CRM after a selection exercise and now need it built to their process.
Manufacturers, distributors and service firms with quotations, approvals and repeat orders the default template ignores.
Leadership teams who want forecasts and reports from the system rather than from an assistant's spreadsheet.
What usually prompts the call
The CRM has been live for months and adoption is still low.
You have just signed a new CRM contract and want it configured before anyone logs in.
A salesperson resigned and took the account history with them.
Two teams report different pipeline numbers from the same system.
You are integrating the website, telephony or WhatsApp and the CRM cannot receive what they send.
An investor, bank or board has asked for pipeline reporting you cannot produce.
What Gully Sales does
The work, component by component.
Requirements and sales process capture
We interview the people who sell, the people who quote and the people who report, and write down how work really moves from enquiry to order. Exceptions, approvals, repeat business and channel deals are captured too, because these are what break a default template.
Why it matters:
A CRM is a model of your selling. If nobody writes the model down, the software's assumptions become the process by default.
You receive:
A sales process map and a requirements document listing every record, field, rule and report, each with its reason.
Business value:
The build is argued about on paper, where changes are cheap, instead of after go-live where they are expensive.
Platform fit confirmation
Before configuration starts we confirm that the platform and edition you hold can actually do what the requirements ask. Gaps are listed with options: configure, integrate, add a module, or change the process. Where a genuine mismatch exists, we say so rather than build around it.
Why it matters:
Most painful CRM projects are discovered halfway through, when a requirement turns out to need an edition the business does not have.
You receive:
A fit report mapping each requirement to a platform capability, with gaps, options and a recommendation.
Business value:
You start the build knowing what the licence you own can and cannot do, and what each gap will cost to close.
Data model and record architecture
We design how information is stored: accounts, contacts, leads, opportunities, quotations, products and any record your business needs, with the fields, picklists, relationships and validation rules that keep them consistent. Naming standards and mandatory fields are agreed here.
Why it matters:
Every report, automation and forecast you will ever want depends on the data model. It is the hardest thing to change later.
You receive:
A documented data model: objects, fields, picklist values, relationships, mandatory rules and naming standards.
Business value:
Reports come out clean because the data went in clean, and later automation has something dependable to work on.
Pipeline and stage design
Your stages are defined as decisions, not as feelings: what must be true to enter a stage, what evidence is required, who owns it and what the next step is. Ageing thresholds and stalled-deal rules are set so the pipeline shows reality rather than optimism.
Why it matters:
A stage that means something different to each salesperson makes the forecast meaningless no matter how good the software is.
You receive:
Pipeline configuration with named stages, entry and exit criteria, required fields and ageing rules.
Business value:
Two managers looking at the same deal reach the same conclusion about where it stands.
Who may see and change what
We build the role hierarchy and sharing rules: who owns a record, who can see it, who can edit it and what leadership sees across the whole business. Territory, branch and product-line boundaries are reflected where they matter, along with approval rights on discounts or quotations.
Why it matters:
When everyone can change everything, nobody trusts the data; when nobody can see anything, managers go back to spreadsheets.
You receive:
A role and permission matrix, configured in the platform and documented for future changes.
Business value:
Salespeople work confidently in their own space and leadership gets the full picture without asking anyone.
Workflow and automation build
The routine work is handed to the system: follow-up tasks created when an enquiry arrives, reminders when a deal goes quiet, alerts when a large opportunity changes stage, approval routing for discounts, and templates for common emails and quotations.
Why it matters:
Discipline that depends on memory fails during a busy week, which is exactly when following up matters most.
You receive:
A configured set of automations with a written rule sheet stating each trigger, action and owner.
Business value:
Follow-ups happen on time without a manager chasing, and exceptions reach the right person quickly.
Integrations and data flow
The CRM is connected to the systems that feed it and depend on it: website enquiry forms, email and calendar, telephony or WhatsApp business messaging, and where the platform allows, your accounting or ERP system for customer and order information.
Why it matters:
Anything that has to be copied by hand between two systems eventually stops being copied, and that gap becomes the data problem.
You receive:
Configured integrations with a field mapping document, sync direction and error handling for each connection.
Business value:
Enquiries reach the system with their source intact, and your team stops re-typing the same information twice.
Testing, launch and handover
We test the build on your own records with your own people, correct what the testing exposes, load the opening data, create users and go live with support beside the team for the first weeks. Configuration and rules are documented for whoever administers the system next.
Why it matters:
A build that has never been tested by a real salesperson on a real deal will be abandoned in its first busy week.
You receive:
A test log, a go-live checklist, configuration documentation, a change log and an administrator handbook.
Business value:
The system starts working on day one and stays maintainable when the people who built it have moved on.
What you will have at the end.
A sales process map: stages, entry and exit criteria, owners and the decision each stage represents.
A requirements document listing every field, record, rule and report the business needs, with the reason for each.
A platform fit report mapping requirements to what your licence and edition can actually do.
A configured environment: objects, fields, picklists, record types, page layouts and validation rules.
Pipeline configuration with named stages, required fields, ageing thresholds and stalled-deal rules.
A role and permission matrix showing who owns, sees, edits and reports on which records.
Integration set-up for website forms, email, calendar and telephony or WhatsApp, where the platform allows.
Standard reports and dashboards for owner, manager and salesperson, each answering a stated question.
A test log recording what was tested, by whom, what failed and what was corrected before launch.
A go-live checklist covering opening data, user accounts, notifications and the first weeks of support.
Configuration documentation, a change log and a short administrator handbook for the person who owns it next.
How it runs
The engagement, step by step.
1
Discovery and process capture
We sit with the people who sell, quote, approve and report, and record how an enquiry becomes an order today, including the exceptions everyone works around. Existing records, spreadsheets and message threads are reviewed as evidence rather than taken on description.
You provide:
Time with sales, inside sales and management, plus access to current records and any existing CRM.
We produce:
A sales process map and a requirements document, each item marked essential, useful or later.
Done when:
The people who sell agree the map describes what they actually do, not what the manual says.
2
Platform fit and build plan
Each requirement is checked against what your platform and edition can do. Gaps are listed with options and costs. We then agree the build sequence, what goes live first, what waits for phase two, and who signs off each element.
You provide:
Administrator access, licence and edition details, and a decision on any gap that needs a purchase or a process change.
We produce:
A fit report and a build plan with scope, sequence, owners and sign-off points.
Done when:
Leadership approves a written scope, and both sides know what is deliberately not in it.
3
Data model and pipeline configuration
We build the record structure and the pipeline: objects, fields, picklists, relationships, validation rules, stages, entry criteria and ageing thresholds. Naming standards and mandatory fields are set so the data stays comparable across teams.
You provide:
Decisions on definitions that only the business can make, such as what qualifies a lead and when a deal is genuinely won.
We produce:
A configured data model and pipeline, with the settings documented as they are built.
Done when:
A sample deal can be walked from first enquiry to closed order through the configured stages.
4
Permissions, workflows and integrations
Roles, sharing rules and approvals are configured, then the automations that carry routine follow-up, alerts and routing. Integrations to website forms, email, calendar and messaging are connected and field mapping is agreed for each one.
You provide:
The reporting structure, approval authorities, and access to the website, email and telephony systems being connected.
We produce:
A permission matrix, an automation rule sheet and configured integrations with field mapping documents.
Done when:
A test enquiry submitted on your website arrives in the CRM, assigned, with a follow-up task created.
5
Reports, dashboards and testing
Reports are built to answer the questions leadership actually asks, then the whole build is tested by your own people on your own records. Every defect is logged, corrected and retested. Testing usually changes the build, and that is the point of doing it.
You provide:
Named testers from sales and management, and a fortnight of their attention during the test cycle.
We produce:
Reports and dashboards by role, a test log with defects and corrections, and an updated configuration.
Done when:
Your testers confirm they can do a full day's work in the system without leaving it.
6
Go-live and early support
Opening data is loaded, user accounts and notifications are switched on, and the system goes live on an agreed date. Gully Sales stays close during the first weeks, correcting friction quickly, because early problems decide whether people keep using it.
You provide:
A leadership instruction that the system is now where the work is recorded, and time for the first working sessions.
We produce:
A completed go-live checklist, a live configured system and a log of early fixes made.
Done when:
The whole sales team is working in the system and the previous spreadsheets are retired.
7
Stabilisation and measurement
For an agreed period after launch we watch how the system is really used: which fields stay empty, which automations fire, which stages stall. Configuration is tuned against evidence rather than opinion, and the baseline metrics are read for the first time.
You provide:
Access to usage data and a monthly review with the manager who owns the system.
We produce:
A usage and data-quality review, tuning changes with reasons, and the first report against baseline.
Done when:
Data completeness and follow-up discipline are measured and moving, with named actions on what is not.
8
Documentation and handover
Everything built is written down: settings and why they exist, automation rules, integration mappings and the change log. The person who will administer the system is walked through it, and open items are handed over as a list rather than as a conversation.
You provide:
A named internal owner for the system, with time to be taken through the configuration.
We produce:
Configuration documentation, an administrator handbook, a change log and an open-items list.
Done when:
Your own administrator can make a routine change without calling us.
Ways to work with us
Build it once, or build it in stages.
Full implementation
Discovery through handover on a single platform: process capture, data model, pipeline, permissions, automations, integrations, reports, testing, go-live and documentation. For businesses starting a new CRM or rebuilding one that was never configured.
Customisation of an existing CRM
Your CRM is already live but does not fit how you sell. We review the current configuration, correct the data model and pipeline, add the missing rules and reports, and document what exists. For businesses with a system in use but low trust in it.
Phased build
A first phase that gets enquiry capture, ownership, pipeline and basic reporting working, then later phases for automation, integrations and advanced reporting. For businesses that want value early and cannot free the team for a long project.
Build with revenue operations support
The implementation combined with data migration, adoption training and ongoing administration from Gully Sales, so one team is accountable from the first workshop through to the system running steadily.
Why Gully Sales
What you are actually choosing when you choose us.
We configure for how you sell, not for how the software demos.
The build starts with a process map made from interviews with your own salespeople. The software is then bent towards that map wherever it can be, and where it cannot, we tell you plainly and give you the options.
Sales people, not only software people.
Gully Sales builds CRMs as a sales consultancy that also implements. The person arguing with you about what a stage means has run pipelines and reviews, so the configuration reflects how deals actually behave.
The build is tested before anyone is asked to trust it.
Your own testers run real deals through the system before launch, and every defect is logged and corrected. A first week of friction is what turns a new CRM into an abandoned one.
Everything is documented so you are not locked in.
Settings, automation rules, integration mappings and a change log are handed over with an administrator handbook. Your next administrator, ours or yours, can see why each decision was made.
The whole revenue system is in scope, not just the licence.
Marketing, sales, channel and customer success specialists sit in the same firm, so a CRM built here connects to how enquiries are generated and how customers are served afterwards.
We separate what we control from what may follow.
Configuration quality, testing and documentation are ours to control. Adoption, pipeline value and win rate also depend on your team and your market, so we measure them against a baseline and report them honestly.
Where it applies
The same service, in different businesses.
Industry
The situation
How it applies
Likely benefit
Manufacturing
An engineering manufacturer sells through enquiries, drawings, samples and negotiated quotations, but the CRM's default stages jump straight from lead to proposal.
A data model with quotation and sample records, a pipeline that reflects technical evaluation, and approval routing for discounts above a set limit.
The pipeline shows where each enquiry really stands technically and commercially, so follow-up goes to the deals that are moving.
Distribution
A distributor with several branches finds that each branch keeps its own customer list and managers cannot see anything outside their own location.
Role hierarchy and sharing rules by branch and territory, account ownership rules, and dashboards that roll branches up to a national view.
Branch managers keep their own space while leadership finally sees one customer and pipeline picture across the country.
Healthcare
A multi-centre clinic receives patient enquiries by phone, website and messaging, and no one can say how many were followed up the same day.
Enquiry capture from every channel with source recorded, ownership rules by centre, and automatic follow-up tasks with escalation when they age.
Every enquiry has an owner and a due follow-up, and the response record can be reviewed rather than assumed.
IT and B2B services
A services firm runs long consultative sales, but opportunities sit in the same stage for months with close dates pushed forward each week.
Stage entry criteria tied to evidence, ageing thresholds, stalled-deal alerts and a forecast view that separates committed from possible.
Review meetings examine the deals that have stopped moving instead of accepting a close date that keeps changing.
Real estate and interiors
A design studio's enquiries come from portals, social channels and referrals, and site visits, quotations and revisions are tracked in personal notebooks.
Lead capture from each source, a pipeline covering site visit, design proposal and revision cycles, and templates for quotations and follow-up mails.
The full history of a client, from first enquiry to final revision, sits in one record any team member can pick up.
Education
An education group's counsellors chase admission enquiries across seasons, and reporting to management is rebuilt in Excel every week.
Admission lifecycle stages, counsellor ownership and reassignment rules, seasonal reporting dashboards and automated reminders through the decision period.
Management opens a live dashboard instead of waiting for a weekly file, and enquiries are worked to a defined cadence.
Manufacturing
The situation:
An engineering manufacturer sells through enquiries, drawings, samples and negotiated quotations, but the CRM's default stages jump straight from lead to proposal.
How it applies:
A data model with quotation and sample records, a pipeline that reflects technical evaluation, and approval routing for discounts above a set limit.
Likely benefit:
The pipeline shows where each enquiry really stands technically and commercially, so follow-up goes to the deals that are moving.
Distribution
The situation:
A distributor with several branches finds that each branch keeps its own customer list and managers cannot see anything outside their own location.
How it applies:
Role hierarchy and sharing rules by branch and territory, account ownership rules, and dashboards that roll branches up to a national view.
Likely benefit:
Branch managers keep their own space while leadership finally sees one customer and pipeline picture across the country.
Healthcare
The situation:
A multi-centre clinic receives patient enquiries by phone, website and messaging, and no one can say how many were followed up the same day.
How it applies:
Enquiry capture from every channel with source recorded, ownership rules by centre, and automatic follow-up tasks with escalation when they age.
Likely benefit:
Every enquiry has an owner and a due follow-up, and the response record can be reviewed rather than assumed.
IT and B2B services
The situation:
A services firm runs long consultative sales, but opportunities sit in the same stage for months with close dates pushed forward each week.
How it applies:
Stage entry criteria tied to evidence, ageing thresholds, stalled-deal alerts and a forecast view that separates committed from possible.
Likely benefit:
Review meetings examine the deals that have stopped moving instead of accepting a close date that keeps changing.
Real estate and interiors
The situation:
A design studio's enquiries come from portals, social channels and referrals, and site visits, quotations and revisions are tracked in personal notebooks.
How it applies:
Lead capture from each source, a pipeline covering site visit, design proposal and revision cycles, and templates for quotations and follow-up mails.
Likely benefit:
The full history of a client, from first enquiry to final revision, sits in one record any team member can pick up.
Education
The situation:
An education group's counsellors chase admission enquiries across seasons, and reporting to management is rebuilt in Excel every week.
How it applies:
Admission lifecycle stages, counsellor ownership and reassignment rules, seasonal reporting dashboards and automated reminders through the decision period.
Likely benefit:
Management opens a live dashboard instead of waiting for a weekly file, and enquiries are worked to a defined cadence.
Proof
Work we can point to.
Premier Marketing
The problem:
Lead handling was not streamlined, which limited how quickly enquiries could be worked across domestic and industrial sectors.
What we did:
Gully Sales worked with Premier Marketing to enhance reach, streamline lead handling and accelerate sales across both sectors, as recorded in the published case study.
The result:
Streamlined lead handling and faster sales across domestic and industrial sectors. The published case study states no figures, and none are claimed here.
It starts with interviews, not with software. We sit with your salespeople, inside sales and managers and write down how an enquiry becomes an order, including the exceptions everyone works around. That map is agreed by the people who sell before anything is configured. The stages, fields and rules in the system are then built from the map, and where the platform cannot support something, we say so and give you options rather than quietly changing your process.
How long does an implementation take?
It depends on how many users and record types are involved, how many integrations are needed, and how quickly your team can give time to discovery and testing. The build itself is rarely the slow part. Decisions about what a stage means, who owns an account and what a qualified lead is take longer, because only your business can make them. The proposal sets out the sequence and what has to be decided at each point, so delays are visible rather than mysterious.
What do you need from our team during the build?
Administrator access to the platform, licence and edition details, and access to the systems being connected. Time with the people who sell, quote and report during discovery. Named testers from sales and management for the test cycle. Decisions on definitions only you can make, such as what qualifies a lead. And a clear instruction from leadership that once the system is live, this is where work is recorded.
How do you measure whether it worked?
Against a baseline recorded before configuration starts: data completeness, lead-response speed, lifecycle conversion, automation adoption, forecast reliability, reporting time and revenue productivity. Data completeness and response speed usually move within weeks. Conversion and forecast reliability need a full sales cycle before they mean anything. We are clear about which of these we control, which is the build and the documentation, and which also depend on your team's discipline and your market.
What is not included in a CRM implementation?
Licence fees and any paid add-ons are yours to buy directly from the vendor. Deep custom code beyond the platform's configuration and standard integration tools is quoted separately if you need it. Bulk cleaning and migration of historic records, adoption training programmes and ongoing administration are related services with their own scope. Anything not written in the proposal is not included, and we would rather say that at the start than discover it during a busy go-live week.
We already have a CRM that nobody uses. Do we start again?
Usually not. In most cases the platform is fine and the configuration is the problem. We review what exists, keep what works, correct the data model and pipeline, add the missing rules and reports, and document the result. Starting again is recommended only when the platform genuinely cannot do what your process needs, and that conclusion comes from the fit report with reasons, not from a preference for a particular product.
Which CRM platforms do you work with?
We work with the mainstream platforms that Indian SMBs actually buy, and the approach is the same across all of them: capture the process, model the data, design the pipeline, set permissions, automate the routine, connect the systems and document everything. If you have not chosen yet, start with CRM consulting and selection so the decision is made against your requirements. If you have already bought, we build on what you hold.
Will you move our existing data into the new system?
A basic opening load of current customers and open deals is part of go-live, because a system with nothing in it will not be used. Cleaning, de-duplicating and migrating years of historic records is a larger piece of work with its own scope and testing, handled as CRM data migration. We tell you at the fit stage which of the two your situation needs, so the effort is planned rather than discovered.
4 more questions
How much customisation is too much?
Customisation earns its place when it reflects something genuinely true about how you sell. It becomes a liability when it copies a habit nobody can justify, because every extra field is a field someone must fill and every extra rule is one more thing to maintain. During discovery we mark each requirement essential, useful or later. A simpler build that people use beats an elaborate one they avoid.
What happens after go-live?
We stay close for an agreed stabilisation period, because the first weeks decide whether the system is adopted or abandoned. We watch which fields stay empty, which automations fire and which stages stall, then tune the configuration against that evidence. After that you can run it yourself with the documentation and handbook we provide, or continue with Gully Sales for administration and support under a separate scope.
Can you connect the CRM to our website, WhatsApp and accounting software?
Where the platform and the other system allow it, yes. Website enquiry forms, email, calendar and telephony or WhatsApp business messaging are the common connections, and accounting or ERP links for customer and order information are often possible. Each integration gets a field mapping document, a sync direction and error handling. Where a connection is not supported, we say so during the fit stage rather than after you have committed.
Can we start small and add more later?
Yes, and for many businesses that is the sensible route. A first phase gets enquiry capture, ownership, pipeline and basic reporting working so the team feels the benefit quickly. Automation, integrations and advanced reporting follow once people are working inside the system daily. The data model is designed at the start for where you are going, so later phases add to the build instead of forcing a rework.
Talk to us
Show us the CRM you have, and how you actually sell.
The assessment is a working conversation about how you sell, what your CRM does today and where the two have parted company. No obligation and no product pitch.
No obligation and no sales script
A reply from someone who does the work
Your details are never sold or shared
Get a free audit of how you sell, and a scored report of where the work is.
