Chapter 17:30 AM
BeforeThe owner shouldn't have to ask anyone for the numbers.
Ivy writes the morning brief
From every automation's logs: what ran, what failed, what needs a decision.

Do more without hiring more. AI and automation from an ops manager who helped grow a practice 130x.
Valisthea Psychiatry is fictional. These four figures are from a real US psychiatry practice where I ran operations.
for a pay run, once I wrote it in code. It now runs twice a month.
manual admin work, estimated, after I rolled out AI tools for documentation, intake and analytics.
collection rate, after I redesigned billing follow-up.
patient volume growth in under 2 years, while I ran operations.
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.
Writes the morning brief from every automation's logs: what ran, what failed, what needs a decision.
Answers staff policy questions with the exact quote from the policy.
Checks their work every Friday and writes a lesson when one gets something wrong.
Valisthea Psychiatry is fictional and every figure is from my own testing. The times are a sample day.
Chapter 17:30 AM
BeforeThe owner shouldn't have to ask anyone for the numbers.
From every automation's logs: what ran, what failed, what needs a decision.
Chapter 28:05 AM
BeforeEvery new inquiry needs a fast reply and an owner, even from people the practice can't see.
It lands as a pipeline card with an owner. A form sent twice still makes one contact.
test inquiries became pipeline cards
Chapter 39:00 AM
BeforeEvery inquiry needs sorting: ready, needs info, not a fit, or urgent.
Ready, needs info, not a fit, or urgent. In testing: 209 ready, 60 need info, 8 urgent.
ready, 60 need info, 8 urgent
Chapter 411:00 AM
BeforeStaff ask questions the written policies already answer.
She answers with the exact quote from the policy.
Chapter 51:00 PM
BeforeProvider pay has to be right every month, and big swings need a second look.
13 pay statements approved, $95,403.92. One line held because the pay was down 37.5%.
13 statements approved, 1 line held
Chapter 63:00 PM
BeforeReview requests need good timing, and not at night.
It arrives 2 hours after the visit. A click on the link ends the run, so no reminder follows.
after the visit
Chapter 7Fri 5:30 PM
BeforeEach automation works on its own, but nothing watches them together.
At the end of the week she checks their work and writes a lesson when one gets something wrong.
Valisthea Psychiatry is fictional and every figure is from my own testing. The times are a sample day.
what ran, what failed, what needs a decision
test inquiries became pipeline cards
ready, 60 need info, 8 urgent
the exact quote from the policy
13 statements approved, 1 line held
after the visit
writes a lesson when one gets something wrong
Nothing is sent, deleted or paid without the owner. They prepare it, and the owner decides.
Half the time the fix is a better process, not another tool. I map it first and tell you which one you need.
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.
You get the documentation and the logins. Nothing only I can fix.
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.
The LLM doing the thinking. Claude, GPT or Gemini, picked for the job, not out of loyalty.
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.
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.
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.
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.
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.
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.
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.
4 for 4
test inquiries became pipeline cards
Round robin
booked slot closed on that provider's other calendars
At once
a cancel stopped its reminders
2 hours
after the visit
15 s
from a YES reply to a booking email
1 min
from a card move to the intro email
1 page
for the last 30 days
461 / 0
test checks / failed
$95,403.92
13 statements approved, 1 line held
282
left open on the tracker
209
ready, 60 need info, 8 urgent
46
people checked
78
replies drafted, 11 quarantined
13 / 13
gaps answered "not in the policies"
3 of 5
hires set up, 2 held with a reason
About 3.5 min
from the check to the alert

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.
of double-digit growth at a Philippine supply and logistics business I've helped run since 2017
supplier cost cuts I negotiated for that business
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.
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.
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.
GoHighLevel, n8n, Make, Zapier and Claude Code, picked to fit the tools a business already has.
Book a call. You get an honest read on what is worth automating and what isn't, before any money is spent.
30 minutes on Zoom. You'll leave with a straight answer on what's worth automating, even if it's nothing.