Operations & AI Automation Manager

Read this part first

We are not looking for someone to maintain an operations function.

We are looking for someone to build one that mostly runs itself and then hold the bird's-eye view over it.

About us

We're a B2B revenue operations consultancy.

We're a small, senior team. We're AI-native by default, not as a talking point, as a working method. If you join us, you will be given the tools and the latitude to automate your own job wherever it makes sense.

What you'll do

First 90 days: expect to grind. You will do a lot of things manually while you figure out what should be automated. Proposal assembly, report packaging, ticket triage, client follow-up chasing. This is not the job forever, but it is the job at the start. You have to feel the pain before you can design it away. If that sounds like a bad deal, this role isn't for you.

After that: build and conduct.

1. Automate the boring layer. Proposal drafting and formatting, delivery reporting, ticket triage and routing, QA passes on tone and completeness, internal reminders and status rollups. You'll build these with AI tooling and MCP connections across our CRM, project management, comms, and storage systems.
2. Own the scope-drift problem. A client sends a message asking for "one small thing." Realistically, it's twenty tickets. Today nobody catches that until margin is gone. You will build the tripwires that catch it, and you'll be the one who says something.
3. Hold the bird's-eye view. Which clients have gone quiet. Which projects have quietly expanded 3x. Where work is falling between two people who each assumed the other had it. You are the person who notices.
4. Push ops outward, not inward. The end state is not "all operations run through you." It's every person on the team able to run their own operations because you built the rails and the automations. You're a force multiplier, not a queue.

Who this is for

• You've run operations somewhere small and messy, and you've felt what it's like when there's no playbook.
• You use AI daily as a working tool, not as a novelty. You've built something real with it, for example an automation, an agent, a workflow that saved actual hours.
• You have opinions about systems. You get physically uncomfortable when something is done manually three times in a row.
• You'll say "that request is bigger than it looks" out loud, to a founder, without being asked.
• You're comfortable being the only person in the room who knows what's actually going on.

Who this is not for

• If your strongest credential is a stack of certifications, please don't apply. Our team is thoroughly certified. Certifications did not solve this problem. Judgment does.
• If you want a defined process to follow, you'll be miserable here. There isn't one yet. You're writing it.
• If "AI-powered" to you means using ChatGPT to write emails, the gap will show up fast in the screening task below.
• If you want a client-facing strategic advisory role — that's a different hire we're making later. This role is internal-facing and systems-first.

What we're screening for

In order of weight:

1. Judgment under ambiguity. Can you look at a messy situation and correctly identify what's really going on?
2. AI and automation fluency. Practical, hands-on. MCPs, agents, workflow tooling, API-level thinking. You don't need to be an engineer, but you need to be dangerous.
3. Follow-through. Noticing the problem is a third of the job. Chasing it down is the rest.
4. Written communication in English. Clear, direct, professional. Much of your output is written.

Helpful, not required: CRM platform experience (we'll teach you — it's what we do), additional language fluency, prior agency or professional services background, light scripting ability.

What you get

• Real ownership of a function, not a seat in someone else's process.
• Full budget and freedom to use the AI tooling you think is best.
• A front-row seat to a fast-scaling consultancy — with the commercial upside that comes with it.
• Direct working relationship with the founders. No layers.
• The chance to build the operating system of the company, which is a much more interesting problem than running someone else's.

How to apply

Do not send a CV alone. It will not be read.

Start your cover letter with "AI RevOps — [Your Name]" containing:

1. The scenario. A retainer client sends this message on a Friday afternoon:

"Hi team, can you just set up our lead routing so leads go to the right salesperson? Should be quick. Also make sure the old leads get reassigned too."

In under 400 words, tell us:

• What questions you'd ask before anyone touches anything.
• Your honest guess at whether this is one ticket or many, and why.
• One automation or tripwire you'd build so this situation stops catching us by surprise.

We are not looking for the "correct" answer. We're looking at how you think.

2. Proof of build. Link to or describe one thing you've actually automated or built with AI. Screenshots, a Loom, a repo, a workflow diagram — anything real. Tell us what it replaced and what it saved.

3. Your CV, and a line on your salary expectation and notice period.

We reply to every applicant who completes the task. Applications without the scenario response are not considered.