Gully Sales turns your pipeline into a number leadership can rely on: stated evidence behind every deal counted, commit separated from upside, and a weekly review that catches slippage while the month can still be recovered.
Gully Sales Private Limited works with small and medium businesses across India, with consultants who have committed a sales number and reported against it.
In one paragraph
Sales forecasting is the discipline of saying in advance, with evidence, how much your business will close in a period. Gully Sales defines what each stage must prove, sets forecast categories and coverage ratios, and installs a weekly review that inspects deals and names risk. You receive a forecast model, a review rhythm and a running record of accuracy against every commitment.
The problem
Most growing businesses do have a forecast. It is a number the sales head reaches by adding the deals that feel likely, adjusted by how the previous quarter went. It runs optimistic early in the month and pessimistic in the final week, and the distance between the two is where planning goes wrong. You order material, approve a hire or promise a delivery date against the first number, then close against the second. Nobody is being dishonest. There is simply no agreed rule about what a deal must prove before it is allowed to count.
Why it persists. It persists because nobody is rewarded for a smaller forecast. A salesperson keeps a stalled deal in the number because taking it out invites questions. A sales head rounds up because the target is the target. And the CRM stages describe what the seller has done, not what the customer has done, so a percentage can be attached to any deal without a single piece of evidence behind it. The forecast becomes a negotiation between people, when it should be a reading of the pipeline.
If it stays unresolved. Left alone, the forecast stops being used. Leadership begins applying its own private discount to whatever sales reports, the team senses that discount and inflates further to compensate, and the two numbers drift further apart each quarter. Planning then moves back to instinct, and the business either carries stock and people it does not need, or turns away work it could have served.
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 forecast model, the stage and category definitions, the review rhythm and the reporting we build with you. How accurate the forecast becomes depends on your team's honesty in the review, the state of your CRM data, and how your market behaves during the period.
Who it is for
What Gully Sales does
Stage definitions and exit evidence
We rewrite your pipeline stages so each one is defined by something the customer has done, not by something your salesperson intends to do. Each stage gets entry criteria, exit evidence and a validity check, so a deal cannot advance because it has been sitting there a long time.
Forecast categories
We separate the pipeline into categories with plain rules: commit, upside, open pipeline and omitted. Each category states what must be true for a deal to sit in it, who may move a deal between categories, and what the business is entitled to plan against from each one.
Probability, weighting and the arithmetic
We set how the forecast is calculated: whether probabilities are attached at all, what each one is derived from, and how weighted pipeline, category roll-up and a judgement view are reported together. Probabilities come from your own historical stage conversion, not from a textbook table.
Pipeline coverage and the gap to target
We work out how much qualified pipeline your business needs to land a given number, using your own win rate and cycle length, then set coverage ratios by stage, segment and salesperson. Coverage is measured for the current period and for the two after it.
The forecast inspection rhythm
We install the meeting that produces the number: a weekly forecast call with a fixed agenda, standard deal inspection questions, a monthly commitment point and a quarterly look further ahead. Managers are trained to inspect a deal without turning the review into an interrogation.
Risk register and slippage control
Every deal in commit carries its risks in writing: an unconfirmed budget, an approval nobody has met, a competitor still in play, a delivery date the plant cannot hold. We track how often deals slip, by how long and for what reason, so the pattern becomes visible.
Actions and the recovery plan
Each review ends with actions, not observations: what each at-risk deal needs this week, which upside deals could be pulled forward if commit falls short, and what the team will do differently when the gap to target is too large to close with the deals in hand.
Reporting and CRM configuration
We configure the stages, fields, categories and reports inside the CRM you already use, and build the one-page forecast view your leadership reads. Where the CRM is not trusted yet, we agree a short data clean-up so the first forecast is not built on stale records.
How it runs
Scoping conversation
We agree what the forecast has to support: cash planning, production, purchase, hiring or a board commitment. We establish who owns the number today, how it is produced, who consumes it, and what decisions currently go wrong because of it. We also agree what sits outside the work.
Accuracy baseline
We reconstruct the last few periods: what was forecast, what closed, which deals slipped and how often. We read stage conversion, win rate and cycle length from your own history, and note where the data is too thin or too dirty to carry a conclusion.
Designing the model
We define the stages and their exit evidence, the forecast categories and their movement rules, the probability method, and the coverage ratios your target requires. Options are put to you with their trade-offs, because a model your team will not maintain is worse than the guess it replaced.
Configuration and reporting
We configure the stages, required fields, categories and reports in your existing CRM, build the leadership forecast view, and run a short clean-up of records that are stale or duplicated, so the first forecast is produced from data people can trust.
Running the first cycles
We run the weekly forecast reviews with your managers, inspect live deals against the new evidence rules, coach the questioning so it stays factual, and correct whatever the first weeks prove impractical. The first commitment is made and then measured openly against what closed.
Review and handover
We compare accuracy against the baseline, report what improved and what did not, and hand over the model, the review formats, the reports and the slippage log. Where you continue with us, this becomes a standing review with your sales head each quarter.
Ways to work with us
Forecast design sprint
The baseline, the model and the review formats, handed to a sales head who will configure and run it with their own team.
Design and implementation
The model plus CRM configuration, reporting, manager training and the first cycles of review run alongside your team until the rhythm holds.
Retained forecast review
We sit in your monthly forecast call, inspect the commit with your sales head, and tighten the model as the team and market change.
Forecast accuracy audit
An independent read of the last few periods: how accurate the forecast has been, where it breaks down, and what would have to change.
Why Gully Sales
We build the forecast from your history, not from a template.
Probabilities, coverage ratios and cycle lengths are read out of your own won and lost record. A model calibrated on someone else's business will mislead yours in its first month.
The rhythm matters more than the spreadsheet.
We spend as much time on the weekly review and the questions asked in it as on the model, because a forecast is a management habit that a document alone has never created.
The forecast is inspected by people who have had to commit one.
Our consultants have committed a forecast to a board and lived with the consequences. That shapes what we ask a salesperson and what we refuse to let into commit.
We work inside the CRM you already own.
Stages, fields, categories and reports are configured in your existing system. New software is a decision we will describe honestly if it is needed, not a condition of the work.
Forecasting is joined to the rest of your revenue engine.
Gully Sales works across marketing, sales, channels, customer success and revenue operations, so coverage gaps are traced back to demand generation rather than blamed on the sellers.
Where it applies
Engineering and industrial manufacturing
Building materials and hardware distribution
Capital equipment and turnkey projects
IT and professional services
Medical devices and diagnostics distribution
Multi-branch service businesses
Proof
Kambar Group
Questions buyers ask
Something the customer has done, not something your salesperson plans to do. Typically a confirmed requirement, a named decision maker who has engaged, a budget the customer has acknowledged, a defined decision date and an agreed next step already in the diary. We set the exact list with your team from your own won deals. A deal missing that evidence can stay in the pipeline, but it does not sit in commit.
Pipeline management is about keeping enough live deals moving and working them well. Forecasting is about saying which of those deals will close in a given period, and how confident the business should be in that answer. They use the same data and support each other. If your problem is that too few deals exist, start with pipeline. If deals exist but the number is never right, start here.
It depends on the number of pipelines and segments, the state of your CRM data, and whether we configure and run the rhythm or only design it. The baseline is the quickest part. The model takes as long as your leadership needs to agree honest definitions, and accuracy only proves itself over several closed periods. We commit in the proposal to a sequence and to review points rather than to a calendar.
A CRM or pipeline export, order and invoice history for the last few periods, whatever past forecasts exist in any form, and access to your salespeople and managers. The real commitment is time: a scoping conversation, a working session to agree stage and category definitions, and your sales head's attendance at the first few reviews. Without those, we can produce a model, but not a habit.
Chiefly by forecast accuracy, measured as the gap between what was committed at the start of a period and what closed by its end, tracked for the team and for each salesperson. Alongside it we watch pipeline coverage, stage conversion, win rate, sales cycle, slippage and quota attainment against the baseline we recorded before anything changed. We report what moved, what did not, and why we think so.
We do not carry your quota or close deals for you; that is outsourced sales, a separate service. We do not replace your CRM, run recruitment, or set the commercial targets themselves, though we will show you what your pipeline can realistically support. Financial budgeting and cash flow modelling sit with your finance team. Anything we believe you need but are not buying from us is named plainly in the proposal.
Yes, though the first step is honest about it. We rebuild the baseline from order history and deal files where the CRM cannot be trusted, and run a short clean-up of stale and duplicated records before the first forecast. Discipline usually improves the data faster than any clean-up does, because the weekly review makes an unmaintained record immediately visible to everyone.
Both, used for different purposes. Categories such as commit, upside and open pipeline are what leadership should read, because they carry clear rules about what may be planned against. Weighted probability is useful for looking at a whole pipeline over a longer horizon. Percentages attached deal by deal without evidence behind them are the version we usually remove first.
That depends on your deal sizes and cycle length, so we set the target from your own baseline rather than quoting an industry figure. A business with many small deals can normally get closer than one where three orders decide the quarter. The first goal is a stable, measured gap you can plan around. Narrowing that gap comes afterwards, once the rhythm holds.
It can, if only misses are punished. We measure accuracy in both directions, so a large overshoot is discussed like a shortfall, and we separate the forecast from the target so a seller is not choosing between honesty and their number. Managers are coached to reward an early warning, because a deal flagged in week two is one the business can still do something about.
Yes, and the method changes. Where a few large tenders or projects decide the year, we forecast each one individually with its own risk register and decision timeline, and report a range across award scenarios rather than a single figure. Coverage is then measured over a longer horizon, because pipeline created this quarter is really serving next year.
No. We configure stages, fields, categories and reports inside the CRM you already own, because the tool is rarely the real constraint. If your system genuinely cannot support stage evidence or category reporting, we say so and describe what changing it would involve as a separate decision for you, with the work it would add and the reasons for it.
Talk to us
It is a conversation, not a pitch. Bring your last three forecasts and what actually closed, and we will tell you what we see, including when we think you do not need us.