Skip to content
GullySales

An interface your customers can use without calling you for help.

Gully Sales designs the screens, flows and interface system of your website, portal or app around the tasks your customers actually come to do, and tests them with real users before a developer writes a line of code.

  • Every screen designed from a task a real customer needs to complete, not from a template.
  • Wireframes tested with your customers and staff before visual design begins.
  • An interface system your developers can build once and reuse on every new page.
Book a free auditTalk to us

Gully Sales Private Limited designs digital experiences for small and medium businesses across India, and every engagement begins with a free audit.

In one paragraph

What is UI/UX design services for Indian businesses?

UI/UX design from Gully Sales gives an Indian business an interface its customers can understand and use without help. We research how your customers buy, map the tasks they come to complete, wireframe and test the flows before visual design, and hand your developers an interface system and specifications that leave nothing to guesswork, so the website, portal or app produces enquiries, bookings or orders instead of confusion.

The problem

Visitors arrive, look around, and leave without doing anything.

Most Indian businesses have a website or portal that was designed to look right in a presentation. It was approved by the owner, built by a developer, and launched. Then the enquiries did not come, the support calls did, and nobody could point to the screen where it went wrong. The interface was never watched in the hands of a customer. If some of these sound familiar, you are in the situation this service was built for.

You will recognise it as

  • Customers phone or WhatsApp to ask things the website was supposed to answer, because they could not find where to look.
  • The enquiry form, quote request or checkout is where most visitors give up, and nobody knows at which field.
  • The site looks fine on the designer's screen, but customers on a mid-range phone keep pinching, scrolling and mis-tapping.
  • Every new page is designed from scratch, so buttons, forms and menus behave differently from one section to the next.
  • The design was approved because it looked good, not because anyone watched a customer try to use it.
  • Your own sales team sends prospects a PDF or a WhatsApp message instead of a link, because the site explains the offer worse than they do.

What it costs the business

  • Marketing spend brings visitors who cannot complete the task they came for, so the cost per enquiry rises while the enquiry count stays flat.
  • Staff time goes into answering questions and re-entering details the interface should have captured correctly the first time.
  • Developers rebuild the same components again and again because there is no interface system, so every change is slower and costlier than it should be.
  • Buyers judge the business by the interface: a portal or app that is hard to use reads as a company that will be hard to deal with.

Why it persists. Interface design is usually bought as decoration. A designer produces attractive screens, the owner approves the look, and the developer builds what was approved. Nobody in that chain is responsible for whether a customer can complete a task. Usability problems only surface after launch, in support calls and abandoned forms, and by then changing the interface means changing the code, so the problems are lived with.

If it stays unresolved. Each redesign repeats the same mistake with a fresh coat of paint. Conversion stays low, support load stays high, and the business keeps paying for traffic that leaks out through an interface that was never tested with the people it was built for.

What changes

What you receive, and what may follow once the interface is live.

In the first weeks

  • User research findings: who uses the interface, what they come to do and where they get stuck today.
  • Task flows and wireframes for every key journey, tested with real users before visual design.
  • An interface system: components, patterns, states and rules your developers can build from.
  • Annotated specifications and a clickable prototype that leave no screen open to interpretation.

In how the work runs

  • Fewer support calls and WhatsApp messages asking for things the interface now makes obvious.
  • Faster development of new pages and features, because components are reused rather than reinvented.
  • One consistent experience across desktop, tablet and phone, maintained by rules rather than by memory.

In sales and marketing

  • Visitors who arrive with intent can complete an enquiry, booking or order without help.
  • Marketing spend works harder because the interface stops leaking the traffic it receives.

In what management can see

  • An interface that is easier to use tends to hold attention longer and be returned to and recommended more often.
  • Accessible, responsive screens that work for customers on the devices and connections they actually have.

Over the longer term

  • A design foundation the business can extend to new products, portals and apps without starting again.
  • A habit of testing with users before building, which makes every future digital decision cheaper.

Gully Sales controls the research, flows, wireframes, interface system and usability testing. Conversion, enquiry volume and support load also depend on your offer, traffic, pricing and how well the build follows the design. We report what the design changed and say what else moved.

Who it is for

This is for you if people struggle to use what you have built, or are about to build.

The businesses it suits

  • A business commissioning a new website, customer portal, dealer app or booking system that should be designed around users before it is coded.
  • An e-commerce or D2C brand whose product pages and checkout are visited far more often than they are completed.
  • A manufacturer or distributor whose dealer or customer portal is bypassed in favour of phone calls and WhatsApp.
  • A clinic, hospital, school or service business whose booking or enquiry flow confuses the very people it is meant to serve.
  • A software company whose product works but whose interface makes trials drop off before the value is seen.
  • An owner whose site looks good and who still asks why it does not produce enquiries.

What usually prompts the call

  • A new website, portal or app is being scoped and the developer has asked for designs.
  • Analytics show visitors reaching the enquiry, quote or checkout step and abandoning it there.
  • Support staff keep answering the same navigation and how-do-I questions every week.
  • A redesign is planned and the owner does not want to repeat the last one's mistakes.
  • The business is moving customers or dealers from phone and paper to a digital channel for the first time.

What Gully Sales does

The work, component by component.

User research

Before any screen is drawn we speak to the people who will use the interface: customers, dealers, patients, students or your own staff. We interview them, watch them attempt real tasks on whatever you have today, and go through your enquiry logs, support messages and analytics to see where people already struggle.

Why it matters:
An interface designed from assumptions serves the person who made the assumptions. Ten minutes watching a real customer fail a task settles arguments that would otherwise run for weeks.
You receive:
A research report with the tasks, frustrations and language users actually bring, supported by anonymised quotes and observations.
Business value:
Design decisions rest on what your customers do, not on what the room believes they do.

Task flows

We list every job a user comes to the interface to complete, rank them by how often they happen and how much they are worth, and map the priority ones step by step: each screen, each decision, each error, each point where a person might give up or need help.

Why it matters:
Most interfaces are organised around the company's departments or the developer's database. Task flows organise them around what the user is trying to finish, which is the only structure that produces completions.
You receive:
A ranked task inventory and a flow diagram for each priority journey, including error and edge states.
Business value:
Every screen has a reason to exist and a place in a journey that ends with an enquiry, booking or order.

Wireframes

Each priority flow is drawn as low-fidelity screens that fix what goes where, in what order and with what emphasis, without colour or decoration. The wireframes are linked into a clickable prototype so the flow can be walked through end to end on a phone or a desktop.

Why it matters:
Layout and hierarchy decisions are cheap to change on a wireframe and expensive to change in code. Removing the visual layer keeps the review on whether the screen works, not on whether people like the colour.
You receive:
Annotated wireframes for every key screen and a clickable prototype of each priority flow.
Business value:
The structure of the interface is agreed and tested before a rupee is spent on visual design or development.

Interface system

Once the wireframes hold up we design the visual layer as a system: typography, colour, spacing, buttons, forms, cards, tables, navigation, messages and every state each component can be in, documented with rules for how they combine. Your brand guidelines, where they exist, are the starting point.

Why it matters:
A system is what stops the fifth page looking and behaving differently from the first. It also lets developers build components once and reuse them, which is where most of the long-term saving lives.
You receive:
A documented interface system with component specifications, states, interaction rules and design files ready for build.
Business value:
Consistency is maintained by the system rather than by whoever happens to be designing that week.

Usability checks

At the wireframe stage and again on the visual design, we put the prototype in front of real users and ask them to complete the priority tasks while we watch, without helping. Where people hesitate, misread or fail, the design changes and the round is repeated until the tasks are completed cleanly.

Why it matters:
Testing before build is the difference between fixing a screen in an afternoon and fixing it in a development sprint after launch, once it has already cost enquiries.
You receive:
Findings from each testing round: task success, where users struggled, what was changed and why.
Business value:
The interface that goes to development has already been used successfully by the people it is for.

Responsive behaviour

We specify how every screen and component behaves on a phone, a tablet and a desktop, in that order of priority for most Indian audiences, including touch target sizes, what collapses, what stacks and what stays visible. Accessibility basics such as contrast, focus order and form labelling are built into the same specifications.

Why it matters:
Most of your customers will meet the interface on a mid-range phone over a variable connection. A design that is only checked on a large monitor fails the majority of the people who use it.
You receive:
Responsive and accessibility specifications per screen and component, with acceptance criteria the developer can test against.
Business value:
The interface works on the devices your customers actually own, not only on the one it was presented on.

What you will have at the end.

  • User research report: interviews, observed sessions and the tasks and frustrations that emerged, with anonymised quotes.
  • Task inventory: every job a customer, dealer or staff member comes to complete, ranked by frequency and value.
  • Task flow diagrams for each priority journey, showing every step, decision and error state.
  • Low-fidelity wireframes for every key screen, annotated with content priority and behaviour.
  • Clickable prototype used in usability sessions and handed to the developer as the reference build.
  • Usability test findings: what was observed, what failed, what changed as a result, per round.
  • Interface system: typography, colour, spacing, components, states and interaction rules, documented for build.
  • Responsive specifications: how each screen and component behaves at phone, tablet and desktop widths.
  • Accessibility notes: contrast, touch target sizes, focus order and labelling for forms and controls.
  • Developer hand-over pack: annotated screens, assets, component specifications and acceptance criteria.
  • An anonymised extract of a past task flow and wireframe set, shared at the audit so you can see the method first.

How it runs

The engagement, step by step.

  1. 1

    Discovery and research

    We agree the scope of the interface, who uses it and what it must achieve for the business. Then we interview users, watch them attempt real tasks on the current site or product, and review enquiry logs, support messages and analytics for the patterns behind the complaints.

    You provide:
    Time with the owner and the people who handle enquiries, access to analytics and support records, and introductions to a handful of customers or dealers.
    We produce:
    A scope note and a user research report with tasks, frustrations and user language.
    Done when:
    The decision-makers have read the research and agreed what the interface must let users do.
  2. 2

    Task inventory and flows

    We list every task users come to complete, rank them by frequency and value, and map the priority journeys step by step, including error states and the points where someone would normally reach for the phone.

    You provide:
    A review session to confirm the ranking and fill in business rules we could not observe.
    We produce:
    A ranked task inventory and flow diagrams for each priority journey.
    Done when:
    The priority flows are agreed and every step in each has an owner on your side.
  3. 3

    Wireframes and prototype

    We draw each priority flow as low-fidelity screens, fix content order and hierarchy, and link them into a clickable prototype that runs on a phone and a desktop. Content placeholders use the real language from research, not lorem ipsum.

    You provide:
    A review session and honest reactions to the structure, ignoring the absence of colour.
    We produce:
    Annotated wireframes and a clickable prototype of every priority flow.
    Done when:
    The structure of every key screen is agreed and the prototype walks end to end.
  4. 4

    First usability round

    We put the prototype in front of real users and ask them to complete the priority tasks while we observe without helping. Hesitations, misreadings and failures are recorded, the wireframes are revised, and the round is repeated where a task still fails.

    You provide:
    Access to five to eight users per round, drawn from customers, dealers or staff, and a quiet place or a video call to run the sessions.
    We produce:
    Usability findings per round and revised wireframes.
    Done when:
    Every priority task is completed by test users without prompting.
  5. 5

    Interface system and visual design

    We design the visual layer as a system, starting from your brand guidelines where they exist: typography, colour, spacing and every component with all of its states. The tested wireframes are then rendered in that system, screen by screen.

    You provide:
    Brand guidelines and assets, and a review session on the visual direction before it is applied everywhere.
    We produce:
    A documented interface system and high-fidelity designs of every key screen.
    Done when:
    The system is documented and every wireframed screen has a final design.
  6. 6

    Responsive, accessibility and second usability round

    We specify behaviour at phone, tablet and desktop widths, check contrast, touch targets, focus order and labelling, and run a second round of usability sessions on the high-fidelity prototype, on the devices your users actually own.

    You provide:
    Another small group of users, ideally including some on older phones and slower connections.
    We produce:
    Responsive and accessibility specifications, second-round findings and final revisions.
    Done when:
    The final designs pass the priority tasks on real devices with real users.
  7. 7

    Hand-over and build support

    We package annotated screens, assets, component specifications and acceptance criteria for your developer, whether that is Gully Sales, your team or an outside agency, walk them through it, and review the build against the design before launch.

    You provide:
    An introduction to the development team and a window for design review before go-live.
    We produce:
    A developer hand-over pack and a design review note on the build.
    Done when:
    The developer has everything needed and the built interface matches the tested design.

Ways to work with us

Design one journey, one product, or stay with us as your design partner.

New interface design

The full process for a new website, customer portal, dealer app or booking system, from user research to a developer hand-over pack and design review of the build.

Journey redesign

One or two priority flows on an existing product, such as checkout, enquiry, booking or dealer ordering, researched, redesigned and tested without touching the rest of the interface.

Interface system

For a product or site that has grown inconsistent: we consolidate what exists into a documented component system and rules, so every new page inherits the same behaviour.

Design partner

Ongoing UX and interface capacity alongside your internal or external developers, so new features are researched, wireframed and tested before they are built.

Why Gully Sales

What you are actually choosing when you choose us.

We design for the enquiry, not the portfolio.

Gully Sales builds sales and marketing systems for Indian SMBs. An interface is judged by whether a customer completes the task and your team receives a usable enquiry, not by how the screens look in a showcase.

Testing comes before taste.

Wireframes go in front of real users before anyone discusses colour. That order is deliberate: it keeps decisions about structure away from decisions about style, and it catches failures while they are still cheap to fix.

Indian users, Indian devices, Indian connections.

We test on mid-range phones over ordinary mobile data, with the people who will actually use the interface, because that is how the majority of your customers will meet it. Bilingual and low-literacy contexts are designed for, not discovered after launch.

Developers get a system, not a picture.

Every hand-over includes component specifications, states, responsive rules and acceptance criteria. A developer can build from it without guessing, and the tenth page behaves like the first.

It connects to the rest of your sales system.

The enquiry, booking or order the interface produces has to land somewhere useful. We design the hand-off into your CRM, WhatsApp or sales process as part of the flow, so a completed form becomes a followed-up lead.

Where it applies

The same service, in different businesses.

Industrial manufacturing

The situation:
A components manufacturer built a dealer portal for orders and stock checks, but dealers still phone the sales desk because the portal takes longer than a call.
How it applies:
Research with dealers on what they check and order most, task flows for those jobs, a redesigned ordering flow tested with dealers on their own phones.
Likely benefit:
Dealers can place a repeat order or check stock faster than they can dial, so the sales desk is freed for new business.

E-commerce and D2C

The situation:
A packaged foods brand gets traffic to product pages from ads and social, but a large share of visitors who add to cart never reach payment.
How it applies:
Journey redesign of product page to checkout: observed sessions, a simplified address and payment flow, clear delivery and return information at the point of doubt.
Likely benefit:
A checkout that answers the questions that were causing abandonment, tested before it goes live.

Healthcare

The situation:
A multi-specialty clinic offers online appointment booking, but patients abandon it and call the front desk, which is already overloaded.
How it applies:
Research with patients and front-desk staff, a booking flow that uses the language patients use for symptoms and doctors, and testing with older patients on their phones.
Likely benefit:
More appointments booked without a call, and a front desk that handles fewer avoidable enquiries.

Education

The situation:
A school group's admissions enquiry form asks for twenty fields up front and most parents leave after the second screen.
How it applies:
Task flow for the admissions enquiry, a staged form that asks only what is needed to respond, and an interface system reused across every campus site.
Likely benefit:
Parents complete the enquiry, the admissions team receives usable details, and every campus site behaves the same way.

Software and SaaS

The situation:
A billing software company sees trial sign-ups drop off before users create their first invoice, and support tickets show they cannot find where to start.
How it applies:
Research with recent trial users, a redesigned first-run flow that leads to the first invoice, and an interface system for the product's forms and tables.
Likely benefit:
New users reach the moment the product proves itself, and the product team has components to build every later feature from.

Hospitality

The situation:
A hotel's direct booking page loses guests to online travel agencies because room, rate and date selection is confusing on a phone.
How it applies:
A mobile-first booking flow with dates, rooms and inclusions in the order guests decide them, tested with travellers on real phones.
Likely benefit:
Guests who arrive from search or social can book directly with confidence, rather than leaving to a third-party site.

Professional services

The situation:
An accounting and compliance firm's website describes services in departmental terms, and visitors cannot work out which enquiry route fits their problem.
How it applies:
Task flows organised around the problems clients bring, an enquiry path that routes each problem to the right partner, and a consistent interface system across the site.
Likely benefit:
Prospects find their situation quickly and the firm receives enquiries that are already routed and qualified.

Proof

Work we can point to.

Kalessi Bathroom Tiles, e-commerce, Australia

The problem:
A bathroom tiles retailer needed an online store its customers could browse and buy from comfortably on any device, and visibility for it once built.
What we did:
Gully Sales designed a user-friendly, responsive ecommerce website, and supported it with content marketing and SEO strategy built around the right keywords.
The result:
The study reports improved user engagement and increased sales on the new e-commerce website, contributing to business expansion across territories in Australia, with higher search rankings and more organic traffic.
Read the case study

Houzeome, interior design studio, Bangalore

The problem:
An interior design studio needed a website that matched its brand and presented its work in a way prospective clients could explore and act on.
What we did:
Gully Sales designed and built a complete brand-aligned website for Houzeome, from visual identity through a fully custom Laravel site and production launch.
The result:
The study records a production-live custom site at houzeome.com, six portfolio projects each with its own detailed page and correctly cropped photography, and a working enquiry pipeline with automated email notifications.
Read the case study

Questions buyers ask

Before you enquire, the answers you will want.

What user testing is included?

Two rounds of moderated usability sessions are standard: one on the wireframe prototype and one on the high-fidelity designs. In each, five to eight real users drawn from your customers, dealers or staff attempt the priority tasks while we observe without helping. Failures are recorded, the design is revised and a task is retested until it is completed cleanly. Sessions run in person or over video, and on the devices your users actually own. More rounds or more user groups can be added where the interface serves very different audiences.

How long does the engagement take?

It depends on how many journeys and screens are in scope, how quickly we can reach users for research and testing, and how fast your side can review. A single booking or enquiry flow is a much shorter piece of work than a full dealer portal with several user types. We set a working schedule at the audit and revise it if the scope changes. We do not promise a fixed number of weeks, because access to users and decision time are usually what set the pace.

What inputs are required from us?

Time with the owner and the people who handle enquiries or orders, access to analytics and support records, brand guidelines and assets if they exist, and introductions to a small number of customers, dealers or staff for research and testing. Later you provide review sessions at each stage and an introduction to whoever will build the interface. The research, design and testing work is ours; your time goes into decisions and into opening the door to your users.

How is success measured?

During design, by task success in usability sessions: can real users complete the priority tasks without prompting. After launch, against the baseline recorded before work began: qualified conversion rate, form and checkout completion, lead quality, page speed on a phone, engagement and cost per conversion, plus the share of support contacts about navigation. We report over an agreed period and separate what the interface changed from what traffic, pricing or the offer changed.

What is excluded from scope?

Deciding what the website should contain and how it is organised is website strategy and information architecture, which comes before this service if you do not yet have it. Writing the final copy, building the interface in code, hosting and ongoing maintenance are separate services, as is testing live variations once the site is running. We can do several of these, but each is scoped and priced on its own so you can see what you are paying for.

Do we need a website strategy or information architecture first?

If you already know what the site or product must do, who it serves and how its content is organised, we start from there. If those questions are still open, we recommend settling them first, because interface design assumes the answers. At the audit we will tell you which position you are in. Where only small gaps exist, the discovery stage of this engagement can close them without a separate project.

Do you also build what you design?

We can, through our website design and development service, and many clients prefer one accountable partner. But this service is designed to hand over cleanly to any competent developer: the pack includes annotated screens, component specifications, responsive rules and acceptance criteria, and we review the build against the design before launch. If you already have a developer or an agency you trust, keep them; we will work alongside them.

Do you design portals and apps, or only websites?

Both. The method is the same whether the interface is a public website, a customer or dealer portal, an internal tool for your staff, a booking system or a mobile app. What changes is who we research and test with, and how many distinct user types the interface has to serve. Portals and apps usually carry more tasks and more states, which affects scope and pricing, and we set that out at the audit.

4 more questions

What is an interface system, and do we need one?

It is the documented set of components, styles, states and rules from which every screen is assembled: buttons, forms, tables, navigation, messages and so on, each defined once. You need one if your site or product will keep growing, if more than one person will ever design or build for it, or if it already behaves differently from page to page. For a small one-off flow, a lighter component set is enough and we say so.

Can you work within our existing brand guidelines?

Yes, and we prefer to. Brand guidelines give the interface system its typography, colour and tone; we extend them with the components, states and interaction rules that guidelines for print and logo rarely cover. Where the guidelines create a usability problem, such as a colour pair with too little contrast or type that is too small on a phone, we flag it, propose an adjustment and leave the decision with you.

Will the interface work for customers on cheaper phones and slow connections?

That is a design requirement from the start, not a check at the end. We specify phone behaviour first, keep touch targets large, limit heavy images and scripts in the design, and run at least part of each usability round on mid-range devices over mobile data. Final performance also depends on how the site is built and hosted, so the hand-over pack includes performance acceptance criteria for the developer.

What happens when users disagree with what the owner wants?

We show you the sessions. When a customer fails a task on a screen the owner liked, the recording usually settles the matter without argument. Where a business rule genuinely has to override user preference, for compliance or commercial reasons, we design the clearest possible version of that rule and test it again. The aim is not to win a debate but to ship an interface that the people who use it can actually use.

Talk to us

Book a free audit and bring the screens your customers struggle with.

The free audit is a working session about your interface, not a pitch. If what you actually need is a strategy first, a developer for finished designs or a fix to one form, we will say so and point you there.

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

Analytics, prototypes and customer details you share are treated as confidential, used only to prepare for the conversation and never disclosed outside Gully Sales.

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