Weekly AI business reports for builders

We connect to any system with a read-only API. Most commonly: Xero or QuickBooks for financials, Tradify or Jobber for job management, and Google Business Profile for review data. If your software is not on that list, we check its API documentation before the setup call — most modern trade software has one.

All connections are read-only — we can never write, edit or delete anything in your source systems. Data is processed on UK-hosted infrastructure, encrypted in transit and at rest, and not retained beyond the reporting window. The pipeline is designed to meet UK GDPR data minimisation requirements, and we document the lawful basis (legitimate interest) in a data processing agreement included with every contract.

Your CRM shows CRM data. Your accounting software shows accounting data. Our report pulls both into a single page alongside your review score, so you see the business as a whole rather than as three separate tabs. The other difference is delivery: you don't log in, it arrives. A dashboard you have to remember to open will be ignored within a month.

Yes, within the single-page constraint. During setup we agree six to ten metrics. We do not add tabs, charts or sub-pages — the discipline of one page is the product. If you want to add a metric later, we drop one of similar weight to keep the format scannable in under three minutes.

The pipeline detects the failure and sends you an alert by 06:00 Monday rather than a report with silent gaps. The alert tells you which source failed, what data is missing and what the fallback behaviour is. We do not deliver a report that silently omits key figures.

Yes. Multi-location firms receive a consolidated single-page view plus individual-site breakdowns as separate pages. Each location's margin, utilisation and review score are visible independently and in aggregate. Setup time is proportionally longer, but the weekly delivery cost is the same flat fee.

Directly, yes. The structured business data in your reports — job types, completion rates, margin bands — can populate case study and project pages on your site using the same schema.org markup we use for GEO. AI engines like ChatGPT and Gemini then have verified, structured evidence of your work to cite. Operational data becomes marketing authority.

Fourteen days on average from signed contract to first live Monday delivery. Week one is API connections and KPI agreement; week two is pipeline build and historical validation; week three is template finalisation and test deliveries; week four is live. If your source systems have unusual APIs or no direct integration, we add up to five working days.

Yes. The report processes business operational data — job counts, revenue, margin, review scores — rather than customers' personal data directly. Where personal data does flow through (for example, job-level records linked to a customer name), we configure data minimisation so only the aggregated metric reaches the report. A data processing agreement documenting the lawful basis is included with every contract.

One page. Fixed sections, top to bottom: week reference and market context (two lines), financial summary (revenue, margin, outstanding receivables), operational summary (jobs completed, team utilisation, average job value), reputation (review score, new reviews this week, trend), and a single flagged item — the one metric that moved most and deserves attention. No charts. No colour coding. Scannable in under three minutes.