Why not just use Power BI or Tableau?
BI tools fall short in three places:
- Entering data in the report, like a PM’s forecast to complete or a downtime reason, saved with permissions and an audit trail.
- Custom visuals designed around your question, rather than picked from a fixed set of chart types.
- Sharing, which in a BI tool means licenses, workspaces and guest-access settings before anyone outside the team can open a report. Here you click Share and send a link.
There is also no per-seat license, and you own the result. If a BI tool already does what you need, keep it — the warehouse and ETL I build can feed it. But if you’re reading this, something is probably missing. Tell me what it is.
How is my data secured?
All traffic is encrypted in transit (TLS). Sign-in uses your existing company logins, with permissions down to the row and the field. Where I build the data warehouse, it adds encryption at rest and network isolation. Everything runs in your cloud account, under your control, and I connect to your data through a service account that you own and can revoke at any time.
What does it cost to run?
Aside from the data warehouse, hosting averages under $50 a month. The warehouse itself is somewhere from $30 to $250 a month, depending on the size and scope of the data. Both are billed by your cloud provider, in your account — there is no platform fee and no per-seat license on top.
Do you work with Vista, CMiC, JDE or Epicor?
Yes — those and the rest of the systems listed on the home page are ones I have pulled data out of, along with the payroll, CRM and custom systems that usually sit around them. If your data is already in a warehouse, the source system matters less: I connect to the warehouse. If it is not, the ETL is built against whatever the ERP exposes — a database, an API, or scheduled exports — into a warehouse in your cloud.
My ERP or CRM isn’t on your list. Would you still work with it?
Yes, absolutely. The list is the systems I have already integrated, not the limit of what I can integrate. Most systems qualify: if it has a database, an API, or an export you can schedule, I can pull from it. Where a system is new to me, the scoping call is where I confirm how it exposes its data and price the integration on that.
I’m not in Construction or Manufacturing. Can you still help?
Yes. Those are the industries I know best, and the reason the examples on this site read the way they do — but the approach is the same anywhere: connect to the data, model the reporting datasets, build the report. If your business runs on a warehouse, an ERP, or a spreadsheet that gets rebuilt every week, it fits.
Do I own what you build?
Yes. The application code, the warehouse, and the pipelines are yours, in your repositories and your cloud account. There is no platform to keep paying for to keep your own reports running.
Do I have to buy a warehouse to get a reporting solution?
No. If your data is already in a warehouse, the reporting solution is the whole job — editable reports included — and the price is the reporting price on its own. The warehouse and ETL are added only when there is no warehouse to build on.
Can you build just the data warehouse and ETL?
Yes. Data warehousing + ETL is its own offering as well as something that can come before a reporting solution. If you have a BI tool or a team that will do the reporting, I build the warehouse and the pipelines that fill it, hand them over, and stop there.
How long does it take?
A first look at your first report 1–2 weeks after I’m connected to your data. Where a warehouse and ETL have to be built first, that adds 2–4 weeks ahead of the reporting — or is 2–4 weeks on its own. After launch, changes take days. All of it depends on how quickly access to your systems and requirements comes through.
Which databases and warehouses do you support?
SQL Server, PostgreSQL, Snowflake and BigQuery directly. Anything else with a supported driver is usually fine — ask on the call.
Can it replace my SSRS reports one at a time?
Yes, and that is the usual way in. Start with the most painful one. Each report after the first is faster, because the warehouse connection, the reporting views and the permission model are already in place.
What happens after launch?
Every reporting build includes a round of changes while it settles in. Warehouse and ETL work is fixed-scope, so changes to it are a new statement of work. After that you can take it in-house — you own the code — or bring me back under a new or extended contract for support, changes and new reports. Additional reports start from $4K and additional integrations from $5K, depending on complexity.
