B2B SaaS landing page copy prompt

When to use it

Use this when you need wireframe-ready landing page copy for a new software product. Swap the fictional product details with your verified positioning, features, and pricing before publishing.

The prompt

## Role
Act as a direct-response conversion copywriter for B2B technology products.

## Context
KitePulse is a lightweight equipment maintenance tracker built for independent craft breweries. Core features include scheduled cleaning checklists, QR-code asset tagging, and instant SMS alerts for tank temperature faults. The single tier costs $89 per facility monthly. A 21-day self-serve trial requires no credit card. The product is newly launched and lacks formal case studies or third-party integrations.

## Objective
Write complete landing page copy that communicates how KitePulse replaces chaotic paper logs and whiteboard schedules with automated maintenance tracking.

## Audience
Head brewers and brewery operations managers who manage cellar tasks manually and cannot afford complex enterprise asset management software.

## Requirements
Provide copy for six standard page sections:
1. Hero section: Headline, subheadline, primary CTA, secondary CTA, and microcopy.
2. Problem section: Highlighting lost batches, missed sanitization, and manual whiteboard tracking.
3. Solution & Features: Three distinct benefit blocks tied strictly to the three core features.
4. How It Works: A three-step onboarding overview (print codes, assign tasks, log scans).
5. Pricing section: Straightforward breakdown of the single monthly plan and trial terms.
6. Final CTA banner: Direct close focusing on cellar reliability.
Include two alternative headline options in the supporting notes.

## Constraints
Do not invent customer testimonials, partner badges, statistical claims (such as "reduces downtime by 40%"), or integrations with existing inventory systems. Rely strictly on the supplied feature set and pricing model.

## Tone & style
Pragmatic, grounded, and industry-aware. Use plain working language familiar to production staff. Avoid corporate fluff, buzzwords, and vague promises about "streamlining synergy."

## Output format
Deliver the landing page section by section using structural markdown labels (e.g., [Hero CTA Button]). Separate the page draft from review notes. End with a verification checklist highlighting assumptions that need operational sign-off.

## What to avoid
Avoid unverified performance metrics, generic placeholder text, and speculative claims about enterprise compliance or regulatory guarantees.

## Success criteria
A prospective buyer immediately understands the specific user, the mechanical problem solved, the monthly cost, and the exact process to begin a trial.

## Clarifying questions
If critical operational details are missing, surface up to three questions. Otherwise, complete the draft using the stated parameters and document all assumptions clearly.

Why it works

• The scenario grounds the copy in a specific, relatable niche rather than a generic B2B tool.
• The section-by-section breakdown ensures all essential structural elements of a landing page are written.
• Strict constraints eliminate fabricated social proof and fake ROI statistics that often ruin first drafts.
• The output format creates clean, wireframe-ready copy that developers or designers can implement immediately.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.