You Ship Code.
I Ship Copy.
Stop hiring writers who need you to explain your API. I'm a technical copywriter who reads documentation and writes revenue-generating copy for SaaS.
Telecom engineer turned B2B SaaS copywriter. 7+ years writing for technical products.
Your docs already tell the story. I turn it into copy.
Technical buyers want specifics, not adjectives. Here's what happens when a line from the docs becomes a line on the page.
From the docs
## POST /v1/events Accepts up to 500 events per request. Failed requests are retried with exponential backoff. Pass an Idempotency-Key header to prevent duplicate writes.
On the page
Every event lands. Exactly once.
Send up to 500 events in one call. If a request fails, it retries on its own, and nothing gets written twice.
From the docs
## SSO configuration Supports SAML 2.0 and OIDC. SCIM 2.0 provisioning syncs user create, update and deactivate events from your identity provider.
On the page
Remove someone in Okta. They lose access here too.
Single sign-on plus automatic provisioning, so access follows your directory and offboarding stops being a ticket.
From the docs
## Query performance Columnar storage. p95 query latency under 1s across 30 days of retained logs. No pre-indexing required.
On the page
Search a month of logs in under a second.
No indexes to plan ahead. Find the bad deploy while the incident channel is still filling up.
Illustrative examples written for this page, not client work.
Why SaaS copy loses technical buyers
It usually comes down to who wrote it.
A writer who didn't get the product
The page says you "streamline workflows." So does every competitor. Engineers read that and close the tab.
An engineer who knows it too well
Every feature is there and every claim is accurate. But it reads like a changelog, and buyers can't find the reason to care.
A template that sounds like everyone
Same headline formula, same benefit grid, same "Get started free." Buyers can't tell you apart, so they compare on price.
What I write
Copy for the pages and messages where technical buyers make up their minds.
See all services- Website and landing pages
- Homepages, product pages and campaign pages built around how your buyers actually evaluate tools.
- Messaging and positioning
- The core story your website, sales deck and onboarding all pull from.
- Onboarding and lifecycle emails
- Emails that get new signups to their first real result in the product.
- Product video scripts
- Scripts that make a complex product easy to follow on the first watch. More on video scripts
- Technical blog content
- Articles that rank, and that engineers actually finish reading.
Selected work
See all work17k+ Organic Views
Video script simplification for a complex DevTool. No ads, just clarity.
Read the case studySeries B Messaging
Complete website rewrite for an AI analytics platform post-funding.
Read the case studyHow a project works
-
1
Discovery call
30 minutes on your goals, your buyers and what the current copy isn't doing.
-
2
Product deep dive
I read your docs, use the product, and go through customer reviews or sales call notes if you have them.
-
3
Draft with reasoning
You get the copy plus short notes on why each section says what it says.
-
4
Revise and ship
We tighten it together until it's ready to go live.
Hi, I'm Bilal.
I studied telecommunications engineering before I started writing for a living. That's why API references, architecture diagrams and changelogs don't slow me down. They're where I start.
I've spent 7+ years writing B2B SaaS copy and content strategy. I'm also Google Ads certified, so I write landing pages with paid traffic in mind.
On the side, I run Techarizma, a tech content channel where I practice making complex ideas simple, in public.
Based in Karachi. Working with SaaS teams remotely.
Questions founders ask
Will I have to explain my product to you?
Less than you think. Send me your docs, a demo login or a recorded walkthrough. I'll still have questions, but they'll be the ones your buyers ask, not "what's an API?"
What do you need from me to start?
Access to your docs or product, any existing brand or positioning notes, whatever customer input you have (reviews, sales calls, support tickets), and one person who can give feedback.
How long does a project take, and what does it cost?
It depends on scope. After the discovery call, you get a proposal with a fixed price and timeline, so there are no surprises.
Do you use AI?
For research and organizing material, yes. The positioning, structure and final copy are mine, and every technical claim gets checked against your product.
Your product is good. Let's make the page say so.
Book a free 30-minute call. Bring a link to the page that's underperforming.
Book a Free Discovery Call