Forward Deployed Engineers Guild The Guild
Field Notes

What a Forward Deployed Engineers Guild Is

The Guild

Most teams have access to AI now and are stuck at the first wall. They have the tool open and no real sense of what it can do for the work in front of them.

Closing that gap is the reason the Forward Deployed Engineers Guild exists. We are a small, hand-picked group of expert Forward Deployed Engineers. We meet to share craft and back each other on big work. This is the first thing we have to say in our own voice, so we want to be clear about what the Guild actually is and how it runs.

What a Forward Deployed Engineer does

A Forward Deployed Engineer does not sit in a meeting and recommend a tool. They embed. They sit with your team, learn the work, find the bottlenecks, and build the tool that removes them. The artifact runs in production and saves hours the day it ships.

The craft we sell is teaching that craft. We work on real problems with your real data, with your people next to us, and we leave on time. By the time we go, the people who built the tools with us can build the next one without us.

A vendor leaves you with a tool and a phone number. When the tool breaks, and tools break, you call the phone number and wait. We leave you with people who can build, debug, and ship on their own. When the prompt drifts or the model updates, the person who fixes it already works for you. Anything else is a vendor relationship with a half-life.

The spine: build, teach, sell

Three words run down the middle of everything the Guild does. Build. Teach. Sell.

Build. We make working artifacts. Not slide decks about AI, not pilots that never reach production. Real tools that run and pay for themselves fast.

Teach. The coaching is the actual product. The build is the vehicle. We build alongside your team so that the capability stays in the room after we leave. The deliverable you keep is the person who can make the next ten tools without us.

Sell. Each operator runs their own house and brings their own clients. The Guild sits next to the operator, not between the operator and the work. It is what lets one operator close a deal bigger than one operator could carry alone.

The shape of the engagement is a two-week residency, Friday to Friday. Week one we sit with the team and learn the work, the bottlenecks, and what is worth building first. Week two we build with your people next to us. By the second Friday they walk into a workshop and leave with working skills and working products they own.

This is not a hypothesis. It is the arc we have already run. One residency this spring put six stakeholder intakes through in seventy-two hours, built a proof slate, and delivered a town hall to roughly sixty people on the final Friday. The two-week framing is anchored on that real engagement, not a brochure.

Why a network of operators beats an agency

Start with how an agency is built. An agency hires juniors, marks them up, and sells you the markup. The senior name on the proposal is rarely the person who shows up. You pay for a brand and get a bench.

The Guild inverts that. Every member is an elite individual operator who will solo the vast majority of the projects they touch. There is no bench of interchangeable resources. There are named people with branded craft. When you hire the Guild, the person who shows up is the person whose name is on the work.

So why have a Guild at all, if everyone works solo? Because of the seams. Occasionally an operator gets a lead they are too busy to close. Seldom a project needs more eyes and hands than one operator can provide. When those situations arise, we help each other. We finish together what we could not alone.

A network of senior operators who back each other on big work, with no one carrying a payroll of juniors, beats an agency on the axes that matter to a buyer. You get the senior on every job. You get a team for the jobs that need a team. You do not pay for the overhead in between.

How the Guild shares the work

We are transparent about the economics because the economics are simple, and a buyer can see the whole thing on one page.

When an operator brings in a lead, the operator who executes the work keeps 70 percent. The operator who sourced the lead keeps 20 percent. The house keeps 10 percent. When the Guild itself sources a lead, the house keeps 30 percent. The vast majority of operator work is solo work, and operators keep 100 percent of that.

Guild resources support members, member projects, and their families when needed. The Guild pays no salaries and has no meaningful operating costs. There are no dues and no commitments beyond what is stated here. Admission is by craft.

That last point is worth sitting on. The Guild has no commercial reason to inflate its own ranks. An agency grows headcount because headcount is revenue. We do not. A member only joins if their craft raises the floor of what the Guild can do. The incentive runs toward keeping the bar high.

What we are not

We are not a software company. We do not sell software. We sell embedded operator time and the capability that time leaves behind.

We are not a staffing agency. Operators are named individuals with their own practices, not resources you rent by the hour and never meet.

We are not a marketing wrapper around one person. Multi-operator work is real and structural. When a deal is too big for one of us, more than one of us shows up.

Where this comes from

The way the Guild works did not come out of a strategy deck. It came out of running residencies and watching what actually leaves a team better off. The teaching, the embedding, the leave-on-time discipline, the refusal to ship pilots that die in a drawer. The same instinct shows up in the public work the operators have already put out, like the open typed-wiki memory pattern at bennichol.com/typed-wiki, a working system shared in full rather than a product behind a wall.

If you have a workflow that has been frustrating you, the fastest way to understand what we do is to watch one get fixed. Bring it to a thirty-minute call and we will show you what wielding AI can feel like, live. The pitch we send people lives at fdeguild.ai/whatwedo, and the door is at fdeguild.ai.

We teach your team how to fish, and then the work is yours.

Swing the axe every day. Row together.

The Guild

Questions

What does a Forward Deployed Engineer actually do?
A Forward Deployed Engineer embeds with your team rather than recommending tools from the outside. They learn the work, find the bottlenecks, and build the artifact that removes them, with your people building alongside them. The artifact runs in production and saves hours the day it ships, and the capability to build the next one stays in the room after the operator leaves.
How does the Guild split revenue?
When an operator brings in a lead, the operator who executes the work keeps 70 percent, the operator who sourced the lead keeps 20 percent, and the house keeps 10 percent. When the Guild itself sources a lead, the house keeps 30 percent. Solo work is the vast majority of operator work, and operators keep 100 percent of that. There are no salaries, no dues, and no meaningful operating costs.
Why hire a Guild of operators instead of an agency?
An agency hires juniors, marks them up, and the senior name on the proposal is rarely the person who shows up. The Guild is named individual operators who solo the vast majority of their work and back each other only when a deal is too big for one person. You get the senior on every job, a team for the jobs that need a team, and you do not pay for a bench in between.