i · the brief
page i

We fix B2B SaaS
landing pages.

A small studio. Founders send us their URL; we send back better copy in days, not months. Same diagnostic framework on every page, applied by careful eyes.

Built for: B2B SaaS founders, $10K–$200K MRR devtools especially

ii · a marked page
page ii the work, plainly

This is what we actually send.

A marked-up version of your page — every line we'd strike, every line we'd replace, with the new copy already written in the margin. The deliverable is the editing of the page, not a deck about it.

excerpt · hero section

The Modern Platform for Workflow Automation
Run your customer-success playbooks without copy-pasting between Slack and Notion.

generic, names no buyer → rewrite specific

Built for modern teams who want to scale.
For CS leads at Series B SaaS who run 10+ playbooks/week and lose the thread between tools.

  • Powerful → 12-step automation workflows
  • Seamless → 30-second integration with Slack, Notion, Linear
  • Enterprise-grade → SOC2-audited security
adjectives → numbers every claim testable

stet · 10 more sections marked · 5-DAY DELIVERY


iii · what we believe
page iii a short essay

Most B2B SaaS pages say nothing.

If you read forty B2B SaaS landing pages in a row, a strange thing happens. The pages start to merge. They all use the same six adjectives — fast, easy, powerful, seamless, modern, intelligent. They all name the same five integrations. They all have the same three-column "Why us" section with the same three icons. After page ten, you couldn't tell whose product is whose.

The pages aren't bad, exactly. They're just unwilling to commit to anything. They describe the category instead of the product. They name "modern teams" instead of senior PMs at Series B startups. They promise to "transform workflows" instead of saving twenty minutes on the Tuesday playbook review. The writing is generic because committing to specifics feels risky — and being specific is exactly the thing that would help the visitor decide.

Our entire job is the opposite of that. We read the page, find every place it has settled for a category-level statement, and rewrite it as a product-level statement. "Modern teams" becomes "customer-success leads at Series B SaaS." "Faster workflows" becomes "a Tuesday playbook review that takes 18 minutes instead of an hour." The buyer who reads the new version recognizes themselves. The one who doesn't was never going to buy.

That's the whole thesis. Specificity converts. Generic doesn't. Most founders know this. They just don't have the time, the writing chops, or the outside perspective to fix the pages they've been staring at for months. So we do it for them.

— Stet


iv · three doors
page iv three ways to work with us

Same product, three depths.

Pick the one that matches how much we're doing for you.

Snapshot Audit

$147 · one-time

A 48-hour written audit. You implement the fixes.

  • 6–8 page PDF with annotated screenshots
  • Your page graded across 10 conversion dimensions
  • Top 5 priority issues, ranked and explained
  • Recommended direction for every fix
  • 48-hour turnaround · 7-day refund
Get a Snapshot — $147

Ongoing Optimization

$1,497 · per month

For founders who want the page to keep improving.

  • Monthly tests and fresh rewrites as your product evolves
  • Conversion data review with recommendations
  • Unlimited written Q&A
  • ~20 min/week from you · we do the rest
  • Three-month minimum · cancel anytime after
Talk to us

Specificity converts. Generic doesn't. The whole framework is built around that single idea.

v · the framework
page v the diagnostic framework

Ten dimensions. Same rubric, every page.

Every page we audit is graded on the same ten dimensions, in the same order, with the same red/yellow/green scoring. Two different auditors should arrive at the same diagnosis on the same page. That's the point of a framework.

i.Hero clarityCan a first-time visitor name what this product does in eight seconds?
ii.Problem articulationIs the buyer's pain named specifically enough that they recognize themselves?
iii.Value-prop specificityAre the claims testable, or could they apply to any product in the category?
iv.Who-it's-for clarityIs the target buyer named in a way that lets visitors self-classify?
v.Social-proof placementDoes proof arrive when doubt arises, or get dumped in one section?
vi.Objection handlingAre the buyer's top three hesitations addressed before they have to ask?
vii.CTA prominence & languageDoes every CTA say what happens after the click?
viii.Visual hierarchyDoes the eye flow through the page in the order the argument needs to land?
ix.Mobile parityDoes mobile preserve the desktop argument, or degrade into something worse?
x.Comparison framingWhen the buyer is choosing between alternatives, does the page help?

vi · short answers
page vi quick questions

Things worth knowing.

Who is this for?
B2B SaaS founders between roughly $10K and $200K in monthly revenue. Solo or small teams without a dedicated marketer. Our starting wedge is devtools — founders whose customers are software engineers — but the framework applies to any B2B SaaS in our revenue band.
Who is this not for?
Consumer products. Enterprise-only SaaS sold through procurement cycles. Course-creator funnels. Local service businesses. Pre-launch products without a real landing page. If we don't think we can help, we'll say so before charging anything.
How fast is "48 hours"?
Calendar hours from your payment, capped at two business days. We don't audit on weekends. Pay Monday morning, get the Snapshot by Wednesday morning.
Why don't you do calls?
Because the work is the work. Calls eat hours, decks add friction, and every minute spent on a video meeting is a minute we're not auditing pages. Everything we'd say on a call lands better in writing — you can re-read it, share it with your team, search it. The deliverable replaces the conversation.
Refunds?
Seven days, no questions, no calls. Reply to the delivery email and we refund. You keep what we sent.
Why "Stet"?
It's a proofreading mark — Latin for let it stand. Editors write it in the margin to tell typesetters which edits to keep. Our entire job is exactly that: look at landing pages and decide what stays, what changes, what gets struck.

vii · about
page vii about us

The brand is the work.

Stet is a small studio. We don't show our faces publicly because the brand is the work — if our audits don't speak for themselves, no founder photo would fix that. Every deliverable is written, designed, and built to be read once and acted on.

We use the same framework on every page we audit, and we'll keep using it after you've seen it. The framework is the IP. The output is yours.

Questions, intros, anything: hello@usestet.com.