unsoup [email protected]

What touches your stack. What never does.

The engagement, step by step — including the parts you can check yourself.

  1. Connect, read-only. You grant read-only API credentials to the systems in scope — CRM, billing, marketing, warehouse. HubSpot is built today; further connectors are added per engagement, not promised up front. Credentials are scoped to the engagement, vaulted, and revocable by you at any time.
  2. One engagement, one box. Your data lands on an isolated machine provisioned for your engagement alone. No shared infrastructure, no multi-tenant database, no other client on the box.
  3. Reconcile. We check what your systems say against each other — record counts, sums, identities across tools. Ambiguous identity matches are quarantined for human review, never silently merged. The finding is where your stack disagrees with itself, and by how much.
  4. Seal. Every result ships as a sealed report: change one field and the seal breaks. Verification runs in your browser — you don't take our word for it. The demo on the front page is the same mechanism, on synthetic data.
  5. You approve. Then changes happen. Fixes are rehearsed in a sandbox copy and reconciled before anything is applied. Nothing writes to a production system until your designated approver signs off on the specific change. You apply approved changes yourself, or we do — the approval is always yours.
  6. The box dies. The proofs don't. At engagement end, the data box and its backups are destroyed. The sealed reports survive — portable, machine-verifiable, yours. Erasure requests during the engagement are honored, with an append-only audit trail.

What never happens

Start with your tool list

Names are enough — billing, marketing, product analytics, warehouse, whatever you argue about in meetings.

send your tool list

or plain email: [email protected]