Skip to content
GullySales

Mobile website experience · Marketing

Your buyers should be able to read, compare, and enquire from their phones.

A dealer opens your product page from a WhatsApp message while visiting a customer. The specifications are too small to read, and the enquiry button disappears below a large banner. Your sales team never hears from them.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A developer testing a mobile website beside a performance report

In one paragraph

Mobile website experience covers how easily someone can read a website, move between pages, and make an enquiry on a phone. GullySales tests your key pages on real handsets, fixes awkward layouts and slow-loading elements, and checks that calls, WhatsApp links, and forms work without making the buyer struggle.

Patients and showroom visitors face the same problem. A website that fits a small screen still fails when its menu is awkward or its form needs too much typing.

GullySales improves the existing mobile journey, from the page buyers land on to the enquiry your team receives. The work starts with your requirements brief, followed by a conversation and a written scope, fee, and term.

Who it is for

This is written for you if these sound familiar.

  • Manufacturers and distributors whose buyers open product links on phones
  • Dealers and showrooms receiving visitors from Google Maps
  • Clinics and hospitals where patients need a phone number or appointment enquiry
  • Restaurants, salons, and local services with phone-based enquiries
  • Owners whose mobile traffic produces fewer enquiries than desktop traffic
  • Established websites with cramped menus or forms that are difficult to complete

Not for

It is not the right fit if.

  • Your records show that almost all relevant buyers use desktop, and the phone journey has no material faults. Check the evidence before spending.
  • You need an app with functions beyond a website. App development is separate work.
  • You need a new website structure and design throughout. A website redesign should be scoped rather than hidden inside mobile fixes.

The problem

Does this sound like your business?

Common situations this work addresses.

  • “People look at products but never enquire”

    The contact button sits far below the product details, or the number cannot be tapped. Buyers should not need to copy a phone number into another app.

  • “The page is blank on mobile data”

    Heavy images and scripts delay the content the buyer came to read. A page that opens quickly on office Wi-Fi needs a separate check on a normal phone connection.

  • “The button moves when I tap it”

    Late-loading images or banners push the page down as the buyer reaches for a link. Reserving their space keeps the layout steady.

  • “The form feels like paperwork”

    Long dropdowns and unnecessary fields turn a short enquiry into a typing task. But removing every question leaves sales with too little information to respond.

Choose the right scope

Start with the work your business needs.

  1. Product enquiry journey

    For manufacturers and dealers sharing catalogue links with buyers. Focus on readable specifications and a reachable enquiry action, with the product named in the opening WhatsApp message so sales knows what prompted the contact.

  2. Local call and visit journey

    For clinics, showrooms, and local services receiving phone visitors from Maps or search. Prioritise the contact number and the information someone needs before calling or visiting, without covering the page with contact buttons.

  3. Existing mobile-page repair

    For a site whose desktop pages work but phone visitors struggle. Address broken layouts and loading problems on the agreed pages while retaining the existing site; wider performance work remains separate if the cause extends beyond this scope.

What we do

The work we can include.

Each deliverable and the purpose it serves. Your written scope confirms what is included, who is responsible, and what it costs.

  1. Mobile findings record

    A written record of faults on agreed pages, checked on a mid-range Android and an iPhone. You can see the affected page and what needs changing, with Google's field data included where available.

  2. Phone layout changes

    Adjusted text sizes, spacing, and content order on the agreed pages. Review the changed layouts on a phone before approval, including any call bar that stays on screen.

  3. Call and WhatsApp links

    Tappable phone numbers and WhatsApp links with an agreed opening message, such as the product being viewed. Test each destination against the number your team actually answers.

  4. Button and link spacing

    Tap targets separated so a fingertip reaches the intended action. Checks cover nearby links and buttons that overlap content or notices.

  5. Mobile page-weight fixes

    Lighter images and agreed changes to scripts, sliders, or autoplay video that delay the page. Before-and-after checks use the same handsets, with any remaining limits recorded.

  6. Mobile menu

    A shorter route to the pages buyers need, with catalogue search where the site requires it. Your team checks that important product and service information remains reachable.

  7. Short enquiry forms

    Forms with agreed essential fields, suitable phone keyboards, and autofill support. A test enquiry checks that the confirmation appears and the details reach the intended recipient.

  8. Mobile action tracking

    Separate events for call taps, WhatsApp taps, and completed form submissions from phone visitors. Test events confirm that each action is recorded without treating a tap as a completed conversation.

How the result is measured

  • Mobile load time and visible layout movement
  • Form completion and confirmed form delivery from phones
  • Call taps and WhatsApp taps, separate from confirmed enquiries
  • Mobile enquiry rate compared with the recorded baseline and desktop
  • Qualified opportunities and completed orders traced through your sales records, where available
  • Reply time and cost per order where source and sales records support the comparison

Recorded as a baseline before work starts, so every later report has an honest comparison.

Marketing and sales together

Your sales team receives the enquiry with its context.

Your sales lead confirms which number receives calls and WhatsApp messages, and who checks form enquiries. Product-specific opening messages carry the page context into WhatsApp, while test forms verify the receiving inbox. At handover, the team receives the contact-path record and an explanation of the tracked events. Call taps are not answered calls, and chat opens are not qualified opportunities; your sales records supply those outcomes.

Decisions to make before the work starts

  1. Website access and code limits

    Implementation depends on access to the existing website and permission to change its theme or code. Restrictions from a site builder or third-party widget may limit a fix; replacements or a rebuild require separate agreement.

  2. Contact ownership and content approval

    You supply the correct receiving numbers and approve essential form fields. Clinics and other regulated organisations must have their own compliance reviewer approve relevant content and enquiry wording before release.

  3. Page coverage and separate services

    The scope names the page types and enquiry paths covered. New website builds, ongoing conversion testing, and checkout optimisation are separate services, as are broader analytics setup or WhatsApp automation.

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

Website speed and performance optimisation
Choose website speed and performance optimisation when pages load slowly on mobile data and the cause is images, scripts or page delivery. Choose mobile website experience when pages load but buyers struggle to read, tap, call or complete a form on a phone.
UI/UX design
Choose UI/UX design when screens are not built yet and you want the buyer journey designed and tested as a prototype first. Choose mobile website experience when the website is live and its phone layout, menu, links and forms need testing and repair.
Website and user experience auditing
Choose website and user experience auditing when you want a ranked written report across phone and laptop before deciding what to fix. Choose mobile website experience when the phone is where buyers meet your website and you want those faults repaired, not only recorded.

A sample of the output

A phone test sheet records what a buyer meets on each key page.

This sheet comes from testing on real handsets. Each row is one page, the task a buyer tries on it, what went wrong, and the repair agreed with you.

Illustrative example, not client data. Yours is built from your own records.
PageBuyer task on a phoneWhat was foundRepair agreed
Home pageOpen the menu and reach a product listMenu links sit too close together and are tapped by mistakeIncrease spacing and enlarge tap areas
Product pageCompare two items and read the specificationSpecification table runs off the screen edgeRestack the table into readable blocks
Contact pageTap the number to place a callNumber is plain text and does not open the diallerReplace with a tap-to-call link
Enquiry formFill in and send a requestKeyboard hides the submit button on some handsetsShorten the form and reposition the button
Chat linkOpen a WhatsApp conversationLink opens with an empty messageAdd a prepared opening line with the page name

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

A short list of pages that matter
Testing covers the pages where buyers decide, so your team should name them. A list of key products or services is acceptable. Without it, time is spent on pages few people reach and the pages that bring enquiries are checked last.
Knowledge of the phones your buyers use
Real handsets are chosen to match your audience. Any evidence is acceptable, such as analytics reports or what your sales team sees on calls. When there is none, a common spread of screen sizes is tested and the limits are stated.
Who answers calls and WhatsApp
Call and chat links only work if someone picks up. Name the people and the numbers that should appear on the website. If the contact route is unowned, links are tested technically but buyers still meet silence.
Permission to change live layouts
Phone fixes touch templates that also affect desktop pages. A named person must approve changes before release. Where approval is slow or unclear, repairs wait in a staging copy and buyers keep meeting the same faults.
The current enquiry form fields
The form is part of the phone journey, so its fields must be known and open to change. A list with reasons for each field is acceptable. If every field is fixed by another system, the form is tested but not shortened.

How it works

How the mobile website experience work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Page and enquiry-path agreement

    We review available device data with you and agree which pages matter commercially. Your team confirms the contact destinations and the baseline enquiry records available.

  2. 2

    Fault review and priorities

    Real-phone testing identifies where reading or enquiry attempts break down. You approve the fixes, including any proposed removal of a banner, widget, or form field.

  3. 3

    Layout and content approval

    You review the proposed phone layout before implementation. Product details and other decision-making content are checked so the smaller screen does not become an incomplete version of the site.

  4. 4

    Implementation and phone testing

    We apply the approved changes and repeat the buyer journey on the agreed handsets. Your enquiry recipient checks test messages, while desktop pages are checked for unintended changes.

  5. 5

    Release and measurement handover

    After approval, the changes go live with a record of what changed and any unresolved limits. Reporting compares mobile actions and confirmed enquiries against the baseline at the interval agreed in writing.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

My website is already responsive. Do I still need this?
Only if the phone journey has problems worth fixing. Responsive layouts fit the screen, but buttons can still overlap and forms can still fail. We check actual use rather than recommend work because the site is old.
Will you change the whole design?
No, this scope focuses on the agreed mobile pages and enquiry paths. Your logo and brand colours stay, although spacing and page layout may change. A full redesign is quoted separately if local fixes cannot address the problem.
Which phones will you test on?
Testing includes a mid-range Android and an iPhone on mobile data. Available analytics inform the device choices. The agreed scope records which pages and handsets are covered, rather than promising every possible combination.
Does the WhatsApp button include automatic replies?
No. It opens a chat to your agreed number with a prepared message. Automated replies, conversation routing, and CRM connections belong to separate WhatsApp work.
Will a faster mobile page bring more sales?
It removes a barrier, but it does not guarantee orders. Price, availability, and your team's response still affect the sale. We separate phone actions from qualified enquiries so extra taps are not presented as revenue.
How do you decide the fee?
The fee follows your requirements brief and a conversation about the site. Page coverage and restrictions in the existing code affect the work. The written proposal separates GullySales time, any media spend, and production costs, and states the term before work starts.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.