Software & IT consultancy · London EC2Write to us
Data ConsultancyConsidered software · clear advice
Software development & IT consultancy

Clear numbers. Considered software.

We help British organisations turn tangled spreadsheets and half-connected systems into software that people trust, and we give plain, independent advice on the technology decisions in between.

Illustrative still life of hand-drawn charts, a brass compass and claret ink on rose paper
Illustrative plate, generated for this site.
Reading oneStart with the decision, then find the data that informs it. Not the other way round.
Reading twoSoftware should fit the way good people already work, and quietly remove the friction.
Reading threeAdvice is only useful if it is independent, written down and easy to check.
Premise

Most data problems are decisions in disguise.

A finance lead says the monthly figures take four days to compile. An operations manager says nobody trusts the stock count. A director asks whether to buy a new system or extend the old one. Each of these sounds like a technology problem. Underneath, each is about a decision someone needs to make with confidence, and about information that arrives too late, too messy or too doubtful to support it.

Data Consultancy Ltd works at that junction. We build software where software is the answer: tools to capture information cleanly, combine it from different places and present it to the people who act on it. We give advice where advice is the answer: on systems, suppliers, architecture and the order in which to do things. Often a project uses both.

We are deliberately modest about what we claim. We do not run data centres, we do not offer round-the-clock operations, and we do not hold certifications we have not earned. What we offer is careful analytical thinking, well-made software and honest written advice.

Two practices

One builds. One advises. Both listen first.

i.

Software development

Business software designed around how your organisation actually works: internal tools, data entry and validation, reporting views, integrations between systems you already use, and careful migrations away from overloaded spreadsheets.

  • Internal web applications and workflow tools
  • Data capture with validation at source
  • Reporting and dashboards for decision makers
  • Connecting systems through their available interfaces
  • Migration from spreadsheets with reconciliation
Read the development practice
ii.

IT consultancy

Independent advice for organisations facing a technology choice they cannot easily reverse. We do not sell products or take commission from vendors, so our recommendations depend only on your circumstances.

  • Systems and data landscape reviews
  • Build, buy or configure assessments
  • Supplier and proposal scrutiny
  • Data handling and access reviews
  • Technology roadmaps sized to your budget
Read the consultancy practice
Situations we recognise

If any of these sound familiar…

The month-end report takes daysUsually the data exists but lives in several places with different definitions. We trace each figure to its source, agree definitions with the people who own them, then automate the assembly so the report becomes a check rather than a construction.
Two systems disagree about the same customerWe identify which system should be authoritative for which fields, design a reconciliation, and build or configure the link so the disagreement stops recurring.
A critical spreadsheet has one guardianWe document its rules with that person, then decide together whether to stabilise it, move it to a shared database, or replace it with a small application.
A supplier proposal looks expensive, or vagueWe read it, ask the questions you may not know to ask, and write a short assessment of scope, risks, lock-in and what is missing.
Nobody is sure who can see whatWe map where information is held and who has access, highlight obvious gaps and suggest proportionate fixes. We do not provide legal sign-off; that remains with your advisers.
Method

Four movements, each with a written result.

Survey

Interviews, a look at the systems and files involved, and a map of how information flows today. Result: a short findings note with the problem stated precisely.

Model

Agree definitions, decide what is authoritative, sketch the target and weigh the options. Result: a recommendation with costs and trade-offs.

Make

Build or configure in short increments, reconciling against the old way so numbers can be trusted. Result: working software and test evidence.

Settle

Train the people who use it, hand over documentation, and review after a few weeks of real use. Result: a system someone else can maintain.

The method in detail

Inputs & outputs

What we ask for, and what we hand back.

From you

Time with the right people
The person who owns the decision and the people who handle the data day to day.
Sight of the current process
Screens, file structures and descriptions; real data only where needed and through an agreed secure route.
Clarity on constraints
Budget, deadlines, policies and anything already promised to others.

From us

Written findings
Plain English, with evidence and a clear recommendation.
Software you own
Code, configuration and accounts held by your organisation.
Definitions and documentation
A data dictionary, run instructions and the reasoning behind key choices.
Try an instrument

Is your spreadsheet asking to be software?

Instrument I Illustrative

Spreadsheet pressure check

Eight questions about a spreadsheet your organisation depends on. The index estimates how strongly it is pushing towards a proper system. You only answer about the file; you never upload it.

Do several people edit the same file at the same time?
Does only one person fully understand how it works?
Is data copied by hand between files or systems each week?
Have errors in it caused real cost or embarrassment?
Would you need to know who changed a value, and when?
Is the underlying process still changing month to month?
Does it hold personal information about customers or staff?
Are the same reports rebuilt by hand every period?

Two more instruments, a build-buy-configure weighing and a column header audit, are on the instruments page.

Delivery standards

The canon we work to.

  1. Numbers reconcile. Any figure our software produces can be traced to its source and checked against the old method during transition.
  2. Definitions are written. "Active customer" or "net margin" means one agreed thing, recorded in a data dictionary.
  3. Least data necessary. We design for minimal personal data and limited access, and we do not copy client data to our own machines without agreement.
  4. Independent advice. No vendor commissions. If we recommend a product, we explain why and disclose any relationship.
  5. Reviewed code. Changes are tested and reviewed before release, and releases can be reversed.
  6. Accessible interfaces. Keyboard support, readable contrast and labelled forms in everything we build.
  7. Plain documentation. Written for the next person, not for us.
  8. Honest scope. Ranges, assumptions and exclusions stated before work starts.
Limits

What we will not pretend to be.

Precision applies to claims as much as to code. These lines keep us honest.

  • A hosting providerWe can advise on and set up hosting with established providers. We do not run our own data centre.
  • A 24-hour operations deskSupport is offered within agreed working hours, Monday to Friday.
  • Your legal or compliance adviserWe help put sensible data practices into systems; formal legal opinions come from qualified advisers.
  • An accountancy firmWe build tools that handle financial data; we do not give accounting or tax advice.
  • A resellerWe do not earn commission from software we recommend.
Illustrative architectural detail of a London building at dusk in claret and saffron tones
Illustrative plate, generated for this site.
Where we are

Registered in Shoreditch. Working wherever you are.

Most engagements combine remote working sessions with occasional in-person workshops at your premises. Correspondence is answered Monday to Friday, 09:00 to 18:00 London time.

Map placeholder

Flat 8, 7 Leonard Street, London, United Kingdom, EC2A 4AN

This is the company's registered office as recorded at Companies House. It is a legal address, not a public office, so there is no pin and no walk-in reception. Meetings are arranged by appointment, often remotely.

Search on OpenStreetMap
Questions

Asked before most first meetings.

Do you only work with large organisations?

No. Much of our thinking suits small and medium-sized organisations, where a single well-built tool can change how a whole team works.

Will you need access to our data?

Not at the start. Early work relies on conversations and structure. If we later need to see data, we agree the minimum necessary and a secure route, under a written agreement.

Can you work with our existing developers?

Yes. We can advise alongside them, review their work, or take on a defined piece of development.

How is work priced?

Advisory work is usually a fixed fee for a defined review. Development is estimated in ranges per phase, narrowed as the work becomes clearer.

Bring us the question behind the spreadsheet.

Describe what you are trying to decide or improve. We reply within two working days with an honest view of whether and how we can help.