Skip to content
GullySales
Tell us what you need

AR, VR and XR development studios · CRM

Record which device a buyer tried, and the next step that was agreed.

A CRM for an immersive studio is the record of every buyer, demo and pilot, with the device and date attached. GullySales sets up the fields, stages and views so a demo does not vanish into a founder's phone.

Tell us what you needor call +91 80958 58589

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

A developer helping a colleague test a virtual reality experience

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Also for AR, VR and XR development studios

Sales and marketing for AR, VR and XR development studios, the overview.

Last updated 22 Oct 2026.

For AR, VR and XR development studios

Where it usually goes wrong, and what we would do.

  • “Demos happen on devices and in places”

    A demo at an expo, a gallery or a college leaves no trace unless someone writes down the device, the scene shown and the reaction. The CRM should hold those details so the follow-up refers to them.

  • “Agencies and clients are two records”

    An agency brings a client's brief. If the studio records only the agency, the end client's name, the launch date and the agency's repeat history are lost.

  • “Pilot to project is a long stage”

    A pilot ends, the buyer talks to a committee and nothing is heard for a while. A CRM stage with an owner and a next date stops the lead from fading.

  • “Founders hold the relationships”

    If the studio's founder keeps contacts in a phone, a sick day or a departure takes them away. A shared record protects the relationship.

What we do

What we deliver for AR, VR and XR development studios.

Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.

  1. Fields that matter

    Device tried, scene shown, use, venue, budget holder, launch date and consent status for each contact.

    Result: A record shows the buyer, the use and the next date at a glance.

  2. Stage design

    Stages from enquiry to demo, pilot, project and repeat, each with a rule for moving in and out.

    Result: Everyone knows where a lead stands.

  3. Agency and end-client linking

    A way to link an agency record to each client it brings, with dates.

    Result: Repeat sources are visible.

  4. Next-step discipline

    A rule that each open lead carries a dated next step and an owner.

    Result: Leads without a next step are listed for review.

  5. Import of existing contacts

    Contacts from phones, spreadsheets and email cleaned and loaded with source noted.

    Result: Past enquiries sit in one place.

  6. Consent and permission notes

    A field for what a client allowed the studio to show.

    Result: The sales team sees what is cleared before sending a sample.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

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

Read the full CRM implementation and customisation page

Fields worth keeping

Keep the fields that tell you what was tried and what was agreed.

Device used in the demo
Filled by whoever ran the session. It shows whether the buyer saw the experience on the model they own, which decides the next conversation.
Agency and end client
Two linked records entered by the founder. They stop you contacting a brand directly when its agency owns the relationship.
Pilot scope in one line
Written after the call. It lets anyone on the team see what was offered without opening the proposal.
Decision owner and trial user
Two names kept apart. The person who tried the demo is rarely the one who signs, and the record should show both.
Permission to share the work
A yes or no with the date, set by whoever handles the client. It controls whether a clip or build can appear on a post or page.

Who it is for

This is written for these AR, VR and XR development studios.

  • Property developers and real estate marketing teams
  • Brand and advertising agencies running launches
  • Schools, colleges and ed-tech companies
  • Corporate training and skilling teams
  • Museums, tourism boards and heritage bodies
  • Retail and showroom brands with a product to place at home
  • Industrial and manufacturing firms needing equipment walkthroughs
  • Event and exhibition organisers

Not for

It is not the right fit if.

  • Every relationship sits with one founder who handles each call, so a shared record would hold nothing the founder does not already know
  • You have not yet agreed a way to tell a pilot from a project, and fields cannot define stages you have not decided
  • Your team will not log a demo after it ends, so the system would show last year's picture of this year's buyers

How it works

How the CRM 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

    Map the sales process

    We sit with the people who sell and write down how a deal moves from enquiry to payment, including where it stalls.

  2. 2

    Agree stages, fields and owners

    Each stage gets a name your team already uses and a proof that the deal has left it. We agree which fields are required at which stage, and who may change what.

  3. 3

    Build on a copy

    Pipeline, fields and views are built on a trial copy where the CRM offers one, or in a separate pipeline where the plan allows. Live work stays untouched.

  4. 4

    Connect channels, then switch on automations

    Channels are connected first. Each automation is then switched on separately, so a misfiring rule is easy to find.

  5. 5

    Test with real deals

    The people who will use the CRM run open deals through it. Gaps are fixed before the whole team switches over.

  6. 6

    Switch over and trim

    Once real use shows which fields stay empty and which stages nobody uses, those are cut and the handover record is updated.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  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

    Sales process design

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

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    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.

Tell us what you need
Which CRM should a small studio use?
Choose one the team will actually open. GullySales looks at your size, your devices for entry and your budget before recommending, and sets up the fields, not just the tool.
Can the CRM store the demo files?
Link the files rather than store heavy builds in the CRM. Keep the demo library in a shared drive and attach the link to the record, with the version and device noted.
Who should own the data?
The studio owns it. Agree who may export, edit and delete, and keep a record of changes. Personal data rules apply to buyer details, so check with your own adviser on consent.
Should the CRM store the build files of a demo?
Keep the link and the version, not the files. The reason is that builds are large and change with every fix, and the record only needs to tell a colleague which build the buyer saw and on which device.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

More for AR, VR and XR development studios

Everything else we would do for you.

Closest to this: leads and follow-up

Also for AR, VR and XR development studios

Or start from the overview: sales and marketing for AR, VR and XR development studios.

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.

Tell us what you need