Hazel Quimpo · AI and automation for small teams · Milwaukee

I'll happily spend four hours automating your ten-minute task so nobody on your team does it by hand again.

I set up automation and AI for small businesses and nonprofits. The dull, repetitive work gets handled, in accounts you own, and a person still signs off on anything that reaches your customers or donors.

Book an audit → How I use AI →
Hazel Quimpo, AI and automation consultant, Milwaukee
Plate 00 — The author Milwaukee, WI
Fig. 01 — Three steps

Three steps, one flat price each.

You can stop after any of them.

Step 01

Audit

$950 · 90 min + written plan

We spend 90 minutes going through how work actually moves around your organization. Within a week you get a written plan with the three automations worth building first, ranked by hours saved, plus a one-page AI policy your team can use right away. If you book a Build within 60 days, the whole $950 comes off it.

  • 90 minutes together, on Zoom or in person around Milwaukee
  • A written plan within five business days
  • Your top three automations, ranked by hours saved
  • Which tools to use, starting with what you already pay for
  • A one-page AI use policy, adapted from NTEN's nonprofit template
  • The full $950 credited toward a Build booked within 60 days
Step 02

Build

$3,500 · 3–4 weeks

I build up to three automations from your plan, inside the tools and accounts you already pay for. Then I write down how each one works, record a walkthrough, and train your people, so nothing breaks or gets stuck if I'm unreachable for a week.

  • Up to three automations from your Audit plan
  • Built in your accounts, so you own every piece of it
  • A person approves anything that goes out to customers, donors, or the public
  • Runbooks and recorded walkthroughs for each one
  • One 60-minute training session with your staff
  • 30 days of fixes after handoff
Step 03

Care

$500/mo

Automations break quietly when a password changes or an app updates. Care is a monthly check-in and up to three hours of fixes and small changes, with a reply within two business days. It's only for Build clients, and I keep it to four organizations at a time.

  • Monthly check-ins to make sure everything's still running
  • Up to three hours a month of fixes and small changes
  • Replies within two business days
  • For Build clients only, with a three-month minimum

I take on two audits and one build a month. That's on purpose, because this work is fiddly and I'd rather do it carefully than do a lot of it.

Book an audit →
Fig. 02 — Usual suspects

The stuff that eats your week.

First projects are usually boring ones. That's where the hours go, so that's where I start.

  1. Website form to spreadsheet or CRM, then a follow-up email that actually goes out
  2. Donor and customer thank-yous drafted for a person to review and send
  3. Meeting notes turned into action items with names and dates on them
  4. Invoice reminders and receipts that don't depend on someone remembering
  5. Volunteer and event sign-ups that land somewhere useful
  6. Monthly reports pulled together from the four places your numbers live
Fig. 03 — House rules

How I use AI, in writing.

Most nonprofits using AI don't have written guidance for it yet. I publish mine, and every Audit client gets a policy of their own.

  1. AI drafts, a person sends.
  2. Your accounts, your data, your workflows.
  3. No sensitive data in tools that train on it.

Read all seven →

Fig. 04 — The archive

Things I've built.

Full portfolio →

Automations, apps, and systems for nonprofits, small businesses, and my family's bakery.

Custom Booking SystemCustom Booking SystemPlate P.01Course Automation for a Wellness CoachCourse Automation for a Wellness CoachPlate P.02Email Funnel — Subscription Culinary ServiceEmail Funnel — Subscription Culinary ServicePlate P.03
Fig. 05 — Peer reviews
It is just downright fun working with Hazel. I can count on her to get shit done.
Shane Pearlman, CEO
She excels at taking an organization that may be immature in marketing, and quickly leveling them up.
Reid Peifer, Product Leadership
My team went from 'we should use AI' to actually using it daily
Team AI Training Workshop
Hazel Quimpo in front of a mural
Fig. 06 — The story

Marketing taught me to communicate. AI taught me to ship.

I've done marketing at art museums, at Yelp, and in software. Somewhere along the way I started building the systems I used to write specs for, and now most of my work is setting those systems up for small teams that can't hire a developer or a full-time ops person.

Read the full story →
Fig. 07 — Next step

Start with the audit.

Ninety minutes, a written plan, and an AI policy you can use whether or not we keep going. If you're not sure it's a fit, grab a free 10-minute call first.

Book an audit → Free 10-minute call →