It is a top-tier language model that reads, writes, and reasons at a higher level than older versions. Think: a tireless senior assistant who drafts, explains, and improves ideas on command.

Better at following instructions, stronger reasoning, longer context, and fewer made-up facts. In practice: clearer answers, less hand-holding, more “nailed it” moments.

No. It predicts text from patterns. The patterns are so good the results feel smart, but it is not conscious or self-aware.

Yes in tools that enable multimodal input. It can analyze screenshots, diagrams, and transcripts, then explain or transform them.

Very, but not perfect. Treat it like a brilliant intern: fast, helpful, and occasionally confident and wrong. Verify critical facts.

Large enough to keep long briefs and multi-step work in memory. Still, shorter prompts are faster. Chunk huge projects into steps.

Not across the board. It crushes summaries, how-tos, and planning. For breaking news, prices, or niche facts, verify with live sources.

It can be with guardrails. Teachers should set clear rules, use classroom plans where possible, and review outputs.

No. It runs in the cloud. You need an internet connection.

Use saved instructions or memory features where offered. For long projects, keep a shared brief and paste key context back in.

Use ChatGPT with GPT-5 enabled, or access it via supported APIs and partner apps. Paid plans see it first. Free tiers may get limited access later.

Sometimes with limits. For real work, plan on Pro or a team or enterprise plan for better caps and reliability.

Pricing changes over time. Historically it is in the “a few coffees per month” range. Check your account for current rates.

Pay as you go per token for input and output. It scales well. Monitor usage and set budgets so there are no surprises.

Do not. Get team seats. You will get shared workspaces, permissions, and usage tracking without violating terms.

Sometimes. Look for education or nonprofit programs, credits, or partnerships announced by the platform.

Open account settings. You will see daily message caps, rate limits, or token quotas depending on your plan.

Often yes via licensing. Enterprises can access GPT-5 style models inside productivity tools if enabled by their admin.

Yes. You keep access until the end of your billing cycle, then it stops charging.

Start with Pro. If you hit caps a lot, consider upgrading or using the API for batch jobs you can schedule off-peak.

Reasoning and instruction following. It stays on brief, handles nested instructions, and keeps logic cleaner across long tasks.

Yes, far less than GPT-4. “Less” is not “never,” so ask for sources and sanity-check numbers.

Generally yes, especially for well-structured prompts. Long outputs still take time. Chunk tasks for speed.

Excellent. Tell it the audience and purpose, then ask for bullet takeaways plus a one paragraph summary.

Yes. Give a mini schema like headings, bullets, tables. Ask it to follow the schema exactly and validate before sending.

Much better. Provide a short style guide and a paragraph sample. It will mirror rhythm, vocabulary, and pacing.

Within the context window, yes. For huge docs, process in sections, then merge with a final synthesis pass.

If browsing or source text is provided, yes. Otherwise it can suggest where to verify. Link to trusted references in public content.

Ask for “brief reasoning in 3 steps, then final answer.” This keeps outputs tight and focused.

Vague goals, hidden constraints, and edge cases. Be clear about success criteria and give an example of the desired outcome.

Yes if your brief is strong. Give the audience, pain, promise, proof, offer, and objections. Then ask for two or three angles before you pick a winner.

Short sentences, concrete examples, specific numbers, and light humor. Avoid hollow buzzwords unless your audience expects them.

AI detectors are hit or miss. Edit for voice, add lived details, and vary rhythm. Readers and platforms respond to that.

Outlines, FAQs, briefs, product bullets, meta, email subject lines, and ad variations. Keep flagship pages human polished.

It can cluster topics, map intent, and draft briefs. Use real tools for search volumes, difficulty, and SERP analysis.

Outline, approve, draft section by section, edit, conclude, then write meta. Review each step to prevent drift.

Yes. Provide the hook, target runtime, and CTA. Ask for beat by beat structure and B-roll notes.

Great for welcome flows, launch series, and re-engagement. Give the offer, timeline, and tone, then ask for five to seven concise emails.

Yes for headlines, primary text, variations, and angle testing. Check platform policies to avoid disapprovals.

Use real People Also Ask questions, answer directly in the first two sentences, add depth, link internally, and update monthly.

Yes. It scaffolds features, explains code, writes tests, and suggests fixes. You still own reviews and runtime testing.

Paste the error, the snippet, expected behavior, and environment. It often spots the issue faster than a junior dev.

Yes from simple selects to complex joins. Provide schema and a sample row. Ask it to explain the query in plain English.

Very well. Describe the pattern and ask for examples plus a quick test plan.

It can draft requests, map endpoints, and outline auth. You will plug it into your stack and handle keys securely.

Paste focused snippets, attach docs, or use tools that load files into context. Keep prompts modular per module.

Yes for summaries, trends, and hypotheses. Provide clean samples or a schema description and ask for a findings report format.

Yes. Ask for unit tests and edge cases, plus a checklist for manual QA steps.

Avoid secrets in public or consumer plans. For sensitive repos, use enterprise options and rotate tokens often.

You can use fine tuning via API with curated examples. For most teams, prompt libraries and retrieval are enough.

Yes: hooks, landing copy, outreach templates, and follow ups. Pair it with your CRM and automation stack to deploy at scale.

Ask it to audit messaging, friction points, and offers. It will suggest quick wins and A/B test ideas you can ship today.

Yes. Describe your process, tools, and owners. It returns a clean, numbered SOP with checks and handoffs.

Feed a column of context like name, niche, and one insight, then generate tailored first lines. Keep it respectful and relevant.

Yes for structure, scope bullets, timelines, and pricing options. You add the custom bits and proof.

It can model scenarios and assumptions. A finance pro should validate before you bet the house.

No, but it will cut hours. Keep strategy, creative direction, and final polish human.

High volume repetitive tasks: briefs, FAQs, ads, email lines, and repurposing. Save human time for strategy and sales.

It can draft plans, dependencies, and risk lists. A human PM still drives deadlines and trade offs.

Track time saved, tasks shipped, quality scores, and revenue influenced. Tie outputs to KPIs, not vibes.

Check your plan’s data policy. Many paid or enterprise plans limit training on your content. When in doubt, opt out and minimize sensitive inputs.

Use it for drafting and research only. A licensed professional should review final advice. Accuracy and liability matter.

State the helpful, harmless goal. Avoid dangerous or illegal asks. If blocked, reframe with safe intent.

It generates new text but can echo common phrasing. Use originality checks for public content and cite any quotes.

Only with permission and the right plan. Mask PII, remove secrets, and follow your contract.

Use enterprise features, data controls, and legal review. Keep an audit trail of sources and decisions.

All models have some bias. Ask for neutral, evidence based language and review sensitive topics carefully.

Yes, but follow privacy laws. Redact sensitive details and secure your archives.

Do not ask it to reproduce paid content. Quote briefly with attribution and link to the source.

Use sourced numbers, avoid absolutes, and prefer “based on tests” or customer quotes with permission.

You assign a job like “Senior CRO strategist.” It sets expectations for depth, format, and the kind of advice you want.

Yes. Say: “Before answering, ask me up to five clarifying questions.” Quality jumps when the brief gets tight.

Ask it to grade its output against your checklist, then improve. Two short passes beat one long draft.

Tell it: “No restating. No recap. New info only.” Then cap words and ask for bullets.

Brief, outline, section drafts, revise, final, QA. Keep each step in its own prompt thread.

Provide two or three samples and a mini style guide with five dos and five don’ts. Reuse with every prompt.

Yes. Ask it to generalize your best prompts into templates with variables for product, audience, and offer.

Work in short chunks, reuse templates, and set strict formats. Long wandering prompts waste tokens and time.

Paste core passages you trust, then ask for synthesis and contrast. You control the inputs. It does the heavy lifting.

Ask for numbered steps, roles, tools, timing, and a checklist. Test it once and fix gaps.

GPT-5 for most tasks. If you have old prompts tuned to 4, test both on the same brief and pick the cleaner output.

All are strong. Many pros keep two or three models and route by task like writing, coding, analysis, or creative ideation.

When you stall. A second model gives fresh angles or catches blind spots. Compare outputs, then merge the best parts.

Great for casual users. Power users often prefer manual control so they know exactly what is doing the work.

Often yes for instruction following and edits. But test alternatives on your specific use cases.

Depends on language and task. Try a short debugging snippet across models and pick the clearest fix and explanation.

API pricing varies. Run a 1,000 item batch test on each model and compare cost per usable output.

The one with enterprise controls you can prove in an audit: data handling, logging, and role based access.

Subjective. Give the same brief to two models and let your audience decide. Humor loves timing and specifics.

Start with GPT-5 in ChatGPT. It is approachable, strong out of the box, and great for learning fast.

Add specifics: audience, product, proof, and examples. Give a short sample of your voice and ask for two contrasting angles.

Conflicting rules or buried asks. Put the key instruction first, use bullets, and cut the fluff.

Ask for sources or add your own references. Tell it to flag uncertainty rather than guessing.

Set a word cap, request bullets, and ask for no recap and no filler. You control the scope.

Say: do not restate prior points. Then ask for net new insights only.

Provide a tiny schema and demand strict adherence. If it drifts, ask it to validate against the schema and fix.

Shorter prompts, smaller chunks, fewer examples. Save templates and reuse them with variables.

Share a one page voice guide, a prompt library, and a review checklist. Culture beats luck.

Time saved, tasks shipped, quality scores, and conversions. Track CTA clicks and assisted revenue.

Start small. Get one win today. Save that prompt. Build your library. Momentum makes experts.

Outline one flagship post, draft five short posts, write two newsletter intros, and script a 60-second video. Ship something daily for seven days.

Generate product bullets, comparison tables, FAQ snippets, and post-purchase emails. Add a returns explainer to cut support tickets.

Update Google Business profile copy, write location pages, create a services FAQ, and draft five neighborhood-specific posts.

Create ICP one-pagers, a sales deck outline, objection handling, and a five-email nurture. Add a case study template and fill one this week.

Lesson outlines, learning objectives, quiz questions, and homework prompts. Draft the sales page last so it matches the real content.

Mission rewrite, donor deck, grant draft, volunteer onboarding, and an email series that tells three short impact stories.

Episode outline, hook, guest questions, ad reads, and post-show summary. Repurpose into show notes and three social posts.

Client intake form, program roadmap, homework templates, and progress check-ins. Build a FAQ that pre-answers common hesitations.

Proposal boilerplates, onboarding checklists, creative briefs, and revision policies. Create a shared prompt library so the team writes in one voice.

Daily plan, meeting notes, decision matrix, and after-action review. At day’s end ask for a one paragraph summary and tomorrow’s top three.

“You are a polite SDR. In one sentence, write a personalized opener for {{prospect}} at {{company}} based on this fact: {{insight}}. Keep it under 22 words. No fluff.”

“Write product bullets in this style: benefit first, then feature, then proof. Five bullets max. Include one comparison bullet vs the status quo.”

“Write a 90-second script with hook, setup, 3 beats, CTA. Add B-roll ideas per beat. Tone: energetic, clear, and friendly.”

“Draft a case study with sections: Client, Problem, Plan, Execution, Results, Quote, Next Step. Ask me questions where data is missing.”

“Give me 7 ad variations: 3 direct, 2 story, 2 curiosity. 20 words max each. Include one hard number in three of them.”

“From this transcript, list 12 real customer questions. Remove duplicates. Sort by purchase stage. Draft concise answers in my voice.”

“Turn this brief into an outline with H2s and H3s. Add estimated word counts and two links I should include per section.”

“Write a 7-slide carousel outline: hook, promise, 4 tips, CTA. Each slide: 12 words max. Punchy and scannable.”

“Create an SOP with steps, owner, tools, timing, checklist, and failure modes. Keep it one page.”

“Summarize this call into decisions, owners, deadlines, risks, and open questions. Return a bullet list I can paste into our tracker.”

Define inputs, outputs, rounds of revision, and success criteria. Include what is out of scope so expectations are clean.

Have it draft a skeleton proposal, then you add case studies and numbers. Include a timeline and two pricing options.

Access, assets, approvals, brand guide, ICP notes, and goals. Ask GPT-5 to turn that into a one page client portal intro.

Two rounds included, then hourly. Feedback must be consolidated and specific. Turn vague notes into checklists.

Make a one page voice guide, a prompt pack, and a sample library. Review the first deliverable together.

Yes to simulate scenarios. You decide margins. Keep a buffer for extra rounds and research.

Briefs, outlines, meeting notes, and reporting paragraphs. Save the human touch for strategy and client calls.

Mask PII, use enterprise plans, and store source docs in your own vault. Share redacted context in prompts.

Define a few leading indicators like time saved, speed to first draft, and approval rate. Tie to funnel metrics later.

Keep a human in the loop on creative direction, claims, and final QA. The goal is better work, not robotic work.

Hook list, pick one, script 60-90 seconds, add B-roll prompts, write thumbnail text, and craft a one line CTA.

Outline chapters, write VO script, create chapter hooks, and draft lower-thirds. Ask for chapter summaries for your blog.

Transcribe, summarize, pull quotes, and create two carousels and three tweets. End with a CTA to your lead magnet.

Three to five words, big contrast, one idea, and no tiny subtext. Speak to curiosity or payoff, not both.

Lead with the hook, add one insight, then a micro CTA. Keep it snackable. Use line breaks to pace the read.

Ask for a 6-panel storyboard with scene, action, audio, and on-screen text. Keep each panel one sentence.

Open with a problem, add one vivid scene, make a single promise, then one clear CTA. 20–30 seconds max.

Time-stamp key moments, extract three clips, write titles and descriptions, and add a highlights summary to your blog.

Write brand, audience, vibe, three examples, must-use assets, and no-go rules. Ask for two routes before you commit.

Ask GPT-5 for 15 B-roll ideas tied to your beats. Keep each idea five words or less so it is easy to scan on set.

Ship evergreen pieces that you can update quarterly. Use modular sections so edits are fast. Keep claims sourced.

Personality, proof, distribution, and speed. The tools are common. Your taste, stories, and audience trust are not.

One page voice guide, prompt library, weekly show-and-tell, and a shared swipe file. Reward reuse and iteration.

Add specifics: numbers, names, places, screenshots, and your own phrases. Cut generic intros. Lead with a point of view.

Bad data, over-automation, stale claims, and vendor lock-in. Keep a checklist for QA and a plan B for key tools.

Monthly light edits. Bigger refresh when features change or performance drops. Track a freshness date on each page.

Be transparent when asked, avoid deception, cite sources, and respect privacy. Choose helpful and harmless by default.

Keep gold-standard examples. Re-run them monthly and compare quality. If quality slips, adjust prompts or try a newer model.

Ten minutes each morning to plan the day, then one small ship before noon. Consistency beats sprints.

Tools do not win. Operators do. Use GPT-5 to go faster, but keep your taste sharp and your promises real.

Pick three metrics max: one for reach (impressions or sessions), one for behavior (dwell time or scroll depth), and one for action (CTA clicks or sign-ups). Add a quality gate (editor score or peer review) so speed doesn’t kill standards.

Flag AI-assisted pages in your CMS. Track indexed URLs, average position, and clicks by page group. Watch time to publish and time to rank — AI’s edge shows up in cycle speed and volume shipped.

Use a simple rubric: clarity, accuracy, usefulness, and brand voice (1–5 each). Anything below 15/20 gets a rewrite. Keep samples of “gold standard” pages to calibrate the team.

Use UTM discipline and model the funnel. Compare assisted conversions for AI-assisted pages vs. human-only baselines over the same period. Direction beats perfection here.

Standardize utm_source, utm_medium, utm_campaign, and add a utm_content tag like “gpt5_v1”. Keep a live sheet so everyone uses the same tags.

Test one variable at a time (headline, CTA, first screen). Run until you hit a minimum sample size and 95% confidence, or timebox to two weeks to keep momentum.

Don’t end tests early on a spike. Use a calculator to set required samples based on expected lift. If traffic is low, use multi-armed bandits to allocate to winners faster.

Publish velocity, average edit time, rankings gained, top pages by dwell time, and CTA clicks. Add a “stale list” of pages older than 90 days without an update.

Lead with leading: outlines created, drafts approved, pages shipped. Lagging (rankings, revenue) follow. If the leads are healthy and lagging isn’t, fix distribution.

Paste KPI snapshots and ask for anomalies, wins, and stuck points. Then ask for three fixes you can ship this week. Keep the loop tight and practical.

Day 1: voice guide + prompt basics. Day 2: outlines. Day 3: first drafts. Day 4: critique loops. Day 5: ship something live. Keep wins visible.

Pick two workflows to automate first. Publish a playbook, run one pilot, then scale. Celebrate “hours saved” and showcase before/after examples.

Give them ownership: they set the style rules and do the final pass. Position GPT-5 as a power tool, not a replacement. Track time saved and redirect it to higher-value stories.

Use a shared library with: goal, inputs, variables, example output, and pitfalls. Version it like code. Retire prompts that cause errors or bland copy.

Reader, editor, admin — keep it simple. Editors can ship, admins manage settings and data controls. Use enterprise features when handling sensitive work.

Two-pass rule: fact check + voice check. Ask GPT-5 to self-critique against your checklist, then a human signs off. No solo publishes.

AI drafts → human sharpens → AI tightens → human final. Each pass has a purpose. Don’t ping-pong endlessly; cap revisions.

Give a real brief and a tight deadline. Look for taste, structure, and judgment. Tools help — taste sells.

Quality score, time to first draft, edit rate, and business impact (sign-ups or leads). Reward reuse of proven prompts.

Collect the prompt, inputs, outputs, and result. Ask GPT-5 for a 5-Why analysis, then capture one process change you’ll adopt next time.

Generally, the user who commissioned the work owns the output, but contracts rule. Spell it out in your MSAs and SOWs so nobody guesses later.

Platform vendors handle model training. Your job is to publish truthful, original work and cite sources when you quote or summarize.

Only with permission and the right plan. Mask PII, avoid secrets, and follow the client’s data policy. When unsure, don’t paste it.

Yes for public sites. Use clear headings, alt text, sufficient contrast, and readable link text. Ask GPT-5 to run an accessibility checklist before publish.

Collect minimal data, disclose usage, allow opt-outs, and secure logs. For GDPR/CCPA specifics, consult counsel and your platform’s enterprise docs.

Careful. Bias and local law apply. Use it to structure questions and summaries, not to make final decisions.

Yes on sensitive topics: “For information only, not professional advice.” Keep claims grounded and link to primary sources.

Keep secrets out of consumer plans. Use enterprise with data controls, and redact sensitive details even there. Contracts should define “confidential.”

Ownership, data handling, revision rounds, accuracy limits, and compliance responsibilities. Add a clause for model changes outside your control.

Store briefs, prompts, drafts, final versions, and sources. If audited, you can show how you arrived at claims and who approved them.

Listing bullets, neighborhood guides, and open-house follow-ups. Record a 60-sec video per listing and let GPT-5 draft captions and local hashtags.

Program outlines, check-in emails, habit tips, and recipe blurbs. Keep custom macros and health advice human-reviewed.

Service pages, FAQs, intake instructions, and reminders. No diagnoses or treatment plans — add disclaimers and review with licensed staff.

ICP one-pager, pain-promise proof headline, pricing table, and onboarding emails. Add a short “why we built this” founder story.

Service area pages, “before/after” galleries, and seasonal tips. Share real customer quotes and add a simple booking form.

Comparisons, FAQs, and “which is right for you” guides. Build trust first; CTAs work best after clarity and proof.

Story bank of 10 impact anecdotes, donor segments, and a 4-email nurture. Publish one success story per week with a photo and a specific ask.

Beta invite, social teasers, webinar outline, and a 5-email cart-open sequence. Add a student FAQ and two strong bonuses with deadlines.

Account briefs, personalized first lines, and objection handling by vertical. Ask for three value props tied to the buyer’s KPIs.

AI eats tasks, not whole roles. The combo that wins is human taste + AI speed. Your edge is judgment, story, and trust.

Clarity beats length. If a long prompt helps, it’s because it clarified the goal, not because it was long. Tight briefs, big wins.

Few-shot often wins for style and structure. One or two crisp examples anchor the output and reduce wandering.

Everyone can ship faster now. What stands out is a point of view. Be useful, but be you — that’s the moat.

Expect agents to chain tasks like draft → check → format → post. You’ll guide the plan and set the taste bar.

Optimize for answer engines: direct first sentence, depth after, and clean structure. Cite sources. Earn quotes and links.

Hub-and-spoke: one strong hub page with spokes for subtopics. Add a “freshness” date and update logs so crawlers and readers trust it.

• Ship one new FAQ page per week.
• Rewrite top 5 pages’ first screen.
• Spin 3 ad angles per offer.
• Add a CTA every ~600 words.
• Review claims; add sources.

• Prompt library + voice guide by Friday.
• Turn briefs into outlines in 10 minutes.
• Self-critique loop before handoff.
• Measure hours saved per deliverable.
• Show clients before/after examples.

• Update top 50 product bullets.
• Add 10 new Q&As to PDPs.
• Create comparison tables for bestsellers.
• Draft 5 post-purchase emails.
• Test a new hero headline weekly.

• Day 1 AM: Topic cluster + SERP skim → choose the pillar.
• Day 1 PM: Outline with H2/H3 + internal link targets.
• Day 2 AM: Draft section-by-section (critique loop on each).
• Day 2 PM: Add screenshots/examples, FAQs, and schema.
• Ship: Update date, interlink 3 ways, add CTA above the fold.

1) Cluster + outline

“Act as an SEO editor. Build a topic cluster for {keyword}. Return: (1) pillar H2/H3 outline with est. word counts, (2) 10 FAQ questions from People Also Ask intent, (3) 6 internal link ideas to related posts (anchor text + slug). Keep it concise.”

2) Section draft with examples

“Draft the section {H2} in 180–220 words, add a concrete example, and end with 3 bullet takeaways. Tone: clear, energetic, human.”

3) Interlink suggestions

“From this outline and these slugs {/post-1, /post-2, /tool}, propose 6 relevant internal links with natural anchor text and placement notes.”

Hook: “Stop writing from scratch. Start with stories.” → share a 3-meal sample plan, a before/after mini-case, and a one-week content schedule. CTA to your toolkit.

• Comparison hub: Product vs. alternatives (table + scenarios).
• “Which is right for you?” Use cases by persona and budget.
• Feature explainer: Screenshots with captions, not fluff.
• Setup guide: 7 steps + pitfalls + FAQs.
• Objections page: Price, support, lock-in, data, ROI.

1) Comparison table

“Create a comparison table for {Product} vs {Alt1} vs {Alt2}: columns = Audience fit, Core features, Learning curve, Support, Pricing notes, Best for. Add one-sentence ‘who should pick this’ row.”

2) Objection crusher

“List top 7 buyer objections for {Product}. For each: a one-line empathic response, a proof point, and a CTA to a relevant tutorial.”

3) First-screen copy

“Write first-screen copy (headline, 2-line subhead, button text) for {Product} review. Angle: ‘clarity over hype.’ Add one credibility line.”

Lead with what agencies actually want: fewer tools, fewer tabs, faster proposals. Show a 3-step ‘day-one setup’ and link a checklist PDF. CTA button every ~600 words.

• Service pages with before/after photos and a simple pricing explainer.
• Neighborhood pages (landmarks, parking tips, local proof).
• Google Business Posts weekly (promo + photo + call button).
• FAQ page that kills phone-tag: hours, insurance, emergencies.

1) Service page draft

“Write a local service page for {service} in {city}. Sections: Who it’s for, How it works, Before/After, Pricing explainer, FAQs (6), Map blurb, CTA. Add 2 local references (streets/landmarks).”

2) Neighborhood page

“Create a neighborhood page for {area}: 3 benefits, 5 nearby landmarks, parking/arrival tips, and a 90-word ‘why we love serving here’ paragraph.”

3) Review response helper

“Write 3 versions of a warm, specific reply to this review: {paste review}. Include one detail that proves we read it.”

Publish “Emergency Dental in Rockford: What To Do Before You Arrive.” Include hours, map, call-now button, and a 5-Q FAQ. This page saves calls — and books visits.

• Brief: ICP, promise, proof, constraints, examples.
• Outline: H2/H3, word targets, assets needed.
• Draft: section passes with critique loop.
• QA: fact check + voice check (two-pass rule).
• Delivery: changelog + next steps + test ideas.
• Retros: save best prompts, retire weak ones.

1) Proposal skeleton

“Draft a proposal for {project}. Sections: Goals, Scope (in/out), Timeline, Deliverables, Success metrics, Assumptions, Risks, Pricing options (2), Next steps. Ask 5 missing questions.”

2) Revision policy

“Write a friendly, firm revision policy: 2 rounds included, consolidated feedback, response within 3 business days, scope creep examples.”

3) QA checklist

“Create a pre-publish QA checklist for {content type}: claims, links, screenshots, accessibility, schema, first-screen strength, internal links.”

Ask for a 4-email “save” sequence targeting the top 3 reasons clients cancel. Include a 10-minute setup video and an offer to fix one thing free.

“Score this draft against {checklist} (1–5 each). List 5 fixes. Apply them without changing meaning. Keep tone: {tone}.”

“From these sources {links or pasted snippets}, synthesize consensus, list disagreements, and cite each claim inline.”

“Create an angle matrix: rows = benefits, cols = persona, third dimension = channel. Return 12 headline ideas across the grid.”

“Rewrite the first screen for {page}: headline, 2-line promise, proof line, and CTA text. Add one credibility badge idea.”

“Summarize this CSV (columns: {cols}) into: 5 insights, 3 risks, 3 quick tests. Add a plain-English recommendation.”

“From these URLs, list content gaps, missing FAQs, and trust signals we can beat in 7 days. Output a punch-list.”

“Given the top 5 results for {keyword} (paste summaries), write a reverse brief: what they cover, what they miss, and how we win.”

“Create 5 press angles with a 20-word founder quote each. Themes: data, human story, industry shift, local impact, contrarian take.”

“In 60 minutes: outline a post, draft 2 sections, write a LinkedIn post, craft a 45-sec video script, and a 3-email follow-up.”

“Audit this page: freshness date, claim checks, new screenshots, internal links added, 3 new FAQs. Return an update plan for this week.”