Start right and make it stick

Data foundation

One trustworthy record per job, from the tools you already run.

Talk to us about this
  1. 01Audit
  2. 02Data foundation
  3. 03Training
  4. 04An owner on your team

Before AI can answer questions about your business, your data has to agree with itself. We connect your sources read-only and build one record per job or customer, with dated history, that reconciles against the systems it came from. Everything else we build stands on it.

Sound familiar?

  • The CRM, the accounting software and the job tool all disagree.
  • We can’t answer simple questions, like which jobs went over budget last year.
  • Customer names are spelled several different ways across systems.
  • Years of job history sit in old systems nobody can query.

What you get

What we hand over

  1. 01Read-only connections to your CRM, accounting, job and file systems
  2. 02One record per job or customer, with matching rules you agree
  3. 03Dated history, so you can see what a record looked like on any day
  4. 04Reconciliation checks that compare totals against each source
  5. 05A data dictionary in plain language: what each field means and where it came from
  6. 06A foundation your dashboards, assistants and drafts can read from

Works with what you run

Names only. We aren’t partners of any of them, and we start from what you already run.

  • Postgres
  • Supabase
  • BigQuery
  • QuickBooks Online
  • Xero
  • JobTread
  • HubSpot
  • Google Sheets

How it stays safe

Our principles, applied here

The same rules run through everything we build. How we work

  • Read-only by default. We copy from your systems and don’t change them.
  • Totals reconcile against the source, and any mismatch is reported, not smoothed over.
  • The database lives in your account and is documented so another developer could run it.

Before you hire us

When you don’t need this

We’d rather say it now than after you’ve paid for it.

  • If you run one main system that holds everything, its own reports may be enough. You don’t need a second copy.
  • If you only need one report, build the report. A full foundation pays off when several things will read from it.

Not sure which side of the line you’re on? Take the scorecard. It’s private, and nothing is sent unless you choose to send it.

Questions

Common questions

It can be, but usually it’s simpler: one database in your account with the records you actually use, kept up to date and checked.

No. It reads. If you later want fixes written back, that’s a separate permission you approve.

Related

Often paired with

See all services

Tell us what you run, and what this would need to do.

Five short steps. We’ll tell you honestly whether this is the right fit.

Start a project