I'm Andrew Henry, an engineer turned data and automation consultant. I build Power BI reporting, automated data pipelines, custom tools and practical AI for field services, financial advisory and e-commerce companies. You work with me directly, from the first call to the handoff.
Free first conversation. I reply within one business day.




Systems in production in field services, financial advisory and e-commerce, running every day.
Pick the one that sounds like your week. Every build comes with documentation your team can operate without me, and you own all of it.
"The numbers come from five spreadsheets and nobody agrees on them."
What I build: Power BI dashboards and reports built on your real data and checked against the systems it comes from, so everyone in the room sees the same number.
What you own: the reports, the data model underneath them, and plain-language notes on how every number is calculated.
Talk about reporting →"Someone on your team spends hours every week copying data from one system to another."
What I build: automated connections that pull data from your accounting, CRM, field software or online store and put it in one place on a schedule.
What you own: pipelines that run on their own, alert me if something breaks, and come with documentation your team can follow.
Talk about automating a process →"The tool your team needs does not exist, or it lives in a spreadsheet only one person understands."
What I build: internal tools and customer-facing apps, such as pricing calculators, document processing and step-by-step workflows, that your team can use from the first day.
What you own: the working software, the code, and the accounts it runs on.
Talk about a custom tool →"People spend their day reading documents and emails and typing in what they find."
What I build: AI that reads documents, sorts incoming requests and drafts responses inside the tools you already use. I test it on real examples from your business before it goes live, and a person approves anything that matters.
What you own: a working setup, the test results, and clear rules for when it hands off to a person.
Talk about AI for your documents →You meet a salesperson and a project manager. The work is done by whoever is available, and every question makes a round trip.
You manage them yourself, hope the portfolio was real, and start over if it wasn't.
Months to hire, one skill set, and the reporting problem needed solving last quarter.
One senior engineer who scopes it, builds it, documents it and hands it over. I run my own company on an AI operations system I built, which is how one person delivers at this pace.
My own company runs on it: a fleet of scheduled AI workers that find work, monitor systems, process email, and keep the books. Every consequential action sits behind a human approval gate, every run is graded, and the whole fleet is visible from a phone. It is the production proof behind everything on this page: I don't sell AI I haven't trusted with my own operation first.
Working examples of my integration and automation patterns, in the open at github.com/HenryLabsConsulting.
A household calendar our family uses daily and a narration engine that turns written reports into audio briefings. I build and operate my own software with the same standards I ship to clients.
Free, about 30 minutes, no pitch. You describe what's going on; I give you an honest read on whether and how I'd help.
I learn how the business actually runs before proposing anything. The build gets designed around reality, not a template.
You see exactly what gets built, what it costs, and how we'll know it works, before any work starts.
Working software, delivered with documentation. You own the code, the reports, the data and the accounts.
A conversation about how the business runs, and access to the systems involved when we get to discovery. You don't need clean data or a written spec; finding out what's really there is my job.
After discovery you get a written scope with a number before any build starts. Hourly or fixed depends on the work; either way the scope says what you're paying for and what "done" means.
The first conversation usually happens within a few days. Delivery depends on scope, and the written scope includes the timeline. Small builds land in weeks, not quarters.
That's the point. I build on what you have: your accounting software, CRM, field software, store, spreadsheets. Replacing systems is a last resort, not a default.
Everything ships with documentation written for your team, and you own the code and the accounts. No part of your operation is locked inside my head.
Yes, deliberately: AI does the repetitive reading and drafting, a person approves anything that matters, and I test on real examples before anything goes live. Your data stays in your systems and accounts wherever possible, and we agree on the boundaries in writing.
I reply personally within one business day.
Prefer email? aj@henrylabs.net