Describe the workflow once.
This form captures the minimum context needed to qualify fit without another back-and-forth just to understand the workflow.
DriftFence is easiest to evaluate when the workflow is concrete: one critical path, one owner, and one CI slice that can exercise the behavior before merge.
Use the intake to decide whether this workflow is ready for a team plan, needs a paid pilot, or needs a clearer boundary before DriftFence is useful.
This form captures the minimum context needed to qualify fit without another back-and-forth just to understand the workflow.
The best fit is one workflow where silent behavior drift has a real operational cost. The first workflow setup path shows what implementation needs; the results page shows the current measured contract-gate proof.
Use Team when the first workflow is already clear. Use Pilot when you want shared rollout work, explicit success criteria, and tighter implementation support.
This page does not send your details to a hosted intake service. It generates a structured private email you can review before sending.