A complete Power BI reporting suite, for your entire business.
The SQL, one governed model, drill-through pages for every department, row-level and object-level security, a business glossary, and training. Three fixed-scope tiers. An optional monthly retainer afterward, if you want us to stay on.
Sized to the part of the business you need to see.
Each tier is a fixed-scope build with a defined page count, source count, and security model. Pricing is quoted after a 30-minute scoping call, and shared before anything starts.
Core
One business area, done completely.
- Scope
- Single domain
- Timeline
- 4-6 weeks
- Pages
- 6-10 report pages
- Pricing
- Fixed project fee
- Business areas
- Finance or Sales or Inventory
Pick the area that hurts most. We engineer the SQL, build the model, and deliver a complete reporting suite for that function, with the glossary, security, drill-through, and training that come with every tier.
- SQL staging & views for one source system
- One governed semantic model
- 6-10 pages: executive summary through transaction detail
- Row-level security for one audience (e.g. by region or entity)
- Drill-through from every summary visual
- Business glossary for every measure
- Two training sessions + recorded handoff
Best for
Companies replacing a monthly spreadsheet pack, or testing what a real BI partner is like before going wider.
Operations
Most commonThe departments that run the business, connected.
- Scope
- Multi-domain
- Timeline
- 8-12 weeks
- Pages
- 15-25 report pages
- Pricing
- Fixed project fee
- Business areas
- Finance + Sales + Inventory / Purchasing
Three or four business areas on one shared model, so sales, inventory, and finance finally agree on the numbers. Cross-domain drill-through, layered security, and a glossary the whole company uses.
- SQL engineering across 2-3 source systems (ERP, CRM, warehouse)
- Shared dimensions: date, customer, item, location, account
- 15-25 pages across executive, departmental, and detail layers
- Row-level AND object-level security (hide tables/columns by role)
- Cross-domain drill-through (sales order → inventory → invoice → GL)
- Business glossary + data dictionary with lineage
- Analyst training cohort + consumer sessions
- Dev / test / prod workspaces with deployment pipeline
Best for
Mid-sized operators on an ERP who are tired of every department reporting different numbers.
Enterprise
Every function, one platform, built to be owned.
- Scope
- Entire business
- Timeline
- 12-20 weeks
- Pages
- 30+ report pages
- Pricing
- Project pricing, milestone-billed
- Business areas
- All departments
A full reporting platform across the company: warehouse or lakehouse engineering, a certified semantic model, executive and departmental suites, governance, and the enablement to run it in-house.
- Warehouse / lakehouse engineering (SQL Server, Synapse, Snowflake, Fabric)
- Certified semantic model with incremental refresh and performance baseline
- 30+ pages: board pack, exec, every department, operational detail
- Full RLS / OLS matrix with documented role assignments
- Drill-through everywhere, plus paginated reports for print and distribution
- Business glossary, data dictionary, model card, admin runbook
- Train-the-trainer program so your analysts become the builders
- Deployment pipelines, lineage, and a governance playbook
- Copilot / natural-language Q&A readiness
Best for
Companies replacing legacy BI, consolidating entities, or standing up analytics for the first time at scale.
Not sure which tier? Most companies on an ERP land in Operations. If you only have one painful spreadsheet pack, start with Core and expand; the model is built to grow, so nothing is thrown away.
Six things that ship no matter which tier you pick.
The size of the suite changes by tier. The engineering standard doesn't.
SQL engineering, not just visuals
Views, staging layers, and stored procedures written against your warehouse (or straight against the ERP when you don't have one yet), so the model refreshes fast and reconciles to the penny.
One governed semantic model
Star-schema model with shared dimensions (date, customer, item, location, account) so every report agrees with every other report.
Business glossary
Every measure, KPI, and dimension defined in plain English, with the SQL and DAX behind it. Published inside the report and as a standalone document.
Drill-through on every page
Summary to detail to transaction. Right-click a number and land on the exact invoices, orders, or journal lines behind it.
Row-level & object-level security
Managers see their territory, departments see their cost centers, and sensitive tables or columns simply don't exist for users who shouldn't see them.
Training & handoff
Live sessions for consumers and analysts, recorded walkthroughs, and a measure-authoring guide so the suite keeps growing after we leave.
We can build the warehouse. We'd rather you already had one.
Data engineering is in scope when you need it, and we'll say so plainly when you do. But the suite is the product, and it lands fastest when the data is already in a governed warehouse.
You have a data warehouse
SQL Server, Azure SQL, Synapse, Snowflake, Fabric, Postgres. This is where we do our best work: the data is already landed, so the engagement goes into modeling, measures, security, and pages from week one.
- Reporting views and a semantic layer on top of your existing tables
- No duplicate pipelines, no second copy of the data
- Your engineers keep ownership of ingestion; we document what we add
Data is in the ERP / CRM only
Dynamics, Acumatica, Sage, NetSuite, Dataverse. We'll build the staging layer that gets it out cleanly: metadata-driven loads, incremental extracts, and the views the model needs. Scoped as a line item so you can see what the engineering costs.
- Staging database with metadata-driven, incremental loads
- Reconciliation back to ERP totals before any report is built
- A path to a real warehouse later, without rebuilding the reports
Spreadsheets and exports
Monthly extracts, shared drives, a few Access databases. We can start here, but we'll be honest: the first milestone is getting that data into a governed table, and we'll quote that separately from the reporting suite.
- Land exports into a small SQL database on a schedule
- Replace manual steps one at a time; keep the business running meanwhile
- Reporting suite built once the sources are stable
Report pages by department.
A sample of what a suite covers. Core picks one column; Operations picks three or four; Enterprise takes the whole grid and adds a board pack on top.
Finance
- P&L with budget vs actual
- Balance sheet & cash
- AR / AP aging
- GL detail drill-through
Sales
- Revenue, margin, mix
- Customer & rep performance
- Pricing & trade agreements
- Order fill rate
Inventory
- On-hand & valuation by warehouse
- Aging & expiring stock
- Stock status & coverage
- Transfer order tracking
Purchasing
- Open PO risk & accruals
- Vendor lead time & cost
- Spend by category
- Receipt variance
Operations
- Fulfillment & shipping SLAs
- Capacity & throughput
- Quality & returns
- Project earned value
Manufacturing
- BOM cost roll-up
- Production vs plan
- Yield & scrap
- Costed unit analysis
What an Operations build looks like on the calendar.
A representative 12-week plan. Core compresses it; Enterprise runs it per department with a platform phase up front.
Wk 1
Scoping & definitions
Department workshops, KPI list, security matrix, source inventory. Glossary starts here.
Wk 2-3
SQL & staging
Reporting views or staging loads, reconciled to source totals. Shared dimensions agreed.
Wk 4-5
Model & security
Star schema, measures, RLS / OLS roles, performance baseline. First pages shown to stakeholders.
Wk 6-9
Pages, weekly reviews
Executive, departmental, and detail pages with drill-through. Reviewed every week with the people who will use them.
Wk 10-11
UAT & hardening
Role-by-role security testing, refresh scheduling, deployment pipeline, runbook.
Wk 12
Training & handoff
Consumer and analyst sessions, recordings, glossary published. Retainer starts if you want it.
What you own on the last day, by name.
A suite is only yours if your team can change it without calling us. Every tier ends with this list checked off and in your repo, your tenant, and your inbox.
- Semantic model (.pbip) in your Git repo with a change log
- SQL scripts, views, and load procedures, versioned and commented
- Business glossary: every measure, KPI, and dimension with DAX and SQL
- Security matrix: every role, who is in it, what it can and cannot see
- Admin runbook: refresh, gateway, pipeline, and how to add a user
- Recorded training sessions and a measure-authoring guide
- Performance baseline: refresh time and visual load times at go-live
Click through a working suite before you buy one.
A fictional distributor, fully synthetic data, real behavior: switch roles to watch row-level security change the numbers, drill from a region to the invoices behind it, and open the glossary on any measure.
An optional retainer, if you want the suite to keep growing.
Your team owns the suite and can run it with the training we provide. If you'd rather have us keep it maintained or keep adding to it, three retainer levels are available, month-to-month, with no commitment baked into the build.
Maintain
Keep it running.
Monthly · fixed hours block
Refresh monitoring, break-fix, small measure changes, and a standing monthly check-in. For teams that want the suite protected without a full-time hire.
- Refresh and gateway monitoring with same-day response
- Bug fixes and small DAX / SQL changes
- Monthly health review and glossary upkeep
- Security role changes as people join and leave
Best for
Suites that are finished and need to stay that way.
Extend
Keep it growing.
Monthly · larger hours block
Everything in Maintain, plus a steady stream of new pages, new measures, and new sources as the business asks for them. Prioritized together each month.
- Everything in Maintain
- New report pages and measures each month
- New source onboarding (a new entity, system, or feed)
- Quarterly performance tuning and model review
- Office hours for your analysts
Best for
Companies whose reporting backlog never quite empties.
Embedded
A fractional BI team.
Monthly · dedicated capacity
Dedicated weekly capacity acting as your BI lead: roadmap, stakeholder intake, data engineering, and delivery. The senior BI hire without the recruiting.
- Everything in Extend
- Weekly stakeholder intake and roadmap ownership
- Data engineering and warehouse changes
- Vendor and ERP-upgrade coordination
- Leadership readouts and KPI governance
Best for
Organizations that need a BI leader, not a ticket queue.
Smaller engagements that stand on their own.
Useful before a tier build, after one, or instead of one.
BI Health Check
1-2 weeksAudit of an existing Power BI estate against Microsoft and Vertipaq best practices, with a prioritized punch list. Often the first step before a Core or Operations build.
Training cohorts
1-5 daysStand-alone Power BI training for analysts and authors, built around your data. DAX, modeling, Power Query, governance, and Fabric tracks.
Warehouse & staging build
ScopedNo warehouse yet? We stand one up (SQL Server, Azure SQL, Synapse, Snowflake, or Fabric) with metadata-driven loads from your ERP, so the reporting suite has a clean, governed layer to sit on.
Performance rescue
1-3 weeksFor the model that times out, the visual that 'exceeds resources', or the refresh that fails every Monday. Diagnosed, rewritten, baselined.
Power BI questions, answered straight.
Every report page a department needs to run, on one governed model, with the SQL engineering underneath it. Core covers one department, Operations covers three or four, Enterprise covers the whole company. All three ship with a business glossary, row-level and object-level security, drill-through to transaction detail, and training.
Have data, ideas, or a backlog you can't get through?
Tell us what's slowing you down. We'll come back with a focused plan, a realistic timeline, and a fixed scope for the first milestone.