Skip to content
04Applications

Your records, structured properly

The spreadsheet that became the business, rebuilt as a real database with screens for the people who use it. Validated, searchable, backed up and shared without breaking.

Get a quote
See the catalogue
Build time
4–20 weeks
Per project
Quoted
Schema and data
Yours
01Client Portals02Internal Dashboards03Inventory Systems04Custom Databases05Workflow Tools06Management Systems
Who it is for

You will knowif this is you.

01There is a spreadsheet nobody is allowed to touch because the business runs on it.
02The same customer, property or asset is typed into three systems and spelt three ways.
03Two people edit at once and one of them loses their work.
04You need to prove who changed a record and when, and cannot.
What it does

Everything the systemtakes off your desk.

Each capability is built to your process and shipped with its own controls. Nothing generic is bolted on.

01

Structure

Tables that match the real things: customers, sites, assets, jobs, certificates. Linked, not copied.

  • Records linked by relationship
  • Required fields and formats
  • Drop-downs instead of free text
  • Calculated fields
02

Screens for real people

Forms and lists built for the person doing the work, not the person who built the sheet.

  • List, detail and edit views
  • Role-based screens
  • Bulk edit
  • Mobile entry in the field
03

Search and reporting

Find anything in a second and answer the questions the spreadsheet never could.

  • Full-text search
  • Saved filters
  • Reports and exports
  • Dashboards on the same data
04

Access control

Who sees which records and which fields. Down to the column if needed.

  • Roles and permissions
  • Row-level rules
  • Field-level visibility
  • Read-only shares for outsiders
05

History and audit

Every change recorded. Nothing overwritten in silence.

  • Change log per record
  • Who, when, from what to what
  • Restore a previous value
  • Retention rules
06

Import, export and integration

Your existing data comes in cleanly and stays reachable from other tools.

  • Mapped imports with preview
  • Deduplication on import
  • CSV and Excel export
  • API and webhooks
From sheet to system

What changesand what does not.

The data is the same. What changes is that it can only be entered one way, seen by the right people and never lost.

01The modelWe map what the spreadsheet actually holds: usually five or six real things pretending to be one grid. Each becomes a table with its own rules.
02The rulesA postcode is a postcode, a date is a date, a customer exists once. Bad data cannot be entered, so it does not have to be cleaned.
03The screensOne per job to be done: the engineer's entry form, the office's list, the manager's report. Nobody sees the raw grid again.
04The historyEvery edit is a row in a log. The question 'who changed this' has an answer.
05The connectionsAn API and exports, so the database feeds the website, the invoices and the dashboard instead of being retyped into them.
Scope and timeline

Sized to the job,quoted per project.

Three sizes from the catalogue's application tiers. The size follows how many real things the spreadsheet was hiding.

01

Single-purpose database

Quoted

4–6 weeks

  • One data model
  • Entry and list screens
  • Validation rules
  • Search and export
  • Import of existing data
  • Cloud hosting
Get a quote
02Most popular

Business database

Quoted

8–12 weeks

  • Several linked models
  • Role-based access
  • Change history and audit
  • Reports and dashboards
  • Document attachments
  • API access
Get a quote
03

Advanced data system

Quoted

12–20 weeks

  • Complex relationships and rules
  • Field-level permissions
  • Workflow on record changes
  • Integrations with existing systems
  • Offline entry
  • Custom reporting engine
Get a quote

Timelines are the ones in the catalogue. The quote fixes the scope, the price and the delivery date before work starts.

Built on the platform

Built on the samedatabase as the platform.

Quooro runs on PostgreSQL with row-level security on every table. A custom database gets the same engine, the same access model and the same backups, and can appear inside the customer's Lounge as its own module.

  • The CRM

    Contacts, companies and a mapped import engine, already in the Lounge. Often the database you need is a CRM with your fields.

  • Quooro Office

    Sheets for the calculations that belong in a spreadsheet, linked to the records that do not.

  • Ownership

    The schema and the data are yours, exportable at any time.

What you own

Yours outright, on the day it launches.

  • The database schema, the application code and the import scripts
  • A data dictionary: every table, field and rule in plain English
  • Your data, imported, deduplicated and exportable at any time
  • Training for the people who enter data and the person who owns it
  • A support period written into the quote

The same terms as every build: read ownership and handover.

How it is built

Four stages, no surprises.

Whole buildSet in your proposal

01

Discover

Starts when you say go

We map how the work gets done today.

What happens

  • Workshops with the people who will use it
  • Your current process mapped, step by step
  • Your data and the systems it lives in audited
  • A written specification of what to build first

What you get

  • The specification
  • A staged plan and a fixed quote

What we need from you

  • Time with the team who do the work
  • Access to the tools you use now
02

Design

After you approve the specification

A clickable prototype before a line of code is written.

What happens

  • Screens and user journeys for each role
  • A clickable prototype the team can try
  • The data model and the integrations agreed
  • Permissions: who can see and change what

What you get

  • The prototype
  • The agreed data model

What we need from you

  • Feedback from real users
  • Sign-off on the prototype
03

Build

After you approve the prototype

Built in stages, with a working demo at the end of each.

What happens

  • Features built in the agreed order
  • A working demo at the end of every stage
  • Your existing data moved across and checked
  • Tested against the real process, not a script

What you get

  • A working system at each stage
  • A test environment to try it in

What we need from you

  • Testing time from your team
  • Decisions when questions come up
04

Launch

After you approve the finished build

Rolled out, taught and supported.

What happens

  • Rolled out to the team, in stages if that suits
  • Training for each role
  • Documentation for how it works and how to run it
  • Support after go-live, with a retainer if you want one

What you get

  • The live system
  • Full ownership of the code and data

What we need from you

  • A go-live date that works for the business
Straight answers

Asked beforeyou ask.

01Is this just Airtable or Notion?Those are good tools for a team that will build and maintain its own. This is for a business that wants the structure designed, the rules enforced and the screens built for its people, and to own the result.
02Can we keep using Excel?For analysis, yes: export any view. For entry, the point is to stop. Data typed into a sheet cannot be validated, and that is where the errors come from.
03How does our old data come in?Through a mapped import: you see each column matched to a field, the duplicates it found and the rows it would reject, before anything is written.
04Who owns the data?You do, always. It is exportable in full at any time, and the schema comes with the handover.

Retire the sheetnobody may touch.

Send us the spreadsheet, or a description of it. We will tell you what it is really holding and what a proper system for it costs.

Get a quote
Talk it through first
03 · PreviousInventory Systems05 · NextWorkflow Tools