Example package
First Power BI report
One report on your key numbers, refreshed automatically.
You get
- Sources connected
- Data model
- Report pages
- Scheduled refresh
How it works
- 1You describe it
- 2A written scope
- 3Milestones you review
- 4Handover and a 30-day fix window
How we work, step by step · The 30-day fix window in our agreement (section 9)
Sound familiar?
What we hear from businesses before a project like this starts.
- Every month someone spends two days building the same report in Excel.
- Our numbers don't match between the CRM, the books and the spreadsheet.
- We bought Power BI licences and never built anything useful.
- The report someone made is slow and nobody knows how it works.
- We need one view of sales, margin and cash without logging into five tools.
- The consultancies we spoke to wanted a data strategy workshop first.
What buyers usually need
The requests that come up most often for this kind of work, and what each one takes to work properly.
01
Your data connected
Accounting, CRM, e-commerce, databases and spreadsheets connected with scheduled refresh.
02
A clean data model
Tables, relationships and measures that give the same answer everywhere.
03
Reports people use
A few pages built around the questions your team asks every week.
04
Sharing and security
Workspaces, apps and row-level security so each person sees the right data.
05
Fixing an existing report
A slow or broken report reviewed, rebuilt and documented.
06
Power BI or something else
If Looker Studio or a simple dashboard suits you better, we say so.
Tools that come up most: Power BI Desktop and Service, Power Query, DAX, Microsoft Fabric, Excel, SharePoint, SQL Server, Azure SQL, Dynamics 365, QuickBooks, Xero, HubSpot, Salesforce, Shopify, Google Sheets, Looker Studio.
What you get
Concrete pieces, each one something you can open and check when it's done.
Data connections
Each source connected, with refresh scheduled and checked.
Power Query, gatewaysData model
Tables, relationships and measures documented.
DAX, star schemaReports
Report pages for phone and desktop, built with your team.
Power BI DesktopSharing
Workspaces, apps and access set up in your tenant.
Power BI ServiceHandover
A guide to the model and measures, and a walkthrough.
DocumentationTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Report rebuild
A slow or confusing report rebuilt and documented.
You get
- Review of the current report
- Model rebuilt
- Faster pages
- Documentation
Example package
Reporting set-up
Workspaces, sharing and security for your team.
You get
- Workspaces and apps
- Row-level security
- Refresh monitoring
- Team walkthrough
How we approach it
The habits that keep this kind of project from going wrong.
1
Questions first
We start from the decisions the report should help with.
2
Your workspace
Built in your Microsoft tenant with access you control.
3
Numbers you can trust
Totals checked against your books and source systems.
How we work
You describe it. We write it down, build it, and hand it over.
You describe it
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
A written scope
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
Milestones you review
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
Handover and a 30-day fix window
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
What shapes the scope
- Number of data sources
- Report pages needed
- Users and security rules
- Refresh frequency
Always included
- A written scope before work starts
- Milestones you review and sign off
- Documentation and a walkthrough at handover
- A 30-day window for fixes, at no charge
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, based in Massachusetts. See example builds.
Questions people ask first
Do we need Power BI Pro or Premium?
Sharing reports usually needs Pro or a capacity licence. The scope says which licences the work needs.
Can you connect QuickBooks, HubSpot or Shopify?
Yes, through built-in connectors, an API or a small data pipeline, with scheduled refresh.
Can you fix a report someone else built?
Yes. We review the model and measures, rebuild what's slow or wrong, and document it.
Is Power BI right for us?
If your team uses Microsoft 365, usually. If not, Looker Studio or a simple dashboard may suit you better, and we will say so.
What happens after handover?
For 30 days we repair anything we built that does not work as the scope describes, at no charge. After that, further work is scoped the same way and agreed with you before we start.
Do it once, we automate it. Show us the job one time and it runs on its own after that, in the tools you already use. Not sure where to start? Start with an Automation Audit.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com