AI AND AUTOMATION BY RUDOLPH ALEJANDRIARudolph Alejandria

Yes to what works. No to what doesn't.

Do more without hiring more. AI and automation from an ops manager who helped grow a practice 130x.

Scroll
Results

What this did at a real practice

Valisthea Psychiatry is fictional. These four figures are from a real US psychiatry practice where I ran operations.

  • Weeks to about an hour for a pay run, once I wrote it in code. It now runs twice a month.
  • 30-40% less manual admin work, estimated, after I rolled out AI tools for documentation, intake and analytics.
  • 45% to 80-90% collection rate, after I redesigned billing follow-up.
  • 130x patient volume growth in under 2 years, while I ran operations.
01Weeks to about an hour

for a pay run, once I wrote it in code. It now runs twice a month.

0230-40% less

manual admin work, estimated, after I rolled out AI tools for documentation, intake and analytics.

0345% to 80-90%

collection rate, after I redesigned billing follow-up.

04130x

patient volume growth in under 2 years, while I ran operations.

The team

Valisthea OS

Valisthea Psychiatry is fictional and every figure is from my own testing.

The layer that runs all the automations.

Each automation works on its own, but nothing watches them together. So I built a small team of AI employees, each with one job. Shown with sample data.

AI employee

Ivy

Writes the morning brief from every automation's logs: what ran, what failed, what needs a decision.

AI employee

Nora

Answers staff policy questions with the exact quote from the policy.

AI employee

June, chief of staff

Checks their work every Friday and writes a lesson when one gets something wrong.

Valisthea Psychiatry is fictional. A sample day.

A 3D model of the fictional Valisthea Psychiatry office: Ivy, Nora and June at their desks, four machines for GoHighLevel, n8n, Make and Zapier, and a table of intake trays.
Fictional
Sample run

A sample day

Valisthea Psychiatry is fictional and every figure is from my own testing. The times are a sample day.

Fictional

Chapter 17:30 AM

Before

The owner shouldn't have to ask anyone for the numbers.

Ivy writes the morning brief

After

From every automation's logs: what ran, what failed, what needs a decision.

Fictional

Chapter 28:05 AM

Before

Every new inquiry needs a fast reply and an owner, even from people the practice can't see.

A new inquiry gets a reply in seconds

After

It lands as a pipeline card with an owner. A form sent twice still makes one contact.

The result · Sample run · Fictional
4 for 4

test inquiries became pipeline cards

Fictional

Chapter 39:00 AM

Before

Every inquiry needs sorting: ready, needs info, not a fit, or urgent.

Intake sorts every inquiry

After

Ready, needs info, not a fit, or urgent. In testing: 209 ready, 60 need info, 8 urgent.

The result · Sample run · Fictional
209

ready, 60 need info, 8 urgent

Fictional

Chapter 411:00 AM

Before

Staff ask questions the written policies already answer.

Nora answers a staff question

After

She answers with the exact quote from the policy.

Fictional

Chapter 51:00 PM

Before

Provider pay has to be right every month, and big swings need a second look.

The pay run holds one line for a second look

After

13 pay statements approved, $95,403.92. One line held because the pay was down 37.5%.

The result · Sample run · Fictional
$95,403.92

13 statements approved, 1 line held

Fictional

Chapter 63:00 PM

Before

Review requests need good timing, and not at night.

A review request goes out

After

It arrives 2 hours after the visit. A click on the link ends the run, so no reminder follows.

The result · Sample run · Fictional
2 hours

after the visit

Fictional

Chapter 7Fri 5:30 PM

Before

Each automation works on its own, but nothing watches them together.

June checks the team

After

At the end of the week she checks their work and writes a lesson when one gets something wrong.

Sample run

The day's total

Valisthea Psychiatry is fictional and every figure is from my own testing. The times are a sample day.

Valisthea Psychiatry
Valisthea Psychiatry is fictional. A sample day.
  1. 7:30 AMIvy

    what ran, what failed, what needs a decision

  2. 8:05 AMSpeed to Lead4 for 4Fictional

    test inquiries became pipeline cards

  3. 9:00 AMIntake209Fictional

    ready, 60 need info, 8 urgent

  4. 11:00 AMNora

    the exact quote from the policy

  5. 1:00 PMPay Run$95,403.92Fictional

    13 statements approved, 1 line held

  6. 3:00 PMReviews2 hoursFictional

    after the visit

  7. Fri 5:30 PMJune

    writes a lesson when one gets something wrong

  8. Total, 7 moments

    Nothing is sent, deleted or paid without the owner. They prepare it, and the owner decides.

How I work

I'll tell you when not to automate.

01

Half the time the fix is a better process, not another tool. I map it first and tell you which one you need.

02

I ran payroll by hand before I automated it. A pay run that took weeks now takes about an hour. So I build for the bad day, not the demo: no double counting, failures that alert a person, bad data turned away with a reason.

03

You get the documentation and the logins. Nothing only I can fix.

Model + harness + environment

The model is a third of the job.

Most people pick a model and stop there. What you get out of AI depends on three parts working together, and I spend most of my time on the last two.

Model

The LLM doing the thinking. Claude, GPT or Gemini, picked for the job, not out of loyalty.

Harness

Everything wrapped around it: the tools it can call, the steps it follows, what it remembers, and the checks it has to pass. Mine use a second model to review the first, and test cases.

Environment

What it can see and touch: your data, your rules and the apps it connects to, set up so mistakes are hard to make and easy to catch before they reach a customer.

Services

Front office

A reply within seconds, day or night

A Harvard Business Review study found a lead answered within an hour is nearly 7 times as likely to turn into a real conversation as one answered an hour later. Mine get a reply within seconds, day or night. Missed calls get a text back, reminders cut no-shows, and patients who drifted away get invited back. For the phone itself, I wrote the setup and the test plan for a clinic's AI phone agent.

  • GoHighLevel
AI with a person in charge

An estimated 30-40% less manual admin work

That was the drop when I rolled out AI tools for documentation, intake and analytics at a US practice. AI drafts the reply or answers the routine question. A person approves anything that leaves the building.

  • n8n
  • Claude
  • ChatGPT
  • Gemini
  • Grok
  • DeepSeek
  • Kimi
  • Qwen
When no-code hits a wall

A pay run that took weeks now takes about an hour

Contractor pay with different rates, payers and splits was too much for a no-code tool, so I wrote it in code. I checked it against past pay runs before it went live, and it now runs twice a month.

  • Claude Code
  • Codex
Back office

Collection rate up from 45% to 80-90%

That came from redesigning billing follow-up at a US practice. The builds match payments to visits, check contractor pay before it goes out, and clean intake data before it reaches your team.

  • n8n
  • Make
  • Zapier
Work

Sixteen builds across four tools.

Valisthea Psychiatry is a fictional practice, so every name and number here is synthetic. I built 16 automations for it, then a layer that runs them. Each card has the problem and a result from my own testing.

GoHighLevelF1

Speed to Lead

Sample data, fictional

4 for 4

test inquiries became pipeline cards

The problem
Every new inquiry needs a fast reply and an owner, even from people the practice can't see.
The result
4 test inquiries made 4 pipeline cards, assigned in turn. A form sent twice made one contact.
GoHighLevelF3

Website and Booking

Sample data, fictional

Round robin

booked slot closed on that provider's other calendars

The problem
Patients need to book online without a provider being double-booked.
The result
Test bookings went round robin to a provider, and the booked slot closed on that provider's other calendars.
GoHighLevelF4

Reminders and No-shows

Sample data, fictional

At once

a cancel stopped its reminders

The problem
Visits need confirming and reminding, and missed ones need a follow-up.
The result
Cancelling a visit stopped its reminders at once. Moving a visit started fresh ones for the new time.
GoHighLevelF5

Reviews

Sample data, fictional

2 hours

after the visit

The problem
Review requests need good timing, and not at night.
The result
The request arrived 2 hours after the visit. A click on the link ended the run, so no reminder followed.
GoHighLevelF6

Reactivation

Sample data, fictional

15 s

from a YES reply to a booking email

The problem
Patients not seen in 90 days drift away.
The result
63 on the lapsed list. A YES reply got a booking email in 15 seconds.
GoHighLevelF7

Partner Pipeline

Sample data, fictional

1 min

from a card move to the intro email

The problem
Referral partners go quiet when nobody follows up.
The result
The intro email went out a minute after the card moved, and 10 idle cards became tasks.
GoHighLevelF9

Owner Dashboard

Sample data, fictional

1 page

for the last 30 days

The problem
The owner shouldn't have to ask anyone for the numbers.
The result
One page for the last 30 days: 9 new leads, 8 appointments, 10 partners.
n8nX1

GoHighLevel Bridge

Sample data, fictional

461 / 0

test checks / failed

The problem
New inquiries in GoHighLevel need to reach intake.
The result
461 test checks, 0 failed. The first live run found 5 contacts and wrote all 5 with no failures.
n8nB1

Pay Run

Sample data, fictional

$95,403.92

13 statements approved, 1 line held

The problem
Provider pay has to be right every month, and big swings need a second look.
The result
13 pay statements approved, $95,403.92. 1 line held because the pay was down 37.5%.
n8nB2

Billing Check

Sample data, fictional

282

left open on the tracker

The problem
Every payment must match a visit, and the odd ones need flagging.
The result
A repeat run found no new problems and left 282 open on the tracker.
n8nB3

Intake

Sample data, fictional

209

ready, 60 need info, 8 urgent

The problem
Every inquiry needs sorting: ready, needs info, not a fit, or urgent.
The result
209 ready, 60 need info, 8 urgent.
n8nB4

Provider Check

Sample data, fictional

46

people checked

The problem
Each provider's registry, exclusion, license, DEA and malpractice dates need checking.
The result
46 people checked: 16 clear, 27 action needed, 3 not checked.
n8nB5

Inbox Triage

Sample data, fictional

78

replies drafted, 11 quarantined

The problem
A shared inbox needs sorting by team, and suspicious mail needs keeping apart.
The result
78 replies drafted for approval, 11 quarantined.
n8nB6

Policy Answers

Sample data, fictional

13 / 13

gaps answered "not in the policies"

The problem
Staff ask questions the written policies already answer.
The result
13 of 13 questions the policies don't cover were answered "not in the policies", not guessed.
MakeM1

Onboarding

Sample data, fictional

3 of 5

hires set up, 2 held with a reason

The problem
New hires need tasks, a contract and a manager email, and overdue tasks need chasing.
The result
Of 5 test hires, 3 were set up and 2 were held with an email saying why.
ZapierZ1

Owner Alert

Sample data, fictional

About 3.5 min

from the check to the alert

The problem
The owner should hear the provider check results the moment the check finishes.
The result
The alert arrived about 3.5 minutes after the check.
About
Rudolph Alejandria

About me

I'm a licensed pharmacist who moved into operations. I've led operations, finance and logistics teams, and I'm on the leadership team of a US psychiatry practice that grew from a handful of appointments to more than 1,800 a month in under two years.

I build my own tools too. I run a team of AI agents I made in Claude Code that handles my daily brief, sorts my inbox and checks payroll, each with a reviewer and test cases.

I'm based in the Philippines and work Pacific time.

7 years

of double-digit growth at a Philippine supply and logistics business I've helped run since 2017

25‑50%

supplier cost cuts I negotiated for that business

Tools
Automation
n8n, Make, Zapier, GoHighLevel
AI
Claude Code, Codex, Claude, ChatGPT, Gemini, Grok, DeepSeek, Kimi, Qwen
Video and visuals
HyperFrames, HeyGen, Higgsfield
Building
Lovable, GitHub, Cloudflare
Knowledge and work
Obsidian, Google Workspace
Training
  • HighLevel CRM, Tara AI Community, 2026
  • AI Automation with n8n, Technical Virtual Assistants PH, 2026
  • Prompt Engineering, Tara AI Community, 2026
  • Make.com, Technical Virtual Assistants PH, 2026
  • Zapier, Technical Virtual Assistants PH, 2026
  • HIPAA Awareness, HIPAATraining.com, 2025

Questions

Who is Rudolph Alejandria?

Rudolph Alejandria is a licensed pharmacist who moved into operations. He has led operations, finance and logistics teams and is on the leadership team of a US psychiatry practice. He runs No Yes Men, is based in the Philippines and works Pacific time.

What is No Yes Men?

No Yes Men is Rudolph Alejandria's AI and automation practice. It builds automations and AI tools for businesses that want to do more without hiring more, and it says plainly what won't work before anything gets built.

What does No Yes Men automate?

The work people do by hand every day: the front desk, follow-ups, billing, payroll checks, reports and inboxes. Most of the work so far has been in US healthcare operations.

What tools does it use?

GoHighLevel, n8n, Make, Zapier and Claude Code, picked to fit the tools a business already has.

How do I start?

Book a call. You get an honest read on what is worth automating and what isn't, before any money is spent.

Tell me what's eating your team's week.

30 minutes on Zoom. You'll leave with a straight answer on what's worth automating, even if it's nothing.

Book a call