On-site diagnosis
Interviews and observation show where time is being lost. We pin down what the problem is before deciding what to build.
FDEForward Deployed Engineer
Engineers who work on site
and see it through: FDE
Placed at your site, we learn your work and data, build the software you need there, and run it.
Compared with the usual options
The people who know the problem and the people who build
belong in the same room.
| Approach | How it works | What usually happens |
|---|---|---|
| Outsourcing | A vendor receives a requirements document, builds, and delivers. | On-site details missing from the document get lost, and nobody is left to fix things after delivery. |
| Buying a product | You buy an existing product and configure it. | It doesn't match how the team actually works, so people drift back to spreadsheets and chat. |
| Hiring developers | You recruit and build an in-house team. | Hiring takes time and money, and learning the business and its data takes even longer. |
| FDE | An engineer stays close to the team and owns the work from defining the problem to running the result. | Software is built and fixed next to the people who use it, so it actually gets used. |
What an FDE does on site.
An FDE (Forward Deployed Engineer) is an engineer placed directly with a client. Instead of waiting for a spec, they watch the real work and build what it needs.
Connecting data and systems
Read and connect data spread across spreadsheets, internal systems, and outside services.
Custom software
Admin screens, automation scripts, internal tools: whatever that site needs.
Deployment and operations
Put the software on real servers and handle errors and change requests directly.
Handover
Documentation and training so your team can run it on its own.
Start small, then grow what works.
- Diagnose
Interviews and a system review set the problems and priorities.
- Pilot
Solve the most urgent problem with software that actually runs.
- Expand
Extend what has proven useful to other teams and tasks.
- Hand over
Pass it on with documentation and training, and your team runs it.
Tools an FDE uses on site
HankyeulLab FDEs use these tools to move quickly across sites and to share progress with clients.
runmcp
Connect to and operate many servers from one screen, and check task status from a phone on the move.
About runmcpHCMS
A portal where progress and requests are shared with the client, with a record of who asked for what and where it stands.
About HCMSAI tools
ChatGPT and Claude for meeting notes and documentation, and for faster development.
A good fit for these teams.
Teams with few or no in-house developers
You know what you want built but have no one to build it.
Organizations with complex processes
So many exceptions that a document alone cannot carry the requirements.
Companies whose product doesn't fit the floor
We find ways to connect or fill gaps instead of throwing it away.
Teams testing a new business quickly
Check real reactions with a working first version before a large development contract.
Ways to work together
Start with only what you need.
Diagnosis
About 2 weeksOn-site interviews and a system review, delivered as a written improvement plan.
Discuss this optionPilot
4-6 weeksOne core problem, solved with software that actually runs.
Discuss this optionResident
MonthlyAn FDE splits time between your site and remote work, building, running, and improving.
Discuss this option
Pricing depends on scope and duration. We quote after a consultation.
Start by telling us
what's happening on site.
Tell us where the work is stuck, and we'll come back with a proposed diagnosis scope and timeline.