Skip to content
GullySales

Lighting designers · CRM

Keep one record of every project, proposal and contact, so no fee is forgotten.

A CRM for a lighting designer is a shared record of project teams, projects, fee proposals and the next step on each. GullySales sets up the fields, stages and views that suit a design studio, and works with whatever tool the studio can keep up.

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

Realistic editorial illustration of architecture firms at work in India

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.

Last updated 14 Nov 2026.

For lighting designers

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

  • “A proposal sits in an inbox”

    A fee proposal sent in an email is easy to lose among drawings and site notes. Without a record of the stage and the decision maker, nobody knows which proposal is waiting and who last spoke to the client.

  • “Contacts belong to people, not the studio”

    When a designer leaves or a principal travels, contacts go with them. A shared record keeps the history of every architect and interior designer with the studio, whoever made the first call.

  • “Project stage is the key field”

    The useful fact about a project is where it stands: concept, design development, tender or site. A record that shows stage lets the studio decide when to call, since the same message is wrong at a different stage.

  • “Crowded forms get ignored”

    A system with a long list of boxes goes unused. A studio benefits from few fields kept honestly: contact, project, stage, fee discussed, next step and date.

What we do

What we deliver for lighting designers.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Fields and stages set up for design work

    A short list of fields and project stages matched to how the studio actually works.

    Result: Every project in the record shows a stage and a next step.

  2. Contact import and clean-up

    Existing contacts gathered from phones, email and spreadsheets into one list, with duplicates removed.

    Result: The studio has a single list of project teams.

  3. Proposal tracker

    A view of every fee proposal with the decision maker, the date sent and the follow-up due.

    Result: The owner sees which proposals are waiting on a reply.

  4. Past-project history

    Each contact tied to the projects done together, so a call starts with what happened last time.

    Result: Nobody phones a past client without knowing the history.

  5. Short training for the team

    A walk-through for the people who will enter the data, with a one-page guide to keep.

    Result: Whoever enters data knows what goes in and when.

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.

Fields worth keeping

Keep these fields on every project and proposal.

Project stage
Set by the lead designer at each call. It decides what you say next and shows which projects are still open to ceiling design.
Space type and city
Entered at enquiry. It lets you find every hotel or museum job and send a relevant past project.
Contacts and their roles
Architect, interior designer, developer, owner, each a person record. It stops one enquiry from being logged as three.
Proposal sent date and fee scope
Entered by whoever sends it. It lets the studio see which proposals are waiting and what each one included.
Drawings received
A yes or no with file link, set by the coordinator. It shows whether the proposal rests on real drawings.
Reason won or lost
Chosen from a short list at close by the lead designer. It shows whether fee, timing or free layouts decided the outcome.

Who it is for

This is written for these lighting designers.

  • Independent architectural lighting design studios
  • Lighting design consultants attached to an architecture or interior practice
  • Hospitality and retail lighting specialists
  • Facade and landscape lighting designers
  • Museum, gallery and heritage lighting consultants
  • Residential lighting designers for premium homes
  • Lighting designers who also supply and commission fittings
  • Theatre, event and stage lighting designers moving into architecture

Before you decide

When this may not be the right fit.

  • You have not decided who updates the record after a site visit, so stages would drift out of date.
  • You hold your projects in a personal notebook and will not share it, so a studio CRM would be a second copy no one reads.
  • You want to import every old contact without cleaning, which would bury the live proposals under stale names.

Before you decide

Agree the work. Know how to judge it.

CRM for lighting designers: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from lighting designers. Anything missing is noted in the written scope, with who will supply it.

Every open fee proposal in one list
A list of live proposals with client, firm, date sent and last contact. A rough sheet is enough. Without it, the first import is empty and the team has no reason to open the record, so we would ask you to enter the live proposals by hand in the training session.
Contacts exported from phones and mail
Architects, interior designers and developers, from every device the studio uses. Exports can be messy. If contacts live only on one person's phone, tell us, since we need that person's agreement to move them, and we agree with you how to handle personal contacts that are not clients.
A named owner for the record
One person responsible for keeping the record true, not the principal unless the studio is one person. When nobody owns it, entries stop within weeks of the training and the proposals go back into the inbox, where the next stale fee proposal will sit unseen once more.
A decision about client confidentiality
State which client details, such as home addresses or fee levels, should be visible to which staff. Some studios hold a home project's details tightly. If unsettled, we set the strictest view, which may slow the team's work.
Scans or files of past project fees
Even a short history of earlier projects and fees helps us fill the past-project history. Without it, the record starts blank and cannot show which architects return, which space types repeat, or which earlier clients deserve a call when a new project begins.

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

    Walk through one project from first call

    We take a recent project and follow it with you from the first call to the signed fee proposal, writing each handover, document and decision. You bring the actual emails and the proposal file. What exists afterwards is the studio's real sales journey on one page, the base for every field and stage, and the place where we notice steps that happen only in someone's head, such as a verbal go-ahead on a site visit.

  2. 2

    Name the stages by project and fee

    From that journey we agree stages such as enquiry, site visit, concept discussion, fee proposal and appointed, and the project stage the building has reached. You approve the names, since the team must recognise them. The project stage becomes the key field.

  3. 3

    Set up the fields and the proposal tracker

    We build the record in the tool the studio can keep up: a project, its contacts, its fee, its next step and the date. You choose whether the tool is a spreadsheet, a simple CRM or the one you already own. A short field list keeps the forms from being ignored, and a proposal tracker shows fee, date sent, who it went to and the next step on one line.

  4. 4

    Clean and import the contact list

    We gather contacts from phones, mailboxes and old proposals, then join duplicates and attach each person to a firm. You tell us who not to contact. Contacts then belong to the studio, not to one designer's phone, and past projects are attached to the architects who brought them, so you can see at a glance which firms have sent the studio work before and which are new.

  5. 5

    Test with live enquiries and proposals

    Two or three open proposals are entered, and a few test enquiries sent through the form. You check that a proposal sitting in an inbox now shows with an owner and a next step. We correct fields that people find awkward before the whole team starts.

  6. 6

    Hand over, then read the open proposals

    We train the team in a short session and give the owner a view of all open proposals. Later, we compare the record with the figures noted at the start: proposals sent, proposals answered, appointments made. You decide which fields to keep, which to remove and who may see the fee column, so the record stays one the team actually opens.

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.

Which CRM tool should a small studio use?
One that the team will open each day. A well-kept spreadsheet works better than an unused system. We recommend a tool after seeing how many people enter data and from where.
Can we keep our client data private?
Yes. We set up access so that only people in the studio see the records, and we explain who holds the data. Follow the rules on personal data that apply to your business.
Will it connect to our email?
Several tools do, and it saves typing. We check what your chosen tool supports and set up only what the team will use.
What should we record about a past project?
The space type, the people involved, the fee scope and where the photographs sit. A few facts per project let you find a similar job the next time an architect asks, and they remain useful for years.
Can the CRM hold drawings and the fee proposal files?
It can link to them. We suggest keeping the drawings in the studio's file store and putting a link in the project record, since a CRM is poor at version control for drawings. The proposal itself can be attached, with its date and version. We set the links up so a proposal can be found from the record without opening the inbox.
What if only one person in the studio will use it?
Then we keep it small: one view of open proposals, one list of contacts and a date for each next step. A solo principal still forgets proposals. We do not build stages and permissions for a team that does not exist, and we leave room to add people when the studio grows.
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.

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.