Gully Sales maps what actually happens to a customer after they say yes, stage by stage, then hands you a prioritised plan for the points where confidence, patience and repeat business leak away.
Gully Sales Private Limited works with small and medium businesses across India, and every map is built from real customer accounts rather than assumptions.
In one paragraph
Customer experience strategy and journey mapping is how you see your business the way a customer does after they buy. Gully Sales speaks to your customers, walks the journey with your own team, draws every stage and touchpoint, marks where people get stuck, and turns the findings into a prioritised plan with named owners.
The problem
Your business almost certainly serves customers well in parts. The sale is handled properly. The delivery team knows its job. Accounts sends the invoice. Yet the customer experiences none of these as separate things. They experience one continuous stretch of time in which they are sometimes informed and sometimes waiting, and it is the waiting they remember. The joins between your departments are where the journey is decided, and no job description covers them.
Why it persists. It persists because every department is measured on its own part and nobody is measured on the join. Sales is judged on orders, operations on delivery, service on tickets closed. Each can hit its number in a month where the customer had a poor time overall. There is also no single view to argue from: the customer's account lives in their memory, your team's account lives in several heads, and the records are scattered across a spreadsheet, a WhatsApp group and a few email threads.
If it stays unresolved. Left alone, the business keeps buying new customers to replace the ones it is quietly losing, and calls that growth. The team grows tired of firefighting the same failures. Long-standing customers become the least attended, because attention follows whoever is shouting. Eventually a competitor with a plainer product but a calmer, more predictable journey takes the accounts you assumed were safe.
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 mapping, the evidence behind it, the target experience written with your team and the roadmap that follows. Whether retention and revenue improve also depends on your product, pricing, competitors and how much of the roadmap your business actually runs.
Who it is for
What Gully Sales does
Journey stages, from the handover out of sales
We agree where the post-sale journey begins and ends for your business, then break it into the stages a customer actually passes through: the handover from the person who sold, the first delivery or first visit, the first problem, the settled routine, and the moment renewal or repeat purchase is decided. Stages are named the way customers describe them, not the way your departments are arranged.
The question a customer is asking at each stage
At every stage a customer carries a question, and a worry behind it. Will this arrive when you said? Who do I call when it stops working? Am I using this correctly? Was this worth what I paid? We collect those questions from your customers in their own words and place each one against the stage where it is asked.
Touchpoint and ownership inventory
We list every place your business meets a customer after the sale: calls, WhatsApp messages, invoices, delivery notes, site visits, service calls, reminders, portals and emails. Each touchpoint gets an owner, a channel, a current standard where one exists, and an honest note on whether it happens consistently or depends on who is on duty that day.
Friction, drop-off and duplicated effort
We mark every point where the journey breaks: a delay the customer was never warned about, information they had to give twice, an escalation with nowhere to go, a step that needs a person who is often unavailable. Each friction point is described with its evidence, placed on the map, and traced through to the effect it has on the customer and on your own team.
Conversion and experience opportunities
The same map shows where the journey could earn more. A customer who has just had a smooth delivery is the easiest person to ask for a referral. A customer whose usage has grown is ready for a conversation about the next product. We mark the stages where an offer, a check-in or a simple question is welcome, and the stages where the same approach would irritate.
The experience roadmap
Findings become a sequenced plan. Each change is written as a task with an owner, the effort it needs, the stage it improves and the measure it should move. Corrections that need only a decision are separated from changes that need new process, new roles or new tools, so your team can begin at once instead of waiting for a budget cycle.
How it runs
Scope, segments and baseline
We agree which journey we are mapping, because a first-time buyer and a five-year account do not travel the same road. We settle the segments in scope, the start and end points, and the questions leadership wants answered. Then we take a baseline from whatever data exists today, however imperfect it is.
Listening to your customers
We speak to a spread of your customers: recent buyers, long-standing accounts, quiet ones and, where possible, a few who left. These are conversations, not surveys. We ask what happened, in order, and where it felt slow, confusing or unnecessary. We also read complaint threads and support messages, because people write plainly when they are annoyed.
Walking the journey with your own team
We sit with the people who actually serve customers: the sales coordinator, the service engineer, the front desk, the accounts assistant. They know where the process bends and where they quietly work around it. We record the journey as they run it rather than as the process document describes it, and mark every step that depends on one person's memory.
Drawing the journey as it is
We draw the current journey on one page: stages, touchpoints, owners, the question the customer is carrying at each stage, and how they feel by the end of it. Where the customer's version and the internal version disagree, both are shown, because that gap is usually the most useful thing on the page.
Deciding what the experience should be
For each stage we write what should happen: what the customer receives, who contacts them, to what standard, and what they should be left knowing. We keep it to what your business can actually staff and sustain, because an ambitious standard nobody meets does more damage than a modest one everybody keeps.
Sequencing the roadmap
Everything found is sorted into what can be corrected now with a decision, what needs a process change, and what needs new roles or systems. Each item gets an owner, a position in the sequence and the measure it should move. We are deliberately conservative about how much runs at once, because a roadmap nobody finishes teaches a team to ignore the next one.
Handover and first review
We walk your team through the map and the roadmap in a working session, so the people who serve customers understand the reasoning and not only the instruction. We agree the review rhythm, then return once the first changes have been in place long enough to show a movement, and read the numbers against the baseline together.
Ways to work with us
Journey diagnostic
One customer segment, one journey. Customer conversations, an internal walkthrough, the current-state map, a friction register and a short roadmap. Suited to a business that wants to test whether the problem sits where it thinks it does.
Full experience strategy
Several segments or several journeys mapped, the target experience written stage by stage, the roadmap sequenced across departments, and the measurement sheet built together with the people who will report on it.
Roadmap support
We stay alongside your owners while the first changes land: joining the review, keeping the measures honest, and adjusting the sequence when reality intervenes. Taken up after you have seen the roadmap, never before.
Annual journey review
A yearly re-reading for businesses that have changed: new products, new branches or a much larger customer base. The journey moves when the business moves, so the map is checked against what customers now experience.
Why Gully Sales
We map what customers experienced, not what the process claims.
The map is built from customer conversations, support records and a walkthrough of the real work. Where the documented process and the lived experience differ, we show both, because the gap between them is usually where the problem lives.
We work across sales, service, delivery and accounts.
Gully Sales works on marketing, sales, channels, customer success and revenue operations together. A journey crosses all of them, so we are not forced to stop at the boundary of one function and hand the rest to someone else.
Every finding carries its source.
Each friction point on the map names its evidence: a customer's words, a support record, a step your own team described. That turns a difficult finding into a conversation about facts rather than about whose department is at fault.
The map ends in owned work, not a poster.
A journey map that decorates a wall has cost you money and changed nothing. Ours ends in a sequenced roadmap where every item has an owner, an effort estimate and the measure it is meant to move.
We build it with the people who will run it.
The frontline staff take part in the mapping and in setting the standards. They know what is workable and what will be quietly abandoned, and work they helped design is work they are far more likely to keep doing.
We are honest about what a map cannot fix.
Journey work will not repair a product that does not perform or a price the market rejects. If the evidence points there, we say so, and you can spend the money on the real problem instead.
Where it applies
Industrial manufacturing and equipment supply
Clinics and hospitals
Software, IT services and subscriptions
Education, training and coaching institutes
Facility management and annual contract services
Real estate and interior projects
Proof
Chord Road Hospital
Questions buyers ask
Every finding on the map is carried into the roadmap as a task with an owner, a place in the sequence and the measure it should move. Some are corrections you can make within days: a message that was never sent, a form asking for information you already hold. Others need a process change or a new role. We separate the two, so your team starts on the simple ones while the larger changes are planned properly.
It depends on how many segments are in scope, how many of your customers agree to speak, and how much of your history is already written down. One journey for one segment moves faster than a map covering several products, branches or locations. You receive a schedule in the written scope after the assessment call, and we would rather agree a realistic one than a flattering one.
Time, mainly. Introductions to a spread of customers who will speak honestly, access to your complaint and support records, order or invoice history, and a few hours with the staff who deal with customers every day. You do not need a CRM, a helpdesk or tidy data. Where records are missing we say so in the baseline and define how that number will be counted from then on.
Against the baseline taken before the work starts. Operational measures such as time to first value, complaint resolution and adoption usually move first. Retention, renewal rate, expansion revenue and lifetime value move much later and are influenced by pricing, competition and your product as well as by experience. We report both, and we are clear about which part of a movement this work can reasonably claim.
We map, decide and sequence. Within this scope we do not rebuild your support process, install a helpdesk, run an ongoing satisfaction survey programme or manage the changes through to completion. Those are separate pieces of work, and the roadmap will tell you which of them your journey actually needs. Buying the map is not buying the build, and we would rather say that at the start than at the invoice.
A survey gives you a score. A map gives you the reason behind the score. Numbers tell you that customers were unhappy last quarter; they rarely tell you that the delivery note arrives two days after the goods, or that the person who sold never introduced the service team. We use survey and complaint data as evidence, but the map itself is built from conversations, records and a walkthrough of the actual work.
It is often more relevant. In a smaller business the journey is held together by two or three people who remember everything, which works until one of them is on leave or resigns. Writing the journey down does not add headcount. It removes the guesswork about who does what, and makes it possible to hand a stage to a new person without the customer noticing.
Yes, with your permission and your introduction. We explain who we are and why we are calling, we sell nothing during the conversation, and we report findings as anonymised themes rather than as named complaints unless a customer asks us to pass something on. Most customers are willing to speak. Being asked at all usually improves the relationship rather than straining it.
That happens, and it is why we record evidence rather than opinion. Each friction point carries its source: a customer's own words, a support record, a step your team described in the walkthrough. The discussion then turns on the evidence rather than on blame. We also involve the people who run each stage while we are mapping, so the finding is rarely a surprise by the time leadership reads it.
We can. Some businesses take the roadmap and run it themselves, which is a sensible choice when the owners are clear and capable. Others want us alongside the first few changes, joining the review, keeping the measures honest and adjusting the sequence when reality intervenes. That is agreed separately, after you have seen the roadmap and decided which parts you want to carry yourself.
No. The map is drawn from conversations, records and observation, and most of the early fixes are decisions rather than systems: a message that gets sent, a person who gets named, a standard that gets written. If the roadmap shows that a system is genuinely needed, it appears with a reason attached rather than as a purchase you make first and justify afterwards.
Enough to stop hearing anything new. We aim for a spread rather than a large sample: recent buyers, long-standing accounts, quiet ones and, where you are willing, a few who have left. In most smaller businesses the themes repeat well before the list runs out. The number in scope is written into the scope document so there is no ambiguity later.
Talk to us
The assessment is a working session, not a pitch. We ask what happens after a customer buys from you, where the relationship tends to go quiet, and what you already suspect. If a full mapping exercise is not what your business needs right now, we will say so.