Name the decision
Identify the budget owner, report user, time spent preparing the report, and the problem a better refresh would solve.
How we work
From a reporting question to an accepted handoff.
Each stage ends with a decision. Your team knows what to accept, what needs investigation, and when a change affects the scope.
Discovery
Decide whether to build.
A planning range is one to two weeks after approved access and samples are available. Timing is agreed for the engagement.
Inspect the inputs
Check supported exports, permissions, schemas, history, volume, and the availability of a source-system owner.
Agree on the scope
Approve measure definitions, workspace, source limits, reference totals, responsibilities, and acceptance checklist. Re-scope if the information or staffing is insufficient.
Implementation
Prove one path before expanding.
A bounded build has a planning range of three to six weeks after scope, access, staffing, and environment approval.
Land and validate
Record source timestamp, batch ID, row count, and errors. Validate data before promoting a batch. A rerun must not duplicate rows.
Model and report
Document row grain, keys, measures, joins, and refresh ownership. Check representative records and dashboard totals with the same dates and filters.
Use the approved platform
Consider the client’s existing Domo environment where it fits. Power BI or another environment requires its own access, technical, and licensing assessment.
Acceptance
Hand over evidence and ownership.
The client data owner and reporting approver sign off on the agreed measures and operating limits.
Refresh and recover
Observe three consecutive scheduled refreshes inside the agreed window. Demonstrate a failed-batch alert and a controlled recovery.
Resolve critical issues
Test role access. Reconcile totals within the signed tolerance or document each accepted variance. Critical issues must be resolved before go-live.
Train the owner
Deliver the runbook, dictionary, mappings, dependencies, known issues, and training. Agree on the defect correction window and how future changes are approved.
Client data
Agree the environment before sharing records.
Discuss access, data minimization, applicable agreements, retention, incident contacts, and access removal with the client’s IT, security, and advisers before receiving sensitive information. The public demonstration uses only fictional figures.