“We got advice divorced from the build, and a build divorced from the business.
BPE Group did both, and it finally worked.”
Operations lead · ABC Wellness Group
Impact
↓95%
Labor time
↑25%
Reliability
↑67%
Visibility
Approach
How we operate.
01
Analyze
We document the process exactly as it runs today, and find where the hours actually go.
02
Design
We design the better version and agree the build and test plan before any code is written.
03
Build
We build it ourselves on production-ready tools, and hand you the source.
04
Test
We run it against your real volume, then train the team that will own it.
Deliverables
What we deliver.
Source code is the root. Everything we build lives in your repo in readable syntax, and
anything configured on an outside platform gets exported back into it — so you keep the control, not the
vendor.
Documentation
Everything written down and kept where your team can find it — the process baseline, the build plan, the
runbook, and short walkthroughs of the system actually running.
MarkdownGoogle DocsMermaidMP4
Data
Where the process keeps its state, chosen for how your team already works. Schema and migrations are
versioned in the repo alongside the code.
SupabaseAirtableGoogle Sheets
Automation
The work itself — deterministic scripts wherever the rules are fixed, and agents only where a judgment
call is genuinely required.
Pythonn8nScriptsAgents
Apps
A real interface when the process needs one, deployed on your own accounts and handed over with the
source.
Next.jsTailwindVercel
Principles
What we commit to.
01
Simplicity
We don't overengineer. A script wherever a script will do, so the system stays cheap to change and easy
for your team to understand.
02
Efficiency
We don't waste your time. Meetings are short and only when a decision needs one — everything else goes
in writing you can read when it suits you.
03
Ownership
You keep the keys. The repo, the accounts and the documentation are yours, and nothing we build depends
on us to keep running.
04
Transparency
You see the work as it happens. Everything lives in a shared repo and doc from day one, not in a deck
at the end.
Results
What we've done.
A process is a system: inputs go in, outputs come out. There are only two ways to make one
better — put less in, or get more out, and every number below is one or the other. Client names are
withheld at their request.
ABC Wellness Group
Wellness · billing
Before — the problem
ABC had no standardized billing process. At $2M in annual revenue, invoicing and collections ran on
ad-hoc steps that lived in people's heads, with no consistent organization behind them. Staff spent 70
hrs a week keeping it moving by hand, reliability sat at 80%, and management could see only 60% of what
was happening.
After — the solution
We standardized the billing process and the organization around it, documented it end to end, then
automated collection and entry with Python and Playwright and scripted the reporting layer in Google
Sheets and Apps Script.
Impact
↓95%
Labor time
↑25%
Reliability
↑67%
Visibility
DAA Financial Group
Financial services · reporting
Before — the problem
DAA had no standardized reporting process. Source data was inconsistent and spread across disconnected
systems, so the work depended on tribal knowledge — 600 hrs a week of manual preparation, only 45% of
the data reachable without asking someone, and 5% of the process written down anywhere.
After — the solution
We standardized the sources and rebuilt the pipeline in SQL Server, Azure Data Factory and Power Query,
automated the manual preparation with Python, Power Automate and VBA, and wrote both technical and
user-facing documentation.
Impact
↓98%
Labor time
↑2×
Data access
↑10×
Documentation
Story
Why BPE Group?
Ariel · Founder
Dear visitor,
Most companies end up hiring two kinds of people. Consultants study the business and hand over a
recommendation. Engineers take a specification and build what it says. Both get paid either way — and
neither one is accountable for whether the process actually got better.
My name is Ariel. I studied mathematical economics at UW–Madison and I'm finishing a master's in
computer science at Georgia Tech, which put me on both sides of that divide: understanding how a business
actually runs, and building the software that runs it.
Prompting has made that gap more expensive, not less. Generating something that works once, for the person
who generated it, takes an afternoon now — genuinely useful, and there has never been more of it. But
output is not an outcome. What I keep finding inside companies is a shelf of AI-built tools, each
impressive on its own, and a business that operates exactly the way it did before any of them existed.
Work only becomes an outcome by moving through three stages in order. First the process —
sitting with it as it actually happens rather than as the org chart describes it, and being willing to say
which steps exist for a reason and which are just scar tissue. Then the engineering — the error
handling, the edge cases, the permissions, the documentation, the unglamorous machinery that decides whether
something still runs on a Tuesday in March when the person who built it is on vacation. Only then the outcome, which is the part the business can actually feel.
That is what BPE Group is for. We do both halves: we redesign the process first, then engineer the
version that should exist. We use the smallest tool that solves the problem, and we leave you the
documentation to own it.
A consultation and a written read on the process you want fixed — what it is actually costing you, and
whether it is worth engineering. No charge, no obligation.
To build
Project-based
One fee for the engagement, scoped to the complexity of the solution and agreed before we start. No
hourly billing, no open-ended retainer.
Contact
Where to start.
Have a business process you think should be engineered? Reach out.
