Custom AI workflows fall into five categories. Each one is narrow on purpose: one trigger, one job, runs every time. Below is the landscape, with concrete examples from each category.
Not sure where to start?
Take the two-minute quiz. Five questions about your business, three workflows worth starting with. Take the quiz.
Follow-up
The most common starting point for small businesses. The work is fragmented, the cost of dropping it is high, and AI handles it well when scoped tightly.
Example workflows
Tenant inquiry triage with AI-drafted replies and human approval
Lead follow-up sequences for real estate agents over the first 90 days
Lost-quote follow-up for trades businesses
Client check-in cadence for solo professional services
Post-purchase nurture for retail or product businesses
Intake and quoting
Inbound inquiries pile up because every one requires a small judgment call: who is this, what do they need, what's the right next step? AI is good at the first 80% of that judgment.
Example workflows
Web inquiry triage that categorizes and routes incoming requests
Quote drafting from intake form data using your existing templates
New client onboarding question-and-answer extraction
Service request scoping for trades
RFP intake and qualification for B2B service businesses
Scheduling and reminders
The quiet category that protects revenue. Appointment confirmations and review requests are the most predictable wins a small business can build.
Example workflows
Appointment confirmation sequences for fitness studios and salons
Review request workflow with smart timing based on service completion
Renewal reminder sequences for subscription or recurring service businesses
Calendar conflict detection and rescheduling drafts
Class or session waitlist notification
Client communications
Status updates, monthly digests, milestone messages. The kind of thing that should be standard but always gets pushed because nobody has a system for it.
Example workflows
Project status emails drafted from your project management tool
Monthly client digest with key activity, billing, and next steps
Owner reports for property management with rent, maintenance, and occupancy
Quarterly check-in cadence with strategic question prompts
Internal team handoff messages with structured context
Operations
Less customer-facing, more internal. Vendor coordination, team handoffs, recurring weekly tasks. These tend to be the workflows owners build for themselves first because the savings are the most direct.
Example workflows
Vendor dispatch and follow-up sequences for property management
Weekly summary digest from multiple tools into one read
Recurring task automation with smart routing based on workload
Document filing and labeling from email or upload
Compliance reminder workflows for licensing or insurance renewals
Most owners pick one category to start, build three workflows that share a discovery foundation, and then add a fourth or fifth later when they're confident the system actually saves the time it promises.
Categories are abstract. Here's what an actual workflow looks like, start to finish, so you can picture yours.
Follow-up · property management
Tenant inquiry triage
A tenant emails. The workflow reads the message, pulls that tenant's unit, lease status, and any open work orders, then drafts a reply and categorizes the request (maintenance, payment, renewal, complaint, urgent). The draft lands in your queue. You glance at it, approve, and it sends. A Saturday-morning "when's rent due" gets answered in an hour instead of Monday afternoon. One trigger (tenant email), one outcome (drafted reply). That's one workflow at $750.
Scheduling · fitness studio
Booking confirmation and review request
A client books a class. The workflow sends a confirmation, a reminder the day before, and (after the class actually happens) a review request timed to the moment they're most likely to say yes. No-shows drop. Google reviews climb without you chasing anyone. This is actually two workflows: the booking confirmation and the post-class review request have different triggers. Two headaches, so it fits the $1,500 tier.
How a workflow is built
The build sequence is the same regardless of category: a 20-minute discovery call to pick the actual problem, a scoping doc that names the trigger and the action precisely, a build week, a test run on your real data, a walkthrough, and a written handoff guide so you understand exactly what's running.
Most workflows ship in about a week. Some categories take longer. Vendor coordination is usually the heaviest because it depends on how your work order system is set up. Quoting workflows depend on how messy your template library is. I'll tell you the real timeline on the call.
What I won't build
I won't build a workflow that auto-sends messages to frustrated customers without human approval. The cost of one tone-deaf reply is way higher than the cost of a five-second approval click.
I won't build a "chatbot" that pretends to be you. If a customer asks a question your business should answer, your business should answer it. AI drafts in your voice; humans review and send. That's the line.
I won't build workflows that try to replace your judgment. If a category requires real decisions, the workflow's job is to gather the context and surface the choice, not make the decision.
How pricing maps to these categories
One less thing is $750. A few less things, the recurring annoyances handled together, is $1,500. Most of the list gone, a whole part of your business running itself, is $3,000. The whole list, AI wired across the entire operation, starts with a conversation, not a price.
One trigger, one outcome. A tenant emails and a reply gets drafted is one workflow. A new lead enters your CRM and a follow-up sequence runs is a second workflow. They can share the same data, but each starting point is its own workflow. If you can't tell how to count yours, that's what the free call is for.
Which workflow should I start with?
Whichever task drains the most time and runs on the clearest rules. For most small businesses that's follow-up, because the work is fragmented and the cost of dropping it is high. The two-minute quiz on the home page points you to three workflows worth starting with.
Can a workflow use the tools I already pay for?
Yes, almost always. Most workflows run on Zapier or Make for automation, Google Sheets or Airtable for the data, and ChatGPT or Claude for the language. If you already pay for some of these, the build uses them. No new platform to migrate to.
Will the AI message my customers automatically?
Only if you want it to, and I rarely recommend it. The default is AI drafts, you approve, it sends. The cost of one tone-deaf message to a frustrated customer is much higher than a five-second approval click.
How long does a workflow take to build?
About a week for a single workflow: a discovery call, the build, a test run on your real data, and a handoff. Some categories take longer. Vendor coordination and quoting depend on how your existing systems are set up. I give you the real timeline on the call.
Want help picking the right workflow?
Twenty minutes on the phone. Free. Tell me what's draining your week.
