Hire a Forward Deployed Engineer: The First Session

You run a real estate team or you are the agent everyone leans on. You have a CRM you half use, a transaction coordinator who may or may not stay, and a Gmail inbox that is the real system of record. Someone told you to hire a forward deployed engineer. The articles you found talk about Palantir, Series B startups and $300,000 salaries. None of them describe your office.

Here is the plain answer. To hire a forward deployed engineer as a small business, you bring in one person who sits inside your actual tools, with you on the screen, and builds the smallest thing that removes a daily problem. They do not hand you a plan. They connect your Gmail, your calendar and your deal portals to an AI, set it to run at fixed times, watch the first run with you, and fix what the first run gets wrong. You pay for a working result, not a document.

If you want to know whether your business has that kind of problem, take the two-minute survey at https://reshapedigital.app/?utm_source=blog&utm_medium=article&utm_campaign=hire-a-forward-deployed-engineer and I will tell you what I would build first.

What "forward deployed" means for a business with no engineers

The phrase came from software companies. An engineer is "forward deployed" when they work inside the customer's business instead of at headquarters. The big-company version involves a whole team and a contract with a lot of zeros. The small business version is one person, usually on a Zoom with you, logged into your software, doing the work in front of you.

That is the whole difference between this and a consultant. A consultant tells you what to do. A forward deployed engineer does it while you watch, then shows you the output the next morning. I wrote a longer definition in a previous post on what a forward deployed engineer for small business actually is. This article is about what happens after you decide to hire one.

Hire a forward deployed engineer: what the first session looks like

Last week I spent an hour and thirteen minutes with a regional manager at a real estate brokerage. Her job is recruiting agents. Her company runs on Microsoft, so the tool was Copilot, not Claude or ChatGPT. That did not matter. The method is the same with any of them.

We did not start with a strategy deck. We started by asking the AI, one question at a time, what it was allowed to touch: read her email (yes), her calendar (yes), Teams meetings (yes), schedule a prompt to run on its own (unclear), create a draft directly in Outlook (yes). Ten minutes, and we knew the shape of what we could build.

Then we built one thing: a morning recruiting inbox agent. It reads her email, calendar, contacts and Teams chats, ranks the messages that most need a reply, and proposes drafts. We set it to run at 7:00 AM every day, removed the end date, hit "run now" and watched it work.

She then asked it to file an email into a folder, and it told her it did not have permission to move items in Outlook. That is a real limit, so we wrote it down for her IT ticket instead of pretending it away.

We built a second agent before the call ended. It summarizes every recorded Teams call in the evening and pulls out decisions, problems, owners and due dates. The dry run showed that several meetings had never been recorded, so we went into the recurring meeting settings and turned recording on. Her next step is to check that the 7:00 AM run actually arrived and read the drafts. That is the acceptance test.

Hiring a forward deployed engineer vs buying another CRM

The second story is a different reader with the same problem. A real estate agent in Northeast Ohio told me she was using "really nothing" for a CRM. She had one and had looked at HighLevel, but never opened either because the pipeline view felt like a second job. She had just signed with an outsourced operations company to handle her transaction coordination, marketing and bookkeeping.

I told her something she did not expect to hear from me: for certain agents, you may not need a CRM if your AI is set up correctly. Almost every agent who has called me in the last two months asked for some version of the same thing, a one-page board that pulls in the stuff they cannot keep organized. Who should I talk to today, what are my live deals, and when did I last talk to this past client?

The reason that works is not magic. She has used the same Gmail for as long as I have known her, her contacts live in her phone, her Facebook and her email, and her deals live in a portal. All of those have a connector. So the engineer's job is not to pick software. It is to connect the three or four places her business already lives to one page, and have that page rebuild itself at 7, 10, 1 and 5 so it is ready when she gets in the car.

I did not build it on that call. I told her to run with the operations company first, and if it still felt stressful in a month, to call me and we would do a Zoom where all we do is Gmail. That is advice and a plan, not a finished result. I am telling you that plainly because the whole point of this role is that you only pay for what runs.

The story that changed how I think about this

The agent who made me rethink CRMs was someone whose transaction coordinator quit on the spot while she had four live deals. She called me and said, "I feel like Claude could do this." My first question was whether she could clearly define what she expected a TC to do on every deal. She said it had been the same thing for ten years.

We connected her Gmail to Claude and described the situation. What came back was one dashboard: every live deal, the last time she spoke to each client, and a pre-drafted nudge message for each one. It also went back through her old deals and flagged every miss the previous TC had made on title and loans. I asked her later whether she would go back to the old way. She said no shot.

That is her account, not a measured study, and I will not put a number on hours saved because nobody timed it. The build took one working session, and the result was a page she opens every day. If someone is not pulling it up on their own by the second morning, the build is not good enough.

What you are actually paying for

When you hire a forward deployed engineer, four things should show up on the invoice in plain words. First, a permissions check: what the AI can read and write in your real accounts, done on your screen. Second, one scheduled job that runs at a fixed time without you asking. Third, a watched first run and a watched second run, with the misses written down. Fourth, a list of what the tool cannot do yet, so you can decide whether that needs IT, a different connector or nothing.

Notice what is not on that list: no roadmap, no "phase two," no dashboard with fourteen stages. If the engineer leaves your first session without a job scheduled to run tomorrow morning, you hired a consultant with a different title.

How to tell if you need this

Answer these honestly.

1. Your inbox is your real CRM, and you know it.
2. You have bought at least one piece of software your team stopped opening within a month.
3. Someone on your team asks you questions they could answer themselves if they could see what you see.
4. You are in the car for two or more hours a day and that time is dead.
5. When a key person quits, the deals in flight are at risk because the process was in their head.

Three or more, and a forward deployed engineer is a better next spend than another subscription. One or two, and you probably need a cleaner follow-up habit first. Read what happened to your last ten leads before you hire anyone.

FAQ

How much does it cost to hire a forward deployed engineer?

The published salary guides start around $150,000 a year for full-time roles at tech companies. Those numbers come from recruiting firms writing for startups, and I am citing them secondhand. A small business does not hire that way. You hire a session, or a fractional engagement by the month, and you judge it by whether the scheduled job ran. If you want the pricing logic, see the earlier post on what to demand from a fractional AI engineer before you pay.

Do I need to be on Claude or ChatGPT or Copilot?

No. The brokerage manager was on Copilot because her company is. The agents are mostly on Claude or ChatGPT. The brand does not matter. What matters is whether your leads, your communication, your past clients and your live deals are all reachable from one place.

Is this the same as hiring a virtual assistant?

No. A VA does the task. A forward deployed engineer sets up the thing that does the task at 7:00 AM without anyone remembering. Some agents expect to need their VA less once the board exists, but that is their expectation, not a result I have measured.

What if my IT department blocks it?

Then you find the window they left open. On the Copilot call, the company had not approved the full autonomous mode, but scheduled prompts inside an agent still worked. Part of the job is finding what is allowed today and documenting what to ask for.

How long before I know it worked?

Two mornings. Did the 7:00 AM job arrive on day one and day two, and did you use what it gave you? That is the standard I use for every build, and I wrote about why in the post on the AI chief of staff.

Who this is for, and who it is not for

This is for a real estate agent or team leader doing enough volume that missed follow-up costs real money, who has already bought software nobody uses, and who wants one page they will actually open. It also fits a home service owner or a loan officer with the same inbox problem.

It is not for someone who wants a tool recommendation and plans to set it up themselves on a Saturday. It is not for a business with no email history to connect. And it is not for anyone who wants a guarantee of hours saved before the first run. I will tell you what I built and what it did. I will not tell you what it will do before it does it.

If you want to know what I would build first for your business, take the short survey at https://reshapedigital.app/?utm_source=blog&utm_medium=article&utm_campaign=hire-a-forward-deployed-engineer and I will reply with one specific job to schedule tomorrow morning.