My role
Landing page copy and launch content
Products
InboxWP · weDocs · FlyWP
Launch pages
Launch posts
The situation
weDevs builds a family of WordPress products. Three of them solve technical problems buyers don’t always have words for: InboxWP handles transactional email delivery, weDocs turns WordPress into a documentation and knowledge base platform, and FlyWP manages servers for WordPress sites.
Each needed a homepage that a busy site owner, developer or agency could understand in seconds, and each launch needed readers from day one.
How I write a launch page
- Start with the buyer’s problem, in their words. The headline names the moment that sends someone looking, not the product category.
- Make one promise above the fold. One clear outcome, one supporting line, one action.
- Put outcomes before features. Each feature block opens with what the user gets, then explains how.
- Answer the cautious buyer. Setup effort, compatibility, pricing and support are answered on the page.
- End with a single next step. Every section points to the same action.
Launch distribution across sister blogs
A new product starts with no audience; its sister products already have one. I wrote launch posts for other weDevs product blogs, each with its own angle for that blog’s readers:
HappyAddons, InboxWP and weDocs blogs, including Introducing FlyWP for server management
WP ERP, weDocs and HappyAddons blogs, including Meet InboxWP for transactional email
Results
What I'd do next
Track sign-up conversion by traffic source, A/B test the headline, and interview the first 20 users to check the promise matches why they signed up.
From there: a one-page sales and partner brief for each product, and a short battlecard against the closest alternative.