Stop doing the same task twice — let the software do it.
For the small teams losing hours to clicks, copy-pastes, and "just one more email." I wire up the stuff you do the same way every week so it runs on its own — and your people go back to the actual work. From $250.
What every automation gets by default.
Not upsells — the floor. Silent failures kill automations, so I don't ship them.
- Alerts when something breaks
- Every run logged
- Safe to retry
- Tested on real data first
- Short doc for your team
- You own it, not me
How I actually build these.
Use what you already pay for, fix the process first, and never automate a mess.
Fix the process, then automate
If the workflow is broken, automation just breaks it faster. First call is usually 'do you actually need this step at all?'
Use what you already pay for
Microsoft 365 includes Power Automate. Google Workspace includes Apps Script. Often the right answer is zero new SaaS bills.
API-first, RPA when not
Real APIs when they exist (clean, fast, stable). Power Automate Desktop RPA for legacy apps with no API — with eyes wide open about the tradeoffs.
Observability built in
Run history, success rates, and a simple dashboard so you can see at a glance whether things are working — without logging into seven tools.
I've replaced $40K+/yr in vendor reporting and automation in-house.
Power Automate flows + Power BI dashboards + a few Cloud Functions, all running on tools the business already paid for. Same outputs, fraction of the cost, fully owned.
Three ways to start. Pick the shape that fits.
Every build is custom, owned by you, and includes the baseline above. Fixed one-page quote after a discovery call.
Workflow
- Timeline
- 1–2 weeks
- Scope
- 1 workflow
- Systems
- 1–2 systems
- One end-to-end workflow (e.g. form → CRM → Slack → reply email)
- Built in Power Automate, Apps Script, Zapier, or Make — whichever fits
- Error alerts + run logs
- Tested in a sandbox against real data
Stack
- Timeline
- 2–4 weeks
- Scope
- Multi-system flow
- Systems
- 3–5 systems
- Everything in Workflow
- Multi-system integration across CRM, accounting, email, storage, etc.
- Webhooks + scheduled jobs + event triggers as needed
- Shared data model so the systems agree on what a customer is
Engine
- Timeline
- 4–10 weeks
- Scope
- Full ops suite
- Systems
- 5+ systems
- Everything in Stack
- Custom Cloud Functions (Firebase / GCP) for anything outside no-code limits
- Power Automate Desktop RPA for legacy apps with no API
- AI Builder OCR / extraction for PDFs, invoices, and intake forms
Extras, when you need them.
Slot onto any package, or add later as the business grows into them.
RPA bot for legacy apps
$1K–$3KPower Automate Desktop bot that clicks through the old AS400 / desktop app that has no API. Last resort, but it works.
AI extraction (OCR / intake)
$800–$2.5KPull structured data out of invoices, resumes, or scanned forms with AI Builder or Document AI. Inbox in, spreadsheet out.
Slack / Teams notifications
$300–$800Smart alerts to the right channel or person — not a firehose. Includes quiet hours and grouping so it doesn't get muted.
Scheduled report emails
$400–$1.2KWeekly or monthly digest emails from your live data — revenue, pipeline, ops metrics — auto-built and sent.
Monitoring dashboard
$800–$2KPower BI or Looker Studio view showing run history, success rate, and any flows that are drifting. So you trust it.
Monthly retainer
$200–$600 / moTweaks, new flows, vendor-update fixes, and 'hey can the bot also do this' moments. Cancel anytime.
How an automation project actually goes.
A call, a process map, a tested build, then a launch where I don't disappear.
20-minute discovery call
Walk me through the task as it happens today — clicks, copy-pastes, the whole thing. I'll flag what's worth automating and what isn't.
Process map + fixed quote
Within 48 hours you get a one-page diagram of the new flow plus a fixed price and timeline. No hourly surprises.
Build + test in your sandbox
I build inside your tenant against real (but safe) data. You see it run before it touches anything live. Revisions are part of the price.
Launch + monitoring + handoff
We turn it on together, set up alerts and logs, and I hand over a short doc for your team. Then I stay reachable for the first month at minimum.
Things people usually ask.
Whichever costs you less to run and is easier to maintain. If you already pay for Microsoft 365, Power Automate is usually free and more powerful. Zapier and Make are great for fast one-offs across consumer SaaS. Custom code only when the no-code tools genuinely can't do it.
Then we use Power Automate Desktop or a similar RPA tool to drive the UI like a person would. It's slower and a little more brittle than an API, but it works on truly ancient software. I'll always tell you upfront when this is the only option.
Stable APIs almost never break. RPA bots and screen-scrapers can break when a vendor redesigns the UI — that's the tradeoff for automating something with no API. Either way, the monitoring tells you the moment it stops working, so it's a quick fix rather than a slow disaster.
You can — the doc and the platform make small tweaks easy. Most clients keep me on a small monthly retainer for new flows and the occasional vendor-update fix. Both are fine.
Usually nothing or close to it. Power Automate is included with most Microsoft 365 plans, Apps Script is free with Google Workspace, and Cloud Functions cost pennies at small-business volume. Zapier / Make have their own subscriptions, which I'll factor into the recommendation.
Tell me what's eating your week. I'll tell you whether it's worth automating.
20-minute call, plain-English process map and quote within 48 hours, or an honest 'this isn't worth automating yet — here's why.' All three happen.