Skip to content
GullySales

Every deal moves through the same steps, whoever is selling it.

Sales process design and implementation turns your selling into a defined sequence of stages, each with evidence a manager can check, built into your CRM and used by your team on live deals from the first week.

  • A stage-by-stage sales process your whole team agrees on and follows.
  • Exit criteria that decide when a deal has moved, not when it feels close.
  • A CRM configured to match the process, so your pipeline reflects reality.
Book a free auditTalk to us

Gully Sales Private Limited works with businesses across India on sales, marketing and revenue operations.

In one paragraph

What is Sales Process Design and Implementation?

Sales process design and implementation defines the stages every deal moves through, from first enquiry to signed order, the evidence needed to leave each stage, and the qualification questions behind them. Gully Sales writes that process with your team, builds it into your CRM, and works alongside your sellers until it becomes how they sell every day.

The problem

Two sellers, two ways of selling, and no way to compare them.

Most Indian SMBs never sat down and designed a sales process. It grew. The founder sold a certain way, the first hire copied about half of it, the second hire invented the rest, and the CRM stages came from whatever the software offered on installation day. Everyone is working hard. Deals do close. But nobody can say what a deal in the middle of the pipeline has actually been through, so every review turns into a discussion of feelings rather than facts, and every forecast is a hope with a number attached.

You will recognise it as

  • Ask two of your sellers how a deal progresses and you get two reasonable, completely different answers.
  • Deals sit in one CRM stage for weeks, then jump to negotiation the day before an order arrives.
  • Nobody can say what a proposal-stage deal has already been through, so reviews become storytelling.
  • Follow-up depends on memory, so enquiries go quiet without anyone deciding to let them go.
  • New sales hires take months to become useful, because the method lives in senior people's heads.
  • The same enquiry gets a site visit from one seller and a quotation by email from another.

What it costs the business

  • The month closes well above or well below what the pipeline suggested, and nobody can point to the stage that was wrong.
  • Weak enquiries are worked as hard as strong ones, so your most expensive selling hours go to deals that were never going to close.
  • Coaching stays general, because a manager can see that a seller is losing deals but not where in the process they lose them.
  • The CRM turns into a reporting chore rather than a working tool, and once its data is doubted, it stops being used.
  • Every new region, product or hire is a fresh experiment, because there is no known way of selling to hand over.

Why it persists. It persists because the process is invisible while things are going well. Nobody misses a document they have never had. The team is busy selling, and stopping to define stages feels like paperwork that takes time away from customers. When someone does attempt it, the first version is usually too heavy, built by one person alone, agreed in a meeting and never used again. That failure becomes the reason not to try again, so the company keeps running on individual habit.

If it stays unresolved. Left alone, your sales capacity stays tied to the few people who already know how to sell here. Growth means adding headcount and hoping each new person works it out. Forecasts stay unreliable, so cash, hiring and stock decisions are made on numbers that move without warning, and the business carries risk it cannot see.

What changes

What changes once the process is written, built and actually used.

In the first weeks

  • One written sales process, from first enquiry to won, lost or parked, that everyone has seen and agreed to.
  • A qualification standard that says plainly which enquiries deserve serious selling time and which do not.
  • A CRM pipeline whose stages mean the same thing to every person entering a deal.

In how the work runs

  • Stage movement becomes evidence-based, so pipeline reviews discuss what happened rather than what is hoped.
  • Managers coach the specific step where deals stall, instead of coaching the seller in general.
  • A new seller learns the process in their first weeks instead of absorbing it over a year.
  • Every open deal has a defined next step, a date and an owner, so fewer opportunities go quiet by accident.

In sales and marketing

  • Selling time shifts towards opportunities that meet the qualification standard.
  • Quotations and proposals go out after the buyer's need, budget holder and decision path are known.
  • Handovers between marketing, inside sales and field sales stop losing enquiries in the gap.

In what management can see

  • Conversion between every stage becomes visible, so weak points are named rather than guessed at.
  • Pipeline coverage and forecast can be read from the system instead of collected by phone each month.

Over the longer term

  • The company owns a repeatable way to sell that survives people joining and leaving.
  • Adding sellers, territories or products becomes a change to a known system rather than a fresh experiment.

Gully Sales controls the design, the CRM configuration, the templates and the coaching that embeds them. Win rates, cycle length and revenue also depend on your market, your offer, your pricing and how consistently managers hold the standard. We commit to the work and to measuring it honestly.

Who it is for

This is built for teams that already sell, and now need it to be repeatable.

The businesses it suits

  • Founders who still close the important deals themselves and want the method taken out of their head.
  • Sales heads leading three to thirty sellers whose individual approaches differ widely.
  • Businesses with a CRM whose stages were never defined, so the reports are not trusted internally.
  • Companies about to hire sellers, where onboarding currently means shadowing whoever is free that week.
  • Teams selling considered purchases involving several meetings, a site visit, a trial or an approval chain.
  • Manufacturers, distributors, service firms and institutional suppliers selling across India.

What usually prompts the call

  • A quarter closed far away from forecast and nobody can explain which deals moved wrongly.
  • You are hiring sales people and have nothing written to hand them on day one.
  • A CRM was implemented, the team fills it reluctantly, and the pipeline report is quietly ignored.
  • Two similar enquiries were handled completely differently, and only one of them was followed up.
  • You are entering a new region, segment or product line and want it sold the same way everywhere.
  • A senior seller resigned and took the working knowledge of your accounts with them.

What Gully Sales does

The work, component by component.

Sales stage design

We map how a deal actually travels through your business today, from first enquiry to order, including the parts that happen outside sales such as costing, a site survey, a sample approval or a credit check. Then we design the smallest set of stages that describes that journey honestly, named in your language rather than in software defaults.

Why it matters:
Stages that do not match how you really sell are abandoned within weeks, and the pipeline goes back to being a list.
You receive:
A one-page sales process map and a stage definition sheet naming each stage, its purpose and its owner.
Business value:
Everyone in the business, including people outside sales, shares one picture of how an order gets won.

Entry and exit criteria

For every stage we write what must be true before a deal enters it and what evidence must exist before it leaves. Not opinions, but checkable facts: the decision maker has been met, the requirement is documented, the budget is confirmed, the sample has been approved. The criteria are written so a manager can verify them in the CRM without a phone call.

Why it matters:
Without exit criteria, stage movement records optimism, and every conversion number built on it is unreliable.
You receive:
Entry and exit criteria for each stage, written as evidence, with the field in the CRM that records it.
Business value:
A deal in a given stage means the same thing on every seller's list, which makes conversion and forecasting real.

Qualification standard

We build a qualification framework suited to what you sell, covering need, authority, budget, timing, competition and fit, with the questions your sellers should ask and the answers that count as satisfied. It includes a disqualification rule, so a seller has permission to stop working an enquiry that will not become a customer.

Why it matters:
Most SMB sales teams lose more time to unqualified enquiries than to lost competitive deals, and nobody measures it.
You receive:
A qualification standard with question sets, scoring and clear rules for parking or disqualifying an enquiry.
Business value:
Selling hours move towards deals that can close, and pipeline stops being inflated by opportunities that will never move.

Stage activities and next steps

Each stage gets the activities expected inside it: what the seller does, who else needs to be involved, what the buyer should receive, and what the agreed next step looks like. Every open deal carries a next action with a date and an owner, so nothing waits on somebody remembering it.

Why it matters:
Deals rarely die from a lost argument. They die from a follow-up that nobody scheduled and nobody owned.
You receive:
A stage activity checklist and a next-step rule your sellers apply to every open opportunity.
Business value:
Follow-up becomes a property of the system rather than a personal habit, so fewer live opportunities go silent.

Working templates

We create the small set of documents the process needs to run: a discovery note, a requirement capture sheet, a proposal structure, an internal handover note, a lost-deal reason form and a deal review one-pager. Templates are built in the tools your team already uses, with a filled-in sample so the standard is visible.

Why it matters:
A process without artefacts stays theoretical, and every seller quietly rebuilds their own version of each document.
You receive:
A template pack with a worked example of each document, ready to use on live deals.
Business value:
Information about a deal survives the person who gathered it, and quality stops depending on who prepared the file.

CRM controls and configuration

We translate the process into your CRM: pipeline stages, required fields at each stage, validation that prevents a deal moving without its evidence, reason codes for wins and losses, activity logging and the reports managers need. Where you have no CRM, we specify what it must do before you choose one, so the tool follows the process.

Why it matters:
If the system permits a deal to jump stages with empty fields, the written process will be ignored within a month.
You receive:
A CRM configuration specification and, where access allows, the configured pipeline, fields and reports.
Business value:
The process is enforced quietly by the system, and pipeline data becomes trustworthy enough to plan against.

Adoption and manager routine

We train the team on the process using their own live deals, sit in on the first pipeline reviews, and coach managers to inspect against exit criteria instead of asking for status updates. Objections from experienced sellers are handled openly, because the ones who sell most have usually spotted a genuine flaw worth fixing.

Why it matters:
Adoption is decided by what managers inspect in week three, not by how good the design looked in week one.
You receive:
Team training sessions, a manager review agenda, and coaching through the first cycles of live use.
Business value:
The process becomes the way work is discussed, which is the only point at which it starts changing results.

Governance and revision

We agree who owns the process, how a change is proposed, and when it is reviewed. Early versions always need adjustment: a stage nobody uses, a criterion that is too strict, a field that adds work without adding insight. A revision log records what changed and why, so the process improves instead of drifting.

Why it matters:
A process left unowned decays back into habit within two quarters, usually without anyone noticing it happening.
You receive:
A named process owner, a change procedure and a revision log with the review cadence written down.
Business value:
The process stays accurate as your products, buyers and team change, so it keeps earning its place.

What you will have at the end.

  • A one-page sales process map covering first enquiry to won, lost or parked.
  • A stage definition sheet stating what each stage means, who owns it and what it is for.
  • Entry and exit criteria for every stage, written as evidence a manager can verify.
  • A qualification standard with question sets, scoring and disqualification rules.
  • A stage activity checklist telling each seller what happens next, by when and with whom.
  • Working templates for discovery, requirement capture, proposal structure and internal handover.
  • A win and loss reason code set your team can apply consistently at closure.
  • A CRM configuration specification: stages, required fields, validation rules and reports.
  • The configured pipeline in your CRM, or a specification your software vendor can implement.
  • A stage conversion, pipeline coverage and forecast report your managers can run themselves.
  • A weekly pipeline review agenda and a monthly process discipline review agenda.
  • An onboarding pack that teaches a new seller the process during their first weeks.

How it runs

The engagement, step by step.

  1. 1

    Understand how you sell today

    We interview your sellers, managers and the people they depend on in costing, operations and dispatch. We read the last set of won and lost deals, listen to how enquiries are handled, and look at your CRM data as it stands. The aim is an honest description of the current route to an order, including the informal steps nobody has written down.

    You provide:
    Access to your sales team for interviews, recent won and lost deals, and read access to your CRM or enquiry records.
    We produce:
    A current-state process map, a list of the gaps and inconsistencies found, and the questions the design must answer.
    Done when:
    You recognise your own business in the map, including the parts that are uncomfortable.
  2. 2

    Design the stages and criteria

    We design the stage set, define entry and exit criteria as checkable evidence, and decide what happens at each handover between marketing, inside sales, field sales and delivery. This is done in working sessions with your sellers rather than presented to them, because a process the team helped write is the only kind that survives a busy week.

    You provide:
    Two or three working sessions with the people who sell, and a decision maker who can settle disagreements.
    We produce:
    The stage definition sheet, entry and exit criteria, handover rules and the deal review one-pager.
    Done when:
    Your sales team and your management agree that the stages describe how deals should move, and sign off on the criteria.
  3. 3

    Set the qualification standard

    We define what a qualified opportunity means for your business, in terms a seller can apply in a first conversation: the questions, the acceptable answers, and the rules for parking or disqualifying an enquiry. We then test the standard against your current open pipeline to see how much of it would actually qualify.

    You provide:
    Your current open pipeline, plus a view of which customers have been profitable to serve and which have not.
    We produce:
    The qualification standard, the question sets, and a re-scored view of your existing pipeline against it.
    Done when:
    You can see how much of today's pipeline is genuinely qualified, and the team accepts the standard.
  4. 4

    Build it into the CRM

    We turn the design into system configuration: stages, required fields, validation that blocks a stage change without its evidence, reason codes, activity logging and manager reports. Where you use a common CRM and give us access, we configure it. Where change must go through your vendor, we write the specification and review their build.

    You provide:
    CRM administrator access or a nominated contact at your software vendor, and a decision on data migration.
    We produce:
    The configuration specification and the built pipeline, fields, validations and reports.
    Done when:
    A deal cannot move stage in the system without the evidence the process requires.
  5. 5

    Create the working templates

    We build the documents the process depends on in the tools your team already uses, and fill one of each with a real deal so the expected standard is visible rather than described. Templates stay deliberately short: anything a seller will not complete under time pressure is redesigned or removed.

    You provide:
    Access to your document tools, and one recent live deal we can use as the worked example.
    We produce:
    The template pack with a completed sample of each document.
    Done when:
    A seller can pick up any template and complete it correctly without asking how.
  6. 6

    Train the team on live deals

    We run the training on your own open opportunities rather than on case examples. Each seller re-stages their pipeline against the new criteria, applies the qualification standard, and sets a next step for every deal. Disagreements surface here, which is useful: they show where the design is unclear or wrong.

    You provide:
    Time for the full sales team, including the senior sellers who are hardest to schedule.
    We produce:
    Training sessions, a re-staged pipeline, and a list of design corrections that came out of the room.
    Done when:
    Every open deal sits in a stage that its evidence supports, with a dated next step and a named owner.
  7. 7

    Embed the manager routine

    We sit in on the first weekly pipeline reviews and monthly process reviews, and coach your managers to inspect against exit criteria rather than ask for updates. We correct the common failures early: the deal parked without evidence, the next step with no date, the forecast that ignores the pipeline.

    You provide:
    Your sales managers in the review meetings, and their willingness to change how they run them.
    We produce:
    A manager review agenda, observation notes after each session, and coaching for the people running reviews.
    Done when:
    Your managers run a review to the agenda without us in the room, and hold the standard when it is inconvenient.
  8. 8

    Measure, review and revise

    We compare stage conversion, cycle length, win rate, pipeline coverage and forecast accuracy against the baseline taken at the start, look at where deals now stall, and revise the process where the evidence asks for it. Ownership, the change procedure and the review cadence are handed to your team in writing.

    You provide:
    Continued CRM access for reporting, and a nominated internal owner for the process.
    We produce:
    A measurement review against baseline, agreed revisions, and the governance and revision log.
    Done when:
    Your named owner is running the process, measuring it and changing it without depending on us.

Ways to work with us

Design the process, build it into the CRM, or run it in with the team.

Process design

Current-state review, stage design, entry and exit criteria, qualification standard and the template pack. You implement it in your own systems with your own team. Suitable where you have a capable sales manager and a CRM administrator already in place.

Design and implementation

Everything in the design engagement, plus the CRM configuration specification, the built pipeline, fields, validations and manager reports, and the first round of team training on your live deals.

Design, implementation and adoption

The full programme: design, build, training, then sitting in on pipeline reviews, coaching your managers, correcting the design where live use exposes a flaw, and measuring against the baseline before handing ownership over.

Process review and repair

For businesses that already have a documented process which is not being followed. We audit the design against how deals really move, find where adoption broke, and repair the criteria, the system controls and the manager routine.

Ongoing process governance

A retained arrangement where we review the process each quarter with your named owner, examine conversion and forecast accuracy, and revise stages and criteria as your products, buyers and team change.

Why Gully Sales

What you are actually choosing when you choose us.

We design for the sale you actually make.

A process copied from a software template or from enterprise software sales does not survive an Indian SMB selling through site visits, samples, distributor relationships and long payment conversations. We design around how your orders are really won.

The process is built into the system, not into a slide deck.

A design that lives in a document is forgotten by the second busy week. We put the stages, the required evidence and the reports into your CRM, so the process is enforced quietly while people work.

We work with the sellers you already have.

Your experienced people usually know what really moves a deal. We build the design in sessions with them, so what emerges reflects real selling and comes with their agreement rather than their resistance.

We stay through adoption, not only design.

Most process work fails after handover, when managers go back to asking for updates. We sit in on the first reviews, coach the people running them, and correct the design where live use shows it is wrong.

Sales, marketing and operations are treated as one system.

Enquiries come from marketing and orders end in operations. We define the handovers on both sides, so leads are not lost at the entry point and commitments made in a sale can actually be delivered.

We hand over the controls.

You get the configuration, the templates, the reports and a named internal owner with a change procedure. The point of the engagement is that your team runs and revises the process without us.

Where it applies

The same service, in different businesses.

Industrial manufacturing and engineering

The situation:
Enquiries arrive from several sources, each needing a drawing review, a costing and often a plant visit before a quotation can be issued.
How it applies:
Stages separate technical qualification from commercial negotiation, and exit criteria require a documented specification and a confirmed costing before a quotation goes out.
Likely benefit:
Quotation effort goes to enquiries that have been technically qualified, and the estimation team stops absorbing work that will never convert.

Building materials and hardware distribution

The situation:
Sales run through dealers, contractors and architects at the same time, with different people influencing and different people paying.
How it applies:
The process defines which party a deal is tracked against, how influencer relationships are recorded, and what evidence is required before a project is treated as live.
Likely benefit:
Project pipeline stops being counted twice through two channels, and coverage figures become dependable enough to plan stock and credit.

Professional and B2B services

The situation:
Every proposal is written from scratch, senior partners are pulled into pursuits late, and much of the effort goes to prospects who were never ready to buy.
How it applies:
Qualification is placed before proposal writing, with budget authority and decision path as exit criteria, and a proposal structure replaces the blank page.
Likely benefit:
Senior time is spent on pursuits that are qualified, and the effort of producing a proposal is matched to the value of the opportunity.

Renewable energy and capital equipment

The situation:
Long buying cycles involve a site assessment, financing, approvals and several stakeholders, and deals go quiet for months without anyone noticing.
How it applies:
Stages follow the buyer's approval sequence, and every deal carries a dated next step, so a stalled opportunity is visible in the review rather than assumed to be progressing.
Likely benefit:
Stalled deals are identified and either revived or parked honestly, so the pipeline shows what is genuinely in play.

Agri-inputs and rural distribution

The situation:
Field teams cover wide territories, deals are agreed in person, and the record of what was promised often exists only in a notebook.
How it applies:
A light mobile-first process captures the visit, the requirement and the next step, with exit criteria a field seller can complete in a few minutes.
Likely benefit:
Territory activity and commitments become visible to managers without adding office work that field sellers will not do.

Proof

Work we can point to.

Kambar Group, a corporate gifting firm in Bangalore

The problem:
The group struggled to optimise its sales processes and set clear objectives, and needed practical criteria for qualifying leads and closing them.
What we did:
Gully Sales analysed customer behaviour and mapped the buyer's journey through awareness, consideration and decision, implemented prospecting methods and lead qualification criteria, and trained the team on closing technique.
The result:
The case study reports increased sales efficiency, with streamlined processes and clear objectives improving the team's work, and qualification producing higher-quality leads.
Read the case study

Questions buyers ask

Before you enquire, the answers you will want.

How will the process actually be embedded in daily selling?

Three things do it, and all three are needed. The system enforces it, because a deal cannot change stage without its evidence. The templates carry it, because the documents sellers already use now match the stages. And managers inspect it, because the weekly review asks what evidence exists rather than how a deal feels. We train on your live pipeline, not on examples, and stay through the first review cycles to correct the habits that slip.

How long does an engagement like this take?

It depends on the number of sales roles, products and regions the process must cover, and on the state of your CRM. Design moves quickly once your team is available for working sessions. Implementation depends on system access. Adoption is the longest part, because it runs through live review cycles rather than a workshop. We give you a scoped schedule in writing after the first conversation, and we do not commit to a date before we understand the scope.

What do you need from us?

Time with your sellers and managers for interviews and design sessions, access to recent won and lost deals, read access to your CRM or enquiry records, and one person senior enough to settle disagreements about how the business should sell. During adoption we need your managers in their own pipeline reviews. The engagement slows down when senior sellers cannot be scheduled, so protecting that time early matters more than anything else.

How is success measured?

Against your own baseline, recorded before we change anything. We track pipeline coverage, stage-to-stage conversion, win rate on qualified opportunities, sales cycle length, target attainment per representative, forecast accuracy and how much of the pipeline carries complete evidence. Some of these move within a month, particularly evidence quality and forecast accuracy. Conversion and cycle length need a full sales cycle before the numbers say anything reliable.

What is excluded from the scope?

We do not write your positioning or campaign messaging, run your marketing, recruit your sellers or replace your sales manager. We do not sell on your behalf under this engagement. Buying a new CRM licence, migrating historical data or custom software development sits with you or your vendor, though we specify what is required and review what they build. Anything outside the agreed scope is quoted separately, never added quietly.

How is this different from a sales playbook?

The process is the sequence of stages a deal moves through and the evidence required to move it. The playbook is what your seller says and shows inside those stages: the positioning, the questions, the objection responses, the competitor comparisons. The process is the track; the playbook is how you drive. They work well together, and many businesses do the process first because the playbook has nowhere to sit until the stages exist.

We already have stages in our CRM. Is that enough?

Usually not, because most CRM stages arrived as software defaults and were never defined. The test is simple: ask two sellers what has to be true for a deal to sit in your proposal stage. If the answers differ, the stage is a label rather than a control, and every conversion number built on it is unreliable. We often keep the stage names your team knows and add the definitions and evidence underneath them.

What if our sales team resists the change?

Expect some resistance, particularly from people who sell well already. We build the design in sessions with them rather than presenting it, because they usually know what actually moves a deal and their objections often reveal a real flaw. We also keep the process light: anything that adds work without adding insight gets removed. Resistance that survives all of that is a management conversation, not a design problem.

2 more questions

Which CRM do you work with?

We work with the common ones used by Indian SMBs and with whatever you already have, including a well-run spreadsheet if that is your current position. Our work is the process design and the configuration specification: stages, required fields, validation rules, reason codes and reports. Where we have administrator access to a mainstream CRM we configure it directly. Where changes must go through your vendor, we write the specification and review their build.

Our sales team is only three people. Is this worth doing?

It can be, if you are about to grow or if the founder is still closing everything. A three-person team needs a lighter process than a twenty-person team, and we scope it accordingly, usually fewer stages and simpler evidence. The value at that size is less about reporting and more about the founder being able to hand deals over without watching every step personally.

Talk to us

See how your last ten deals actually moved through the business.

It is a conversation, not a pitch. We look at how deals move through your business today and tell you plainly whether process design is the right thing to spend money on now.

  • No obligation and no sales script
  • A reply from someone who does the work
  • Your details are never sold or shared

Your details are used only to reply to your enquiry. We do not sell or share them. Anything you tell us about your pipeline, customers or team stays confidential.

Protected by reCAPTCHA — Google’s privacy policy and terms apply.

Get a free audit of how you sell, and a scored report of where the work is.

Book a free audit
Book a free audit