Start remote, and earn the trip
Forward deployed engineering earned its enterprise price tag honestly, because the original model puts an engineer on a plane, houses them near the client, and bills for airfare, lodging and days on the ground for the duration. When the engagement runs into the millions, that arithmetic works. When the travel line item is a visible fraction of the total, it never had a chance of working, which is why this class of help stayed unavailable to most of the businesses that needed it, including some very substantial ones.
So discovery, workflow mapping, system construction and testing against live conditions happen through screen shared sessions with the people who do the work. By the time travel is on the table, the systems and data are understood, something has been built and is running, and the remaining questions have been narrowed to the ones that genuinely cannot be answered over a screen. At that point a visit has a defined purpose and a defensible cost.
"A firm that recommends travel by default is billing you for its own convenience, and a firm that refuses to travel at all is not serving businesses that move physical product."
When onsite earns its cost
When the work is physical
A warehouse floor, a production line, a shop with equipment in it. How product actually moves through a building, where the bottlenecks are, what people work around without noticing. That information exists in the space and not in anyone’s description of it.
When observation matters more than the interview
People describe their process as it is supposed to work. Watching reveals the informal steps that keep a business running, the handwritten note on the monitor, the sequence that gets reversed when things are busy.
When a full team needs to move at once
Bringing an entire staff onto a new way of working happens better in a room, particularly where some of the team is uneasy and the reassurance needs to come from a person standing in front of them.
When equipment or a physical network is involved
Hardware, machinery, scanners, printing or fabrication systems, or a network configuration that cannot be reached from outside. Some things must be touched.
When trust needs a face
Some owners, entirely reasonably, want to meet the people they are handing their operation to before they hand it over. That is a legitimate reason to travel.
When onsite adds cost without adding value
Discovery conversations with people who work at a desk go just as well over a screen, and often better, since we are looking at the actual system together rather than at a projector. Building and testing gains nothing from proximity. Routine training on software workflows works well remotely and has the advantage of being recordable for staff hired later. Ongoing support after handoff almost never requires presence. Physical reality and group dynamics benefit from being there. Anything that happens on a screen does not.
The hybrid we normally recommend
Discovery starts remotely, covering the systems, the data, the workflows and the constraints, which means that by the time anyone travels the fundamentals are already understood. If there is a physical dimension, a short focused onsite visit follows, spent watching the operation rather than sitting in a meeting room. Building happens remotely, with regular working sessions against real data. Where a team rollout warrants it, a second visit covers training. Support afterward is remote. That structure typically compresses the onsite portion to a few days across an entire engagement rather than weeks.
What the remote sessions actually look like
These are working sessions rather than status meetings. Screens are shared in both directions, we are in the actual system with the people who use it, and things get built and tested while everyone is present. Questions get answered in the moment by the person who knows the answer rather than routed through a project manager. Sessions are short and frequent rather than long and occasional, because that matches how the work actually progresses.
Two secondary advantages come with this. Sessions can be recorded, so a decision made in month one is still reviewable in month six and new staff can be shown why something was built the way it was. And scheduling is dramatically easier, meaning a thirty minute session to resolve one question happens the same day rather than waiting for the next trip.
Where AI shortens the ground time
Part of why the onsite portion has compressed is that work that used to require an engineer sitting with the business for weeks no longer does. Analyzing an existing data set, mapping how fields relate across systems, drafting transformations, and identifying exceptions that need a human decision are all substantially accelerated. The questions we bring to a visit are precise rather than exploratory. The visit is used for what only presence provides.
How travel is handled commercially
Travel is quoted separately and approved by you before it happens, never absorbed into a rate where it becomes invisible. When we recommend a visit, we say what it is for and what we expect it to produce. If you would rather try remotely first and travel only if it proves necessary, that is a reasonable position and frequently the right one. The related work is covered in team enablement for training and handoff, and in workflow automation for the process logic that observation on the floor usually informs.