01
Teams arrive with different totals
Trace the reporting period, exclusions, record grain and source behind each total before deciding whether a calculation or a business definition needs to change.
BUSINESS INTELLIGENCE · SAUDI ARABIA & THE GCC
When sales, finance and operations arrive with different totals, another chart is only part of the work. We define the measures with your team, connect the agreed sources and build reports with clear ownership and refresh rules.
Proposal after scope review. Sources, metrics, report views, access and ongoing operation are agreed before implementation.
A useful report carries its definitions.
- Source
- The agreed system and record owner.
- Calculation
- The formula, exclusions and reporting period.
- Freshness
- The last successful refresh and expected delay.
- Access
- Who can view, edit and export the report.
Illustrative reporting specification
A planning illustration, not a live dashboard or business result. Measures, permissions and refresh behaviour depend on the agreed sources and platform.Business dashboards & reporting
Metric definitionsSource mappingData checksReport designRefresh ownership
START WITH THE REPORT YOU USE
Bring an existing report and the decision it supports. We review definitions, source quality and the work already included in your current services.
02
The same spreadsheet work repeats
Identify which extraction, preparation and reporting steps can be repeated safely, with visible failures and a named person to resolve them.
03
Each audience needs a different view
Define which information a manager, operator or partner needs, then test the supported viewing, editing and export permissions.
FROM SOURCE RECORDS TO A REVIEWABLE REPORT
The proposal names the data, calculations, report views and acceptance tasks. Tool selection follows those needs and your team's ability to operate the result.
A decision and metric brief
Record the audience, decisions, reporting periods and calculations. Agree what a row represents, which records count and who approves a definition change.
A useful report carries its definitions.
- Source
- The agreed system and record owner.
- Calculation
- The formula, exclusions and reporting period.
- Freshness
- The last successful refresh and expected delay.
Metric definitionsSource mappingData checksReport designRefresh ownership
An agreed source and preparation map
Document the required fields, access, identifiers and transformations. Scope cleanup and integration work explicitly before connecting operational systems.
Reports built around working tasks
Design the included views, filters and detail paths around the decisions people make. Include Arabic and English labels, mobile use or exports where agreed.
Reconciliation and acceptance evidence
Compare representative records and totals with the source. Check exclusions, duplicate joins, missing values and filters so reviewers can explain the result.
Access and refresh checks
Test the agreed viewer and editor roles, credential ownership and refresh behaviour. Document stale data, failed refreshes and the person responsible for recovery.
A practical operating handover
Deliver the agreed report files or workspace access, metric dictionary and maintenance notes. Name the owner for source changes, licences, refresh failures and future requests.
LET THE DECISION GUIDE THE BUILD
We work from a specific business question to a report that your team can check against the source. Each stage has an owner and acceptance evidence.
Choose the decision and the users
Review the current report, the action people take and the disagreements it creates. Agree the first audience, measures and scope, including existing service inclusions.
An agreed reporting brief
- Audience, decision and review cadence
- Metric definitions and approval owner
- Existing inclusions and additional work
Trace the data and test feasibility
Inspect authorised sample data and source access. Check identifiers, data quality, reporting latency and platform capabilities before committing to the implementation design.
A source map and a bounded prototype
- Sources, grain and supported connections
- Preparation and quality findings
- Licence, access and refresh assumptions
Build and reconcile the agreed views
Implement the included model and reports, then compare them with source records. Let the intended users complete real reporting tasks with representative data.
A report with acceptance evidence
- Calculations, exclusions and filter results
- Viewer, editor and export checks
- Arabic, English and agreed device layouts
Hand over a report people can maintain
Document definitions, access and operation. Agree how the team detects stale data, handles source changes and requests further work after the release.
Named reporting responsibilities
- Report assets and definition register
- Refresh failure and recovery procedure
- Training, support and change ownership
CONCEPT WORK
These demo interfaces help discuss the records a business might need to report on. They are design concepts, not delivered BI projects, connected dashboards or measured client outcomes.
Questions behind an order report
A storefront concept helps frame which order, payment and fulfilment states need separate definitions in a business report.
Questions behind an enquiry report
A property interface provides a starting point for discussing enquiry creation, assignment and follow-up without inventing performance figures.
ENGAGEMENT OPTIONS
Define a reporting brief, build a bounded first release or agree ongoing operation. Each option receives its own proposal and acceptance criteria.
Discovery and definition
Define the reporting brief
For a team that needs agreed measures, a source inventory and a feasible first scope.
Proposal after scope review
- Decision and audience review
- Metric and source dictionary
- Data-readiness and platform assessment
- Prioritised implementation brief
Scoped implementation
Build a defined dashboard
For named sources and reporting tasks with agreed access and acceptance tests.
Proposal after scope review
- Agreed source preparation and model
- Named report views and filters
- Reconciliation and access checks
- Report assets and operating handover
Ongoing reporting work
Operate and extend reporting
For an existing reporting setup that needs a defined review and maintenance programme.
Proposal after scope review
- Agreed refresh and failure review
- Definition and source-change ownership
- Prioritised reporting improvements
- Named support and maintenance responsibilities
The proposal confirms sources, preparation, metrics, report views, languages, access, refresh, exports, training and support. Licences, paid connectors, hosting, major cleanup and wider data engineering are separate unless included. AI Systems, AI Automations and marketing dashboards remain included as published; we check overlap before quoting additional business reporting. Forecasting, accounting advice and AI-generated analysis are not implied by a dashboard engagement.
BEFORE YOU COMMISSION A DASHBOARD
AI Systems, AI Automations and marketing plans include specified dashboards and reports for the work they deliver. Those inclusions remain unchanged. This service covers separately agreed business reporting across other processes or sources. We review your current scope before proposing additional work.
No. Extracting records, applying agreed calculations and refreshing reports can use ordinary data and reporting tools. Generated commentary or conversational analysis is a separate decision with its own data, evaluation and review needs. We choose the implementation around the task.
We assess the sources, calculation needs, viewing and editing roles, refresh requirements and the tools your team can maintain. Power BI, Data Studio or another suitable platform may fit. We confirm the relevant edition, licences and connector costs before agreeing the build.
The refresh requirement is agreed for each source. Available data, connector behaviour, platform limits, credentials and cost affect what can be delivered. We document expected delay, the last successful refresh and failure handling rather than treating every dashboard as continuously current.
We assess the data needed for the agreed reports and name the preparation work in scope. Major cleanup, correcting operational records or building a wider data platform requires an explicit scope. The report should expose known gaps instead of hiding them behind a complete-looking chart.
We define viewer, editor, export and data-access requirements, then test the controls supported by the chosen platform and edition. A filter on a page is not automatically an access control. Credential and workspace ownership are included in the handover discussion.
Bring a redacted example of the current report, the decision it supports, a list of source systems and the people who own the definitions. Describe the desired review frequency and audiences. We agree appropriate access after scope; account passwords and full customer exports are unnecessary for an initial brief.