Your CRM gets a named administrator instead of nobody in particular.
Gully Sales runs your CRM after go-live: user access and licences, a request queue with agreed response commitments, changes tested before release, integrations under watch, and a monthly report of what changed and what quietly broke.
- A named administrator and a request queue, instead of asking whoever has time.
- Access, licences and permissions kept current as people join, move and leave.
- Changes tested before they reach your team, and vendor updates checked before they land.
Gully Sales Private Limited administers CRM systems for businesses across India, and runs the sales and marketing work that depends on them.
In one paragraph
What is CRM Administration and Support?
CRM administration and support is the ongoing work of keeping a live CRM correct, current and usable after go-live. Gully Sales acts as your named administrator: users, licences and permissions, a request queue with agreed response commitments, tested configuration changes, monitored integrations, vendor release checks and a monthly health review. Your team gets a system it can trust without depending on one person's memory.
The problem
The CRM is live, and nobody is actually running it.
Nobody decided to stop looking after it. The person who set it up moved on, the vendor's project closed, and the CRM carried on running. Now requests go to whoever seems to know: a field is added in a hurry, someone leaves and keeps a licence, a report breaks and a manager rebuilds it in a spreadsheet instead. Each of these is small. Together they are the reason the CRM your team uses today is not the CRM you approved.
You will recognise it as
- Change requests go to a salesperson or an office executive who fits them in between their real work.
- People who left months ago still have logins, and you are still paying for their licences.
- A field, stage or form was added by someone in a hurry, and nobody can say why it is there.
- An integration stopped syncing and you found out from a customer, not from the system.
- The vendor pushed an update and something in your workflow behaved differently the next morning.
- Nobody has written down how your CRM is configured, so the knowledge sits in one person's head.
What it costs the business
- Small requests wait for weeks, so the team drifts back to spreadsheets and chat groups, and the CRM stops holding the truth about your pipeline.
- Access is wider than it should be: everyone can see and edit everything, including customer contacts and pricing.
- Licences are paid for people who no longer work with you, and for editions with features nobody switched on.
- The system drifts away from the process it was built for, so reports quietly stop describing the business.
- When the one person who understands the setup takes leave or resigns, the CRM becomes untouchable.
Why it persists. CRM administration is nobody's job description in most SMBs. Implementation had a budget and an end date; running the system afterwards had neither. The work is also invisible when it is done well, so it loses every contest for attention against a customer meeting or a month-end. And because each individual request is genuinely small, no single one ever justifies hiring a person or calling the vendor, which is exactly how a year of small requests turns into a system nobody trusts.
If it stays unresolved. The CRM keeps running and steadily stops mattering. Reporting moves back to spreadsheets, the pipeline review depends on what people remember, and the money you spent choosing and implementing the system is written off quietly, usually at the point where someone suggests replacing it with a different one.
What changes
The system stays as good as the day it was signed off.
In the first weeks
- A named administrator and one channel for requests, so nothing depends on catching the right person.
- A current record of every user, role, licence and permission, with the leavers removed.
- The backlog of pending small changes cleared and closed, each one confirmed by the person who asked.
In how the work runs
- Changes built in a test environment first and released with a note, so your team is never surprised on a Monday.
- Integrations and scheduled jobs watched, so a failed sync is found by us rather than by a customer.
- Existing reports and dashboards kept working as fields, stages and people change.
In sales and marketing
- Sales time returns to selling, because the system does the admin work it was bought to do.
- Licences matched to people who actually use them, so you pay for the seats you need.
In what management can see
- A monthly administration report: what changed, what broke, what is pending and what needs your decision.
Over the longer term
- A documented configuration your business owns, so a new administrator can take over without archaeology.
Gully Sales controls the administration: access, changes, releases, monitoring, documentation and the response commitments we agree with you. Whether the CRM improves your revenue depends on the process your team runs inside it and on how consistently they use it.
Who it is for
Who this is for, and when it starts to matter.
The businesses it suits
- Indian SMBs running a live CRM with no one whose actual job is to administer it.
- Businesses where the CRM was implemented by an agency or vendor whose engagement has now ended.
- Companies with ten to two hundred CRM users, where requests, joiners and leavers arrive every week.
- Owners who want the CRM to stop depending on one employee's memory and goodwill.
- Firms whose sales, marketing and service teams share the CRM and keep asking different things of it.
- Businesses with an internal administrator who needs cover, a second pair of hands, or someone to escalate to.
What usually prompts the call
- The person who looked after the CRM has resigned, changed roles or gone on long leave.
- Your implementation partner's support period is ending and nothing has replaced it.
- A licence renewal is due and nobody can say who is actually using the system.
- Something broke after a vendor update and the team lost a day working around it.
- Requests to change the CRM have been pending long enough that people stopped raising them.
What Gully Sales does
The work, component by component.
Administration ownership and service desk
We take formal ownership of the day-to-day administration of your CRM. One channel receives every request from your team. Each request is logged, prioritised against the definitions we agree with you, and closed with the person who raised it. You know who is responsible on any given day, and so does your team.
- Why it matters:
- When administration is a favour rather than a role, urgent requests jump the queue and ordinary ones never move at all.
- You receive:
- A named administrator, an agreed request channel, and a live request log with status and owner.
- Business value:
- Your team stops chasing individuals and starts raising requests that visibly get done.
Users, roles, licences and access
We keep the people side of the system correct: joiners set up with the right role, movers changed, leavers deactivated the day they go, and permissions kept to what each role needs to do its work. Before every renewal we reconcile the licences you hold against the accounts actually being used, and tell you what can be released.
- Why it matters:
- Access left open after someone leaves is both a security exposure and a bill you keep paying without noticing.
- You receive:
- Access matrix by role, a joiner-mover-leaver checklist, and a licence reconciliation before renewal.
- Business value:
- The right people see the right records, and you pay for seats that are being used.
Configuration change control
Fields, layouts, stages, picklists, templates and validation rules change as the business changes. We take the request, check what it affects, build it in a sandbox or test environment where your platform provides one, have the requester confirm it, then release it with a short note to the users affected.
- Why it matters:
- An unrecorded change made straight into the live system is how reports break with nobody able to say which change did it.
- You receive:
- Change log carrying the request, the approver, the test evidence and the release date.
- Business value:
- The system evolves with the business, and every change can be traced and reversed.
Vendor release and update management
CRM vendors ship updates on their own schedule, and some of them touch things you rely on. We track the release notes for your edition, test the parts that affect your workflows, automations and integrations before or as they land, and tell your team in plain language what will look different.
- Why it matters:
- Updates arrive whether or not anyone is watching, and the first person to notice a change should not be a salesperson mid-call.
- You receive:
- Release watch notes and a pre-release check on the workflows your business depends on.
- Business value:
- Updates stop being events, and your team is told before they see the change.
Integration and automation monitoring
Website forms, ad platforms, telephony, email, messaging, accounting and any other system feeding the CRM go on a check schedule: is the sync running, are records arriving, are queued jobs completing, have error logs filled up. We fix what is ours to fix and raise the rest with the platform or the vendor on your behalf.
- Why it matters:
- A silent integration failure looks exactly like a quiet week in the market, until someone counts the missing enquiries.
- You receive:
- A monitored list of every connection, with owner, check frequency and failure history.
- Business value:
- Broken connections are found and reported by us, not discovered weeks later in a review.
Report and dashboard upkeep
The reports and dashboards your managers already depend on need maintenance. A renamed field, a new stage, a person who left an assignment or a changed target can quietly break a view. We keep the existing set working, retire what nobody opens any more, and make the small edits managers ask for.
- Why it matters:
- A dashboard that shows the wrong number for a month costs more trust than a dashboard that was never built.
- You receive:
- A maintained report inventory with owner, purpose and last-reviewed date.
- Business value:
- Managers keep reading the same numbers each month without rebuilding them in a spreadsheet.
Documentation, backup and continuity
We write down how your CRM is actually configured: objects and fields in use, stages, automations, integrations, roles, and the reasons behind the choices that matter. We confirm the backup and export arrangements your platform offers, and keep an administrator handover pack current so the system never depends on one person being reachable.
- Why it matters:
- Undocumented configuration is why businesses replace working systems: nobody can safely change what nobody can explain.
- You receive:
- Configuration document, administrator handover pack, and a confirmed backup and export routine.
- Business value:
- You own the knowledge about your own system, and can move it in-house or elsewhere whenever you choose.
What you will have at the end.
- CRM handover audit: current configuration, users, licences, integrations, automations and every open issue found.
- A named administrator, an agreed request channel and response commitments written into your service note.
- Live request log: every request with its raiser, priority, status, owner and closure date.
- Access matrix by role, plus a joiner-mover-leaver checklist your HR or office team can follow.
- Licence reconciliation before each renewal: seats held, seats used, seats you can release.
- Change log with test evidence and release notes, so every configuration change is traceable.
- Integration and automation monitor: every connection, its check schedule and its failure history.
- Maintained report and dashboard inventory with owner, purpose and last-reviewed date.
- Configuration document and administrator handover pack, kept current as the system changes.
- Monthly administration report: changes made, incidents, pending requests and decisions you need to take.
- An anonymised extract of a request log and a change log, shown to you before we start.
How it runs
The engagement, step by step.
- 1
Take over the system
We begin with a handover audit of the live CRM: users and licences, roles and permissions, fields and layouts in use, stages, automations, integrations, scheduled jobs, the reports still being opened, and everything currently broken or pending. Where an implementation partner is leaving, we do this with them while they are still available.
- You provide:
- Administrator access, the licence and renewal details, and an introduction to whoever has been looking after the system.
- We produce:
- A handover audit describing the current state of the system, with the open issues listed and ranked.
- Done when:
- You can see, on one document, what you actually have and what is wrong with it.
- 2
Agree how support will work
We set the service model with you: which channel requests come through, how priorities are defined, what counts as urgent, who in your business approves a change, and what we will do without asking. Response commitments are agreed with you and written down rather than assumed.
- You provide:
- Named approvers for changes, your working pattern, and the areas that must not be touched without notice.
- We produce:
- A service note stating scope, request channel, priority definitions, approvers and response commitments.
- Done when:
- Everyone knows how to ask for something, and what will happen when they do.
- 3
Clear the backlog
We work through the open and abandoned requests found in the audit. Some are done, some are merged, some are declined with a reason, and a few turn out to hide a process question that goes back to you. Access is corrected at the same time: leavers removed, roles fixed, unused licences identified before the next renewal.
- You provide:
- Decisions on the requests that need a business answer, and a current list of employees and their roles.
- We produce:
- A cleared backlog with each item closed, merged or declined in writing, and a corrected access list.
- Done when:
- The queue is empty enough that the only requests waiting are new ones.
- 4
Put change control in place
We establish how changes will be made from here: raised, checked for impact, built in a test environment where the platform provides one, confirmed by the requester, released with a note, and logged. The same route applies to a new field and to a new automation; only the depth of testing differs.
- You provide:
- Approval of the change route, and the names of the people who sign off changes on your side.
- We produce:
- A change control routine and a change log, with the first changes already run through it.
- Done when:
- No change reaches your live system without a record of who asked, who tested and who approved.
- 5
Set up monitoring
We list every integration, automation and scheduled job the business depends on, decide how often each is checked and what a failure looks like, and put those checks on a schedule. Where the platform can alert us, we switch that on; where it cannot, the check is done by hand on a rhythm.
- You provide:
- Access to the connected systems, and the vendor or partner contact for each of them.
- We produce:
- A monitoring list with check frequency, failure signal and escalation path for every connection.
- Done when:
- A failed sync has a defined way of being noticed and a named person to act on it.
- 6
Run the monthly cycle
Administration becomes routine: requests handled through the agreed channel, joiners and leavers processed, changes released, vendor updates tracked and tested, monitoring reviewed, reports maintained, documentation updated. Once a month you receive a report of what changed, what broke and what needs a decision from you.
- You provide:
- Notice of joiners and leavers, decisions on the items raised, and a short monthly review call.
- We produce:
- A monthly administration report and an updated configuration document.
- Done when:
- You spend the monthly review deciding things rather than discovering them.
- 7
Review, and keep the option to leave
Each quarter we look at the system rather than the queue: what the pattern of requests is telling you about the process, where usage has fallen away, which licences to release, what should be simplified, and what the business now needs that the system does not do. The handover pack is refreshed at the same time.
- You provide:
- A conversation with the sales, marketing and service leads about what has changed in the business.
- We produce:
- A quarterly system review with recommendations, and a current administrator handover pack.
- Done when:
- You could bring administration in-house or move it elsewhere without losing anything.
Ways to work with us
Take the whole job, or only the part you cannot cover.
CRM administration health check
A one-time audit of the live system: configuration, users, licences, permissions, integrations, automations and open issues, with a ranked list of what to fix. Useful before you decide whether to run administration in-house or with us.
Managed CRM administration
Ongoing ownership of the day-to-day: request desk, access and licences, change control, release management, monitoring, report upkeep, documentation and a monthly report. The usual arrangement where there is no internal administrator.
Support desk only
The request channel, break-fix support and user administration, without change control or the monthly reporting cycle. Suited to a smaller system where changes are rare and someone internal still owns the design.
Cover and escalation
Backup for an internal administrator: leave and notice-period cover, a second pair of hands during busy periods, and someone to escalate to when a change is larger than one person should make alone.
Administration handover
We run the system, document it, and train your chosen employee to take it over, then stay available on call while they settle in. For businesses that intend to own administration internally.
Why Gully Sales
What you are actually choosing when you choose us.
We administer the system, and we know the revenue process it serves.
Gully Sales works on sales, marketing and revenue operations for Indian SMBs. When a request arrives to add a field or change a stage, we ask what it does to your pipeline and your reporting before we build it.
One request channel, and a queue you can see.
Every request is logged with a raiser, a priority, an owner and a status. Nothing lives in a chat thread. Your team can check where a request stands without asking anyone, and you can see what is waiting.
Nothing reaches your live system untested.
Changes are built and checked away from your users wherever the platform allows, confirmed by the person who asked, and released with a note. If something behaves oddly afterwards, the log says exactly what to undo.
The knowledge stays with your business.
Your configuration document, access matrix, request log and handover pack live in your own files, not ours. If you take administration in-house or move to another partner, you keep everything we wrote down.
We work with the CRM you already run.
The system you chose and paid for is the starting point. Our job is to make it correct and dependable, not to move you onto something else. If it genuinely cannot do what you need, we will say so plainly.
Administration is a service, not a favour.
Scope, priorities and response commitments are agreed and written down. Ordinary requests get done on a rhythm instead of waiting behind whatever is shouting loudest that week.
Where it applies
The same service, in different businesses.
Manufacturing with a dealer network
- The situation:
- Area managers, dealers and the internal sales desk all use the CRM. Field requests are added straight into the live system by whoever holds admin rights, and the dealer pipeline report has stopped matching the dispatch numbers.
- How it applies:
- Access reduced to defined roles, one request channel for the field team, change control over the dealer and enquiry records, and the dealer reports repaired to read from the corrected fields.
- Likely benefit:
- The dealer pipeline and the dispatch numbers describe the same business again, and field requests have a route that works.
Multi-location clinic or hospital
- The situation:
- Patient enquiries arrive into the CRM from a website form, a call tracking number and social media. Front-desk staff change often, and access is granted by copying a colleague's login setup.
- How it applies:
- Role-based access with a joiner-mover-leaver checklist, every enquiry source placed under monitoring, and licences reconciled before the annual renewal.
- Likely benefit:
- New front-desk staff are productive on day one, and a broken enquiry source is caught in the same week it fails.
IT and software services
- The situation:
- A growing services firm has a well-implemented CRM and one operations executive who administers it alongside billing. Requests from four sales pods now take weeks, and she is due a long leave.
- How it applies:
- Cover and escalation: we take the request desk and release management, keep her as the design owner, and hold the system through her leave.
- Likely benefit:
- The pipeline keeps running while she is away, and she returns to a queue that was worked rather than paused.
Education and training institutes
- The situation:
- Admission counsellors work in seasonal peaks. Every intake brings new counsellors, temporary logins and a rush of changes to forms and stages, and none of it is recorded anywhere.
- How it applies:
- A seasonal joiner and leaver routine, temporary access with an expiry date, change control over the admission stages, and documentation refreshed after each intake.
- Likely benefit:
- Each intake starts on a system that matches the current process, with access that closes when the season ends.
Real estate and property
- The situation:
- Enquiries come from portals, ads and site visits. Two portal connections stopped delivering leads after a vendor update, and it was noticed only when the month's enquiry count looked low.
- How it applies:
- Every lead source placed on a monitoring schedule with a defined failure signal, release notes tracked for the edition in use, and critical workflows tested before updates land.
- Likely benefit:
- A dead lead source is reported within the check cycle instead of at month end, when the enquiries are already lost.
Professional services firms
- The situation:
- Partners, associates and a shared admin all see every record, because a single role was applied to everyone at implementation. Client confidentiality has become a real concern for the partners.
- How it applies:
- An access matrix built around roles and record ownership, permissions tightened in stages with the partners' sign-off, and the whole change documented.
- Likely benefit:
- People see the clients they work on, and the firm can show a client how access to their records is controlled.
Questions buyers ask
Before you enquire, the answers you will want.
What does CRM administration and support actually cover?
It is the ongoing work of running a live CRM: adding and removing users, managing roles, permissions and licences, making configuration changes safely, testing vendor updates before they affect your team, watching the integrations and automations that feed the system, keeping existing reports working, and documenting how everything is set up. It is the job that starts on the day implementation ends, and in most SMBs nobody has ever been given it.
We have someone in the team who looks after the CRM. Do we still need this?
Often what you need is cover rather than replacement. If one person holds all the knowledge, the business is exposed every time they take leave, get busy or resign. We can run the desk while they keep design ownership, act as escalation for larger changes, or document what only they know so it stops living in one head. Some businesses use us until an internal administrator is ready, then take the handover.
What information and internal involvement are required to start?
We need administrator access to your CRM, the licence and renewal details, access or contacts for the connected systems, and an introduction to whoever has been looking after it. From your side we need named approvers for changes, notice when people join or leave, and a short monthly review. Beyond that, the involvement is answering the business questions a technical request sometimes hides, such as why a particular stage exists.
How long does the administration arrangement run?
The handover audit and the backlog clearing are a defined piece of work, and their length depends on the size of your system, the number of users and how much is pending. Administration itself is ongoing by nature, because joiners, leavers, changes and vendor updates do not stop. We do not commit to a calendar before the audit shows us what we are taking over, and the arrangement is reviewed at points you agree.
How quickly do you respond when something breaks?
Response commitments are agreed with you and written into the service note, with different commitments for a system-down problem, a change that blocks work, and an ordinary request. We prefer to set those against your working pattern rather than quote a standard number, because a manufacturer with a month-end rush and a clinic taking evening enquiries do not need the same cover. Every request is logged and visible either way.
Which CRM systems do you administer?
We work with the CRM you already run, whether it is an Indian platform or an international one, and whether you are on a starter edition or something heavily configured. The handover audit tells us how much of the platform you actually use and where the setup is unusual. If your system was never properly implemented, we will say so, because rebuilding it is different work from running it.
How is the administration service itself measured?
Against the baseline we record before starting. The direct measures are administration ones: request resolution time, the age of the oldest open request, licence utilisation, and integration failures found and fixed. The business measures follow from those: data completeness on the fields your reports depend on, lead-response speed, lifecycle conversion, automation adoption, forecast reliability, and the hours managers spend building numbers outside the system.
What does the administration retainer not cover?
Administration keeps the system you have running well. It does not include rebuilding a badly implemented CRM, migrating data in from another system, building new integrations, designing a new reporting suite, cleansing and deduplicating your database, or negotiating your licence contract with the vendor. Each of those is separate work we can scope for you. Training beyond ordinary user support is also handled separately.
3 more questions
How are changes approved, and can they be reversed?
Every change is raised through the agreed channel, checked for what it affects, and confirmed by a named approver on your side before release. Where your platform provides a test environment, it is built and shown there first. Each change is logged with the requester, the approver, the test evidence and the release date, so if something behaves unexpectedly afterwards we know precisely what to undo and when it was done.
Is our customer data safe with an external administrator?
We work inside your CRM under your own account, with named individuals holding named administrator logins that you control and can withdraw at any time. We do not take copies of your database out of the system for our own use, and access to your connected platforms stays yours. Confidentiality terms and the list of people with access are agreed in writing before any work starts.
What happens if we want to bring administration back in-house?
That is a planned outcome, not a problem. The configuration document, access matrix, request and change logs and the administrator handover pack live in your files and are kept current, so a new internal administrator inherits a working record rather than a mystery. We normally run a handover period and stay available on call while your person settles into the role.
Talk to us
Ask us to look at how your CRM is being run today.
Request a Revenue Operations Assessment and we will review your live CRM as it stands: users, licences, permissions, integrations, pending requests and the state of the reports your managers rely on. You get a ranked list of what needs attention, whether or not you engage us to run it.
- No obligation and no sales script
- A reply from someone who does the work
- Your details are never sold or shared