A customer spreadsheet is a database with no rules, no history and one person allowed to edit it.

Early access

Customer Database Software in Nottinghamshire

Customer Database Software built, hosted and supported in the UK, serving Nottinghamshire including Nottingham, Mansfield and Newark-on-Trent. Set up around how your team actually sells, not the other way round.

Across Nottinghamshire we see the same problem in different clothes: plenty of customer information, but not in one place, and not in a form the whole team can act on.

Customer Database Software is how you stop relying on memory.

Almost every business starts with its customers in a spreadsheet, and for a while that is fine. Then the spreadsheet grows columns nobody understands, several copies appear, somebody sorts one column and not the others, and the question "which customers bought from us last year but not this year?" becomes an afternoon of work. CubeCRM turns that spreadsheet into a proper customer database: one record per customer with rules about what must be filled in, duplicates prevented, every change recorded, and the history of every conversation, quote and case attached. Segments and lists can be built from anything on the record in seconds, and the data stays in step with your accounts package.

  • 1

    Record per customer, duplicates prevented

  • Any

    Field can drive a segment or list

  • Every

    Change recorded, with who and when

What it does

Inside customer database software

The parts of CubeCRM that make up customer database. Everything here sits on the same customer record, so nothing needs re-keying between them.

  • From spreadsheet to database

    Your existing columns mapped to proper fields during import, with required fields, picklists and validation so the data stays clean from then on.

  • One record per customer

    Duplicates merged on import and prevented afterwards, so the same customer is not in the list three times with three phone numbers.

  • Custom fields as standard

    Add the fields your business needs - sector, size, account tier, equipment installed, renewal month - without paying for a higher edition.

  • Segments in seconds

    Build lists from any combination of fields and history - "customers in the Midlands with no contact in six months" - and save them for next time.

  • Every change recorded

    An audit trail of who changed what and when, so an overwritten phone number can be traced and put back.

  • In step with the accounts

    Customer details and invoiced revenue shared with Xero, Sage or QuickBooks, so the database and the ledger agree.

In practice

Problems this actually solves

Typical situations, anonymised. What businesses tell us before they change anything, and what changes afterwards.

  • Case 1

    The spreadsheet only one person could edit

    Before

    A trade supplier’s customer list was a large spreadsheet maintained by the office manager. Others had read-only copies, which were always slightly out of date, and her holidays meant a fortnight of changes waiting.

    With CubeCRM

    The spreadsheet became a CubeCRM database the whole team can update, with required fields and an audit trail. The office manager now reviews the data rather than being its only editor.

  • Case 2

    Lapsed customers nobody could list

    Before

    A wholesaler wanted to contact customers who had ordered the previous year but not this year. Producing the list meant cross-referencing the spreadsheet with an export from the accounts package.

    With CubeCRM

    With invoiced revenue synced from the accounts package, the lapsed-customer list is a saved segment that updates itself. A monthly call campaign now works through it.

  • Case 3

    Columns nobody understood

    Before

    A service company’s customer spreadsheet had grown to over sixty columns, several with names like "Status 2" and "Old ref". Nobody was sure which were still used.

    With CubeCRM

    Import was an opportunity to agree what each field meant. The useful twenty became proper fields with picklists, the rest were archived, and the data became trustworthy again.

Local coverage

Customer database across Nottinghamshire

Our Nottinghamshire coverage includes Nottingham, Mansfield, Newark-on-Trent, Worksop, Retford and Hucknall, and the NG1, NG2, NG3, NG4 and NG5 postcode districts. If you are in Nottinghamshire and not on that list, we almost certainly still cover you - ask.

Getting to you

61miles from our Olney office

Discovery and training can be done at your office - watching how enquiries really arrive and how the team really sells tells us more than any questionnaire.

Postcode districts

  • NG1
  • NG2
  • NG3
  • NG4
  • NG5
  • NG6
  • NG7
  • NG8
  • NG9
  • NG10
  • NG11
  • NG12
  • NG13
  • NG14
  • NG15
  • NG16
  • NG17
  • NG18
  • NG19
  • NG20
  • NG21
  • NG22
  • NG23
  • NG24
  • NG25

Areas we cover

Nottingham, Mansfield, Newark-on-Trent, Worksop, Retford, Hucknall, Kirkby in Ashfield and Arnold.

Customer database elsewhere in Nottinghamshire

How it happens

What getting started involves

The same process wherever you are, and for Nottinghamshire discovery and training can be done in person.

  1. 1

    Discovery

    A short, structured session on how enquiries arrive, how you quote, and where customer information lives now - the inboxes, the spreadsheet, the old CRM and the notebook in the car. We come back with what works as standard and what needs configuring.

  2. 2

    Setup

    Pipeline stages, fields, quote templates, email connection, teams and permissions set up to match how you sell - not a demo account with your logo dropped on it.

  3. 3

    Data import

    Contacts, companies, open opportunities and quote history brought across from spreadsheets, inboxes or your previous CRM, with duplicates merged. You check it against what you had before anybody switches over.

  4. 4

    Training & rollout

    Short, role-based training so the sales team learns the pipeline and the office learns enquiries and cases - in person where it helps. Guides and screen recordings left behind for new starters.

  5. 5

    Ongoing support

    UK support from the people who built the platform, with a named contact, agreed response times, and a product roadmap you can influence.

You might call it something else

If you searched for any of these, this is the page you wanted.

  • Customer database system
  • Customer records software
  • Client database
  • Customer list software
  • Single customer view

Questions

The things people ask first

  • We map your columns to CubeCRM fields during setup, clean and de-duplicate the data, and import it. You check the result against the spreadsheet before switching over.

  • Yes. Custom fields, including picklists, dates, numbers and checkboxes, are part of the standard product. Setup is a good time to decide which columns are still worth keeping.

  • Yes, at any time, in full and in open formats. Saved lists can also be exported to a spreadsheet when you need one.

  • Yes - it is a full CRM, with enquiries, pipeline, quotes, email sync and service cases on the same records. But plenty of businesses start by using it as a better customer database and add the rest later.

Working in Nottinghamshire?

Customer database for your Nottinghamshire business

Tell us what your current system does badly. We will tell you whether CubeCRM fixes it, and what it would take.