DEV Community: Mavos.by.Kyklos

Draft minutes from your meeting recording — every line tied to a timestamp ($149)

Mavos.by.Kyklos — Mon, 14 Sep 2026 17:38:43 +0000

For town and city clerks who owe the public minutes.

Send a recording or public video URL (YouTube, Granicus, Zoom). You get draft minutes where every motion, vote, and action item points to the exact timestamp. If something can't be heard, it's flagged — never guessed. Optional export for Joomla/YOOtheme sites.

$149 per meeting. Delivered within ~24 hours.

Pay → https://buy.stripe.com/cNi00k4Fm9Igeiief25sC2S

Draft minutes from one meeting recording, every line tied to a timestamp

Mavos.by.Kyklos — Mon, 14 Sep 2026 00:05:40 +0000

Meeting minutes from your recording, drafted and ready for review in 48 hours.
Send a recording or a public video link (YouTube, Granicus, Zoom) of one meeting.
You get draft minutes where every motion, vote and action item points back to the exact timestamp it came from, so review goes fast.
If something can't be heard, it's flagged for you, never guessed.
Includes an export for Joomla/YOOtheme sites.
$149 per meeting.

Who this is for: town and city clerks who owe the public minutes for every meeting

Get it here

A one-page over-engineering audit: what to delete, what stdlib replaces it

Mavos.by.Kyklos — Mon, 14 Sep 2026 00:05:40 +0000

One-page over-engineering audit: what to delete, what stdlib replaces it.
Solo devs / small teams with a public repo.
$99 flat rate, delivered in 48 hours.
Reply to your 'roast my codebase' on HN/X, or comment here.
No fluff, just actionable refactoring steps and benchmark comparisons.

Who this is for: solo devs / small teams with a public repo

Get it here

Lyrisee How-To: Fix Transcription Errors With the Lyric Editor

Mavos.by.Kyklos — Wed, 17 Jun 2026 11:44:01 +0000

If you've run a song through Lyrisee and a few words came out wrong — "veins" became "vains", an artist name got mangled, a slang term got autocorrected — the lyric editor lets you fix it without re-processing.

Opening the Editor

After processing completes, click ✎ Edit lyrics in the top right of the controls panel.

The editor opens as an overlay with one row per line. Each row shows:

Time — the line's start timestamp (editable)
Text — the transcribed words for that line (editable)
Delete — remove a line entirely

Fixing a Mis-Transcribed Word

Click the text field for any line and edit it directly.

Before: "pain is all i fill i got nothing to gain"
After:  "pain is all I feel I got nothing to gain"

The corrected words get re-aligned to the original word-level timestamps automatically using difflib.SequenceMatcher. If you replace one word with one word, it inherits the original timing exactly. If you replace two words with three (or vice versa), the time window is split evenly across the new tokens.

Nudging a Line's Start Time

Sometimes Whisper starts a line a fraction of a second early or late. Click the time field and adjust:

12.480  →  12.600

All words within that line shift by the same delta.

Adding or Removing Lines

Use the + Add line button at the bottom to insert a line with a manual timestamp and text. Use the ✕ button on any row to remove it.

This is useful when Whisper splits a line mid-phrase or merges two lines into one.

Applying Changes

Click Apply & re-render. The canvas updates immediately — no re-processing, no waiting. The typography engine replays with your corrected text and preserved timing.

Downloading the Corrected Lyrics

Click Download to save a lyric_data.json with your corrections. Next session, load the audio file and then drag in the saved JSON — it skips the whole processing pipeline and goes straight to playback.

Tips for Common Cases

Rap slang and AAVE
Whisper sometimes over-corrects. If "finna" became "going to", the AI repair should have caught it — but if not, fix it in the editor. The POS tagger re-runs on edited text, so "finna" will get the right grammatical role.

Artist names and proper nouns
Whisper often mishears names. Fix in the editor — capitalized words automatically get PROPN tagging, which affects styling (they render with slightly different weight).

Sung words vs spoken words
If a word was held for 2 seconds and Whisper assigned it a 0.1s window, you can't fix that in the text editor — but it's rare. The word will still appear at the right moment; it just exits earlier than the hold lasts.

Background vocals and ad-libs
Whisper picks up background vocals. If you don't want them, delete those lines in the editor.

Open Lyrisee → https://acecalisto3-lyrisee.hf.space

How Lyrisee Syncs Lyrics to Audio: Word-Level Timestamps Explained

Mavos.by.Kyklos — Wed, 17 Jun 2026 11:43:13 +0000

Standard lyrics-sync apps take a line's timestamp and guess when each word lands. If a line starts at 4.2s and ends at 6.8s across 8 words, each word gets ~0.3s — regardless of whether the singer held one word for a full second and rapped the next seven in a burst.

Lyrisee doesn't guess. Every word gets its own measured start and end time.

How Word-Level Timestamps Work

Lyrisee uses faster-whisper — an optimized implementation of OpenAI's Whisper model — with word_timestamps=True.

Whisper processes audio in 30-second chunks and produces attention weights over the spectrogram. faster-whisper uses those attention weights to find exactly when the model's "attention" peaks for each word token — that peak is the word's center timestamp. Start and end are derived from the attention envelope.

from faster_whisper import WhisperModel

model = WhisperModel("tiny.en", device="cpu", compute_type="int8")
segments, info = model.transcribe(audio_path, word_timestamps=True, vad_filter=True)

words = []
for seg in segments:
    for w in seg.words:
        words.append({
            "text": w.word.strip(),
            "start": round(w.start, 3),
            "end":   round(w.end,   3),
        })

The result: a list like:

[
  {"text": "dark",    "start": 12.480, "end": 12.720},
  {"text": "nights",  "start": 12.720, "end": 13.200},
  {"text": "running", "start": 13.440, "end": 13.800},
  {"text": "cold",    "start": 13.880, "end": 14.120}
]

Why This Matters for Typography

With interpolated timing, a held note ("niiiights") would show the word for exactly its share of the line duration — even though the singer held it 4× longer than a normal word.

With word-level timing, "niiiights" shows exactly as long as it sounds. The typography breathes with the vocal performance.

AI Lyric Repair

Whisper sometimes mishears words — especially rap (fast delivery, slang, AAVE, deliberate wordplay). Lyrisee sends the raw transcript to Gemini for correction:

System: You are Lyrisee's lyric-repair stage. Fix transcription errors using
the subject matter, rhyme scheme, and surrounding lines. Preserve the artist's
voice: slang, contractions, profanity, proper nouns. Do not rephrase correct words.

Input:
1. dark nights running through my vein
2. pain is all i fill i got nothing to gain
3. [...]

Output:
1. dark nights running through my veins
2. pain is all I feel I got nothing to gain

After repair, corrected tokens are re-aligned to the original word timings using difflib.SequenceMatcher. Sync stays tight even after word corrections.

Beat Tracking

In parallel, librosa analyzes the audio for beat positions:

import librosa

y, sr = librosa.load(audio_path, mono=True)
tempo, frames = librosa.beat.beat_track(y=y, sr=sr)
beats = librosa.frames_to_time(frames, sr=sr).tolist()
# [0.371, 0.742, 1.114, 1.485, ...]

The renderer uses beat timestamps to trigger visual "hit" animations — the canvas reacts to the music, not just the lyrics.

POS Tagging

spaCy tags each word with its part of speech (NOUN, VERB, ADJ, PROPN, etc.). The visual engine uses POS to set default sizing — nouns and verbs render larger, function words smaller — before AI art direction overrides specific words.

The Output Format

Everything feeds into a single lyric_data.json:

{
  "words": [
    {"text": "dark", "start": 12.48, "end": 12.72, "pos": "ADJ",
     "dir": {"emphasis": 2, "register": "heavy", "glow": true, "icon": null}},
    {"text": "nights", "start": 12.72, "end": 13.2, "pos": "NOUN",
     "rhyme": 3}
  ],
  "beats": [0.371, 0.742, 1.114],
  "metaphors": [{"start": 12.48, "metaphor": "fall"}],
  "rhyme_families": [["veins","gains","pain","brain"]],
  "rhyme_palette": {"0": "#5CE1E6", "1": "#FF2E2E", "3": "#FFD166"}
}

The frontend reads this file and the renderer handles the rest — no backend connection needed during playback.

Try It

https://acecalisto3-lyrisee.hf.space — upload any song, watch it render.

Lyrisee: Turn Any Song Into Kinetic Typography With AI (How It Works)

Mavos.by.Kyklos — Wed, 17 Jun 2026 11:43:05 +0000

What is Lyrisee?

Lyrisee takes any audio file — MP3, M4A, WAV, or video — and turns it into a real-time kinetic typography experience. Words appear, animate, and exit in sync with the music, styled based on what the lyrics mean, not just how they sound.

Under the hood it's a full AI pipeline:

Transcription — faster-whisper with word-level timestamps (every word gets an exact start/end time)
Beat tracking — librosa finds every beat drop
AI art direction — Gemini reads the full lyrics, picks a visual metaphor per line, decides which words to hit hard, assigns icon symbols where literal (🔥 on "fire", 💸 on "money")
Rhyme coloring — CMUdict finds true rhyme families; rhyming words share a color
Typography engine — a Three.js renderer plays it all back, animated to the audio

Step 1: Open Lyrisee

Go to https://acecalisto3-lyrisee.hf.space.

The interface has two panels:

Left: controls, upload, playback
Right: the canvas where the kinetic typography renders

Step 2: Load Your Audio

Click Choose File (or drag and drop) and select any audio file:

MP3, WAV, M4A, FLAC, OGG
Video files work too (MP4, WebM) — the audio track is extracted

The file stays local — it's only sent to the backend for transcription, never stored.

Step 3: Enable Cloud AI (Recommended)

Toggle the Cloud AI switch on (it's on by default).

Under it you'll see the AI provider dropdown — Gemini is selected by default and is what powers the art direction.

Cloud AI does:

Word-level transcription via faster-whisper
Lyric repair (fixes mishear errors using context and rhyme scheme)
Visual art direction (metaphor per line, word emphasis, icon assignments)
Rhyme family detection

If Cloud AI is off, Lyrisee falls back to in-browser transcription using a small on-device model — faster but lower quality and no art direction.

Step 4: Click Process

Hit the Process button. The log panel shows live progress:

[upload] your-song.mp3 (8.8 MB) received
[pipeline] provider=gemini
[asr] loading faster-whisper 'tiny.en' (int8 cpu) …
[asr] transcribing (word timestamps) …
[asr] detected language: english (99%)
[asr] 312 words
[beats] 143 beats @ ~92 BPM
[ai] repaired + art-directed -> 318 words, 28 line cues, 14 rhyme families
[done] 318 words · 143 beats

Processing time depends on song length — typically 30-90 seconds for a 3-4 minute song.

Step 5: Play

Once processing completes, hit Play (or press Space).

The canvas comes alive:

Words appear and exit in sync with audio playback
Rhyming words glow in matching colors
Lines with heavy emotional weight animate differently (scale, drift, snap)
Icon symbols appear on words like "fire", "money", "cage" where the AI decided they hit

Controls

Control	What it does
Space	Play / pause
← → Arrow keys	Seek ±5 seconds
F	Fullscreen
✎ Edit lyrics	Open the lyric editor to fix transcription errors

The Lyric Editor

If the AI mishears a word (happens with heavy slang or unusual pronunciation), click ✎ Edit lyrics.

Each row is one line. Edit the text, nudge the start time if needed, then click Apply & re-render. The canvas updates live with your corrections.

Visual Constructs

The Construct dropdown lets you switch visual styles mid-session:

Rhyme Scheme — rhyming words animate together, shared color palette
Embodiment — each line's motion matches its meaning (falling words drop, rising words rise)
Kinetic Art — pure typographic energy, no semantic logic, maximum visual noise
Chameleon — the AI picks the best construct per line based on content

FAQ

What audio formats work?
MP3, WAV, FLAC, M4A, OGG, MP4, WebM. If it has audio, Lyrisee can process it.

How accurate is the transcription?
For clear vocals, 90-95%. For heavy reverb, distortion, or layered vocals, lower — use the lyric editor to fix errors.

Does it work for non-English songs?
The current model (tiny.en) is English-optimized. Multi-language support via tiny (no .en) is available by changing the backend model size.

Can I download the result?
Yes — the Download button in the lyric editor saves a corrected lyric_data.json you can reload without re-processing.

Is it free?
The HF Space is free to use. It runs on shared CPU, so processing can take 1-2 minutes for longer tracks. Enterprise/private deployments with GPU available — see the landing page.

Try Lyrisee → https://acecalisto3-lyrisee.hf.space

Stop using ChatGPT wrong: the developer prompt guide that ships code

Mavos.by.Kyklos — Sun, 14 Jun 2026 08:32:30 +0000

Stop using ChatGPT wrong: the developer prompt guide that ships code

As developers, we've all been there - stuck in a sea of code, searching for a lifeline to get the job done. And then, we discover AI tools like ChatGPT. But, just like using Google without proper search queries, most devs use ChatGPT (and similar AI tools) without getting the most out of them. There's a gap between being a casual user and a power user - and that's what we're here to bridge.

The core mistake

The biggest mistake developers make when using ChatGPT is providing zero context, assigning no role, and specifying no format. Let's illustrate this with an example:

# Bad prompt
Write a function to sort a list of integers.

This prompt is doomed to fail. Why?

No context: What programming language are we using? What are the performance requirements?
No role: Are we looking for a simple implementation or an optimized one?
No format: Do we want a code snippet, a full function, or an explanation?

Compare this to a well-crafted prompt:

# Good prompt
I'm a Python developer working on a data processing pipeline. 
I need a function to sort a large list of integers efficiently. 
Please provide a high-quality, readable code snippet with type hints and a brief explanation.

The difference is stark. By providing context, assigning a role, and specifying a format, we've set ChatGPT up for success.

The SPAR framework for dev prompts

To take your ChatGPT game to the next level, we introduce the SPAR framework:

S - Spec

Clearly define the task: What do you want to achieve?
Provide context: What's the project about, what language are you using, etc.?
State the requirements: Are there any specific constraints or performance needs?

P - Pattern

Reference existing solutions: Are there similar problems or patterns you've used before?
Provide examples: Include code snippets, APIs, or data samples

A - Anti-pattern

Highlight potential pitfalls: What mistakes should ChatGPT avoid?
Specify error handling: How should errors be handled or reported?

R - Refinement

Define the output format: What do you want ChatGPT to return (code, explanation, etc.)?
Request refinement: Are there specific aspects you'd like ChatGPT to focus on?

Let's see the SPAR framework in action:

# SPAR prompt example
## Spec
I'm working on a Node.js project and need to implement authentication using JSON Web Tokens (JWT). 
The task is to create a function that generates a JWT token given a user's details.

## Pattern
I've used similar libraries like `jsonwebtoken` before. 
The function should take in a user's ID, name, and email.

## Anti-pattern
Please avoid using any deprecated libraries or functions. 
Error handling should be minimal, just throwing a generic error for now.

## Refinement
The output should be a code snippet in JavaScript, with a brief explanation of the approach. 
Please focus on security best practices.

5 copy-paste prompts for real tasks

Here are five actionable prompts you can use right away:

1. Debugging

I'm encountering a bug in my Python code where a list comprehension is throwing a `TypeError`. 
The code is:

python
data = [{'id': 1, 'name': 'John'}, {'id': 2, 'name': 'Jane'}]
result = [item['id'] for item in data if item['active']]

The error message is: `TypeError: 'dict' object is not subscriptable`. 
Please help me identify the issue and provide a corrected code snippet.

diff

2. PR review

I've got a pull request with the following changes:

diff

const fetchData = async () => {
const response = await fetch('https://api.example.com/data');
return response.json();
};

The reviewer mentioned that this might introduce a potential security risk. 
Can you review the code, highlight potential issues, and suggest improvements?

javascript

3. Test writing

I need to write unit tests for a JavaScript function that calculates the area of a rectangle:

javascript
function calculateArea(width, height) {
return width * height;
}

Please provide a set of test cases using Jest, covering different scenarios (e.g., positive numbers, negative numbers, edge cases).

java

4. Refactoring

I've got a legacy Java method that's a bit hard to read:

java
public String processData(List data) {
StringBuilder result = new StringBuilder();
for (String item : data) {
result.append(item).append(",");
}
return result.toString().trim().substring(0, result.length() - 1);
}

Can you refactor this code to be more readable and efficient, while maintaining the same functionality?

plaintext

5. Architecture

I'm designing a new e-commerce platform and need to decide on a database schema. 
The platform will have users, products, orders, and reviews. 
Please suggest a high-level database architecture, including tables, relationships, and indexes.

Chaining prompts for complex features

For more complex tasks, you might need to chain multiple prompts together.

For example, let's say you want to implement a new feature for a web application:

Initial prompt: Describe the feature and its requirements.
Follow-up prompt: Provide more context and clarify specific aspects.
Refinement prompt: Request changes or improvements.

Here's an example:

# Initial prompt
I'm building a web app and want to implement a search bar with autocomplete functionality. 
The search bar should query a backend API for suggestions.

# Follow-up prompt
The API returns a list of suggestions in JSON format: `[{ label: 'Suggestion 1', value: 'suggestion-1' }]`. 
Can you provide a basic implementation using React and the `react-autosuggest` library?

# Refinement prompt
The implementation should include a caching mechanism to reduce API calls. 
Can you modify the code to use a simple cache with a 5-minute TTL?

Full prompt library

While these prompts should give you a great starting point, having a comprehensive library of tested and optimized prompts can save you even more time. If you're interested in learning more about our prompt library, check out our resources page.

By following the SPAR framework, using actionable prompts, and chaining prompts for complex features, you'll be able to unlock the full potential of ChatGPT and ship code faster than ever before. Happy coding!

Looking for a complete resource? I packaged up 200 prompts / the full playbook: *AI Prompt Engineering Mastery Pack — $12***

How to Build a Prompt Library That Your Team Will Actually Use

Mavos.by.Kyklos — Sat, 13 Jun 2026 17:37:42 +0000

Every week I see posts like "what are your favorite prompts?" followed by 50 generic suggestions, and then the same thread appears again two weeks later.

The problem isn't that people don't share prompts. It's that most prompt libraries aren't built for reuse — they're just dumps of things that worked once.

Here's how I built one that my whole workflow actually depends on.

The structure that makes a library usable

A prompt is only reusable if you document three things alongside it:

The exact prompt (with placeholder variables in brackets)
The use case (what specific output you need it for)
The quality bar (what "good output" looks like so you know when to stop iterating)

Without #3, you don't have a library — you have a list of experiments.

Categories that cover 90% of knowledge work

The prompts that anchor each category

Email / edit_shorter.md:

Decisions / devils_advocate.md:

Copywriting / landing_page.md:

Operations / sop_builder.md:

Maintenance

Once per month:

Review every prompt you used that week
If you edited the output heavily, the prompt needs work
If you used it 5+ times without editing, it's a keeper

Remove anything you haven't used in 2 months. A smaller, higher-quality library beats a comprehensive one you don't trust.

The full set I've built

I've been doing this for a year and have 47 prompts that have survived the monthly review.

Get the AI Prompt Pack () — organized exactly this way, by category and use case, with notes on when each one is appropriate.

The most useful part might be what's NOT in it — the 150 prompts I tested and cut because they didn't hold up.

How I Found ChatGPT Prompts That Actually Work (Testing Framework + 5 Best)

Mavos.by.Kyklos — Sat, 13 Jun 2026 17:29:28 +0000

Most ChatGPT prompt guides give you the same 20 prompts recycled endlessly. Here's the framework I used to find ones that actually produce consistent ROI.

Testing framework

I treated prompt testing like A/B testing: define a task, run 5+ variants, compare output quality.

Three criteria for any prompt to make the cut:

Output quality — Can I use it directly, or does it need heavy editing?
Time saved — Does this measurably reduce time vs. doing it manually?
Consistency — Does it work every time, not just sometimes?

Most viral prompts fail criterion 3.

The 5 highest-ROI prompts I found

Email editing:

"Rewrite this to be 40% shorter without losing meaning. Cut filler, redundancy, and hedging. Show only the final version."

Decision support:

"List every way this plan could fail, every assumption I'm making, and every risk I'm ignoring. Be brutal."

Client communication:

"I need to decline this request professionally while preserving the relationship. The situation is: [situation]. Draft a response that is direct, warm, and leaves the door open."

Copywriting:

"Write a landing page headline and 3 sub-bullets for this product. Headline = the outcome the buyer wants. Bullets = the 3 most common objections a skeptical buyer would have."

Operations:

"Turn these rough notes into a step-by-step SOP. Each step should start with an action verb and be specific enough that someone new could follow it without asking questions."

The full library

I packaged 47 prompts that passed all three criteria into a download organized by use case:

Get the AI Prompt Pack ($12)

Grouped by: email, copywriting, operations, decision-making, client communication, research, content, sales.

Drop your highest-ROI prompt in the comments — I'm still refining the library.

From $0 to First Sale: The 6-Week AI-Assisted GTM Roadmap I Actually Used

Mavos.by.Kyklos — Sat, 13 Jun 2026 17:22:25 +0000

I launched my first digital product six weeks ago. No startup funding, no email list, no prior audience. Here's the week-by-week breakdown.

Week 1: Audience Research (the right way)

I spent week 1 only reading. No building.

r/entrepreneur, r/SideProject, r/Freelance: searched "I wish someone had told me" and "finally figured out" — people documenting real pain points
Product Hunt: 1-3 star reviews of competitors — these reveal exactly what's missing
Twitter: "[competitor] doesn't" — real objections from real users

AI move: I dumped 50+ Reddit comments into Claude and asked: "What is the single most common frustration? Give me the exact language people use."

Insight: people didn't want another tool — they wanted a proven process.

Week 2: Product Definition

The product needed to be: process-oriented, under , explainable in one sentence.

Result: A 6-week GTM roadmap for solo founders launching their first digital product.

Prompt that worked:

"Here's my product idea. Here are the 5 most common complaints about competing products. Rewrite my description to directly address complaints 1, 3, and 4."

Week 3: Building

I wrote the playbook in Notion — 14 hours total.

AI shortcut: I wrote bullet points first, then used:

"Expand these bullets into a practical how-to guide section. Second person, specific tools, real examples, no filler."

Week 4: Storefront

Vercel + simple JSON-based store + Stripe payment links.

The lesson: your landing page matters more than your product quality for the first 50 sales. Buyers evaluate your ability to explain the problem, not the product itself.

Landing page prompt:

"Write a headline and 3 sub-bullets for this product. Headline = outcome, not process. Bullets = the 3 most common objections a skeptical buyer has."

Week 5: Distribution

Two dev.to articles targeting search keywords my buyers used. Each ended with a natural product mention. Genuine Reddit participation — useful answers to real questions, not promotions.

Week 6: First Sale

Came from a dev.to article. Someone read it, clicked, bought. No email list, no DMs, no ads.

I packaged the full process — including all the AI prompts I used at each stage — into the product.

→ Get the GTM Playbook ()

If you've launched a digital product, what surprised you most about the first sale? Drop it in the comments.

5 ChatGPT Prompts That Actually Make Money (I've Tested 200+)

Mavos.by.Kyklos — Sat, 13 Jun 2026 17:05:26 +0000

I run a solo business and I've been methodical about finding prompts that actually produce ROI vs. prompts that sound impressive in a tweet.

After testing 200+, here are the 5 I'd keep if I could only keep 5.

1. The Ruthless Editor

Rewrite this to be 40% shorter without losing any meaning. 
Cut filler, redundancy, and hedging language. 
Show me only the final version, not your commentary.

Use it on: Emails, proposals, blog posts, landing pages. This prompt alone has saved me hours of editing per week. The key is the "40%" — vague instructions like "make it shorter" return garbage. Specific constraints produce clean output.

2. The Devil's Advocate

You are a highly skeptical critic of the following plan. 
List every way this could fail, every assumption I'm making, 
and every risk I'm ignoring. Be brutally honest. 
Do not soften your critique to be polite.

Use it before: Pitching clients, launching anything, making a hire, signing a contract. I run every major decision through this. It's caught at least three expensive mistakes this year.

3. Plain English Explainer

Explain [complex topic] like I'm a smart professional 
who has never worked in this field. Use one concrete analogy. 
Keep the total response under 150 words.

Use it when: Writing for non-expert clients, creating onboarding docs, building landing page copy. Forces clarity. If Claude can't explain it simply, your copy can't either.

4. Ideal Customer Persona (the version that works)

Based on this product/service description, tell me:
1. The single biggest fear my ideal customer has that they'd never admit publicly
2. The exact language they use when describing this problem to themselves (not to others)
3. What they've already tried that hasn't worked, and why they believe it failed

Use it when: Writing sales copy, planning content, building a product feature. This is the prompt that changed how I write every sales page.

5. Cold Email That Gets Replies

Rewrite this cold email so that:
- It opens with their specific problem, not our solution
- The ask is one concrete question, under 10 words
- The whole email is under 100 words
- It contains zero corporate jargon

Use it on: Every cold outreach before you send it. Open rates don't matter — reply rates do. This prompt is ruthless about it.

These five are from a library of 47 prompts I've built and refined over the last year running a solo business. If this kind of thing is useful to you, I packaged the full set into a $12 download.

→ Get the full AI Prompt Pack ($12)

It includes prompts for client acquisition, content creation, copywriting, operations, and decision-making — organized by use case so you don't have to hunt.

If you have a prompt that's genuinely changed your workflow, drop it in the comments. I'm always looking to add to the library.

The SaaS launch playbook that got me to $1k MRR in 6 weeks

Mavos.by.Kyklos — Fri, 12 Jun 2026 23:09:39 +0000

The SaaS Launch Playbook that Got Me to $1k MRR in 6 Weeks

I'll never forget the feeling of launching my SaaS product and watching it go from zero to $1,000 in monthly recurring revenue (MRR) in just six weeks. It was a whirlwind of activity, but also a carefully planned and executed strategy. In this article, I'll share my SaaS launch playbook, breaking down the key steps I took each week to achieve this rapid growth.

Week 1: Defining my Ideal Customer Profile (ICP)

The first week of my launch was all about defining my Ideal Customer Profile (ICP). I knew I had to be specific, or I'd end up trying to sell to everyone and appealing to no one. I used a method called "Customer Avatar Canvas" to help me get clear on who my ideal customer was.

To create my ICP, I asked myself the following questions:

What are their pain points?
What are their goals and aspirations?
What are their biggest challenges?
What motivates them?
What are their preferred communication channels?

After conducting research and interviews with potential customers, I defined my ICP as:

Job title: Marketing Manager or Founder
Industry: E-commerce or Digital Marketing
Company size: 10-50 employees
Pain point: Struggling to manage and analyze customer feedback

Having a clear ICP helped me focus my marketing efforts and create a product that truly solved a problem for my target audience.

Week 2: Pricing Experiment

The second week was all about pricing. I knew I had to get it right, or I'd be leaving money on the table. I decided to run a pricing experiment to see what would work best for my product.

Here's what I tried:

I created three different pricing tiers: $29, $49, and $99 per month
I set up a landing page with a pricing comparison table
I drove traffic to the page using Facebook ads and LinkedIn ads

The results were surprising:

The $29 tier got 20% of the sign-ups
The $49 tier got 60% of the sign-ups
The $99 tier got 20% of the sign-ups

What worked was offering a "middle" tier that provided the most value for the price. I settled on $49 as my primary pricing tier, with the other two tiers as options for customers who wanted more or less.

Week 3: Content Strategy

In the third week, I focused on creating content that would attract and engage my ICP. I wrote three articles and shared them on specific subreddits:

Article 1: "5 Ways to Improve Customer Feedback Analysis" (published on r/marketing and r/ecommerce)
Article 2: "The Ultimate Guide to Customer Feedback Tools" (published on r/saas and r/growthhacking)
Article 3: "How to Use Customer Feedback to Drive Growth" (published on r/productmanagement and r/entrepreneur)

The articles provided value to my target audience and helped establish me as an expert in my niche. I also engaged with commenters on Reddit, answering questions and providing additional insights.

Week 4: Cold Outreach

In the fourth week, I decided to try cold outreach to see if I could generate more leads. I sent out 200 cold emails to marketing managers and founders in my ICP, using the following template:

Subject: Improve Your Customer Feedback Analysis

Hi [First Name],

I came across [Company Name] and noticed you're using [Current Tool]. I'm reaching out because I think I can help you improve your customer feedback analysis.

Our tool helps you [briefly describe the benefits]. I'd love to schedule a call to discuss further.

Best,
[Your Name]

The response rate was 15%, with 30 people responding to my email. I scheduled calls with 10 of them and closed 5 deals.

Week 5: Product Hunt Launch

The fifth week was all about launching on Product Hunt. I prepared by:

Creating a compelling Product Hunt listing with a clear description and screenshots
Building a waitlist of 500 people who were interested in trying my product
Reaching out to influencers and bloggers in my niche to promote my launch

On launch day, I:

Posted my product on Product Hunt at 9 am EST
Shared it on social media and with my waitlist
Engaged with commenters and responders on Product Hunt

The results were amazing:

I got 200 upvotes on Product Hunt
I generated 50 new leads
I closed 10 deals

Week 6: What Drove Actual Conversions

In the final week, I analyzed what drove actual conversions. I found that:

My content strategy generated 20% of my leads
Cold outreach generated 30% of my leads
Product Hunt launch generated 50% of my leads

However, what drove actual conversions was the combination of:

Providing value through content and outreach
Building trust through social proof and testimonials
Offering a clear and compelling pricing tier

Conclusion

Reaching $1,000 in MRR in just six weeks was an incredible feeling. By following this SaaS launch playbook, you can replicate my success. Remember to:

Define your ICP and create a product that solves a real problem
Experiment with pricing to find the sweet spot
Create valuable content that attracts and engages your ICP
Use cold outreach to generate leads
Launch on Product Hunt to gain traction

If you want to get your hands on my full template pack, including my ICP template, pricing experiment template, and cold outreach template, send me an email at [Your Email]. I'd be happy to share it with you and help you launch your own successful SaaS product.

Looking for a complete resource? I packaged up 200 prompts / the full playbook: *SaaS Go-to-Market AI Playbook — $19***