About
A small studio that builds automations and says no a lot
RayonIntel exists because most operational software promises transformation and delivers a dashboard. We do narrower work: pick a process that genuinely wastes your team's time, automate it properly, hand it over, and leave.
Principles
How we operate
These aren't aspirations. If we break one of these, hold us to it.
We'll talk you out of bad automation
A process that runs twice a month, or changes every quarter, usually shouldn't be automated. Saying so costs us a project and earns a client who comes back.
Humans stay on the exceptions
We build systems that handle the predictable path confidently and escalate everything else. Anything that claims to remove people entirely is either lying or about to fail quietly.
You own what we build
Code, workflows, prompts, documentation and the accounts they run on. We don't design dependencies to keep you subscribed.
Fixed scope, fixed price
You get a number before work starts. If we misjudge the effort, that's our problem to absorb — not a change order.
Measured, not asserted
We agree the success metric during scoping and report against it honestly, including when the result is smaller than we hoped.
Your data stays yours
It stays in your systems wherever possible. Where a model provider is involved we use enterprise endpoints with training disabled, documented before we build.
Team
The people who'll actually do the work
No account managers between you and the person building your system.
Yajat Makhija
Founder
Builds AI voice agents and operational automations for clinics and teams that still run on manual outreach, spreadsheets, and phone tag.
LinkedInWhat we take on
- Processes that run often enough for automation to pay back within a year
- Work where the rules are knowable, even if nobody has written them down
- Teams willing to give us a few days with the people doing the work
- Projects where success can be measured against something concrete
What we decline
- Automation of decisions that carry legal, clinical or financial liability
- Low-volume processes where the build costs more than the manual work
- Open-ended "add AI to our product" briefs with no defined outcome
- Anything designed to obscure that a person is talking to a machine