Stripe docs starts with one product

Developer Markepear testimonials

What to say when you have many products? 

Dev tool companies over time grow from one product to suite of products to platforms with products built on top of the core one.

The result is that it is harder to communicate without going full-on fluff mode (my fav "built better software faster").

But for most companies, there is this core capability/product where people start.  The entry product. Why not use that?

I really liked what Stripe did on their docs page here:

  • They have maaaany products: billing, tax, radar, identity etc.  
  • But all of them are built on top of their core payments product
  • So they focus on getting folks to start with the payments
  • And make it clear that there are many other products

Even though this is docs, the same applies to homepages and other dev comms.

If you have many products, figure out what is the most important one, the one where most people enter. Focus on that. "Upsell" to other products later.

  • See Stripe docs
Browse 100+ examples like this ->
developer experience
pricing
docs

Pricing in the docs from fly.io

developer experience
landing page
hero section

Auth0 developer portal hero section visual

copy
call to action
landing page
hero section

Great developer-focused CTAs from Plaid

developer experience
docs

Devex in ReactJS documentation

copy
developer experience
landing page
hero section

Header design from Alpaca

copy
landing page
hero section

Auth0 header copy

copy
developer experience
call to action
landing page
hero section

Header content CTA from Plaid

developer experience
docs
hero section

Docs header diagram from Hopsworks

copy
developer experience
social proof
landing page
hero section

Landing page header from MedusaJS

copy
landing page
hero section

Header copy from Supabase