Founding Customer Engineer

You take a customer from "we signed up" to "our AI teammate is live in a client channel and the client just replied." Then you turn what you learned into the playbook that gets the next ten customers there faster.

Who we are

Five million people in America make a living by putting their judgment to work inside other people's businesses: agencies, consultants, bookkeepers, recruiters. They are already trusted and already inside millions of companies. Nobody has built AI for how they work.

The big AI players build for the enterprise: one agent inside one company, and the expertise ends up owned by the platform. We believe expertise should belong to the people who built it. An agency works differently. One expert serves many clients at once, and no client may ever see another client's world. So we build AI teammates for that: they live in the agency's own tools, learn by watching the agency work, and go to work for each client under the agency's name.

We were our own first customer. AJ grew an agency to twenty-four people, Dan ran a software studio at three million a year, and we built Ergoly inside the agency we ran together. Today agencies run real client work through it, and every week another consultant tells us they are teaching themselves to code to stay ahead. Those are our people.

The big players got the enterprise. We are here for the five million.

The team is small. Nothing is someone else's department, there is no layer between building something and shipping it, and what you build reaches real agencies and their clients within days.

The role

The deployments

A customer signs on Monday. By Tuesday you have read their tools, their client list, and their Slack, and you can say: here are the three AI teammates worth building, this one first, and it goes live Thursday. Then you make that happen — set it up, connect it, ship it — and you live in the shared channel with them, where most of what you write is three lines long.

The playbook

Customer four teaches you something. Customer five gets it on day one. You write down every setup step, learn every place customers get stuck, and turn every fix into a template — until a new customer goes live on a playbook anyone can run, including our own AI teammates.

Who this is for

Then read the next six lines slowly. They are about you.

• You get a kick out of understanding someone else's world fast, and drawing it back to them better than they explained it. You can follow an API doc, a Zapier flow, or a database schema and build the small thing that connects them.
• You want to talk to customers. Real ones, every day, in their Slack, about what is broken and what they wish existed.
• You have built something with an LLM and felt the moment it worked. You want that feeling again, with someone else's business riding on it.
• "Find out why customers go quiet between day 3 and day 10" is the assignment you would pick for yourself.
• You drive when there is no structure yet. You spot what is broken, fix it, and write it down so it stays fixed.
• You know service businesses from the inside: what a retainer, a client channel, and a burned-out account lead look like.

If you have done Dev Rel, solutions engineering, or forward-deployed work, or you were the technical person at an agency who made everything fit together, you already know this job.

What a good week looks like

A customer asks for an AI teammate. You answer with how it is built, and it is live by Thursday. That week reads like this.

# ergoly-northwind
· shared channel

• May…