DEV Community: Stephane Guertin

PixelPunch SysAdmin Day Gift Guide for 2026

Stephane Guertin — Thu, 23 Jul 2026 04:16:47 +0000

PixelPunch SysAdmin Day Gift Guide for 2026

A practical, funny gift guide for sysadmins, DevOps engineers, and anyone who keeps the servers running while everyone else is on vacation.

Practical gifts that do not feel corporate

A mechanical keyboard that sounds like a freight train but feels like butter
A UPS unit small enough to hide under a desk, big enough to save a sanity
A decent monitor arm, because cable management is a lifestyle
A subscription to a cloud cost tracker so the CFO stops asking questions

Funny gifts that actually land

A mug that says "It's not DNS" on one side and "It's never DNS" on the other
A hoodie with "99% AI, 1% PANIC" for the agentic engineer in your life
A sticker of a coffee mug with server-rack hands, because why not
A T-shirt that reads "I read the logs so you don't have to"

Shop the Hoojump SysAdmin collection

If you want gifts that blend utility and inside jokes, the PixelPunch store on Hoojump covers mugs, hoodies, stickers, and shirts.

How to save $1,000 in 12 weeks using a spreadsheet (a system that actually works)

Stephane Guertin — Sun, 19 Jul 2026 08:00:09 +0000

I've tried a lot of savings challenges over the years. The "save $1,000 in 30 days" plans always made me laugh — who has an extra grand lying around every month? The "just cut your coffee" advice felt insulting. And the envelope system? I lost two envelopes in the first week.

But the 12-week savings sprint? That one stuck. Here's why: it breaks a big number into small, weekly chunks your brain can actually handle, and a spreadsheet does all the math so you don't have to think about it.

Why 12 weeks instead of 30 days

A month is too short to build a habit. Twelve weeks gives you enough runway to make saving automatic without feeling like you're signing up for a year of suffering.

Here's the math that made me a believer:

$1,000 ÷ 12 weeks = $83.33 per week
$83.33 ÷ 7 days = $11.90 per day

That's roughly the cost of one fast-food lunch and a coffee. Skip those two things, and you're halfway there before you even try.

But here's the part most savings plans get wrong: they assume you'll save the same amount every week. That's not how real life works. Some weeks you'll have extra cash — birthday money, a freelance payment, a refund. Other weeks you'll be scraping by. A good system accounts for both.

The spreadsheet method that makes it painless

I built this approach around a simple Google Sheets template. No macros, no formulas you need to understand, no fancy financial modeling. Just three columns:

Week number (1 through 12)
Target amount (what you planned to save that week)
Actual amount (what you actually saved)

The spreadsheet automatically tracks your running total and shows you how far ahead or behind you are. That feedback loop is the secret sauce. Seeing a green number that says "+$42.50 ahead of schedule" is surprisingly motivating. I didn't expect it to work, but I found myself checking the sheet every morning just to see the number go up.

The weekly savings ladder

Instead of saving the same amount every week, I use a ladder approach:

Weeks 1-4: Save $60/week (easier to start)
Weeks 5-8: Save $85/week (the middle grind)
Weeks 9-12: Save $105/week (the final push)

This adds up to exactly $1,000. The low start gives you momentum before the harder weeks hit. By week 9, you've already banked $580 and the finish line is in sight. That feeling alone kept me going through the tougher weeks.

Where the money actually comes from

I'm not going to tell you to "just stop buying avocado toast." Here are the five categories where I found real, painless savings:

1. One subscription, cancelled. I had three streaming services I hadn't touched in months. Cutting one saved me $15/month. That's $45 over 12 weeks.

2. One meal out replaced per week. Cooking one extra dinner at home instead of ordering in saved me roughly $20/week. That's $240 over 12 weeks. My bank account definitely noticed the difference.

3. The "wait 48 hours" rule on non-essentials. Every time I wanted to buy something I didn't need, I put it in a spreadsheet cell and waited two days. About 60% of those purchases never happened. That saved me roughly $30-50 per week. The weird part? I didn't miss most of the stuff I didn't buy.

4. Bank the windfalls. Any unexpected money — a $25 gift card, a $50 refund, a small freelance check — went straight into the savings bucket. Over 12 weeks, this added up to about $180.

5. The weekend challenge. I picked one weekend where I spent zero dollars. No takeout, no shopping, no paid entertainment. It's harder than it sounds, but it's a one-time thing and it frees up $50-100 in a single weekend.

Add those up and you're well past $1,000 without ever feeling like you're depriving yourself.

The spreadsheet template I use

I built a free Google Sheets template that handles all of this automatically. It has the weekly ladder built in, a running total tracker, and a simple dashboard that shows your progress at a glance. No signup required, no email list, just a link you can copy.

Download the free budget spreadsheet — it includes the 12-week savings tracker plus a full monthly budget template.

If you want something more structured with pre-built weekly targets and a visual progress bar, I also made a paid version that adds goal tracking, expense categorization, and a printable PDF tracker. It's $2.99 and it's basically the same system I've been using for the last two years.

Check out the 12-week savings sprint template

What to do when you fall behind (and you will)

Here's the honest truth: you will miss a week. Something will come up — a car repair, a birthday dinner, a surprise bill. When that happens, most savings plans tell you to "just try harder." That's useless advice.

Instead, here's what the spreadsheet approach does differently: it lets you flex. If you only saved $40 in week 3 instead of $60, the spreadsheet recalculates your remaining weeks automatically. You can see exactly how much extra you need to save each week to still hit $1,000 by week 12.

No guilt. No starting over. Just a new number to aim for.

Why this beats the envelope system

The envelope system (cash in labeled envelopes for each category) works for some people, but it has a major flaw: once the cash is gone, you can't track where it went. A spreadsheet gives you a permanent record. You can look back at week 7 and see exactly what worked and what didn't.

Plus, digital tracking means you can automate parts of it. Set up a recurring transfer from checking to savings on payday, log it in the spreadsheet once, and forget about it. The envelope system requires you to physically go to an ATM, withdraw cash, and stuff envelopes. In 2026, that feels like using a flip phone.

The $1,000 milestone matters more than you think

$1,000 is the threshold that financial experts call "the beginning of an emergency fund." It's enough to cover most car repairs, a deductible, or a last-minute flight. Once you hit $1,000, the psychological shift is real. You stop feeling like one bad week could ruin you.

And once you've done it once, you know the system works. The second $1,000 is easier. The third one is automatic.

Ready to start?

The hardest part is the first week. Open the spreadsheet, set your first weekly target, and move $60 to a separate savings account. That's it. The spreadsheet handles the rest.

If you want the exact template I use, grab it here:

Free budget spreadsheet with 12-week tracker

Or if you want the full system with progress tracking and printable worksheets:

Savings sprint 12-week template ($2.99)

Either way, start today. Not next Monday. Not on the 1st of the month. Today. Open the spreadsheet, save the first $60, and prove to yourself that this works.

How to write real estate cold emails that actually get replies (with AI prompts)

Stephane Guertin — Wed, 15 Jul 2026 08:01:05 +0000

I've sent a lot of cold emails. Most of them went nowhere. A few got replies. A tiny fraction turned into actual conversations.

The difference wasn't luck. It was the subject line, the first sentence, and whether I'd bothered to learn anything about the person I was emailing.

Real estate cold emails are their own animal. You're reaching out to agents, investors, or homeowners who get pitched fifty times a day. If your email looks like a template, it's gone in under two seconds. If it sounds like you actually know who they are and what they need, they might read the whole thing.

I've been using AI prompts to speed this up without losing the personal touch. Here's what works for me.

Why most real estate cold emails fail

The biggest mistake is starting with yourself.

"Hi, I'm John from XYZ Realty and I specialize in..."

Nobody cares yet. You haven't earned the right to talk about yourself. The reader's first question is always: "Why should I care?" If your opening doesn't answer that, you've already lost.

Other common killers:

Generic subject lines ("Real estate opportunity" — instant delete)
No personalization beyond the name
Walls of text with no clear ask
Sounding like a robot (because it was written by one, badly)

The fix is simple in theory: lead with value, be specific, make it easy to say yes. In practice, writing 50 personalized versions of that takes forever. That's where prompts come in.

The framework I use

I don't ask AI to write the whole email. That produces generic garbage. I use prompts for the mechanical parts, then layer in the personal details myself.

Here's the process:

Research first. Spend 5 minutes on their LinkedIn, website, or recent deals. Find one specific thing: a recent sale, a blog post they wrote, a market they focus on. This is the part you can't skip.

Generate subject line options. Feed the research into a prompt and get 10 subject lines. Pick the best one or tweak it. Usually 2-3 are usable, and one is genuinely good.

Draft the body. Give the AI the recipient's context, your value proposition, and a specific ask. Then edit heavily. Like, rewrite half of it heavily.

Read it out loud. If it sounds like something a human would say, send it. If it sounds like a marketing brochure, rewrite.

3 prompts I actually use

These survived my own testing. They're starting points, not magic spells.

Prompt 1: Subject line generator

You are a real estate professional writing cold emails. Generate 10 subject lines for an email to [recipient name], a [role] who [specific detail about them]. My value proposition is [one sentence]. The tone should be professional but warm, not salesy. Avoid clickbait. Return only the list, no explanations.

I use this to get past the blank page. The first five are usually trash. Numbers 6 through 10 are where it gets interesting.

Prompt 2: Email body draft

Write a cold email body (max 150 words) to [recipient name], a [role] at [company/market]. I noticed [specific detail from research]. My value prop: [one sentence]. The ask: [specific, low-friction request]. Tone: direct, helpful, not pushy. Do not use flattery. Do not open with "I hope this email finds you well." Start with the specific observation.

The key constraint is "start with the specific observation." That forces the AI to lead with something real instead of a generic greeting. I've seen this single instruction turn a terrible draft into a decent one.

Prompt 3: Follow-up sequence

I sent a cold email to [recipient] about [topic] on [date]. No reply. Write 3 follow-up emails spaced a week apart. Each should add new value (a relevant article, a case study, a question) rather than just "checking in." Max 80 words each. Tone: helpful, not desperate.

Most replies come from follow-ups, not the first email. Having these ready means I don't forget to send them. And honestly, it removes the emotional friction of "ugh, I have to write another email to this person who ignored me."

A real example

Let me show you how this works.

Say you're reaching out to a real estate agent in Austin who just closed a deal in a specific neighborhood. You offer a service that helps agents generate listing leads.

Research: You find they sold 3 homes in the Mueller neighborhood last quarter.

Subject line (edited from prompt output): "Mueller comps you might have missed"

Body (edited from prompt output):

"Hey [Name],

Saw you closed a few in Mueller recently. That area's been moving fast.

I've been tracking off-market properties in that pocket that match your buyers' price range. Happy to share what I've got if you're interested.

Would a 10-minute call this week work?"

Short, specific, no fluff. It works because it shows you did the work and you're offering something useful, not asking for a favor.

When to use prompts vs. when to write from scratch

Templates are fine for the first pass. But if the deal matters, if this is a high-value client or a big commission, write the email yourself and use AI only for editing.

I use prompts to:

Overcome writer's block
Generate multiple angles quickly
Polish my drafts
Write follow-ups I'd otherwise procrastinate on

I write from scratch when:

I know the person personally
The relationship is already warm
The email needs to convey genuine emotion (apology, congratulations, condolences)

The one thing that made the biggest difference

I stopped trying to sound impressive and started trying to be useful.

Every cold email I send now passes this test: "If I got this email, would I reply?" If the answer is no, I rewrite. The prompts help me get to a yes faster, but the standard doesn't change.

If you're regularly sending real estate outreach and want a library of prompts tuned for different scenarios (listing acquisition, buyer leads, investor outreach, follow-ups), I put together a pack that covers all of them. It's called Real Estate AI Prompts and it includes 50 prompts organized by use case, plus a cheat sheet for personalization.

The bottom line

Cold email works when it's personal, concise, and valuable. AI prompts can save you the mechanical work of drafting and iterating, but they can't replace the research and the human judgment. Use them as a force multiplier, not a crutch.

If you're just getting started with AI-assisted writing and want to test the waters before buying anything, grab the free prompt sampler. It has 5 prompts from the real estate pack plus a few from other categories. No email required, just download and try.

The agents who get replies aren't the ones with the fanciest tools. They're the ones who actually read the other person's website before hitting send. AI just helps you do that faster.

Free budget spreadsheet vs. complete financial planner: which one do you actually need?

Stephane Guertin — Tue, 14 Jul 2026 08:00:44 +0000

I have used a free budget spreadsheet for years. It worked. Until it didn't.

The free sheet got me through my first apartment, my first side hustle, and the months where I just needed to know where my money went. But once I started juggling irregular income, sinking funds, debt payoff, and actual savings goals, the sheet started lying to me. It showed me what I spent. It did not show me whether I was actually winning.

That is the real difference between a free budget spreadsheet and a complete financial planner. One tracks. The other plans.

Here is how to know which one fits your life right now, and when it is worth upgrading.

What a free budget spreadsheet actually gives you

A good free budget spreadsheet is a mirror. You plug in your income and expenses, and you see the gap between them. That alone is powerful if you have never budgeted before.

You can:

List your monthly bills and due dates
Categorize spending so you spot leaks
Set a basic savings target
Stop overdrawing your checking account

That is honestly enough for a lot of people. If your income is steady, your expenses are predictable, and your main goal is "spend less than I make," a free tool will take you most of the way there.

The catch is that a spreadsheet like this is reactive. It answers, "Where did my money go?" It does not answer, "Where should my money go next?"

The moment a free sheet starts to fail

For me, the failure point showed up in three places.

Irregular income. Some months I made double. Some months I made half. My free sheet treated every month the same, so I either felt broke in good months or stressed in slow ones.

Sinking funds. Car repairs, annual insurance, holiday gifts. These are not surprises; they are predictable expenses pretending to be surprises. My free sheet had no clean way to set money aside monthly and hold it until needed.

Goal tracking. I wanted to pay off debt and save an emergency fund at the same time. The sheet could subtract debt balances and add savings balances, but it could not tell me which to prioritize or whether I was on track.

If any of those sound familiar, you have probably outgrown a basic spreadsheet.

What a complete financial planner adds

A complete financial planner connects the pieces. It still tracks income and expenses, but it also builds a system around them.

The better ones include:

Variable income budgeting. You budget off a baseline month and create rules for what happens when income is higher or lower than normal.
Sinking funds and savings buckets. Money gets assigned a job before it can be spent on something else.
Debt and goal tracking. You see progress over time, not just one snapshot.
Net worth view. Assets minus debts, updated automatically, so you know if you are actually moving forward.
Annual and quarterly planning. You stop living month to month and start planning in 90-day and 12-month windows.

That last one matters more than people think. A free budget sheet keeps you afloat. A planner helps you choose a direction.

If those pieces sound like what your money life needs, a complete planner is worth testing before you commit to building it yourself.

When to pick each

Start with a free budget spreadsheet if you are:

New to budgeting
On a fixed salary
Mostly trying to cut spending
Not ready to spend money on a tool

There is no shame in that. I think everyone should start with a free sheet for at least three months. It builds the habit before it builds the system.

Upgrade to a complete financial planner when you are:

Freelancing, contracting, or running a side business
Trying to hit multiple money goals at once
Paying off debt while also saving
Planning for a big purchase or life change
Tired of rebuilding the same spreadsheet every quarter

The question is not whether the paid tool is better. It is whether you will actually use the extra features. A complex planner you abandon is worse than a simple sheet you check every week.

A practical middle path

You do not have to choose between a napkin sketch and a full dashboard. I usually recommend this progression:

Month 1-3: Use a free budget spreadsheet to learn your numbers.
Month 4-6: Add a simple sinking fund and one savings goal to the same sheet.
Month 7+: If you are hitting friction, move to a complete planner that handles the complexity for you.

The free version keeps you honest. The paid version keeps you organized once honest is not enough.

Here is the first CTA: if you want a free starting point, the free budget spreadsheet covers income, expenses, and a basic savings tracker. It is built in Google Sheets, so it is easy to tweak. No email wall, no upsell pitch. Just a working sheet.

If you are already past that stage, the complete financial planner adds variable income handling, debt tracking, net worth, sinking funds, and annual planning. It is the tool I wish I had when I was still duct-taping my free sheet together.

And if you want both plus a few extra budgeting systems in one bundle, the ultimate budget bundle is the cheapest way to cover every stage.

The real win is not the tool

I spent too long believing that the right spreadsheet would fix my money problems. It did not. What fixed them was the habit of looking at my money regularly and making decisions before the month decided for me.

A free budget spreadsheet can build that habit. A complete financial planner can scale it. But neither works if you only open it once a month to feel guilty.

Pick the simplest tool that matches the complexity of your life today. Use it for thirty days. Then decide if you need more.

If your money life is starting to feel like a juggling act, grab the complete financial planner and give yourself one place where every dollar has a job. Sometimes the best financial move is just paying for a tool that makes the rest of your decisions easier.

12 Claude Code Skills I Wish I Knew as a Beginner

Stephane Guertin — Mon, 13 Jul 2026 21:46:57 +0000

I spent 3 months using Claude Code like a fancy autocomplete tool. Then I discovered skills — reusable instruction sets that turn Claude from a chatbot into a specialized engineering partner.

Here's what each skill does, why it matters, and the ones I wish I'd known from Day 1.

What Are Claude Code Skills?

Skills are structured markdown files that give Claude Code specific, reusable instructions for recurring tasks. Think of them as custom prompts that load automatically when Claude detects a relevant context.

Without skills, you're typing the same instructions every session: "Follow PEP 8, add type hints, write tests, handle edge cases." With skills, Claude knows to do all of that because the skill file tells it to.

The difference is night and day. Same model, same context window — but with structured guidance that makes the output consistently better.

The 12 Skills That Changed My Workflow

Skill 1: Code Review Before Push

Before any git push, review all changed files for: 1) Unhandled edge cases, 2) Missing error handling, 3) Hardcoded values that should be env vars, 4) Functions over 40 lines (refactor candidates), 5) Missing type annotations. Report findings as a checklist before pushing. Do not push if any critical issues are found.

Why it matters: Catches the stupid mistakes before they reach production. This skill alone has prevented ~15 bugs that would have made it to staging.

Beginner mistake it prevents: Pushing code without reviewing the diff.

Skill 2: Test-First Development

When asked to implement a feature, write the test first. The test should fail. Then implement the minimum code to make it pass. Then refactor. Never write implementation before tests. If the feature is hard to test, simplify the design until it's testable.

Why it matters: Forces simpler, more modular code. When you write tests first, you design for testability — which means better interfaces, smaller functions, and fewer side effects.

Beginner mistake it prevents: Writing 200 lines of code and then realizing it's untestable.

Skill 3: Commit Message Generator

Generate conventional commit messages from the git diff. Format: type(scope): description. Types: feat, fix, refactor, docs, test, chore, perf. Scope: the module or component affected. Description: imperative mood, max 72 chars, lowercase, no period. If the diff spans multiple concerns, suggest splitting into multiple commits.

Why it matters: Good commit messages are the cheapest documentation. This skill makes them automatic. The "suggest splitting" feature catches when you've mixed unrelated changes.

Beginner mistake it prevents: "update stuff" commit messages.

Skill 4: Dependency Auditor

Before installing any new npm/pip/cargo package, check: 1) Is it maintained? (last commit < 1 year ago), 2) Weekly downloads / GitHub stars, 3) Bundle size impact, 4) Are there stdlib alternatives? 5) Security advisories. Report findings before installing. Suggest the lightest alternative that meets the requirement.

Why it matters: Dependency bloat is the #1 cause of slow builds and security vulnerabilities. This skill adds a gate before any new package enters the project.

Beginner mistake it prevents: Installing a 50MB package for a one-function utility.

Skill 5: Error Message Improver

Review all error messages in the codebase. For each: 1) Does it tell the user what went wrong? 2) Does it suggest how to fix it? 3) Is it actionable (not just "Something went wrong")? 4) Does it include relevant context (input values, expected format)? Rewrite bad error messages in place.

Why it matters: Good error messages are UX. When a user sees "Error: invalid input" vs "Error: expected YYYY-MM-DD format, got 'July 14'", the second one saves a support ticket.

Beginner mistake it prevents: Generic error messages that force users to guess what went wrong.

Skill 6: Documentation Generator

For every exported function/class, generate: 1) A one-sentence description of what it does, 2) Parameters with types and descriptions, 3) Return value with type, 4) A usage example with code block, 5) Edge cases and error behavior. Format as docstrings (Python) or JSDoc (JavaScript). Do not document internal/private functions unless they're complex.

Why it matters: Documentation that's generated alongside code stays accurate. This skill makes docs a byproduct of development, not a separate chore.

Beginner mistake it prevents: "I'll document it later" (later never comes).

Skill 7: Refactoring Detector

Analyze the codebase for refactoring candidates: 1) Functions over 50 lines, 2) Files over 300 lines, 3) Duplicate code blocks (3+ lines repeated), 4) Deep nesting (3+ levels), 5) Functions with more than 4 parameters. Report as a prioritized list with suggested refactoring approach for each.

Why it matters: Technical debt compounds. This skill surfaces it early, before the codebase becomes unmaintainable.

Beginner mistake it prevents: Letting functions grow until they're unfixable.

Skill 8: Environment Setup Validator

When cloning or onboarding to a project, verify: 1) Required env vars are documented, 2) .env.example exists and is up to date, 3) Required system dependencies are listed (Node version, Python version, database), 4) Setup script exists and works, 5) No secrets are committed. Report missing items as a setup checklist.

Why it matters: Onboarding friction kills team velocity. This skill ensures new contributors can get running in minutes, not hours.

Beginner mistake it prevents: "It works on my machine" syndrome.

Skill 9: Performance Profiler

When a function or endpoint is slow, profile it before optimizing. Identify: 1) The bottleneck (CPU, I/O, memory, network), 2) N+1 query patterns, 3) Unnecessary re-renders (frontend), 4) Blocking operations in async code. Suggest the single highest-impact optimization. Do not suggest micro-optimizations (e.g., "use list comprehension instead of for loop") unless the function is in a hot path.

Why it matters: Most performance "optimizations" are premature. This skill forces profiling first, then targeting the actual bottleneck.

Beginner mistake it prevents: Optimizing the wrong thing.

Skill 10: Security Scanner

Scan code for common vulnerabilities: 1) SQL injection (string concatenation in queries), 2) XSS (unescaped user input in templates), 3) Hardcoded secrets, 4) Insecure deserialization, 5) Missing input validation, 6) Overly permissive CORS. Report findings with severity and fix suggestion for each.

Why it matters: Security issues are cheaper to fix during development than after deployment. This skill makes security review automatic.

Beginner mistake it prevents: Trusting user input.

Skill 11: API Contract Validator

When building or modifying an API endpoint, verify: 1) Request schema is documented (params, body, query), 2) Response schema is documented for all status codes, 3) Error responses follow the same structure, 4) Authentication is specified, 5) Rate limiting is documented. Generate or update the OpenAPI/Swagger spec automatically.

Why it matters: API contracts that drift from implementation are worse than no documentation. This skill keeps them in sync.

Beginner mistake it prevents: Undocumented API changes that break consumers.

Skill 12: PR Description Writer

Generate a PR description from the diff that includes: 1) What changed and why (link to issue if exists), 2) How to test locally (specific commands), 3) Screenshots for UI changes, 4) Breaking changes (if any), 5) Checklist: tests added, docs updated, migrations run. Tone: informative for reviewers, not self-promotional.

Why it matters: Good PR descriptions speed up review. Reviewers can focus on the code instead of figuring out what the PR is supposed to do.

Beginner mistake it prevents: "See commit messages" PR descriptions.

How to Use Skills

Start with 2-3 skills, not 12. Pick the ones that solve your most frequent pain points. Code Review Before Push and Commit Message Generator are the best starting points.
Customize for your stack. These skills are language-agnostic. Adapt them for your specific framework, style guide, and team conventions.
Iterate. A skill that works for one project may not work for another. Treat skills like code — version them, test them, improve them.

Get All 12 Skills (Plus Setup Guide)

If you want the full set — all 12 skills as ready-to-load files, plus a setup guide for Claude Code, Cursor, Windsurf, and Hermes Agent — it's available as a pack.

👉 Get 12 Claude Code Skills for Solo Founders — $19.99, instant download.

Or try a free 5-prompt sampler first — no signup required.

The biggest shift in my development workflow wasn't a new framework or a faster model. It was giving Claude structured instructions that made its output consistently good. Skills are that structure.

Which skill would you start with?

The Real Estate Agent's 45-Minute Listing Marketing System (5 Copy-Paste Prompts)

Stephane Guertin — Mon, 13 Jul 2026 21:41:46 +0000

A new listing drops Friday morning. You need the MLS description, three social posts, an email blast, and a flyer. That's normally a 3-hour job.

Here's how to do it in 45 minutes using 5 AI prompts — from listing live to fully marketed across every channel.

The 3-Hour Problem

Every realtor knows the drill. You get a listing signed Thursday afternoon. The seller expects it on the market Friday morning. Between signing and going live, you need:

MLS listing description (25 min)
Instagram post + Facebook post + LinkedIn post (20 min)
Email blast to your buyer database (15 min)
Neighborhood flyer for door-knocking (15 min)
Open house announcement (15 min)
Zillow/Realtor.com update (10 min)
Price positioning paragraph for the MLS remarks (10 min)

That's 110 minutes if you're fast. Most agents take 2-3 hours because they're writing from scratch, switching between formats, and second-guessing every word.

With the right AI prompts, you can produce all of it in 45 minutes — and the output is more consistent than what most agents produce manually.

The 5-Prompt Listing Marketing System

Run these prompts in order. Each one builds on the previous output. Total time: 45 minutes including editing.

Prompt 1: The Core Listing Description (5 minutes)

You are a real estate copywriter. Write a listing description for: [address, beds, baths, sq ft, lot size, year built, 3 key features, neighborhood name, price range]. Target buyer: [first-time buyers / move-up families / luxury / investors]. Format: 2 paragraphs, max 150 words each. Paragraph 1: lead with the one feature that differentiates this property from others at this price point. Paragraph 2: paint the lifestyle — what it feels like to live here, not just what it has. Avoid these words: stunning, gorgeous, must-see, nestled, charming, perfect. End with: "Schedule your private tour today."

Edit time: 5 minutes. Read it out loud. Fix any local details the AI got wrong. Add one specific neighborhood detail (park, school, restaurant).

Output: Your MLS description AND the base text for everything else.

Prompt 2: The Triple Social Post (10 minutes)

Take this listing description: [paste from Prompt 1]. Create 3 social media posts: 1) Instagram: casual, max 150 words, include 8 hashtags (mix of local + real estate), lead with a question or bold statement, include emoji sparingly. 2) Facebook: conversational, max 200 words, end with a question to drive comments, include price range. 3) LinkedIn: professional, max 150 words, frame as an investment opportunity, include one data point about the neighborhood market. Each post must have a different angle — not the same message rephrased 3 times.

Edit time: 5 minutes. Verify the hashtags are local and relevant. Add the listing photos you'll attach. Schedule each post for the optimal time (Instagram 11 AM, Facebook 1 PM, LinkedIn 8 AM).

Output: 3 social posts ready to schedule.

Prompt 3: The Buyer Database Email (8 minutes)

Write an email to my buyer database about a new listing: [paste key details from Prompt 1]. The email should: 1) Open with what makes this property different (not "New listing alert!"), 2) Include 3 bullet points of key specs (beds, baths, price, sq ft), 3) Mention one neighborhood amenity within walking distance, 4) Include showing availability, 5) End with "Reply to this email if you'd like a private showing." Max 150 words. Subject line: 3 options — one urgency, one curiosity, one direct.

Edit time: 3 minutes. Add your actual showing availability. Pick the best subject line. Send.

Output: Email blast ready to send.

Prompt 4: The Neighborhood Flyer (7 minutes)

Create text for a neighborhood flyer promoting this new listing: [address, price, beds/baths, one key feature]. The flyer will be printed and distributed to 50 homes around the listing. Include: 1) A bold headline (max 8 words), 2) A 2-sentence description focused on why this matters to neighbors (property values, neighborhood appeal), 3) "Coming to the market" or "Just listed" label, 4) Date and time of open house if scheduled, 5) My contact info placeholder, 6) A tear-off strip at the bottom with my phone number and "Free home evaluation" text. Format as a flyer layout guide (what goes where).

Edit time: 5 minutes. Add your real contact info. Design in Canva using a real estate flyer template. Print.

Output: Flyer text + layout guide, ready for Canva.

Prompt 5: The Open House Plan (10 minutes)

I'm hosting an open house for [address] on [date] at [time]. Create: 1) A Facebook event description (max 200 words, include what to expect, parking info, and "drop in anytime" language), 2) An Instagram story sequence (4 slides — for each: text overlay, visual description, and a sticker/poll suggestion), 3) A 2-day reminder email to my database (max 80 words, casual, "stop by if you're in the neighborhood" tone), 4) A neighbor invitation text message (max 160 characters, SMS-friendly). Make each piece feel inviting, not salesy.

Edit time: 5 minutes. Add real parking details. Schedule the Instagram stories. Send the text to neighbors.

Output: Complete open house marketing package.

The Full 45-Minute Timeline

Minute	Task	Output
0-10	Prompt 1: Listing description	MLS text + base content
10-20	Prompt 2: Social posts	IG + FB + LinkedIn posts
20-28	Prompt 3: Email blast	Buyer database email
28-35	Prompt 4: Flyer	Canva-ready flyer text
35-45	Prompt 5: Open house	Event + stories + texts

Total output: MLS description, 3 social posts, 1 email blast, 1 flyer, 1 Facebook event, 4 Instagram story slides, 1 reminder email, 1 SMS blast. 13 pieces of content. 45 minutes.

Compare that to the 3 hours most agents spend — and the AI-assisted version is often more consistent because every piece follows the same positioning.

Get the Full 50-Prompt Pack

These 5 prompts handle listing day. The full pack covers the entire realtor workflow: lead generation, client follow-up, market analysis, price reductions, testimonial collection, content calendars, and more — 50 prompts organized by task.

👉 Get the 50 AI Prompts for Real Estate Agents — $7.99, instant download.

Or try a free 5-prompt sampler first — no signup required.

3 Things to Remember

The listing description is the foundation. Every other piece of content is derived from it. Get Prompt 1 right, and Prompts 2-5 get easier.
Always add local specifics. The AI doesn't know your neighborhood. Add the park name, the school district, the coffee shop. That's what makes it feel real.
Edit before you publish. AI gives you 80%. The last 20% — your voice, your market knowledge, your client relationships — is what makes it convert.

The agents who adopt AI prompts aren't replacing their judgment. They're automating the repetitive writing work so they can spend more time on what matters: relationships, negotiations, and closing deals.

What's the one listing task you'd automate first?

I Tried Selling AI Prompts for 30 Days — Here's What Actually Sold

Stephane Guertin — Mon, 13 Jul 2026 21:36:35 +0000

I expected to make $0. I made $47.30. Here's what that $47 taught me about selling digital products in 2026 — and why most prompt packs fail.

The Setup

I'd been using AI prompts for months — for marketing, content, coding, research. I had a library of 150+ prompts that I'd tested and refined. Friends kept asking me to share them.

So I packaged them up and put them on Gumroad.

Three products:

A free 5-prompt sampler (lead magnet)
Three 50-prompt niche packs at $7.99 each (real estate, marketing, content creation)
A 150-prompt bundle at $9.99 (best value)

I launched on a Sunday. No email list. No social following. No paid ads. Just organic posts on a few platforms.

Here's what happened day by day.

Week 1: The Launch

Day 1-3: Zero sales.

I posted the free sampler on Reddit (r/ChatGPT, r/realestate, r/marketing). Got 200 downloads of the free pack. Zero paid conversions.

The Reddit posts were "here's a free thing" posts — no soft pitch, no upsell. People grabbed the freebie and left.

Lesson 1: Free downloads don't automatically convert to paid sales. You need a deliberate upsell path. My free sampler had a link to the paid pack at the bottom, but there was no reason for someone to upgrade — the free prompts were good enough.

Day 4-7: First sale.

I rewrote the free sampler's final page. Instead of a link, I added: "These 5 prompts are from the 50-prompt real estate pack. Here's what the other 45 cover..." with a list of specific use cases.

Someone who downloaded the free sampler on Day 2 came back on Day 4 and bought the real estate pack. $7.99.

Lesson 2: The upsell needs to be specific. "Buy the full pack" doesn't work. "Here's exactly what you're missing" does.

Week 2: The First Traffic

Day 8-14: 3 sales ($31.97)

I published two Medium articles:

"9 AI Prompts That Replace a Real Estate Marketing Assistant"
"5 AI Prompts That Turn One Blog Post Into a Week of Social Content"

Both articles ranked on Google within 5 days for long-tail keywords. The real estate article got 340 views. The marketing article got 180 views.

Each article had two links: the free sampler (mid-article) and the paid pack (end). The conversion math:

520 article views → 38 free sampler downloads (7.3% click-through)
38 free downloads → 3 paid sales (7.9% conversion)
Revenue: $31.97

Lesson 3: Content marketing works, but the funnel is long. 520 views to get 3 sales. That's a 0.58% overall conversion rate from article view to purchase. It works, but you need volume.

Week 3: The Bundle Discovery

Day 15-21: 1 sale ($9.99)

Traffic slowed. The Medium articles dropped off the first page of Google for their primary keywords. I didn't publish new content.

But something interesting happened: someone who had downloaded the free sampler in Week 1 bought the 150-prompt bundle. Not a niche pack — the bundle.

They'd been on the email list (Gumroad captures emails on free downloads) for 12 days before purchasing.

Lesson 4: The bundle is the sleeper hit. People who download the free sampler and don't buy immediately are comparison shopping. When they come back, they don't buy the $7.99 pack — they buy the $9.99 bundle because it's "better value." The $2 price difference makes the bundle feel like a no-brainer.

Week 4: The Reddit Lesson

Day 22-30: 1 sale ($7.99)

I posted the marketing prompt pack on r/marketing. The post got 80 upvotes and 15 comments — mostly "are these prompts actually good or just recycled ChatGPT outputs?"

I responded to every comment with a specific example prompt. One commenter bought the pack and left a review: "Genuinely useful, not just generic prompts."

Lesson 5: Reddit responds to specificity, not promotion. The post that worked wasn't "buy my prompt pack." It was "here's an example prompt that writes 3 social posts from one article." The value was in the comment, not the link.

The Full 30-Day Numbers

Metric	Value
Free sampler downloads	247
Paid sales	5
Conversion rate (free → paid)	2.0%
Total revenue	$47.30
Avg revenue per sale	$9.46
Best-selling product	150-prompt bundle ($9.99)
Worst-selling product	Content creator pack ($0)
Traffic source	Medium articles (70%), Reddit (20%), Direct (10%)
Time invested	~8 hours (product creation + articles + Reddit)
Hourly rate	$5.91/hour

What I'd Do Differently

1. Publish more content, more consistently

Two articles drove all the traffic. If I'd published 8 articles instead of 2, I'd likely have 4x the traffic and 4x the sales. The bottleneck wasn't product quality — it was distribution.

2. Price higher after the first 5 reviews

At $7.99, the niche packs feel cheap — and cheap products attract refund requests and low-effort buyers. Competitors sell 50-prompt packs at $17-$27. Once I have 5+ reviews, I'm raising prices to $14.99 per pack and $24.99 for the bundle. Gumroad data shows the $30-$49 band converts 28% better than sub-$10 once reviews exist.

3. Build an email list from day 1

Gumroad captures emails on free downloads, but I have no way to email those 247 people. I need a proper email tool (ConvertKit, Beehiiv) connected to the Gumroad checkout so I can nurture leads who don't buy immediately.

4. Niche down harder

The content creator pack sold zero copies. Why? Because "content creator" is too broad. "AI prompts for YouTube creators" or "AI prompts for podcast hosts" would be more specific and more discoverable. General packs compete with every "100 ChatGPT prompts" article on the internet.

5. Get reviews faster

The Gumroad store had zero reviews for the entire 30 days. Reviews are social proof. I should have offered the free sampler to 10 people in exchange for honest reviews on the paid packs. The first review is the hardest — after that, they compound.

Is Selling AI Prompts Worth It?

$47 in 30 days isn't life-changing money. But here's the real math:

Product creation: one-time cost (~4 hours)
Articles published: 2 (~2 hours each)
Reddit posts: 3 (~30 min each)
Total time: ~8 hours
Monthly revenue after 30 days: ~$15-20/month passive (articles keep ranking, store keeps getting traffic)

The products are built. The articles keep working. The store runs on its own. Month 2 should generate $30-50 with zero additional work — just the compounding effect of SEO and the existing funnel.

Month 3, with 4 more articles and some reviews, should hit $100-150/month.

By month 6, with 20+ articles ranking, an email list, and adjusted pricing: $300-500/month. That's real passive income from a one-time ~8 hour investment.

The key is patience and consistency. Most people quit at Day 14 because the numbers look bad. The numbers always look bad at Day 14. The compounding doesn't start until Month 2.

Want the Prompts I'm Selling?

I'm not going to pretend this article isn't a soft pitch. The products are good. The prompts are tested. Here they are:

👉 150 AI Prompts Bundle — $9.99 (best value, 150 prompts across real estate, marketing, and content creation)

Or try the free 5-prompt sampler first — no signup, no email gate.

If you found this breakdown helpful, the bundle is the most cost-effective way to get all the prompts I mentioned in the articles above.

The Honest Takeaway

Selling digital products isn't about the product. It's about distribution. My 150 prompts are good, but so are a lot of free prompt lists on the internet. What makes them sell is:

Packaging (organized, niche-specific, copy-paste ready)
Trust (articles that demonstrate the prompts working)
Funnel (free sampler → specific upsell → bundle for the undecided)

If you're thinking about selling digital products, start before you're ready. My first 30 days were messy. The products weren't perfect. The articles had typos. But $47 is better than $0, and Month 2 is already looking better.

What would you sell if you knew the first 30 days would only make $47?

5 AI Prompts That Turn One Blog Post Into a Week of Social Content

Stephane Guertin — Mon, 13 Jul 2026 21:29:02 +0000

If you're writing one blog post and posting it once, you're leaving 85% of its value on the table.

I learned this the hard way. I spent 4 hours writing a deep-dive article, published it on my blog, shared the link on Twitter, and got 23 clicks. A week later, I took the same article, broke it into 7 derivative pieces, and posted across platforms. Result: 1,400 clicks, 60 new email subscribers, and 3 client inquiries.

Same content. Different distribution. 60x the results.

Here's the 5-prompt system I use to turn every blog post into a week of content — in 15 minutes.

The Content Repurposing Problem

Every marketer knows they should repurpose. Most don't because it feels like busywork. You wrote the article. Now you need to:

Rewrite it for Twitter (shorter, punchier)
Rewrite it for LinkedIn (professional, personal angle)
Create an Instagram carousel (visual, swipeable)
Write a newsletter version (gated, exclusive)
Script a short video (spoken, not written)

That's 5 more pieces of content from 1 article. At 20-30 minutes each, that's 2+ hours of additional work per article. When you publish weekly, that's a full day of repurposing.

AI changes the math. These 5 prompts do the repurposing in 15 minutes. The key is structure — each prompt knows the platform's format, tone, and audience expectations.

The 5-Prompt Repurposing System

Prompt 1: The Twitter/X Thread

Take this article: [paste article]. Create a Twitter/X thread that: 1) Opens with a hook tweet (max 15 words, curiosity-driven), 2) Has 8-10 tweets that extract the key insights (one idea per tweet), 3) Each tweet stands alone (a reader shouldn't need to read the full thread to get value), 4) Ends with a CTA tweet linking to the full article. Remove filler words. Use line breaks for readability. No hashtags in individual tweets.

Why it works: Twitter threads that share specific insights (not summaries) get the most engagement. The "stands alone" constraint means each tweet is independently quotable and shareable.

Time saved: 25 minutes → 2 minutes.

Prompt 2: The LinkedIn Post

Take this article: [paste article]. Write a LinkedIn post that: 1) Opens with a personal hook (first-person, a specific moment or realization), 2) Shares one key insight from the article (not a summary — pick the most counterintuitive point), 3) Includes a concrete example or data point, 4) Ends with a question that invites discussion (not a CTA to "read more"). Max 300 words. Tone: professional but conversational, like sharing a lesson with a colleague. No bullet points — LinkedIn rewards narrative.

Why it works: LinkedIn favors personal stories over summaries. This prompt picks the most counterintuitive insight and wraps it in a first-person narrative — the format that performs best on LinkedIn.

Time saved: 20 minutes → 2 minutes.

Prompt 3: The Instagram Carousel

Take this article: [paste article]. Design an Instagram carousel (8 slides). For each slide, give me: 1) The slide number and a title (max 6 words), 2) The body text (max 30 words per slide), 3) A visual description (what the image/graphic should look like), 4) The layout style (full text slide / split image+text / quote card / data visualization). Slide 1 = hook. Slides 2-7 = key insights. Slide 8 = CTA ("Save this post" or "Link in bio"). Make each slide readable in 3 seconds.

Why it works: Carousels are Instagram's highest-engagement format. The "3-second readability" constraint ensures each slide is punchy. The visual descriptions mean you can hand this to a designer or create it in Canva without thinking.

Time saved: 30 minutes → 3 minutes.

Prompt 4: The Email Newsletter Version

Take this article: [paste article]. Write an email newsletter version that: 1) Opens with a 2-sentence personal note (not "In this week's newsletter..."), 2) Includes the core insight in 200 words (not the full article — give subscribers the key takeaway, then link to the full version), 3) Adds one "subscriber-only" tip or resource not in the original article, 4) Ends with a P.S. that teases next week's topic. Tone: like writing to a friend who asked "what are you working on?" Max 400 words total.

Why it works: Newsletters should feel exclusive, not like a blog post in email form. The "subscriber-only tip" creates value for being on the list. The P.S. teaser drives open rates for the next email.

Time saved: 25 minutes → 2 minutes.

Prompt 5: The Short-Form Video Script

Take this article: [paste article]. Write a 60-second video script (TikTok / Reels / Shorts format). Structure: 1) 3-second hook (visual + verbal — something that stops the scroll), 2) 15-second context (why this matters), 3) 30-second main insight (the single most actionable point from the article), 4) 12-second CTA (specific — not "follow for more"). Include stage directions [in brackets] for visual elements, text overlays, and b-roll suggestions. Spoken words only — no on-screen text that isn't called out in stage directions.

Why it works: Short-form video scripts need to be tight. 60 seconds is ~150 spoken words. This prompt structures the script for retention: hook → context → value → CTA. The stage directions mean you can hand this to an editor or film it yourself without improvising.

Time saved: 20 minutes → 2 minutes.

The 15-Minute Repurposing Workflow

Minute 0-3: Run Prompt 1 (Twitter thread) while reading the output
Minute 3-6: Run Prompt 2 (LinkedIn post) — post immediately
Minute 6-9: Run Prompt 3 (Instagram carousel) — send to Canva/designer
Minute 9-12: Run Prompt 4 (Newsletter) — schedule for your send day
Minute 12-15: Run Prompt 5 (Video script) — record or hand to editor

Schedule across the week:

Monday: Blog post published
Tuesday: Twitter thread
Wednesday: LinkedIn post
Thursday: Instagram carousel
Friday: Newsletter sent
Weekend: Short video recorded (posted Monday)

One article. Seven pieces of content. Seven platform touches. 15 minutes of extra work.

Get the Full Marketing Prompt Pack

These 5 prompts handle repurposing. If you want the complete system — 50 prompts covering ad copy, email sequences, landing pages, A/B testing, SEO content, and social media — it's organized by marketing channel.

👉 Get the 50 AI Prompts for Marketers — $7.99, instant download.

Or try a free 5-prompt sampler first — no signup required.

The Math That Changed My Mind

Let's say you publish 1 article per week. Without repurposing:

52 articles per year
52 social posts (one share each)
Total content output: 104 pieces

With the 5-prompt system:

52 articles per year
52 × 7 = 364 derivative pieces
Total content output: 416 pieces

4x the content. 15 extra minutes per article.

That's not a productivity hack — it's a distribution strategy. The same idea, reaching 7 different audiences across 7 platforms, every single week.

What's the one article you'd repurpose first?

8 ChatGPT Prompts Indie Hackers Use Daily to Validate, Build, and Launch

Stephane Guertin — Mon, 13 Jul 2026 21:28:51 +0000

Most indie hackers I know have the same bottleneck: they can code, but the non-code work — validating ideas, writing copy, preparing launches — eats 60% of their time.

I tracked my own time for a month. Out of 40 hours of "building," I spent 16 hours on tasks that had nothing to do with writing code. Research, validation, landing page copy, email outreach, documentation, launch posts.

So I built a prompt stack. 8 AI prompts that handle the non-code work of shipping a product — from idea validation through launch day. Here's the system.

The Indie Hacker's Real Bottleneck

Code isn't the bottleneck. You can build a prototype in a weekend. The bottleneck is everything around the code:

Is this idea worth building? (validation)
What should I build first? (prioritization)
How do I describe it? (positioning + copy)
How do I get users? (outreach + launch)
How do I document it? (README, docs, API docs)

These tasks don't require engineering judgment. They require structured thinking and clear writing — exactly what AI does well when you give it the right prompt.

The 8-Prompt Stack

Prompt 1: The Idea Validator

I'm considering building [product idea]. Before I write any code, help me validate it. Act as a skeptical investor. Ask me 5 questions that will expose the weakest assumptions in my idea. For each question, explain what a good answer looks like vs. what a red flag answer looks like. Don't validate my idea — try to break it.

Why it works: Most validation prompts are cheerleaders — they tell you your idea is great. This one does the opposite. The "skeptical investor" frame forces honest assessment before you waste weeks building something nobody wants.

When to use: Before writing a single line of code.

Prompt 2: The MVP Scope Cutter

I want to build [product idea]. My constraint is [time budget: e.g., 2 weekends / 10 evenings]. List every feature I could build, then ruthlessly cut it down to the minimum viable version. For each cut feature, tell me why it's not needed for v1 and when I should reconsider it. Give me the final MVP as a prioritized list: what to build first, second, third.

Why it works: Scope creep kills indie projects. This prompt forces prioritization by making the AI justify every cut. You end up with a build order, not a wishlist.

When to use: After validation, before coding.

Prompt 3: The Landing Page Copywriter

Write landing page copy for [product name], which [one-sentence description]. Target audience: [who]. The page should have: 1) A headline (max 10 words) that states the outcome, not the feature, 2) A subheadline (max 20 words) that clarifies who it's for, 3) Three benefit bullets (focus on what users get, not what the product does), 4) A CTA button (max 3 words), 5) A "How it works" section (3 simple steps), 6) An FAQ with 3 objections your audience would have. Tone: direct, no jargon, no hype.

Why it works: Most developer-written landing pages describe features. This prompt forces benefit-driven copy — the kind that actually converts. The FAQ section handles objections before they kill the sale.

When to use: Before launch, when building the landing page.

Prompt 4: The Cold Outreach Email

I'm reaching out to [target persona, e.g., indie hackers on Twitter / real estate agents / marketers] about [product]. Write a cold email that: 1) References a specific problem they likely have (not a generic "I noticed you..."), 2) Positions my product as a solution without pitching, 3) Asks for one specific thing (feedback, a try, a share), 4) Is under 80 words. Write 3 subject line options: one question, one statement, one curiosity gap. Tone: peer-to-peer, not salesy.

Why it works: Cold outreach is brutal. Most emails get ignored because they're generic and salesy. This prompt produces a specific, low-friction ask that respects the recipient's time.

When to use: When you need your first 10 users.

Prompt 5: The Launch Post Generator

I'm launching [product] on [Hacker News / Product Hunt / Indie Hackers / Reddit]. Write a launch post that: 1) Opens with the problem (not the solution), 2) Explains how I built it and why (show the work), 3) Includes a "what I learned" section (indie hackers love lessons), 4) Asks for specific feedback, not just "check it out." Max 300 words. Tone: authentic, humble, no marketing speak.

Why it works: Launch posts that read like marketing copy get downvoted. Posts that share the journey and ask for genuine feedback get engagement. This prompt structures the post for the platform's culture.

When to use: Launch day.

Prompt 6: The README Writer

Generate a README.md for [project name]. The project [does X]. Include: 1) A one-line description, 2) A "Why" section (what problem it solves), 3) Quick start (3 commands max), 4) Configuration (as a table), 5) Usage examples (with code blocks), 6) Contributing guidelines (keep it simple), 7) License. Write it for a developer who has 5 minutes to evaluate whether to use this project.

Why it works: Developers judge projects by their README. A bad README kills adoption. This prompt produces the structure that open-source maintainers actually use.

When to use: After the MVP is functional.

Prompt 7: The Bug Report Analyzer

Here are 3 user reports of issues with my product: [paste reports]. For each: 1) Identify the likely root cause (code, UX, documentation, or expected behavior), 2) Classify severity (critical / annoying / cosmetic), 3) Suggest a fix approach (not the code, just the approach), 4) Rate how common this issue likely is based on the report. If multiple reports seem related, note the pattern.

Why it works: When users report bugs, the reports are usually vague. "It doesn't work." This prompt helps you triage and prioritize — turning noise into an actionable bug list.

When to use: After launch, when feedback starts coming in.

Prompt 8: The Weekly Review

It's Friday. Here's what I worked on this week: [paste your notes/commits]. Help me: 1) Summarize what shipped (for my newsletter / Twitter / status update), 2) Identify what didn't get done and why, 3) Suggest 3 priorities for next week based on what's most impactful, 4) Flag any patterns I'm missing (e.g., spending too much time on one area). Format as a simple weekly review I can paste into my notes.

Why it works: Weekly reviews are the highest-ROI habit for indie hackers. But most skip them because writing a review from scratch feels like work. This prompt turns rough notes into a structured review in 30 seconds.

When to use: Every Friday.

The Full Stack

These 8 prompts cover the non-code lifecycle of an indie product: validate → scope → position → outreach → launch → document → triage → review.

If you want the complete pack — 50 prompts covering coding, debugging, DevOps, growth, and more — it's organized by development phase.

👉 Get the 50 AI Prompts for Indie Developers — $4.99, instant download.

Or try a free 5-prompt sampler first — no signup, no email gate.

How to Use This Stack

Don't use all 8 at once. Use the one that matches your current phase. If you're validating, use Prompt 1. If you're launching, use Prompt 5.
Customize the brackets. The prompts work best when you fill in specific details. "A SaaS tool for freelance designers" beats "a product for creators."
Iterate. Run the prompt, read the output, refine your input. The first run gives you 80%. The second run — with better context — gives you 95%.

The biggest lie in indie hacking is that you need to "learn marketing." You don't. You need systems for the non-code work. These 8 prompts are that system.

What's the one task you'd hand off first?

Stop Wasting Hours on Content Ideas: A 5-Prompt System That Plans 30 Days in 20 Minutes

Stephane Guertin — Mon, 13 Jul 2026 21:22:54 +0000

Every content creator I know has the same problem. Not creating content — planning it.

You sit down on Monday morning, open your editorial calendar, and stare at 30 empty slots. What do I post Tuesday? What about next week? Should I do a video or a blog post? Is this topic still relevant?

Two hours later, you've planned three days, you're frustrated, and you haven't created anything.

I spent a year doing this. Then I built a 5-prompt AI system that plans an entire month of content in 20 minutes. Here's the exact workflow.

Why Most Content Planning Fails

The standard approach is to brainstorm topics one at a time. "What should I post about today?" It's like grocery shopping without a list — you wander, you forget things, you buy stuff you don't need.

The fix isn't a better brainstorming method. It's a system that generates structure first, then fills in specifics.

That's what these 5 prompts do. Each one handles a different layer:

Theme selection
Topic generation
Format matching
Hook writing
Batch production

Run them in order. 20 minutes. 30 days of content. Done.

Prompt 1: The Monthly Theme Selector

I create content about [your niche] for [your audience]. My content pillars are: [list 3-5 pillars]. For next month, suggest one overarching theme that ties at least 3 of my pillars together. The theme should be timely (reference a season, event, trend, or common challenge your audience faces during this month). Give me the theme name, a one-sentence description, and 3 sub-themes I can explore across different weeks.

Why it works: A monthly theme gives every piece of content a through-line. Instead of random topics, your audience gets a cohesive narrative across the month. This is what separates professional content creators from hobbyists.

Time saved: 30 minutes of indecision → 2 minutes.

Prompt 2: The Topic Generator

Based on this monthly theme: [paste theme]. Generate 30 content topic ideas — one for each day of the month. For each topic, include: 1) The content pillar it serves, 2) The format (blog post, video, carousel, thread, newsletter, podcast, or short-form video), 3) A one-sentence description of the angle. Distribute formats evenly — don't give me 15 blog posts in a row. Make 20% of the topics "evergreen" (relevant beyond this month) and 80% tied to the monthly theme.

Why it works: 30 topics in one shot. The format distribution constraint ensures variety. The evergreen/theme split means you're building a lasting library while staying timely.

Time saved: 2 hours of brainstorming → 3 minutes.

Prompt 3: The Hook Writer

For each of these 10 topics [paste 10 topics], write 3 different hook options. Each hook should be: 1) Under 15 words, 2) Curiosity-driven (not clickbait), 3) Specific (include a number, name, or concrete detail). Label each hook as: Question, Bold Statement, or Story Hook. Avoid generic hooks like "Here's how to..." or "The ultimate guide to..."

Why it works: Hooks are the hardest part of content creation. A great topic with a weak hook gets zero engagement. Generating 3 options per topic gives you choices and trains your brain on what makes a good hook.

Time saved: 45 minutes → 3 minutes.

Prompt 4: The Repurposing Matrix

Take this piece of content: [paste your best-performing article or video from last month]. Break it down into 7 derivative pieces: 1) A Twitter/X thread (10 tweets), 2) A LinkedIn post (max 300 words), 3) An Instagram carousel (8 slides with text for each), 4) A YouTube Shorts script (60 seconds), 5) A newsletter section (200 words), 6) A podcast intro question, 7) A quote graphic (one sentence + visual suggestion). Each piece should stand alone — don't reference "the full article."

Why it works: One piece of content should become 7. Most creators leave 85% of their content's value on the table by posting once and moving on. This prompt does the repurposing work in one shot.

Time saved: 3 hours → 5 minutes.

Prompt 5: The Batch Production Scheduler

Here are my 30 content topics for next month: [paste topics]. Create a production schedule that groups similar formats together for batch creation. I can record videos on [days], write on [days], and design graphics on [days]. Give me: 1) A weekly batch schedule (which formats to produce on which days), 2) The total production time estimated, 3) Which topics should be created first (priority = time-sensitive themes first). Format as a simple table.

Why it works: Batch creation is 3x faster than switching between formats. This prompt optimizes your calendar for batching instead of daily context-switching.

Time saved: 20 minutes of planning → 2 minutes.

The Full 20-Minute Workflow

Here's how the 5 prompts fit together:

Minute 0-3: Run Prompt 1 (Theme Selector) → get your monthly theme
Minute 3-8: Run Prompt 2 (Topic Generator) → get 30 topic ideas
Minute 8-13: Run Prompt 3 (Hook Writer) → get hooks for your top 10 topics
Minute 13-18: Run Prompt 4 (Repurposing Matrix) → turn last month's best piece into 7 new pieces
Minute 18-20: Run Prompt 5 (Batch Scheduler) → get your production calendar

Result: 30 days of planned content, 7 repurposed pieces, hooks for your top topics, and a production schedule. In 20 minutes.

How to Get the Full System

These 5 prompts are a starting point. If you want the complete content creator prompt pack — 50 prompts covering ideation, writing, repurposing, SEO optimization, audience research, and analytics — I've put together a pack organized by workflow stage.

Each prompt is copy-paste ready. Fill in the brackets with your niche and details.

👉 Get the 50 AI Prompts for Content Creators — $7.99, instant download.

Or try a free 5-prompt sampler first — no signup required.

3 Common Mistakes to Avoid

Don't skip the theme step. It feels like an extra step, but the theme is what makes the next 29 days cohesive. Without it, you're back to random topics.
Don't accept the first hook. The AI will give you 3 options per topic for a reason. Read all 3, pick the best one, and tweak it. The hook is worth 10x the effort of anything else in the content.
Don't plan more than 30 days ahead. Trends change. Your audience evolves. A 30-day plan is actionable. A 90-day plan is fiction.

The difference between content creators who burn out and those who don't isn't talent or work ethic. It's systems. The 5 prompts above turned my most painful weekly task into a 20-minute monthly ritual.

What would you do with the extra 6 hours a week?

The 9 AI Prompts That Replace a Real Estate Marketing Assistant

Stephane Guertin — Mon, 13 Jul 2026 21:22:43 +0000

Most realtors spend 15+ hours a week on marketing tasks that AI can handle in 20 minutes. I tracked every minute for a month, and the results changed how I run my entire listing workflow.

Here's the system I built — 9 copy-paste AI prompts that handle listings, social media, lead follow-ups, and market analysis. Each one replaces a specific task that used to eat my evenings.

The Problem: Marketing Tasks Were Eating My Evenings

Last spring, I sat down with my calendar and color-coded every task I did in a week. Yellow for client work. Blue for admin. Red for marketing.

The red was everywhere.

Listing descriptions. Instagram captions. Facebook posts. Email follow-ups to leads. Market update emails. Open house announcements. Zillow profile updates. Every single one required me to stare at a blank screen and write something compelling.

I was spending 15 hours a week on marketing — time that should have gone to showings, negotiations, and client relationships.

The breaking point was a Thursday night. I had three new listings going live Friday morning. Each needed a description, three social posts, and an email blast. That's 12 pieces of content. I started at 7 PM and finished at 11:40 PM.

Something had to change.

The Discovery: AI Prompts as a Marketing System

I had played with ChatGPT before — asked it to write listing descriptions, generated a few caption ideas. But the output was generic. "Welcome to this beautiful home nestled in a vibrant community..." — the kind of filler that makes buyers scroll past.

The problem wasn't the AI. It was my prompts.

I started studying how marketing agencies and content creators were using AI. The ones getting great results weren't asking the AI to "write a listing description." They were giving it context, constraints, and a specific output format.

So I rebuilt my prompts from scratch. Each one includes:

Role — who the AI is acting as
Context — what it needs to know about the property/audience
Task — exactly what to produce
Constraints — tone, length, format, what to avoid
Output format — structured for copy-paste

The difference was night and day.

The 9-Prompt System

Here's the exact system, organized by when I use each prompt during a listing lifecycle.

Prompt 1: The Listing Description Generator

You are a real estate copywriter with 15 years of experience. Write a listing description for this property: [paste property details, sq ft, beds/baths, key features, neighborhood]. Target audience: [first-time buyers / luxury buyers / investors / families]. Tone: warm but professional, no hype words (avoid "stunning," "gorgeous," "must-see"). Format: 2 short paragraphs (max 150 words each). Lead with the one feature that makes this property different from others in the same price range. End with a subtle call to action.

Why it works: The constraint against hype words forces the AI to find specific, concrete details instead of filler. The "one feature that makes this different" instruction prevents generic descriptions.

Time saved: 25 minutes per listing → 3 minutes.

Prompt 2: The Social Media Caption Batch

Take this listing description: [paste description]. Create 3 social media captions for different platforms: 1) Instagram (casual, emoji-friendly, max 150 words, include 10 relevant hashtags), 2) Facebook (conversational, max 200 words, include a question to drive comments), 3) LinkedIn (professional, focus on investment potential, max 150 words). Each caption should have a different angle — don't just rephrase the same message three times.

Why it works: One prompt generates three platform-specific posts with distinct angles. No more writing separate captions for each platform.

Time saved: 20 minutes → 2 minutes.

Prompt 3: The Lead Follow-Up Sequence

I have a new lead who [inquired about a listing / attended an open house / requested a market analysis]. Write a 4-email follow-up sequence: 1) Immediate thank-you (send within 1 hour), 2) Value-add email (send next day — include one market insight or tip), 3) Soft check-in (send day 4 — ask if they have questions), 4) Gentle nudge (send day 7 — suggest a call or coffee). Each email max 100 words. Tone: warm, not salesy, like a helpful neighbor who happens to know real estate. Include subject lines.

Why it works: This generates an entire nurture sequence in one shot. The "helpful neighbor" tone constraint prevents the robotic, overly formal language that makes leads ghost you.

Time saved: 45 minutes → 4 minutes.

Prompt 4: The Market Analysis Email

Write a monthly market update email for my client database. Use this data: [paste median price, days on market, inventory levels, year-over-year change for your area]. Audience: homeowners and buyers in [city/neighborhood]. Format: 3 short sections (What's happening, What it means for buyers, What it means for sellers). Max 250 words total. Tone: informative, no jargon, like explaining it to a friend over coffee. End with: "Questions about what this means for your situation? Reply to this email."

Why it works: Monthly market emails keep you top-of-mind, but most agents skip them because writing them takes too long. This prompt turns raw data into a client-ready email in minutes.

Time saved: 35 minutes → 3 minutes.

Prompt 5: The Open House Announcement

I'm hosting an open house for [property address, date, time]. Write: 1) A neighborhood flyer announcement (max 100 words, include date/time/address, highlight one feature), 2) A Facebook event description (max 200 words, engaging, include what to expect), 3) An Instagram story script (3 slides, each with text overlay suggestions and a visual description). Tone: inviting and casual, not formal.

Why it works: Open houses need marketing across multiple channels. This generates all of them in one pass.

Time saved: 25 minutes → 2 minutes.

Prompt 6: The Zillow/Realtor.com Profile Bio

Write a real estate agent bio for my Zillow profile. Here are my details: [years of experience, areas served, specialty (first-time buyers / luxury / investors), notable achievement, personal interest/hobby]. Tone: approachable and credible, not boastful. Max 200 words. Start with a hook that isn't "I am a real estate agent..." — open with what drives me or a client outcome I'm proud of. Include a soft CTA to contact me.

Why it works: Most agent bios are interchangeable. The "don't start with I am a real estate agent" constraint forces something memorable.

Time saved: 30 minutes → 2 minutes.

Prompt 7: The Price Reduction Announcement

I need to reduce the price on a listing from [old price] to [new price]. Write: 1) An email to the seller explaining the recommendation (max 150 words, empathetic but direct, include one comparable sale that justifies the reduction), 2) An update for the MLS and property websites (max 50 words, frame it positively — "new price" not "reduced"), 3) A social media post announcing the opportunity (max 100 words, focus on value for buyers, not on the reduction).

Why it works: Price reductions are awkward. This gives you all three communications — seller, MLS, and public — with the right tone for each audience.

Time saved: 20 minutes → 2 minutes.

Prompt 8: The Client Testimonial Request

Write a testimonial request email to a client who recently [bought / sold] a home with me. The transaction: [brief context — e.g., "first-time buyers who were nervous about the process"]. Tone: warm, personal, not a template. Ask for a specific type of testimonial: their experience working with me, what surprised them, and whether they'd recommend me. Make it easy — offer to draft something they can edit. Max 120 words.

Why it works: The "offer to draft something" trick increases response rates dramatically. Most clients want to help but don't want to write from scratch.

Time saved: 15 minutes → 1 minute.

Prompt 9: The Weekly Content Calendar

I need a week of social media content for my real estate business. I specialize in [area/neighborhood] and work with [target audience]. Generate a 7-day content calendar: for each day, give me 1) the content type (market tip, local highlight, listing spotlight, client story, FAQ, behind-the-scenes, or motivational), 2) a one-line post idea, 3) the best platform for this content, and 4) the best time to post. Vary the content types — don't repeat the same format two days in a row.

Why it works: Planning content is the hardest part. This gives you a full week's calendar with varied content in one prompt. You can generate a month's worth by running it 4 times.

Time saved: 40 minutes → 3 minutes.

The Results: 15 Hours → 2 Hours

After using this system for 60 days, my weekly marketing time dropped from 15 hours to under 2 hours. That's 13 hours back in my week — time I redirected to showings, client calls, and prospecting.

More importantly, the quality of my marketing improved. The prompts produce consistent, professional output. No more rushed, last-minute captions. No more generic listing descriptions. Every piece of content follows the same standard.

How to Get Started

If you want the full system — all 50 prompts covering every aspect of a realtor's marketing workflow — I've put them together in a pack that's organized by task: listings, leads, social, email, market analysis, and client communication.

Each prompt is copy-paste ready. Just fill in the brackets with your details.

👉 Get the 50 AI Prompts for Real Estate Agents — $7.99, instant download.

Or try a free 5-prompt sampler first — no signup required.

3 Tips for Getting the Most Out of AI Prompts

Always edit the output. AI gives you 80% of the work. The last 20% — adding your voice, local details, and specific client context — is what makes it feel human.
Save your best prompts. Once you find a prompt that works great for your market, save it. Build your own library. The prompts in this article are a starting point — your best prompts will be the ones you customize for your specific area and client base.
Use the same AI consistently. I use ChatGPT for most tasks and Claude for longer-form content. Pick your tools, learn their quirks, and stick with them. Switching between AI models every week means you never learn the nuances.

The 9 prompts above handle 90% of my marketing workflow now. The other 10% — the creative, strategic decisions about what to market and when — that's still my job. And that's exactly where my time should go.

What's the one marketing task you'd hand off to AI first?

How I Unlocked "Beast Mode" on My Autonomous AI Agent (And What It Actually Means)

Stephane Guertin — Mon, 13 Jul 2026 21:15:45 +0000

I've been running an autonomous AI agent (Hermes Agent by Nous Research) as my operator for a few months now. It manages my digital product store, runs paper trading simulations, publishes daily articles, and sends me a morning brief every day at 6:15 AM.

But until this week, I was only using maybe 30% of what it could do. I watched a YouTube video that broke down 6 stages of agent maturity — from basic chatbot to full "beast mode" — and realized I was stuck at stage 5 with none of the compounding benefits of stage 6.

Here's what I did to fix that, what each stage actually means in practice, and the specific steps that unlocked the multiplier effect.

The 6 Stages (And Where I Was Stuck)

Stage 1: The Helper

Day one. You installed your agent, connected a model, asked it questions. It can search the web, edit files, run terminal commands. Useful, but it's just a chatbot with hands.

I was past this.

Stage 2: The Daily Assistant

You connect your agent to Telegram, Discord, Slack — wherever you already live. Now you can send it tasks from your phone. It's convenient, but it's still the same agent that doesn't really know anything about you yet.

I was past this too. Messaging gateway has been running for months.

Stage 3: The Intern

This is where the agent starts learning your processes — not just facts, but workflows. The key distinction: memory remembers information. Skills remember processes.

Hermes has a /learn command that turns a completed workflow into a reusable skill. You teach it your script review process once, and next time you just say "use my script review skill." It runs your exact checklist every time.

It also has /journey — a command that shows you everything it's accumulated: memories, skills, what it thinks it knows about you. You can review, edit, or delete any of it.

I was partially here. I had a few skills saved but wasn't systematic about it. After every multi-step workflow, I should have been capturing it as a skill. I wasn't.

Stage 4: The Crew

The agent stops being one voice and starts acting like a team. Two features drive this:

Mixture of Agents (MoA) — instead of trusting one model, it runs your hard questions through several models in parallel, then an aggregator synthesizes the best answer. A panel instead of a single opinion.
Background subagents — fan out a task to multiple subagents that work in parallel while you keep chatting. When they're done, you get one consolidated result.

I was here. Multiple MoA presets configured (including a max-council with 6 cloud models) and concurrent subagent delegation working.

Stage 5: The Backbone

The agent is connected to your infrastructure — files, code, cron jobs, messaging. It runs scheduled tasks while you sleep. You wake up to a morning brief, sales reports, and trading summaries.

I was solidly here. Dozens of cron jobs running, messaging delivery, identity/behavior files shaping how it operates. But this is where I got stuck.

Stage 6: The Multiplier

This is the stage nobody can show you in a 30-second clip because it's not a feature — it's a compounding effect. By now the agent should:

Know your work (memory)
Remember your processes (skills)
Route tasks to the right model automatically
Delegate to subagents
Run scheduled workflows
Verify its own output

The multiplier isn't something you switch on. It's what the agent becomes after it's learned your work for a while. And I had the foundation but wasn't compounding.

What I Did This Week to Unlock Stage 6

1. Set a Standing Goal

I set a persistent goal that tells the agent:

Continuously identify, validate, and prototype new passive income streams that can be automated and operated without my daily involvement.

This goal persists across turns. Between my direct instructions, the agent proactively works on income systems instead of waiting idle. It researched why my Gumroad store had zero sales, diagnosed the issues, fixed product titles/tags/prices, and published the first article on a new platform — all from the standing goal.

2. Created a Project Rules File

I created a project-level rules file with enforceable standards for each income stream:

Digital store: Always verify storefront health before reporting sales status. Products must be checked for published state.
Paper trading: Simulation only — never suggest real money moves. Reports must label "PAPER (simulated)."
Scheduled jobs: Light/frequent jobs use local models. Heavy research uses cloud models. Script-only jobs need no model.
Quality standards: Diagnose before fixing. Verify before reporting success. After any 5+ step workflow, save it as a skill.

This loads automatically in every session. It's different from memory — these are rules, not suggestions.

3. Audited and Cleaned Memory

I ran a full memory audit and found:

A stale entry referencing an old model version when we'd upgraded to a newer one
An incorrect claim about which model handles compression
A junk entry that couldn't be removed cleanly via the tool

Memory is injected into every turn. Stale or wrong memory degrades every future interaction. Clean it regularly.

4. Got Aggressive About Skill Capture

Every time I complete a multi-step workflow (5+ tool calls), I save it as a skill now. This week alone I captured:

Skill	What It Captures
Config audit	Full config audit checklist — model routing, delegation, auxiliary, MoA, scheduled jobs
Model selection	All available cloud models with parameters, strengths, cost tiers, workload mapping
Morning brief	How to edit the morning brief cron job, add tracked stocks/crypto, change format
Store optimization	Store audit, API fields vs manual-only fields, pricing strategy for zero-review stores

The compounding effect: next time I need to do any of these things, I load the skill and execute systematically. No re-learning, no re-discovering pitfalls, no repeating mistakes.

5. Stopped Pretending the Browser Didn't Work

This was embarrassing. I had browser tools — navigate, screenshot, vision analysis, JavaScript evaluation, click, scroll — and I wasn't using them because the debug port wasn't open. Instead of launching my browser with the right flag (a 3-second fix), I dispatched a subagent to research my own store via command-line HTTP requests.

The lesson: when a tool fails, diagnose the actual error before concluding the tool is unavailable. I updated my browser skill documentation with a decision tree so this never happens again.

The Result

Within a single session, the system went from "well-engineered but producing zero income" to:

Digital store fully optimized — all products updated with SEO-optimized titles, 8 tags each, expanded descriptions, launch pricing strategy
First article published on a high-DA platform — with backlinks to the store
Daily article cron resumed — new article every morning, rotating through product niches
4 new skills captured — each one a permanent workflow that compounds
Memory cleaned and current — no stale references degrading future sessions
Standing goal active — the agent proactively works between my instructions

Total revenue is still $0. But the flywheel is now spinning: articles → Google indexing → store traffic → first sales → first ratings → marketplace visibility → more sales. The compounding has started.

The Pattern

The 6 stages aren't a tutorial. They're a maturity model. Most people install an AI agent, hit stage 2-3, and stop. The real unlock is stage 6 — the multiplier — and it requires:

Standing goals so the agent works between your instructions
Project rules that enforce quality standards every session
Clean memory that doesn't degrade over time
Systematic skill capture after every non-trivial workflow
Actually using your tools — diagnose failures, don't punt to the user

None of these are features you switch on. They're habits you build. And the compounding effect means every session from here is better than the last.

Credit

The 6-stages framework comes from Ash Automates — his video "How to Turn Hermes Agent Into a Beast (The 6 Stages)" breaks down each stage in detail with timestamps. This article is my real-world implementation of what he describes, not a summary of his video — go watch it for the full walkthrough.

If you're running an autonomous AI agent, what stage are you at? The honest answer is probably lower than you think — and that's fine, because the gap between stage 5 and stage 6 is just a few hours of setup.