Abhibhaw Asthana

Work / Devtron · Growth and enterprise

Devtron Platform: a trial that converts, and approvals enterprises need

Trial users left before they saw value, and regulated enterprises could not adopt us without sign-off before production changes. I fixed both.

4xinbound leads
33%faster conversion to paid
3xmore likely to stay, for users who deployed in 20 minutes
User
Teams evaluating Devtron in a trial, and platform teams at regulated enterprises such as banks.
Problem
Trial users left before their first deploy. Enterprises could not adopt Devtron without sign-off before changes reached production.
Decision
Rebuild the trial around one guided first deploy. Add multi-level approvals and deployment windows that plug into the existing release flow.
Not built
More features in the trial. The data showed that setup friction, not missing features, stopped conversion. For approvals, no separate workflow engine: rules attach to the deploy flow teams already use.
Result
4x inbound leads and 33% faster conversion to paid. Approvals became a key reason enterprises chose Devtron.

Devtron is an open-source platform that companies use to deploy and run software on Kubernetes. This case covers one growth problem and one enterprise problem.

Part 1: The trial

Users who deployed their own app within about 20 minutes stayed 3 times more. Most never got there.

Before
  1. Sign up
  2. then
  3. removed: Connect cluster, set up pipeline, find next stepmost users stopped here
  4. few reach
  5. First deploy
After
  1. Sign up
  2. guided path
  3. First deployusers who got here in 20 min stayed 3x more
  4. then
  5. Paid33% faster
The trial now leads to one goal: the user's own app, deployed.

I left out new trial features. Users left before they saw the features we already had.

Devtron welcome screen with three starting paths: deploy a Helm chart, connect a cluster, create an app

Onboarding today starts from direct paths to a first deploy. Public image from Devtron docs.

Result: 4x inbound leads, and 33% faster conversion to paid.

Part 2: Approvals

In more than 15 interviews, regulated companies said the same thing. Their rules required sign-off before any change reached production.

Production release
  1. Deploy or config change
  2. needs
  3. Approval policy1 to 6 approvers, people or groups
  4. then checks
  5. Deployment windowblocked or maintenance period
  6. releases to
  7. Production
Emergency
  1. Named person
  2. acts, and it is recorded
  3. Production
Approvals attach to the release path teams already use.
Create approval profile screen requiring approvals from specific users before deploying to banking-prod

An approval profile for production. Public image from Devtron docs.

Dialog saying deployment is blocked, with time until the restriction ends and the users allowed to act

A deployment window says who may still act, and for how long. Public image from Devtron docs.

Result: approvals became a key reason regulated enterprises chose Devtron.