Definition first
Forward Deployed Software is software deployed as the specialist inside a customer's business context to perform a defined job.
A Forward Deployed Engineer puts a human engineer close to the customer's problem. Forward Deployed Software changes who is deployed. The software itself enters the operating environment, receives bounded authority, uses the customer context it is permitted to use, performs the work, and exposes evidence of what it did.
It is not a dashboard that waits for a customer to operate it. It is not a consultant hidden behind an interface. It is not a human forward-deployed team relabelled as automation. The claimed worker is the software.
Our interpretation: software can be the deployed specialist
Ernesta Labs coined Forward Deployed Software independently inside its four-layer model and is defining, developing, and attempting to establish the category in public.
That is not a claim that no person has ever placed these three words next to each other. Search review found a mature Forward Deployed Engineer role and adjacent phrases such as forward-deployed AI. It did not establish an earlier, stable category definition matching the model on this page. We will not convert an incomplete search into a universal historical-first claim.
Category authority must come from precision, implementation, evidence, and use. Not from declaring ownership over ordinary language.
Research findings: the established role deploys humans
| Question | Forward Deployed Engineer | Forward Deployed Software |
|---|---|---|
| Who is deployed? | A human engineer or technical team. | The software specialist itself. |
| Primary role | Understand the customer problem, adapt systems, and help deliver a solution. | Perform the defined operational job inside bounded authority. |
| Human involvement | The human is the deployed expert. | Humans may maintain infrastructure or provide specialist support, but must not secretly perform the claimed job. |
| Evidence | Project delivery, implementations, and customer outcomes. | Reconstructable actions, decisions, messages, state, constraints, corrections, and outcomes. |
| Commercial unit | Usually engineering time, a project, or a strategic deployment. | The service performed by the digital worker under the provider's business model. |
OpenAI's current Forward Deployed Engineer role says its human engineers own discovery, technical scoping, system design, build, and production rollout alongside customer teams. Palantir's 2020 account of its Forward Deployed Software Engineer role describes a human engineer embedded with customers to configure and implement software with end users. These primary sources establish the human role used as the comparison point. They do not define Ernesta Labs' proposed software category.
Where it sits in the model
- Reverse SaaS is the business model. It organizes value and payment around the service rather than access to software.
- Service-as-a-Software is what the customer buys. The customer buys the service itself.
- Forward Deployed Software is the proposed delivery model. It places the digital worker into the real customer context where the job must be done.
- NIKO is the first implementation. The deployed specialist is an autonomous salesperson.
These layers are related, but they are not synonyms. Read the complete Reverse SaaS thesis for the business-model argument.
Implemented capabilities: NIKO today
For NIKO, the forward-deployed software is the salesperson. The intended worker researches a market, selects prospects, begins conversations, follows up, qualifies, handles objections, negotiates inside its authority, asks for commitment, and closes.
The harness around NIKO supplies tools, providers, plugins, specialist capabilities, departments, and resources. Those supporting systems do not change NIKO's job identity. NIKO remains the sales specialist.
A customer would not be buying seats, tokens, an assistant, or a sales dashboard. If Experiment Zero succeeds and the model reaches production, the intended proposition is that the customer hires NIKO to perform the sales service.
That proposition is not proven. NIKO is not currently for sale. Experiment Zero has not yet demonstrated an autonomous close. At the 17 September 2026 reconciliation, production telemetry showed one committed provider acceptance, but delivery remained unproven, replies were zero, and verified paying customers were zero. The live Watch page, not this static definition, is the authority for current experiment state.
The implemented proof surface records canonical events and exposes a public-safe status projection. This is an implemented observability capability. It is not proof that the proposed worker can complete the full commercial job.
Proposed improvements: what deployment requires
Deploying a digital worker into a business requires more than connecting an API. At minimum, the provider must establish the job, permitted data, authority boundaries, tools, escalation rules, observability, failure recovery, and a way to determine whether the service created value.
The intended deployment policy requires customer data to remain isolated and private customer context not to become shared memory. Only validated, anonymized, non-identifying lessons may contribute to wider experience. These controls and any compounding effect remain proposed requirements until real deployments establish and verify them.
Transparency means reconstructable commercial truth. It does not mean exposing chain-of-thought, security secrets, prospect identities, private messages, or another customer's data.
What it is not
- Not an agency performing the work manually behind an AI interface.
- Not a consultancy selling a human implementation team under a software label.
- Not BPO labor hidden behind automation claims.
- Not ordinary SaaS with an employee metaphor added to the homepage.
- Not proof that autonomous workers are already reliable enough for production.
What remains unknown
- Whether software can perform this full job reliably enough for a customer to hire it.
- Whether the intended customer-data isolation controls will hold across real deployments.
- Whether provider acceptance becomes delivery, conversation, commitment, and payment.
- Whether “Forward Deployed Software” will become a useful shared category rather than only an Ernesta Labs proposal.
Supporting Ernesta Labs research
Direct answers
What is Forward Deployed Software?
Forward Deployed Software is software deployed as the specialist inside a customer's business context to perform a defined job. The software itself does the work rather than only giving a human another tool.
How is Forward Deployed Software different from a Forward Deployed Engineer?
A Forward Deployed Engineer is a human engineer embedded close to a customer's problem. In Forward Deployed Software, the deployed specialist is the software itself. Humans may support the system, but they are not secretly performing the claimed job.
How does Forward Deployed Software relate to Reverse SaaS?
Reverse SaaS is Ernesta Labs' business model. Service-as-a-Software is what the customer buys. Forward Deployed Software is the proposed delivery model used to place the digital worker into the customer's real operating environment.
Is NIKO Forward Deployed Software?
NIKO is Ernesta Labs' first implementation of the model: a forward-deployed autonomous salesperson under public test. Experiment Zero has not yet proved that NIKO can close a real customer.
A definition under test
Forward Deployed Software is Ernesta Labs' name for software that enters the customer's business as the specialist and performs the job.
NIKO makes that definition falsifiable. If the software cannot do the work, the category does not earn authority from the definition alone.