Meetext
Start free

Forward deployed engineering

Forward deployed engineering should scale like software.

It is the least scalable role in enterprise software, and it is growing because AI products are being sold to enterprises faster than anybody can deploy them. The repeatable work belongs in a system.

Your team's judgment

Understand the customer. Design the fit.

Meetext
Meetext / Customer deploymentExample

The repeatable work. Taken care of.

  1. Package

    A version for each customer

  2. Authorize

    The permissions they approved

  3. Validate

    A real capability, executed

  4. Operate

    Health, changes and recovery

Keep the judgment. Lose the repetition.
Customer approvals stay with the customer

Who is in the middle

Sold as a product.
Delivered as a project.

Enterprise software is sold like a product and delivered like a project. Something has to sit between the two.

Traditional
  1. Software vendor
  2. Forward deployed engineer
  3. Enterprise customer

A person in the middle. They do not scale, they are your most expensive engineers, and every customer needs one again.

Meetext direction
  1. Software vendor
  2. Meetext
  3. Enterprise customer

Software in the middle. The repeatable parts run without anybody, and the parts that still need judgement arrive with the context to make it quickly.

Eleven steps. Every customer.

The job, broken down

Before arguing about which parts can be automated, it helps to say what the job actually is. Eleven things, in roughly this order, for every customer.

  1. 01
    Understand requirementsHuman judgment
  2. 02
    Understand the environmentHuman judgment
  3. 03
    Plan the deploymentHuman judgment
  4. 04
    ConfigureMeetext supports the repeatable work
  5. 05
    Handle security and admin approvalMeetext prepares · customer approves
  6. 06
    DeployMeetext supports the repeatable work
  7. 07
    ValidateMeetext supports the repeatable work
  8. 08
    DiagnoseMeetext supports the repeatable work
  9. 09
    RepairMeetext supports the repeatable work
  10. 10
    UpgradeMeetext supports the repeatable work
  11. 11
    OperateMeetext supports the repeatable work

Steps one and two are judgement and will be for a while. Steps four through eleven are the same motions against a different tenant, and they are where the weeks go.

AIThe Meetext Agent

The forward deployed engineer, as somebody you can ask

Steps four through eleven are the same motions every time, so the agent does them when you ask: it adds the customer, sends the install link, starts the security review, chases the admin, and checks in every morning. Each change waits for your confirmation.

Meet the agent
  • “We signed Globex. Add them and send their admin the install link.”
  • “Start a security review for Globex and share it with their team.”
  • “Every morning, tell me who is waiting on an admin.”

What is software, and what is not

The left column runs today. The right column does not. We keep them apart because the second column is only believable if the first one is accurate.

Software today

Running in the product. This is what a customer can rely on this week.

Deployment packaging
Capabilities frozen into a package per customer.
Entitlements
What this customer bought, enforced at the package.
Authorization lifecycle
OAuth, admin consent, reconnection, revocation.
Security review
A generated artifact with claims and their provenance.
Validation
A real capability executed before anyone is told it works.
Credential management
Per environment, rotated before expiry.
Health
Three layers, watched separately because they disagree.
Incident handling
Fingerprinted, deduplicated, correlated with changes.
Versioning and rollback
Per customer, to packages that actually worked.
Operational history
Append only, replayable, with attribution.
Requirement capture
What a customer asked for and could not get, recorded where it happened.
Fleet-wide demand
The same request across every customer, counted rather than remembered.
Change authoring
A pull request on your repository, with the evidence and the acceptance criteria attached.
Entitlement remediation
A customer asking for something you already ship, granted rather than queued.
Acceptance drafting
A brief drawn from what the deployment was actually asked, for the customer to correct.
Verified closure
Nothing is called fixed until a case the customer agreed to passes.
The Meetext Agent
Does any dashboard step you ask for, emails teammates and customers' contacts, and runs checks on a schedule. Every change waits for a person to confirm it.
Permissions per person
One permission on or off for one teammate, beyond their role. The agent working for them obeys it too.
Approval before a change
Deletions in a customer's workspace always wait for a person, and writes can too.
Personal data masking
Applied to every tool result before any client or model reads it, under the customer's policy.
Spend control
A monthly budget per customer, checked before every model call, and a switch that stops everything.
First reading of an incident
A likely cause and a next step, written by the agent and labelled as unverified.

Where people stay involved

Meetext prepares the context and evidence. Scoping, commercial judgment and review still need people; validation depth depends on the language of the change.

Scoping the engagement
Sitting with a customer who does not yet know what they want. Meetext arrives with a draft; the conversation is still a person's.
Reading the review
A comment on a pull request is feedback nobody has taught the loop to answer yet.
Expansion
The evidence is assembled. Somebody still has to make the call.
Deeper verification
Generated Python is parsed and its imports resolved. Every other language gets less, and says so.

The order matters

You cannot automate diagnosis of a deployment you do not have a record of. Every entry in the right hand column above needs the same thing first: a trustworthy account of what each customer is running, what they approved, what changed, what broke and what fixed it last time.

An agent that can actRests on it

Proposes the fix, having read a record it can cite.

Automated diagnosisRests on it

Recognises this failure because it has seen it across customers.

A trustworthy accountBuilt today

What each customer runs, what they approved, what changed, what broke, and what fixed it last time.

An agent reasoning over a pile of API responses will be confidently wrong. An agent reasoning over an append-only deployment record, with provenance on every inference, can be checked. That is why the entry point is infrastructure and not an assistant.

Questions

What is a forward deployed engineer?
An engineer who works inside a customer's environment to get a product actually running there: understanding their systems, configuring the integration, getting through security review, handling identity and permissions, proving it works and keeping it working. The title varies. Solutions engineer, implementation engineer, customer engineer and post-sales engineer describe substantially the same work.
Why does the role exist at all?
Because enterprise software is sold as a product and delivered as a project. The product is the same for every customer; the environment is different for every customer. Somebody has to close that gap, and today it is a person.
Why does it not scale?
The work is roughly the same each time and roughly as expensive each time, because almost nothing from the first customer is reusable as software. Whatever a first enterprise deployment costs a team in weeks, the tenth tends to cost something similar. Headcount is the only lever, and forward deployed engineers are among the most expensive engineers to hire.
Is Meetext an AI FDE?
Yes: forward deployed engineering as a service. Meetext deploys your product into each customer, passes their security review, keeps it working, answers what goes wrong, and turns what they ask for into pull requests verified against their own cases. The Meetext Agent does the legwork and asks a person before anything risky. A few FDE systems are still being built, such as enterprise SSO, search over customer documents and ROI reports, and they are marked as coming rather than claimed.
Does Meetext replace our solutions engineers?
It removes the repeatable work from their week. Understanding a customer's requirements and designing what they should get is judgement. Running the same OAuth flow, the same security questionnaire, the same validation and the same upgrade for the fortieth time is not.
Your next customer is waiting.

You build the product.
We take it from here.

Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.

Start free Talk to the team