Automation & RPA Consulting

The shortcut: Half of RPA consultants sell expensive bots to clients who actually need a better spreadsheet — or a Power Automate flow they're already paying for and don't know it. Diagnose the process before you scope a tool, and lead with Power Automate inside Microsoft 365 shops because the license is already on the invoice.

Industry: Software & Tech | Investment level: Small — $2,000-$10,000 | Time to launch: 4-8 weeks (UiPath/Power Automate cert + one documented pilot gate the launch) Best for: A developer or analyst who can read someone else's broken Excel macro, sit through a 45-minute "show me what you do every Monday" walkthrough without losing patience, and explain to a non-technical operations manager why the bot will break the next time IT changes the login screen. What you'll likely make: $2,000-$3,500 month 3, $5,000-$9,000 month 6, $10,000-$18,000 month 12 (one or two builds plus a small maintenance retainer book). Math is in Section 4.

Market Opportunity

The dirty secret of RPA is that most "bots" sold to small and mid-size businesses are wallpaper over a process nobody bothered to fix. The AP clerk copies invoice data from a PDF into SAP because SAP has no API. A consultant builds a UiPath bot to mimic the clerk's clicks. Six months later, SAP pushes a UI update, the bot crashes silently, the clerk goes back to copy-paste, and the client calls the consultant who's now on a new contract.

That's the failure pattern. It's also the opportunity. The consultants who survive diagnose the process first, recommend the cheapest tool that solves it (often Power Automate, sometimes Zapier, occasionally a 30-line Python script), and price ongoing maintenance from day one.

The crowded part is "we do RPA" generalists fighting over UiPath enterprise gigs. The quiet part is the SMB segment running on Microsoft 365 Business Premium ($22/user/month, Microsoft 365 plan comparison) where Power Automate is already included in the seat license. Most of those clients have no idea they're paying for it. You walk in, automate three approval workflows in a week, and they pay you $4,000-$6,000 because it feels like magic — the tool was already in their tenant.

Launch With AI

Pro section. AI is the entire pitch — but most RPA consultants never use it on their own practice. They write process audits in Word, draft SOWs from scratch, and respond to bot-broke 9pm pages without observability. Eat your own dog food: AI for the audit doc, AI for the bot logic generation, AI for the bot-broke triage. The hours you reclaim get spent on what AI can't do — sitting in the AP clerk's chair watching what she actually does, refusing the bot when the answer is a better spreadsheet, and walking the IT director through service-account hygiene before bot one ships.

The trap most first-year RPA consultants fall into: they think AI generates the bot for them. Backwards. AI generates a bot that looks right, runs once, and silently corrupts the next 1,000 invoices because nobody verified the path-coverage. AI is for the writing tail (audits, SOWs, retainer reports) AND for the bot's exception handling design — but every Power Automate flow + every UiPath workflow gets your eyes on it before it goes to production.

Important up-front: AI cannot sit the process audit, refuse the client whose problem is actually a missing API, or walk IT through service-account credentials. It will also confidently generate UiPath code that uses deprecated activities. You own every bot, every credential decision, every exception handler; AI scales the writing and the boilerplate around them.

AI Tools You'll Use

Tool	Price	What it does
ChatGPT Plus	$20/mo	Process audit deliverables, SOW templates, sales follow-ups, retainer reports
Claude Pro	$20/mo	Long-context process documentation review, multi-system workflow analysis
Cursor + Copilot	$20-$40/mo	Power Automate JSON, UiPath XAML review, scoped Python/PowerShell scripts
Power Automate Copilot / UiPath AI Center (built-in)	included with platform	Flow generation, document AI, exception suggestion, anomaly detection
Loom AI	free	Bot walkthroughs, client training videos, retainer monthly summaries

The Workflow

Process audit deliverable (Claude long-context, ~3 hours/client). The 1-2 week audit decides whether the client gets a bot or a better spreadsheet. Paste the recorded employee shadowing notes + their current process docs into Claude:

"Below are my notes from shadowing 5 employees over 1 week at [client, Microsoft 365 Business Premium shop, 80 employees]. Tasks observed: [paste]. Generate the audit deliverable: (a) the 1-page roadmap — for each task, the hours-saved-per-month + the recommended tool (Power Automate / Zapier / Make / UiPath / 'fix the spreadsheet first / fix the source system first'), (b) the 3 tasks that should NOT be automated (broken process, low volume, source system about to be replaced), (c) the build cost vs annual savings ROI per recommended automation, (d) the priority order for the first 90 days. Tone: senior consultant respectful of the client's existing licenses (Power Automate is in their seat). NEVER recommend UiPath when Power Automate suffices. Output as a 6-page Notion-ready audit doc."

Read every recommendation. Half your audits should end with 'don't automate this — fix the spreadsheet' — that filter is what builds the trust that wins every future bot.
Power Automate flow generation (Power Automate Copilot + Cursor, ~30 min/flow). For each automation in the audit, generate the flow with platform AI + verify with Cursor. In Power Automate Copilot:

"I need a flow: when an invoice email lands in invoices@client.com, extract the vendor, amount, and PO number from the PDF attachment, save the PDF to SharePoint /Invoices/[Year]/[Vendor], create a row in QuickBooks Online with vendor + amount + PO + PDF link, and post a Teams message to #ap-channel with vendor + amount + 'approve in QBO?' button. If extraction confidence is below 85%, route to manual-review SharePoint folder instead. Generate the flow."

Open the JSON in Cursor. Verify: (a) the document AI confidence threshold + manual-review fallback, (b) the SharePoint path matches naming convention, (c) the Teams approval button posts back to the right channel. The 30-min review per flow is what protects you from a silently-corrupted invoice run.
Bot-broke triage runbook + Loom training (Cursor + Loom AI, ~60 min/bot). Every bot needs a runbook for when it breaks. Paste:

"I just shipped a [Power Automate / UiPath] bot that does [task]. Generate the bot-broke runbook: (a) the 5 most likely failure modes (source UI change, credentials expired, downstream API rate limit, file format change, network timeout) with the 1-line diagnostic per mode, (b) the 5-min initial-response checklist (where to look, what to test, how to roll back), (c) the client-facing 'we paused the bot, here's why' email template, (d) the maintenance retainer-funded fix vs out-of-scope fix decision tree, (e) the post-incident report template. Output as Notion-ready runbook + a 4-min Loom script I record + send to the client's IT contact."

Loom AI auto-titles + transcribes the training video. The runbook + Loom is what justifies the $750/month retainer — without it, every break is an emergency.
Service-account hygiene + SOW boilerplate (ChatGPT, ~20 min one-time). Service-account credentials are the legal trap. Paste:

"I'm a freelance RPA consultant. Build the service-account + IT-handover boilerplate I'll insert into every SOW: (a) every bot runs under a documented service account (NEVER an employee's personal credentials), (b) the client's IT team owns the service account + rotates credentials per their policy, (c) I document the bot's permission scope in writing (read which folders, write to which systems), (d) the bot's disable-in-60-seconds procedure (the IT contact + the kill-switch), (e) my E&O policy details + liability cap at fees paid trailing 12 months. Output as paste-ready SOW clauses."

Without this clause, one ex-employee + one personal-credential bot = a bot that suddenly runs unauthorized. The clause is your liability shield.
Monthly retainer report + UI-change tracker (ChatGPT, ~20 min/client/month). Bots break when source UIs change — that's the deal. Paste:

"I run the RPA maintenance retainer for [client]. This month: (a) [bot 1] ran [N] times, [N] successful, [N] failed (failure cause: source UI change in [system]), (b) [bot 2] ran [N] times, all successful, (c) I patched [bot 1] for the new UI within [time]. Generate the 1-page client retainer report: (a) bot uptime per workflow, (b) hours saved this month vs baseline, (c) what I patched and why, (d) what I'm watching for next month (vendor patch deployment, API deprecation), (e) one strategic recommendation. Tone: senior advisor. Output as Notion-ready 1-pager."

Send first business day of every month. The retainer renews itself when the client sees a real uptime + savings memo, not just an invoice.

Time Saved Per Week

Roughly 6-9 hours/week once your audit template, service-account boilerplate, and retainer report format are built:

Process audit deliverable: 6 hours/client → 3 hours (Claude long-context)
Flow generation: 90 min/flow → 30 min (Power Automate Copilot + Cursor verification)
Bot-broke runbook + training: 3 hours/bot → 60 min (Cursor + Loom AI)
Service-account boilerplate: one-time → reused on every SOW
Retainer monthly reports: 60 min/client → 20 min (ChatGPT template)

Trade that time for: 5 cold messages/day to ops managers, the second UiPath certification ($150), and the LinkedIn talk you've been delaying.

Total AI Stack Cost

Budget tier ($20/mo): ChatGPT Plus only. Power Automate Copilot is free with the M365 license; UiPath Community is free under size threshold; Loom AI free. Right for first 90 days.
Full tier ($60/mo): ChatGPT Plus + Claude Pro + Cursor. Worth it once you sign anchor client 2 — Claude long-context on multi-system workflow analysis alone saves 3+ hours per audit.
Compare: A junior RPA dev for audit + flow generation + retainer reports runs $4,000-$8,000/mo. The full AI stack is one-hundredth that cost — and you keep eyes on every flow before production.

Cancel anything you don't open in a 7-day window. Pick UiPath OR Automation Anywhere (not both) for your secondary platform — Power Automate is always primary in M365 shops.

Your First Win

30 minutes from now your "API check" elimination filter is built. Open ChatGPT (free tier works). Paste:

"I'm a freelance RPA consultant. Build me a 1-page client filter I'll run BEFORE quoting any bot — the 'do they actually need RPA?' diagnostic: (a) the 8 questions I ask in the discovery call (Does the source system have an API? — if yes, recommend integration, NEVER RPA. Does the process change frequently? — if yes, RPA will break. Does the volume justify the build cost? — if under 10 hrs/month saved, recommend a better spreadsheet. Is the client on Microsoft 365 Business Premium? — if yes, lead with Power Automate. Does the workflow need human approval? — yes, build the approval into the flow. Does the source system have a UI that changes? — yes, scope the maintenance retainer. Does the data touch PII or PHI? — yes, scope the credential + audit trail.), (b) the 4 'don't automate this — do this instead' alternatives (better spreadsheet, vendor API, native platform automation, process redesign), (c) the 1-paragraph 'why I'm declining this bot' template I send when the answer is 'don't automate.' Tone: senior consultant. NEVER 'I'd love to help' eager filler."

Use the filter on every discovery call. Half your prospects should leave the call WITHOUT a bot quote — that filter is the trust that wins the next 5 referrals from the same client. Worth more than your first 6 retainers combined.

Product / Service Offering

You sell one of three things. Pick which you lead with before your first sales call.

Process audit + automation roadmap. A 1-2 week paid engagement: shadow 3-5 employees, document repetitive tasks, score each by hours-saved-per-month vs build cost. Deliverable: a one-page roadmap naming what to automate, what tool to use, and what to leave alone. $2,000-$5,000. The right starter — it filters out clients whose real problem is a better spreadsheet.
Single-process automation build. One workflow built end-to-end in Power Automate, UiPath, or Zapier. Invoice intake from email to QuickBooks. Weekly reports across SharePoint and Excel. New-hire provisioning across HR/email/Slack. $3,000-$10,000, 1-3 weeks. Bread-and-butter once you've shipped two roadmaps.
Maintenance retainer. Bot monitoring, UI-change patches, log review, quarterly process re-scoring. $400-$1,500/month. Sell it in the same proposal as the build, not three months later when the bot is already broken.

Standard stack: UiPath Community Edition (free for individuals and companies under 250 employees / under $10M revenue), Power Automate (already in Microsoft 365 Business Premium), Automation Anywhere Community when the client is standardized on it, Zapier and Make for API-based glue work that doesn't need a true RPA bot.

The most important sentence in your sales call: "If your source system has an API, you don't need RPA — you need an integration, and it'll cost 30% less and break 90% less." Saying that loses you a few bot-shaped projects. It earns you the trust to win every other one in the building.

Revenue Model

Unit economics for a solo consultant working off a laptop, no employees, billing through Stripe:

Service	Price	Variable cost (tool licenses + Stripe)	Build time	Take-home per project
Process audit + roadmap	$3,500	$0 (Community editions) + $101.80 (Stripe 2.9% + $0.30)	1-2 weeks	~$3,400
Single-process Power Automate build	$5,000	$0 (client owns license) + $145.30	1-2 weeks	~$4,855
Single-process UiPath build (SMB)	$7,500	$0 (Community) or $420/mo Pro pass-through + $217.80	2-3 weeks	~$7,280
Maintenance retainer	$750/mo	~$50 (monitoring tools) + $22.05	3-5 hrs/mo	~$680/mo

Your first $1K month = one process audit at $3,500 with 30% deposit upfront = $1,050 in the door. Roughly two days of focused interview work plus a write-up.

Your first $3K month = one Power Automate build at $5,000 (50% deposit, $2,500) + one $750 retainer signed = $3,250 in the door. Roughly one week of build plus 4 hours of retainer maintenance.

The retainer is the real business. Bots break when source UIs change, and source UIs always change — that's the deal. Six retainers at $750 is $4,500/month base before any new build closes. Sell the retainer at proposal time as a percentage of build value (10-15%/month is the normal range), not as an afterthought when something breaks.

Startup Costs

UiPath certification: UiPath Certified Professional Automation Developer Associate exam is $150. Academy course content is free. Single biggest credibility purchase in the first 30 days.
Automation Anywhere certification (optional): Automation Anywhere Certified Advanced RPA Professional is $149. Skip unless your prospect base is already on AA.
Microsoft 365 Business Premium for your own tenant: $22/month, ~$264/year. Build Power Automate flows on your own data to demo them.
Tool licenses: UiPath Community is free under the size threshold. Power Automate Premium add-ons start at $15/user/month, billed as pass-through.
GitHub or Azure DevOps: $4-$6/user/month. One repo per client.
LLC + EIN: $35-$500 LLC filing — see the LLC University 50-state table. EIN is free at IRS EIN Online — never pay a third party.
E&O insurance: $800-$2,000/year. Quote via Hiscox or Insureon. A bot that posts a duplicate $80,000 invoice to a client's ERP is exactly the claim E&O exists for.
Contracts: $200-$500 attorney review of an MSA + SOW template from Bonsai — must include bot service-account language.

Realistic all-in: $2,000 if you self-cert, defer insurance 30 days, and use Microsoft 365 Personal for demos; $10,000 if you take both certifications, bind insurance year one, and pay for a full attorney review before the first signed contract.

Legal & Formation

Business entity. Single-member LLC the moment you take a paying client. A bot you built that mass-emailed 4,000 customers because of a stuck loop is a much smaller problem when the lawsuit names your LLC, not your house. Filing fee runs $35-$500 — see the LLC University 50-state table. EIN is free at IRS EIN Online — never pay a third party. Once net profit clears $80K-$100K/year, run the math on an S-corp election via IRS Form 2553.

Licenses & sales tax. No state professional license is required for RPA consulting. Custom development billed as a professional service is generally not taxable. The wrinkle: the moment you host bots on your infrastructure and bill recurring access (managed-bot service, hosted orchestrator, monitoring dashboard), about 25 states treat that recurring access as taxable SaaS. Cross $100K in sales or 200 transactions in any state and you have economic nexus there — see the Avalara state SaaS tracker. Use Stripe Tax or Avalara if you're billing recurring across states.

Industry-specific risk. Three traps will kill an RPA consulting practice if you don't address them in writing before the first bot runs.

First, service-account credentials. An unattended bot logging into a client's ERP under an ops manager's personal credentials is an audit finding in any regulated industry — and a personal-liability disaster if that manager gets fired and you lose access overnight. Every bot runs under a documented service account with scoped permissions, named in the SOW. The client's IT team owns the account. You document what the bot does, when it runs, what it touches, and how to disable it in 60 seconds.

Second, scope-creep through "while you're at it." RPA scoping rots faster than any other software work because the client keeps asking "while you're in there, can you also automate X?" Each one is a 4-hour change order minimum. Send a one-page scope document — what's in, what's out, what triggers a change order — before every build.

Third, no maintenance promise without a maintenance retainer. Bots break when source UIs change — not a defect in your work, just how RPA operates. Your contract needs an explicit clause: bot reliability depends on stability of source applications outside your control, you do not warrant ongoing operation absent a maintenance retainer, and emergency fixes outside the retainer are billed at a posted hourly rate ($150-$250/hour is standard). Cap total liability at fees paid in the prior 12 months.

Marketing & First Customers

Your first 3 paying clients come from people who already know you can ship work. After that:

Direct outreach to 30 ops managers in Microsoft 365 shops. Use Apollo or LinkedIn Sales Navigator to filter ops/finance/HR managers at 50-500-person companies on Microsoft 365 Business Premium. Two-sentence message: "I help Microsoft 365 shops automate the 5-10 manual workflows you're already paying Power Automate to do — no new tools, no new licenses. Free 20-minute audit?" Send 10-15/day. Reply rate 3-6%, call-to-paid 15-25% on a $3,500 audit. Fastest path to month-three revenue.
Process-audit lead magnet. A 2-page PDF titled "7 workflows in your Microsoft 365 tenant Power Automate can run today." Names specific flow templates (invoice approvals, new-hire onboarding, contract signature routing). Converts 8-12% to paid audit calls when promoted on LinkedIn.
UiPath Marketplace + community presence. Post one reusable component on the UiPath Marketplace and answer 3-5 questions a week on the UiPath Community Forum. Slow burn (2-3 inbound leads/quarter) but the leads already have UiPath licenses.
Chamber of Commerce + industry associations. SMB ops managers go to these. One 20-minute talk titled "Three workflows your team is doing manually that Microsoft already automated" lands 1-2 audit clients per event.

Skip generic "we do automation" landing pages. The lead is the audit, not the build.

First 90 Days

Week 1. File LLC. Get free EIN. Start the UiPath Academy Automation Developer Associate path.
Week 1-2. Pass the UiPath Certified Professional exam ($150). Add the credential to LinkedIn the day you pass.
Week 2-3. Build two demo bots on your own data: one Power Automate flow (invoice email → SharePoint → Teams) and one UiPath bot (legacy desktop app → Excel → web form). Capture both as 90-second Loom videos.
Week 3-4. Attorney reviews MSA + SOW with service-account and bot-maintenance language. Bind E&O insurance. Set up Stripe.
Week 4-6. Send 30 cold messages to ops managers in Microsoft 365 shops. Land 1 paid audit at $2,500-$3,500.
Week 6-8. Deliver the audit. Convert it to a $5,000-$7,500 build with a $750/month retainer attached.
Week 8-10. Ship the build. Document a case study with hours-saved-per-month and dollar value. Post on LinkedIn.
Week 10-12. Raise audit price to $4,000. Land 1 more audit and 1 more build. Target: 2-3 paying clients, 1-2 retainers, ~$8,000-$12,000 in 90-day revenue.

Common Pitfalls

Selling a bot when the client needs a process redesign. Three out of four RPA pilots quietly fail because the underlying process was broken before automation arrived — you just made the broken process run faster. Run a paid 1-2 week audit before any bot quote. Half your audits should end with "don't automate this — fix the spreadsheet first." The half that proceed convert at 80%+ and never come back complaining.
Quoting UiPath when Power Automate is on the client's invoice. UiPath Pro runs $420+/month per developer. If the client is on Microsoft 365 Business Premium, Power Automate is already in their seat license and ships 80% of SMB use cases. Quoting UiPath in that scenario costs the client $5,000+/year in needless licensing and burns your credibility the moment a sharper consultant points it out. Reach for UiPath only when the use case needs it — heavy unattended desktop work, complex orchestration, regulated audit requirements.
Running bots under personal credentials. A bot logging into the client's ERP as an ops manager's user account is one HR transition away from a production outage and a finger pointed at you. Every bot gets a documented service account named in the SOW. The hour you spend negotiating this with IT in week one saves you a $20,000 emergency call in month nine.
Treating maintenance as a phase-two conversation. Bots break — that's the deal with RPA, not a defect in your work. Source UIs change, vendor patches ship, an employee renames a SharePoint folder. Quote the retainer in the same proposal as the build, not three months later. Clients who hear "$7,500 build" without "$750/month maintenance" assume the bot runs itself forever, then disappear when it stops — and the next consultant replaces you on every future engagement.

Get your full launch plan — take the free 60-second quiz.