Self-Service Cybersecurity Purchasing

Turn assisted enterprise purchasing into a self-service path for SMB customers

CrowdStrike’s enterprise sales model was built around high-touch deals. The checkout connected a marketing-led storefront to Chargebee customer and payment records so SMB customers could understand a product, create or verify an account, provide billing and payment information, and complete an order.

The screen was simple; the customer states behind it were not

Account identity, subscription state, payment methods, product eligibility, order records, and Chargebee all shaped what a customer could do. A clean screen would not help if those dependencies produced the wrong next step.

Keep the model adaptable while account and payment rules moved

Cart scope shifted, payment options changed, and the team was learning Chargebee’s boundaries. Two marketing teams, engineering, product, and product leadership brought different priorities, so the design had to preserve a stable sequence while individual requirements changed.

Design the state model before polishing the path

New and returning customers required different context. Missing payment methods, incomplete accounts, and existing subscriptions needed explicit recovery.

1. Identify account
2. Resolve eligibility
3. Select product
4. Recover payment
5. Confirm subscription
6. Preserve order context

Use familiarity as a risk-control strategy

Competitive and heuristic review compared stepped, all-in-one, and sidebar directions. The team selected the all-in-one model because it kept the sequence and order context visible and could reflow naturally on mobile.

Trace each customer state back to the rule creating it

The checkout was not one happy path. Customer progress depended on account, payment, and order states, with recovery interrupting the sequence when those records were missing or incomplete.

Protect the workflow when a visual decision changes

I recommended a restrained card treatment; product leadership preferred a larger branded visual. I presented the competitive evidence and mobile implications, then carried the selected direction into the final design while preserving sequence, review, and recovery.

Use the preserved evidence without inventing precision

The work included competitive and heuristic analysis, concept comparison, stakeholder reviews, and usability testing.

The workflow is documented; the business effect is not

The delivered work included the selected all-in-one model, new- and returning-customer screens, persistent order context, missing-payment recovery, and responsive criteria.

1. Measured: no checkout-specific production metric is sufficiently supported
2. Context only: the work occurred during company growth; causation is not established
3. Not proven: launch scope, completion, conversion, adoption, support reduction, or revenue impact

Familiarity was a risk-control decision, not a lack of ambition

The important work was translating account and payment rules into understandable states, preserving recovery, and knowing which visual tradeoffs could change without breaking the customer workflow.