Data that stays in sync
Spreadsheets, trackers, and reporting that agree without manual cleanup.
Designing, Building, & Automating
with AI.
Claude Code
Codex
Cursor
Google Workspace
I use AI to build systems that improve operational efficiency, simplify workflows, and deliver actionable business intelligence.
Paul Uipi
What I'm Building
Real Systems.
Still Running.
These are the kinds of systems I build for businesses. The portfolio has the projects, the architecture, and what is running today.
Payroll that checks itself
Rates, bonuses, split pay, and the calculations behind getting paid right.
Dashboards that answer
Live reporting that turns the right data into an answer, not another tab.
Tools that fit the business
Websites, connected workspaces, and email workflows built around how work happens.
Projects
Websites and Google Workspace automations I’ve designed, built, and still run, shown the way they actually work.
See the projects →How I Build
Boring Tools.
On Purpose.
There is a version of this work that involves buying four new platforms. This is the other version.
Scripts do the work. People make the calls.
Anything repetitive and rule-based gets handed to code that behaves the same way every time. Judgment stays with a person. The failure mode I am avoiding is the one where something clever makes a decision nobody reviewed and nobody can explain a month later.
Build on what is already paid for.
Most small businesses already own more capability than they use. Sheets, Apps Script, and their existing Workspace account cover a surprising amount of ground. Adding a platform adds a bill, a login, an integration, and a migration. I reach for that only when the existing tools genuinely cannot do the job.
Two models, and they are different.
Some things I build once and hand over with documentation, and they are yours to run. Other things I run on an ongoing basis, because payroll and compliance do not stop needing attention after launch. Those are genuinely different arrangements, and conflating them is how people end up disappointed.
Show the parts that went badly.
A build log with no failures in it is marketing. The useful information is usually in what broke, what it cost, and what I changed afterward.
What Broke
The Parts I
Got Wrong.
Shipped mistakes, what they cost, and what changed afterward.
Entry title
What happened, what it cost, what changed afterward.
Built For Real Businesses.
Work With Me
If You Want This
For Your Practice.
The building above is the same work I do for clients. Two ways in.
Practice operations
Payroll, books and taxes, compliance and HR, run for you on an ongoing basis. Built specifically around how behavioral health and wellness practices actually operate. Pricing and scope are on the page.
See practice operations →Projects
Websites and Google Workspace automations I've designed, built, and still run, shown the way they actually work.
See the projects →Practices I work with
Send me a note
Questions about a build, something you are stuck on, or work you want to talk through.
Protected by reCAPTCHA. Google Privacy Policy and Terms of Service apply.