Gully Sales writes the rules your pipeline has to meet — what each stage means, what evidence keeps a deal in the forecast, when a deal is flagged — and installs the rhythm that keeps those rules alive.
Gully Sales Private Limited works with small and medium businesses across India, and every rule we write is calculated from your live pipeline.
In one paragraph
Pipeline hygiene and governance is the standard your opportunity records must meet, plus the rules and rhythm that keep them meeting it. Gully Sales defines each stage and the evidence behind it, sets forecast categories and ageing limits, agrees who may change what, and installs an inspection cadence so your pipeline stays worth reading.
The problem
Sellers update the CRM around customer work, not instead of it, and every business starts with a stage list that made sense when there were two people and thirty deals. Then the team grew, the deal count grew, and nobody went back to say what each stage actually means or what has to be true before a deal enters it. So the pipeline fills up with deals that are real, deals that were real last quarter, and deals somebody is hoping about, and from the outside all three look identical.
Why it persists. It persists because hygiene is everybody's job and nobody's responsibility. A seller has no reason to close a stale deal when a fuller pipeline reads better in a review, and a manager forced to choose between chasing records and chasing revenue will choose revenue every time. There is also no agreed standard to enforce. Without a written definition of a stage, asking someone to clean the pipeline is a matter of opinion, and opinions are hard to insist on week after week.
If it stays unresolved. Left alone, the pipeline keeps growing while trust in it keeps shrinking. Leadership starts running a private forecast in a spreadsheet, sellers keep a second list of the deals they actually believe in, and the CRM becomes a place where data is entered rather than a place where decisions are made. Any tool, dashboard or automation bought after that point is built on the same sand.
What changes
In the first weeks
In how the work runs
In sales and marketing
In what management can see
Over the longer term
Gully Sales controls the definitions, rules, configuration, scorecard and cadence, and we run them with your team until they hold. Whether the forecast then proves accurate depends on how consistently your managers inspect deals and how honestly they are recorded.
Who it is for
What Gully Sales does
Stage definitions and exit criteria
We write what each pipeline stage means in your business, what must be true for a deal to enter it, and what evidence lets it leave. Definitions are drafted in the language your sellers already use and placed inside the CRM at the point where the stage is chosen, rather than in a document nobody opens.
Probability and forecast categories
We separate two things that are usually confused: the probability attached to a stage, which is an expectation drawn from your own conversion history, and the forecast category a manager judges a deal into — Commit, Upside, Pipeline or Omitted. Each category gets a written test that any manager can apply the same way.
Coverage and pipeline sizing
We work out how much qualified pipeline your team needs to hold to reach the target, using your own conversion rates and sales cycle length rather than a rule of thumb, and set that coverage figure by seller, by segment and by period.
Hygiene rules and system enforcement
We turn the standard into rules the system holds: required fields at each stage, a next step and date on every open deal, ageing limits per stage, close-date discipline, and automatic flags when a rule is broken. Where your CRM can enforce a rule we configure it; where it cannot, the rule becomes a named check inside the review agenda.
Risk flags and review criteria
We define what makes an open deal risky in your business — no contact within a set number of days, a close date pushed more than twice, a single contact with no second relationship, no next meeting booked, a discount above a threshold — and make each signal visible on the deal record itself and in a risk view.
Inspection rhythm and review agenda
We set who inspects what, how often, and against which list: a short daily check on new and stalled deals, a weekly deal inspection with a fixed agenda, a monthly forecast review, and a quarterly review of the rules themselves. Every one of them ends with named actions and dates rather than a discussion.
Governance, ownership and the scorecard
We name who owns the rules, who may change a stage definition or reopen a closed deal, how an exception is requested and granted, and how compliance is measured. A hygiene scorecard reports by team and by seller on record completeness, deal ageing and next-step discipline.
How it runs
Pipeline audit
We export your open pipeline and examine it deal by deal: how old each one is, when it last moved, whether a next step and date exist, how far close dates have shifted, and how the same stage is being used by different sellers. We also sit in one of your existing reviews to see how deals are discussed out loud.
Stage and category design
We run a working session with your sales leadership and two or three sellers to agree what each stage means here, what evidence moves a deal forward, and what separates a Commit deal from an Upside one. Definitions are drafted in your words and then tested against real deals pulled from the audit.
Rules, coverage and risk signals
We convert the agreed design into rules: required fields by stage, ageing limits, close-date discipline, the coverage each seller must carry, and the signals that flag a deal for attention. Every threshold is tested against the audited pipeline so it matches your reality rather than a benchmark from another company.
System configuration
We configure what your CRM can hold — fields, picklists, validation, ageing flags, saved views and scorecard reports — in a sandbox or with a small group first, then across the team. Anything the system cannot enforce is written into the review agenda instead, so nothing important depends on memory.
Clean-up to the new standard
We work through the existing pipeline with the owner of each deal and bring it to the standard: close what is dead with a reason, restage what is misplaced, merge duplicates, add missing next steps and correct close dates. The old figures are kept so you can compare before and after honestly.
Cadence launch and manager coaching
We run the first weeks of the new rhythm alongside your managers: the deal inspection, the forecast review and the scorecard conversation. Managers practise inspecting a deal against its evidence instead of accepting a verbal update, which is the habit that decides whether any of this survives us.
Handover and rule review
We hand the standard to a named owner inside your business, walk them through the governance charter and exception process, and return after an agreed interval to check whether the rules held, where they were bent, and which thresholds need changing now that you have live data on them.
Ways to work with us
Pipeline hygiene audit
A focused review of your open pipeline and one live deal review, ending in a written audit: what is stale, misstaged or unevidenced, what that is costing your forecast, and the rules we would set first.
Governance build
The full design and build: stage map, forecast categories, probabilities, coverage model, risk signals, CRM configuration, clean-up and scorecard, delivered with your team and handed to a named owner.
Cadence embedding
We run your deal inspections, forecast reviews and scorecard conversations alongside your managers for an agreed number of cycles, then step back as they take them over.
Governance retainer
A periodic check on compliance and drift: the scorecard read with your sales head, rules amended where reality has moved, and new sellers, products or branches brought onto the standard.
Why Gully Sales
Rules written against your pipeline, not a template
Every threshold — ageing limits, coverage, the evidence a stage demands — is calculated from your own closed deals. A rule borrowed from another company is the fastest way to have your sellers dismiss the whole standard.
Sales and operations sit in the same team here
The people writing your stage definitions have sat in deal reviews and run sales processes for Indian SMBs. The standard is written so a seller can follow it on a busy Tuesday, not so it reads well in a document.
We configure the system, not only the policy
A rule that lives in a slide decays. We put what we can into your CRM as fields, validation and flags, and route the rest into a review agenda, so the standard survives the month after we leave.
The clean-up happens with your team, not behind them
Deals are closed, restaged and corrected with the seller who owns them, in a working session. That is slower than a bulk update, and it is the only version the team accepts afterwards.
We are honest about what governance cannot do
Clean records will not create demand or repair a weak offer. What they do is stop you deciding on a picture that is not true, and let you see the real problem sooner than you otherwise would.
Where it applies
Industrial equipment manufacturing
Healthcare and clinics
Interior design and project services
Financial and professional services
IT and software services
Building materials and distribution
Proof
Kambar Group
Natural Gases
Questions buyers ask
We set that with you and write it down. A forecast deal typically needs a named decision maker, a recorded requirement, a quoted value, a next meeting on the calendar and a close date the buyer has acknowledged. A deal that cannot show those can stay in the pipeline, but it drops out of the Commit category. The point is that the test is identical for every seller and every month, so the forecast can be compared.
It depends on how many sellers and products the pipeline covers and how much clean-up the records need. Audit and design move quickly, because they are working sessions with a small group. Configuration depends on what your CRM allows. Clean-up takes as long as the deal count demands, since we do it with the deal owners rather than in bulk. We give you a written sequence after the audit, and we do not commit to a date before we have seen the pipeline.
Access to the CRM or a full export of open and closed opportunities, your targets by seller and period, two to three hours from your sales head for the design session, an administrator who can make changes in the system, and one working session per seller during clean-up. The heaviest requirement is manager attendance at the first reviews. Without that, the rules exist but nothing enforces them.
Against the baseline we record before starting. In the first weeks we watch data completeness, deal ageing and the number of deals breaching a rule. From the second month, coverage and the time spent preparing reviews. Forecast reliability comes last, because it needs at least two sales cycles of clean data before the variance means anything. Every reading is taken from your own system.
We do not sell your deals or take the pipeline over. We do not replace your CRM, though we will tell you if the one you have cannot hold the rules. Territory design, quota setting and incentive structures sit outside this work, as does building your dashboards, which is a separate piece once the data underneath can be trusted. Hiring or removing sellers stays entirely your decision.
It should reduce it. Most of the burden in a badly governed pipeline is repair work: re-explaining a deal in the review, rebuilding a report, digging out what happened in March. We add a small number of required fields at the points where the information is already in the seller's head, and remove the fields nobody reads. If a rule costs more than it returns, we take it out at the quarterly review.
Because we change what updating gets them. Rules are agreed with sellers in the design session rather than handed down. Fields nobody uses are removed. The review runs from the record, so a seller who keeps it current spends less time being questioned. And managers stop accepting a verbal update in place of the record, which is the single change that decides whether any standard survives.
In most cases yes. We have worked with the systems Indian SMBs commonly run, and the design always comes first: we agree the standard, then configure whatever your system can hold and route the rest into the review agenda. If your CRM genuinely cannot support required fields, ageing flags or saved views, we will tell you during the audit rather than after the build.
Pipeline management is the sales discipline of working deals: coverage, the weekly review, and moving specific opportunities forward. This work sits underneath that. It sets the standard the records must meet, the rules the system enforces, and who owns them, so that any review, dashboard or forecast built on the pipeline is standing on something reliable. Many clients take both, in that order.
They are closed with a reason recorded, not deleted. That reason list becomes useful data in itself: it shows where deals die, whether losses cluster around price, timing or a competitor, and which stages leak most. Your pipeline figure will drop when we do this, sometimes noticeably. That drop is not a loss. It is the correction of a number that was overstating what you had.
A named person inside your business, agreed at the start. Usually the sales head, sometimes a sales operations or CRM administrator. They hold the governance charter, approve exceptions and read the scorecard each week. We hand over the rules, the reasoning behind every threshold and the change log, then return at an agreed interval to check whether the standard held.
No. Cleaning is part of the work, and arriving with messy records is normal rather than embarrassing. What we do need is a shared place where deals are recorded and a leadership decision on how far back to clean. If your deals currently live in individual spreadsheets and nobody agrees which list is current, we start by getting them into one place.
Talk to us
The assessment is a conversation, not a pitch. We look at your open pipeline with you, say where it is overstating what you actually have, and tell you which rule we would set first.