Operating Essay · · 2 min
Introducing XYZ Lab: we put AI to work for you
Two founders who install and run AI systems in the back office of service firms. What we do, how we work, and what we refuse to automate.
XYZ Lab installs and runs AI systems inside service firms. We work with B2B firms doing $5M to $50M in revenue, on four parts of the business: visibility, pipeline, hiring and operations.
We build each system in your accounts, connect it to your data, and then run it every month against a scoreboard you agree to before we start.
Who is behind XYZ Lab?
Two founders who have shipped products side by side for more than eight years.
Rajat spent eight years buying Meta ads across 70+ brands, and built Shhots AI, Blinkstore and Hapramp. Mofid founded Mockey.ai and co-built Hapramp and Blinkstore.
The people on your call are the people building your system. There is no account manager and no junior team behind us.
Why not just buy an AI agent?
For most back-office work, what a firm needs is a standing order.
A standing order is an instruction that runs without being asked. Pay this invoice on the first of the month. Send this report every Friday. Flag any lead from a company over 50 people.
An agent is useful when the next step is unclear. A standing order is useful when the next step is clear and someone keeps missing it. In the firms we talk to, the second problem comes up far more often.
Most of the back office in a growing firm looks like this. The rules are known, the work repeats, and forgetting it costs money.
How does an install work?
Every system we build follows the same four steps:
- Write the rule down, in plain language.
- Connect the data the rule needs.
- Run it, and log every run.
- Put a person on the exceptions.
The model does the reading and drafting. The rule decides what happens next.
What does working with us look like?
Three stages, each with a fixed shape:
| Stage | Length | What you get |
|---|---|---|
| Diagnostic | Two weeks, fixed fee | A ranked map of where AI changes the result, and a 90-day plan |
| Build | Three to six weeks, fixed scope | Working systems in your accounts, and a scoreboard agreed before we build |
| Run | Monthly, six-month minimum | A written report every month, and direct access to both founders |
The systems live in your accounts. If you stop, you keep everything.
What won’t we automate?
Anything your team is still arguing about. Automating an unsettled process only makes the argument faster.
We also keep a person in the loop wherever a wrong answer costs a client relationship: final outbound messages, hiring decisions, and anything that commits money.
Where do the recipes come from?
We run these systems on our own businesses first. Each recipe on this site is a write-up of one install: what we built, what it cost, what came out and what broke.
The first one shows how Mockey moved 328 posts off WordPress onto a pipeline Claude runs.
How do you start?
Pick a time in the calendar below for a 30-minute call with both of us. Bring the three repeating tasks from the note at the end of this post.