About
About Zhorx. We build it, then we stay.
You are about to let somebody inside the systems your business runs on. Here is who, what we can build, and what you keep.
The team
Small on purpose. Nothing between you and the build.
Zhorx is an AI automation agency, founded by Zubair Imran, who is its CEO and is on every first call.
Founded Zhorx after watching too many automation projects get built, handed over and quietly abandoned. Sits in on every first call and writes the map of where a client’s hours actually go, and has spent long enough inside small businesses to know which processes are load-bearing and which ones are just habit.
LinkedIn, Zubair ImranTap the card to get in touch.
Why we exist
Almost every automation we were asked to rescue had the same fault.
It worked. Someone built it, demonstrated it, invoiced for it and left. Six weeks later a supplier changed a file format, or an API version retired, or somebody added a field to a form. It stopped quietly, and nobody in the building knew how to start it again.
That failure is structural rather than technical. An automation lives inside a business that keeps changing, so something has to change with it. Selling it as a project makes that nobody's job.
So we sell it as a service. A fee to build, then a flat monthly fee to run it: monitoring, fixes, changes and a report. When it breaks, it is our phone that goes off.
What we know how to build
Named as capabilities rather than logos, because the logo tells you nothing about whether the hard part is covered.
The tools behind itJoining systems that were not built to talk
REST and GraphQL APIs, webhooks, OAuth, file drops, and the older systems that offer none of those and have to be driven another way.
Language models doing real work
Extraction, classification, drafting and routing, with the prompt under version control and a check on the output before it is acted on.
Data that arrives messy
Deduplication, matching records across systems that spell the same customer four ways, and validation that fails loudly rather than silently.
Code where a platform runs out
Most of a workflow fits in an automation platform. The last ten percent usually does not, so we write it, and it stays in a repository you can read.
Knowing when it broke
Retries, alerting to a person, and a log of every run, because the failure mode that kills automation is the one nobody notices for a month.
Handing it over properly
Documentation, credentials in your name, and an export of every workflow, so another developer could pick it up without calling us.
How a build actually goes
Five steps, in order, with the point at which you can stop marked at each one.
- 01
Week 0
We watch the job being done
A call, then a walk through the process as it actually runs, including the exceptions everybody works around. The written map of it is yours whether or not we go further.
- 02
Week 0
You get a number and a scope
What we would build, what it touches, what counts as done, and a fixed price. Nothing is built before you approve it.
- 03
Weeks 1 to 3
It is built against your real data
Not a demo on sample records. We run it beside the manual process and compare outputs until they match.
- 04
Go live
It runs with a human in the loop first
Anything with a real consequence gets approved by a person for the first stretch. The step comes out when the numbers say it can.
- 05
After
We keep running it, or you take it
Monthly management covers monitoring, fixes and changes. If you would rather run it yourself, you get everything and we help with the handover.
The three questions nobody asks out loud
What do we own at the end?
Your data throughout, and the automations, prompts and configuration once the final invoice is paid. No exit fee and no hostage-taking.
Read the termsWhat can you see of our data?
Only the systems a workflow needs and only the parts of them it uses. Nothing is used to train any model, and access is removed when a project ends.
Read the detailWhat does it cost to find out?
The audit is free and it ends in a written recommendation, including the recommendation not to automate something. Build prices are published as ranges.
See the ranges
How we work
Four rules we do not bend.
- We only build what we are willing to run
- Building something clever and handing it over is easy. Building something you will still be maintaining in two years is not. We do the second kind, because the monthly fee depends on it.
- Nothing gets replaced unless it has to
- New software is a cost with a long tail: licences, training, the fortnight where nobody can find anything. We work with what you have far more often than we replace it.
- You can always see what it did
- Every run is logged, every step is visible, every workflow exports. Taking it in-house is a decision, not an escape.
- If it is not worth doing, we say so
- A job that runs four times a year is not worth automating. Saying that costs one project and earns a call back in eighteen months.
FAQ
Who is the founder of Zhorx?
Zubair Imran is the founder and CEO of Zhorx. He sits in on every first call, writes the map of where a client's hours go, and is on contact@zhorx.com.
Where is Zhorx based, and where does it work?
The work is remote by design and we take clients wherever they are. Everything is built and supported over the tools you already use rather than in person, so the timezone matters more than the country, and we work around yours. Pricing and invoicing are in US dollars.
Is Zhorx a big agency?
No, and deliberately not. You deal with whoever built the thing rather than an account manager standing between you and them, which is why we turn down work that is not worth automating instead of taking it.
Start with the job that annoys you most.
Even if it turns out not to be the right one to automate first, it is the fastest way into the conversation.