Forward Deployed Engineering

Engineers embedded in your business. Solutions built around how you work.

PMG’s forward deployed engineers work inside your teams to find the problems worth solving first, then design and ship solutions that work with your data and your approval rules. Most engagements reach production in four to eight weeks, and your people decide how the system works.

Last updated

The challenge

Why do custom solutions stall before they ship?

Few marketing teams have tools built around how the work happens, where a trader sets up a campaign or a brand lead signs off on a version for a new market. What’s missing is usually small and specific: an approval rule, a product taxonomy, or an attribution method that no packaged tool supports.

Until now, teams have had two options. A consultancy writes a roadmap and leaves the build to your team, or the request joins an internal engineering backlog that can take months to reach it.

Campaign settings checked by hand across ad platforms

Trader hours on setup, and errors that slip through

What FDE deliversA tool that checks settings against your rules and stages the changes for a trader

A creative version for each market and format

Weeks of production for each launch

What FDE deliversA pipeline that generates, resizes, checks, and tags versions for brand and legal review

Packaged tools that ignore your approval chain

Work happens in spreadsheets beside the tool

What FDE deliversAn app built around your team’s approvals and decisions, in Alli Apps

Conversion signal lost to privacy changes

Bidding works from incomplete data

What FDE deliversFirst-party signal pipelines that send conversions back to the ad platforms

The system

What does a forward deployed engineer do at PMG?

A forward deployed engineer (FDE) is a software engineer who works inside a client’s business, alongside the people who run it, to find the problems that cost the most and solve them in production, with AI where it helps. At PMG, they map how decisions get made, then design and ship the systems behind them, and they stay until the team runs the system as part of its normal work. What they learn feeds back into Alli’s products, so later clients get those improvements as well.

The work ships in one of three places: inside Alli as an app in Alli Apps or an automation in Generative Workflows, as agent skills in Alli4u, or as an integration with the client’s own systems through their APIs. Each build has a named team that owns it and uses it.

FDE is separate from PMG’s other teams, so each request reaches the right people:

TeamWhat it deliversWhat it doesn’t do
Forward Deployed EngineeringSolutions in production: custom apps, API automations, agent skills, and integrationsBuild dashboards or run routine data pulls
Advanced AnalyticsDashboards, KPI reports, attribution models, and incrementality studiesBuild custom apps or automate platform actions
Alli product engineeringFeatures every Alli client getsBuild one-off tools for a single client
Account and strategy teamsAccount plans, media plans, and budget recommendationsWrite code or configure API integrations
In action

What problems does FDE solve?

These four examples show the kinds of engagement FDE takes on. They’re illustrations, so no client results are named.

Example scenario

Campaign and media operations

The situation

Traders set budgets, flight dates, and targeting across several ad platforms, then check each setting by hand. Pacing problems surface after the money is spent.

What FDE delivers

A tool that checks campaign settings against the client’s business rules, stages bulk changes through the platform APIs, and watches budget pacing. When delivery drifts, it posts a summary in Slack with the change it suggests.

What you decide

The rules each campaign is checked against, and each change before it goes live, with a trader signing off on it.

Example scenario

Creative and content production

The situation

A launch needs versions for each market, language, and ad format. Each one is made, resized, and checked by hand, and production takes weeks.

What FDE delivers

A creative automation pipeline that connects product data and the promotion calendar to image and language models. It generates versions, resizes them for each placement, checks them against brand rules, and tags them for reporting.

What you decide

The brand rules and the legal checks. Regional leads review each version before it goes to the ad platforms. The pipeline works alongside Alli Creative Studio, which handles template-based production.

Example scenario

A custom app for one team’s decisions

The situation

Some decisions, such as setting a promotion’s discount or localizing ads for franchise locations, depend on rules no packaged tool knows, so the team makes them in a spreadsheet.

What FDE delivers

A single-purpose app in Alli Apps, built around that decision: a promotion margin calculator, a store performance view, or a franchise ad manager. It has role-based access and logs each change.

What you decide

Who can use the app, what each role can change, and when a new version ships after its review.

Example scenario

Measurement and signal engineering

The situation

Privacy changes and disconnected point-of-sale data cause signal loss. They leave holes in conversion tracking, so ad platforms optimize against incomplete signal.

What FDE delivers

Conversions API pipelines, automated clean-room queries, and identity matching that send first-party conversions back to the ad platforms. Where Alli Audience Gateway covers the need with managed server-side tracking, FDE handles what sits around it.

What you decide

Which data is shared, with which platforms, under your privacy and consent rules. Reporting on the results stays with Advanced Analytics.

People in charge

Where do your people stay in charge?

Built to scale your team’s judgment, not replace it.

FDE designs the system and writes the code. Your team sets the rules it follows and signs off on the decisions that matter. Each engagement starts with a named owner who will use the system day to day.

Choosing the problem

What FDE and Alli doMap the workflow and size the manual effort

What your people doPick the problem worth solving, and name the owner

Setting the rules

What FDE and Alli doTurn the team’s criteria into checks the system runs

What your people doDefine the rules, and approve changes to them

Running the system

What FDE and Alli doStage changes, flag problems, and draft the next step

What your people doApprove each change before it goes live

Shipping new versions

What FDE and Alli doTest each version with the people who use it

What your people doReview each deploy, and decide when it ships

Measuring the result

What FDE and Alli doRecord what the system did and when

What your people doJudge whether it met the goal set at the start

What does FDE build on?

FDE builds on Alli, so each system starts from data and security that are already in place. Alli Data and the Semantic Layer give each system the same definitions and numbers. Alli4u is where engineers develop and test agent skills and automations. Alli Apps turns them into apps a team uses in its daily work, with role-based access, a review on every deploy, and an audit trail on every run.

For AI across the whole company, see Alli for Enterprise AI. For recurring jobs your own team sets up, see Alli for Workflow Automation.

See why teams trust Alli’s data 
Your options

How is FDE different from consultants or in-house engineering?

TopicOff-the-shelf softwareConsulting firmInternal engineeringForward Deployed Engineering
What you getStandard features built for all customersA roadmap and recommendationsCustom code, when the request reaches the top of the backlogA working system in production, built around your business
Who builds itThe vendor, for its whole marketYour team, after the engagementYour engineersPMG engineers, with your team
Time to productionImmediate, if the features fitAfter the roadmap, on your own timelineOften monthsTypically four to eight weeks
Fit with your rulesYou adapt to the toolDepends on your buildHighBuilt around your approvals and data
Getting started

How does an FDE engagement work?

Most engagements run four to eight weeks from kickoff to production, in three phases. Each one is tied to a business goal agreed at the start.

PhaseWhat happensWhat you have at the end
Discovery and scopeFDE maps the workflow with the people who do it, and agrees the goal and the first versionA scoped first version and the measure of success
Build with your teamFDE writes the first version and tests it with the people who’ll use it, week by weekA working version that your team has used and shaped
Harden and roll outSecurity review, production setup, and rollout to the whole teamThe system in daily use, with an owner and a support plan

FDE takes on work that meets three conditions. The problem has a clear business stake, such as margin, retention, or a large amount of manual work. A named person or team will use the system and own its rules. And the goal can be met in one bounded engagement.

Forward Deployed Engineering FAQ

What PMG’s Forward Deployed Engineering team does, and how an engagement works.

  1. What does FDE stand for?

    FDE stands for forward deployed engineer: a software engineer who works inside a client’s business, close to where the work happens, to solve its costliest problems in production. At PMG, Forward Deployed Engineering is also the name of the team those engineers belong to, so “FDE” can refer to either.

  2. What is Forward Deployed Engineering at PMG?

    It’s a PMG team of software engineers who work with a client’s business teams to build solutions on Alli and put them into production. They pick the problems with the biggest business stake and stay until the team runs the app, automation, or integration as part of its normal work. Your people set the rules and sign off on what the system does.

  3. How long does an FDE engagement take?

    Most engagements run four to eight weeks from kickoff to production. The first phase maps the workflow and scopes the first version. In the second, FDE delivers it and tests it with the people who’ll use it. The third covers the security review and rollout. Each engagement is tied to a goal agreed at the start.

  4. Does FDE build dashboards and reports?

    No. Dashboards, KPI reports, attribution models, and incrementality studies come from PMG’s Advanced Analytics team. FDE’s systems act: apps, automations, agent skills, and integrations that stage changes for people to confirm. When a project needs both, the two teams work on it together.

  5. Who owns the work when the engagement ends?

    Your organization owns the code. Each system has a named owner on your team from the first week. After rollout, FDE can keep supporting it, or your own engineers can take it over. Systems built in Alli Apps keep their role-based access, reviews, and audit trail either way.

  6. Is it secure to build on Alli?

    Yes. The Alli platform holds a current SOC 2 Type II report from an independent auditor. Apps built in Alli Apps use role-based access, deploy reviews, and audit trails. Agents act within each user’s existing permissions, and your security team checks the system before rollout.

  7. Does FDE work on AI search visibility?

    Yes. PMG’s teams, including Forward Deployed Engineering, do the AEO and GEO work for clients: readable pages, crawler access, structured data, and product feeds. Alli Brand Equity then measures how often AI answers name and cite the brand, next to the brand’s other signals.

  8. Who can work with Forward Deployed Engineering?

    FDE works with PMG clients on problems with a clear business stake and a named team that will rely on the system. Book an intro with your PMG team to talk through the workflow you want to change.

Bring us the problem that costs your team the most.

Book an intro and walk us through the problem. We’ll tell you whether it fits an FDE engagement, and what the first version would do. Forward Deployed Engineering is available to PMG clients.