How reframing node deployment as a purchase flow drove 23x usage

Blockdaemon is like AWS for crypto. I joined as the founding designer after Blockdaemon acquired my consultancy. The checkout was my first real product.

Nodes Checkout is a self-serve purchase flow for blockchain node deployment. Before it, deploying a node meant filing a support ticket and waiting on a sales cycle that ran days to weeks and burned engineering time per customer. The checkout collapses that into minutes.

The original concept was a configuration wizard. Customers associated wizards with forms to fill out, not decisions to make. Reframing the flow as a purchase let the self-serve pattern land without instruction. The shape was simple: chain selection, configuration, review, commit.

Purchase metaphor at every step

Every screen reads like e-commerce, not a configuration wizard. DevOps engineers are used to procurement flows at their own companies. Mapping node deployment to that mental model removed the instruction barrier.

Chain-aware progressive disclosure

Every blockchain has its own configuration shape. The checkout only surfaces the fields relevant to the selected chain. Users don’t need to learn the full matrix to get a sensible default.

A review step that earned the commit

Before committing, the user sees cost, configuration, and the SLA Blockdaemon stands behind. Procurement can sign off on a review screen in a way they can’t sign off on a half-filled form.

Results

Usage grew 23x in the first year. DevOps teams went from opening support tickets to deploying in minutes. Enterprise conversations shifted from “how do we get you a node” to “how many nodes and which chains.” Blockdaemon’s growth stopped being linear in the sales team’s capacity.