PostHog Handbook Library / Forward Deployed Engineering

1,619 words. Estimated reading time: 8 min.

FDE engagement lifecycle

Auto TL;DR

At a Glance

This long page covers these main areas. The list is generated from the article headings, so it updates with every handbook rebuild.

  1. Stages
  2. 1. Opportunity
  3. 2. Scoping
  4. 3. Pending acceptance
  5. 4. Active engagement
  6. Paused or stalled
  7. 5. Closed
  8. Completed

FDE engagements are short-term projects with a tight scope. We scope the problem, design the solution, and ship something production-ready in the customer's environment. Every engagement moves through the stages on this page.

Three principles apply at every stage:

Stages

  1. Opportunity
  2. Scoping
  3. Pending acceptance
  4. Active engagement
  5. Closed: completed, partial delivery, canceled, assisted, or lost
flowchart LR
    O["1. Opportunity"] --> S["2. Scoping"] --> P["3. Pending acceptance"] --> A["4. Active engagement"] --> C["5. Closed<br>Completed · Partial delivery · Canceled<br>Assisted · Lost"]
    O -. "Standard package" .-> P
    A -. "Paused or stalled" .-> A
    O -. "Didn't go ahead" .-> C
    S -. "Didn't go ahead" .-> C
    P -. "Declined or deadline passes" .-> C

An active engagement can also be paused or stalled.

1. Opportunity

An opportunity is a chance for FDE to help a customer in a way that grows revenue or protects the revenue we already have. Opportunities come from two places:

At this stage, we qualify the opportunity. Answer these questions:

Once the customer agrees to a scoping call, or asks an FDE for a formal proposal, the opportunity moves to scoping.

2. Scoping

The opportunity is qualified, and the customer is open to an engagement. Now we work out exactly what needs to be delivered for the engagement.

Scoping is free, so time-box it. If scoping turns into real work, such as an audit or a problem analysis we hand to the customer, record it. This work still counts if the engagement doesn't go ahead (see closed as assisted).

Once a formal FDE engagement proposal has been sent to a customer, the engagement moves to pending acceptance.

3. Pending acceptance

The customer has the proposal, and we're waiting for a signature.

Once the customer signs, the engagement moves to active engagement. If they decline, or the deadline passes without a signature, close it as assisted or lost, depending on whether we delivered any work. If the customer comes back later, start again from scoping, because the scope and our capacity have probably changed.

4. Active engagement

The customer has signed, and the engagement is in flight.

Once the customer's named owner approves the final deliverable and the handover is done, the engagement moves to closed. If the customer stops early, close it as partial delivery or canceled.

Paused or stalled

An active engagement can be paused or stalled when:

When this happens:

Once the customer re-engages, the engagement moves back to active engagement. If it stays paused or stalled for more than two months, decide with the team and the account owner whether to restart it or close it as canceled.

5. Closed

An engagement closes in one of five ways. For every closed engagement, record the stage it closed from, so we can see where in the pipeline engagements stall or drop out.

Completed

We delivered all the agreed milestones, and the customer approved them.

Retro

Every engagement that closes as completed, partial delivery, or canceled gets an internal retro. The purpose is:

The retro covers:

Partial delivery

The customer chose to stop after some of the milestones, and stopping there made sense for them. For example, the first milestones solved their main problem.

Canceled

The engagement was active, but it ended early for a negative reason. For example, the customer pulled out, or the engagement stayed paused or stalled for more than two months and didn't restart.

Assisted

The customer never became an active engagement, but we delivered work in an earlier stage, such as an audit or a problem analysis.

Lost

The formal engagement didn't go ahead, and we didn't deliver any work.

A retro on a lost engagement is optional. Consider one when the reason it was lost could teach us something, for example if pricing, scoping, legal, or a product gap blocked the engagement.

At the end of each quarter, we may also run a wider retro across all closed engagements from that quarter (completed, partial delivery, canceled, assisted, and lost), to help set objectives and improvements for the next one.

Canonical URL: https://posthog.com/handbook/forward-deployed-engineering/fde-engagement-lifecycle

GitHub source: contents/handbook/forward-deployed-engineering/fde-engagement-lifecycle.md

Content hash: 3e1818d9a41035aa

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: PrivateLink.