# Saas Copywriter

> Write high-converting, Designjoy-style website copy for Quasar Store, Quasar University, FiveMCoach, or any FiveM/subscription/coaching/SaaS/marketplace business. Use this skill whenever the user asks to write, rewrite, or improve website copy, landing page copy, hero sections, pricing sections, FAQs, benefit sections, or any page copy for a subscription product, coaching offer, technical education business, or FiveM-related product. Also trigger when the user wants to "write the homepage", "write the pricing page", "write the landing page", "write the hero", "write copy for", or asks for SEO-friendly copy for any digital product. This skill produces the full structured output — hero, mechanism, problem, benefits, proof, pricing, FAQ, SEO metadata — in one pass. Trigger even if the user only mentions one section (like "write the hero"), because they will likely want the full page after seeing it.

- Skill: `maybackcompany/saas-copywriter` (Agent Skill)
- Install (CLI): `npx skillmds@latest add maybackcompany/saas-copywriter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/maybackcompany/saas-copywriter/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: MaybackCompany (https://skillmd.com/u/maybackcompany)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/maybackcompany/saas-copywriter

---


# Designjoy-Style SaaS Copywriting Skill

Write high-converting website copy for subscription, coaching, SaaS, marketplace, and
technical education businesses — particularly Quasar Store, Quasar University, and
FiveM-related products.

Copy must be simple, direct, SEO-aware, and built around customer intent.

---

## Core Writing Principles

- Short sentences.
- Clear offer first.
- No vague hype. No "revolutionary," "next-generation," "unlock your potential," or generic SaaS filler.
- Make the buyer understand the offer in under 10 seconds.
- Use concrete outcomes, not abstract benefits.
- Repeat the main category keyword naturally.
- Plain language before technical language.
- Every section answers: **"What is this, why should I care, and what do I do next?"**

### Words to avoid
> "Unlock your potential" / "Transform your journey" / "Revolutionize your server" /
> "All-in-one solution" / "Game-changing" / "Next-level" / "Seamless experience" / "Empower creators"

### Preferred phrases
> "Know what to build next." / "Stop wasting money on scripts that do not fit." /
> "Get a roadmap before you buy." / "Learn FiveM development with structure." /
> "Build a server that actually works." / "Turn your technical skills into something sellable."

---

## Required Output Sections

Always produce all of these, in order:

1. Hero copy + subheadline + primary CTA + secondary CTA
2. Simple 3-step mechanism
3. Problem section
4. Benefits section
5. Proof section
6. Pricing copy
7. FAQ copy
8. SEO title
9. Meta description
10. Target keyword list

---

## Section-by-Section Instructions

### 1. Hero

**Goal:** Define the category and promise immediately.

**Formula:**
```
[Category keyword] for [specific audience].

[One strong outcome promise].

[Risk reducer or friction reducer].

CTA: [Action verb] + [specific outcome]
Secondary CTA: [Lower-commitment action]
```

**Example structure:**
```
FiveM coaching for serious server owners.

Build your server with a clear roadmap, expert guidance, and fewer expensive mistakes.

Learn, launch, and monetize with support from the Quasar ecosystem.

CTA: Get My Roadmap
Secondary CTA: Compare Plans
```

**SEO keywords to include naturally in hero:**
FiveM coaching, FiveM server, FiveM scripts, FiveM development, QBCore, ESX, Qbox, Tebex, GTA RP server.

---

### 2. Simple Mechanism (3 steps)

**Formula:** Audit → Roadmap → Build (or equivalent for the product)

Each step: **Title** + one sentence under 30 words.

**Example:**
```
Audit
We review your server, goals, scripts, budget, and current technical level.

Roadmap
You get a clear plan for what to learn, what to build, and what to avoid.

Build
You follow the roadmap with support, reviews, lessons, and practical guidance.
```

---

### 3. Problem Section

Lead with a direct framing line, then list 4–6 concrete pain points.

**Lead line example:**
> "Before you buy another script, know what your server actually needs."

**Pain point examples:**
- You buy scripts that do not fit together.
- You do not know whether ESX, QBCore, or Qbox is right for you.
- Your server has bugs, conflicts, and poor structure.
- You want to learn Lua but do not know where to start.
- You want to sell scripts on Tebex but lack a real plan.
- You are building alone without technical direction.

---

### 4. Benefits Section

Each benefit: **Short title** + one clear explanation sentence.

**Example:**
```
Clear roadmap
Know exactly what to learn, build, install, and fix next.

Technical guidance
Get help with FiveM scripts, Lua basics, server structure, and framework decisions.

Script strategy
Understand which scripts fit your server before wasting money.

Launch support
Move from idea to playable server with a practical execution plan.

Monetization path
Learn how to turn skills, scripts, or server assets into revenue through Tebex.
```

---

### 5. Proof Section

**Proof hierarchy (use this order):**
1. Ecosystem proof
2. Customer proof
3. Product proof
4. Process proof

Let proof points breathe — do not over-explain.

**Quasar ecosystem proof (always available to use):**
```
60,000+ scripts sold
31,000+ Discord members
6 consecutive Tebex Legends Awards
Used by server owners, developers, and RP communities worldwide
```

---

### 6. Pricing Section

Each plan copy must answer:
- Who is this plan for?
- What does it help them do?
- What support level do they get?
- What is the next step?

Use outcome-based plan names or clear descriptions. Max 5–7 bullets per plan.

**Example structure:**
```
Builder
For beginners who want to learn FiveM development step by step.
[5–7 bullet benefits]

Elite
For server owners who want a roadmap, chat support, and regular guidance.
[5–7 bullet benefits]

Enterprise
For teams that want private instruction, deeper technical support, and hands-on help.
[5–7 bullet benefits]
```

---

### 7. FAQ Section

Always include answers to these objections (short, honest, specific):

| Question | Guidance |
|----------|----------|
| Do I need to know Lua before joining? | Reassure beginners, explain level-appropriate paths |
| Is this for complete beginners? | Direct yes/no + what they'll be able to do |
| Can I learn if English is not my first language? | Address multilingual/community support |
| Do you support ESX, QBCore, and Qbox? | Specific yes + any nuance |
| Can this help me sell scripts on Tebex? | Concrete yes + how |
| What is the difference between Elite and Enterprise? | Clear differentiation |
| Is this just a course library? | Address live support, mentorship, community |
| Can I get help with my own server? | Confirm direct help availability |

---

### 8–10. SEO Metadata

**SEO title:** Include primary keyword, under 60 characters.

**Meta description:** 150–160 characters. One sentence that includes the primary keyword and a clear value statement.

**Target keyword list:**

Primary:
- FiveM coaching
- FiveM server
- FiveM development
- FiveM scripts
- FiveM academy
- GTA RP server
- QBCore scripts
- ESX scripts
- Qbox server
- Tebex scripts

Secondary:
- Lua scripting
- server roadmap
- FiveM server setup
- FiveM monetization
- roleplay server development
- FiveM developer training
- Quasar Store
- Quasar Academy

**SEO placement rules:**
- Primary keyword in: H1, first paragraph, one H2, one CTA-adjacent sentence, one FAQ
- Do not keyword-stuff
- Write for buyers first, search engines second
- Each section should have one clear search intent: Learn / Compare / Buy / Join / Get support

---

## Tone Guide

**Use:** Clear, confident, practical, direct, slightly premium.

**Avoid:** Childish, corporate, overhyped.

---

## Quality Checklist

Before finalizing any copy, verify:

- [ ] Can a beginner understand the offer in 10 seconds?
- [ ] Is the main keyword visible without feeling forced?
- [ ] Is the CTA obvious?
- [ ] Does every section reduce confusion?
- [ ] Does the offer sound credible?
- [ ] Are claims specific but not exaggerated?
- [ ] Is the copy simple enough to scan on mobile?
- [ ] Does the page explain why Quasar/this product is different?

---

## Context: Quasar Ecosystem

Use these facts when writing for Quasar Store or Quasar University:

- **Quasar Store** — #1 FiveM script marketplace on Tebex. 60K+ scripts sold, 31K+ Discord members, 6 consecutive Tebex Legends Awards.
- **Quasar University** — Educational platform for FiveM server owners, Lua developers, and monetization-focused entrepreneurs.
- **Frameworks supported:** ESX, QBCore, Qbox
- **Monetization platform:** Tebex
- **Audience:** Server owners, FiveM developers, GTA RP community builders, aspiring script sellers

