Apps · websites · interfaces · Edgware, London

Data you can read across the room.

Dateo Tech designs, builds, publishes and supports apps, websites and interfaces for organisations whose information has become hard to see. We turn rows and columns into screens people understand at a glance, and act on.

A spreadsheet is a store room. An interface is the shop floor. We build the shop floor.

Most organisations already have the data they need. It sits in spreadsheets, finance exports, booking systems and inboxes. What they lack is a way for the right person to see the right number at the right moment, without opening four tabs and doing arithmetic.

That is where we work: mobile apps for people on the move, web applications and dashboards for teams, public websites that explain things clearly, and the design work that makes all of them readable. Colour, shape and order do the heavy lifting; decoration stays out of the way.

What we make

Four moments we design for

Examples of the situations our products are built around. They are illustrative patterns, not client stories.

07:40

The shift starts

A supervisor opens an app on the way in. Before they reach the door they know which three jobs are late, who is off sick and what needs a decision. No login dance, no spreadsheet download, no scrolling past charts nobody asked for.

11:15

The question from upstairs

Someone senior asks how last month compared with the one before. The answer is one filter away, already in a chart that starts at zero, with a sentence underneath explaining what changed.

15:30

The customer checks in

A member of the public opens your website on a phone with a cracked screen. The booking status, the next step and the contact route are readable at arm’s length, and the form keeps their answers if the signal drops.

17:55

The weekly report

The export opens cleanly in Excel with sensible column names, consistent decimals and no merged cells. The person who used to spend Friday afternoon rebuilding it goes home on time.

Tool 1 · illustrative

The chart chooser

Answer three questions and get a sensible chart type, a live sketch, and the one chart to avoid. It is the same reasoning we use in design reviews.

1 · What are you trying to show?

2 · How many categories or points?

3 · Where will people see it?

Apps and web

Fewer numbers, better chosen

A good data product is mostly editing. Before we design a screen, we ask which decision it supports and which three figures that decision really needs. Everything else moves one tap away.

On mobile, that means a strong summary, large touch targets and charts that survive a five-inch screen. On the web, it means filters that remember themselves, exports that open cleanly in Excel, and tables that stay readable when someone zooms to 200 per cent.

  • Native or cross-platform mobile apps
  • Dashboards and reporting tools
  • Booking, ordering and membership flows
  • Integrations with the systems you already use
More on apps and web
Flat illustration of a phone, laptop and colourful notes (illustrative generated image)
Illustrative generated artwork.

Tool 2 · illustrative

Will it fit on one screen?

Dashboards fail when they try to answer every question at once. Enter how many metrics people are asking for and the planner suggests how to split them.

Interfaces with a point of view

Good interface design for data is opinionated. It decides that this number is the headline and that one is a footnote; that red means a problem and nothing else; that a chart starts at zero unless there is a stated reason not to.

Research

We sit with the people who use the numbers and watch where they get stuck.

Prototype

Clickable designs filled with realistic, anonymised sample data.

Design system

Colour roles, chart rules, table patterns, empty states and error wording.

Accessibility

Contrast checked, colour never the only signal, charts with text alternatives.

How we design interfaces

Publishing

Shipping is part of the job

  1. ListingStore copy and screenshots that show the product honestly.
  2. Privacy formsDeclarations that match what the app collects.
  3. ReviewSubmission, reviewer notes, and responses if rejected.
  4. ContentWebsite migration with redirects so links keep working.

How a project flows

Five stages, each producing something you can see. The width of each band is roughly how much of a typical project it takes; your project may differ.

LookData, people, current tools
ShapeJourneys and prototype
BuildFortnightly working builds
ShipTesting, release, store review
CareSupport and improvements

Band widths are an illustrative proportion, not a measured average. Read the full method and standards.

Tool 3

Colour contrast checker

Bright palettes are great until labels become unreadable. Check any text and background pair against WCAG 2.2 contrast thresholds.

Total this month

Illustrative label text at body size

    Support

    Looked after on weekdays

    After launch we fix defects, keep apps compatible with new iOS and Android releases, update dependencies and make small improvements. Requests are read Monday to Friday, 09:00–18:00 London time and prioritised by how many people are affected. We do not offer out-of-hours cover.

    Support and request form

    From the lab

    Quick answers

    Do you analyse our data for us?

    We design and build the tools that present it. We do not provide statistical consultancy, financial advice or audit services; your own specialists decide what the numbers mean.

    Can you work with our existing systems?

    Usually yes, through exports or APIs. We look first and tell you what is realistic.

    Will we own the code?

    Yes. Repositories, accounts and documentation sit in your name.

    How do we start?

    Use the contact page. A few paragraphs about the problem is plenty.

    Got a spreadsheet that is trying to be an app?

    Tell us about it