Who this is for
Analytics lead with a clear spec for a few reporting tables and no spare engineering time.
The spec is written and agreed, the tables are not built, and last time a hurried build gave numbers that did not match finance.
The result
Up to three reporting tables are built as tested models or views from your written spec in a pull request, each reconciling to control totals you sign off, with tests for keys, nulls and joins. Your team reviews and merges, and we touch nothing in production.
What is included
- Up to three tables defined in a written spec you supply
- dbt models or SQL views with tests for unique keys, not-null columns and join fan-out
- Reconciliation of each table to control totals you supply
- Work on a masked read-only clone and a private branch
- A pull request, short documentation and run steps
You receive
- The pull request with models or views
- The tests
- The reconciliation table against your control totals
- Short documentation of each table
- Run steps
What is not included
- Deciding what a number should mean
- Access to production data or deployment
- More than three tables without a larger quote
- Dashboards
- Personal data columns
What we need from you first
- The three tables in a sentence each
- The tool that holds the data (dbt, plain SQL) and how big it is
- No real records, personal data or credentials in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- Each table reconciles to the control total you supply, within the tolerance you set in writing.
- Tests for unique keys, not-null columns and join fan-out exist for every table and pass on the clone.
- Three input rows that you change on a second snapshot, without telling us which, move each table by an amount you compute yourself.
- The pull request touches only the agreed model paths.
Your named person signs the control totals and your reviewer merges the pull request. Payment follows sign-off.
When we would stop or decline
- The spec is disputed or changes during the build
- No control totals exist to check against
- Only production data is available
- Personal columns cannot be masked
Questions
Who decides what the numbers mean?
Your stakeholders, in the spec. We build to it and prove it against your totals.
Do you deploy the models?
No. Your team reviews and merges the pull request.
What if the totals do not reconcile?
The table is reported as failed with the difference, and that table's share of the price is not due.
Price and terms
From £695 · untested offer price. The fixed price is set in the written quote. Nothing is charged before you agree it, and payment follows your sign-off that the control totals reconcile.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.