Looking for people who make presentations regularly to help me test my product

I’m looking for a few people who regularly make presentations for work to help me test Narrate.

Narrate is a presentation builder that takes most of the design and layout work out of the process, so you can focus on your content instead. Personally, it reduced the time I spend making my sprint review presentations from 3–4 hours to around an hour.

I’m mostly looking for people who do things like sprint reviews, monthly or quarterly reviews, project updates, or similar presentations regularly.

I’d like you to use Narrate for your real presentations for a while and let me know what works, what doesn’t, and what’s missing.

I’ll activate a Pro account for free for anyone who participates so you can properly test everything.

If you’re interested, please comment or send me a message. I’d really appreciate the help.

Narrateview.com

reddit.com
u/realDubDub — 5 days ago

Looking for people who make presentations regularly to help me test my product

I’m looking for a few people who regularly make presentations for work to help me test Narrate.

Narrate is a presentation builder that takes most of the design and layout work out of the process, so you can focus on your content instead. Personally, it reduced the time I spend making my sprint review presentations from 3–4 hours to around an hour.

I’m mostly looking for people who do things like sprint reviews, monthly or quarterly reviews, project updates, or similar presentations regularly.

I’d like you to use Narrate for your real presentations for a while and let me know what works, what doesn’t, and what’s missing.

I’ll activate a Pro account for free for anyone who participates so you can properly test everything.

If you’re interested, please comment or send me a message. I’d really appreciate the help.

Narrateview.com

u/realDubDub — 5 days ago

PMs using AI for discovery/planning: how do you hand off the output to devs?

I’ve been using AI more during discovery and planning, and I usually end up with a bunch of context files for a project, requirements, notes, edge cases, mockups, technical context, etc.

I’m struggling to find a good workflow for what happens after that.

Do you just give those files to the dev team as-is? Do you turn everything into user stories/tickets first? Or are you using a specific tool or process to package all of that context for engineering?

Curious what’s actually working for people

reddit.com
u/realDubDub — 7 days ago
▲ 23 r/IndieAppCircle+3 crossposts

Finally got my first paying user

I’m just so happy that this finally happened. After launching Narrate a few months ago, I hit the same wall that I think all first time founders hit, how the hell should I get users?

But this week, after a lot of trial and error, I got my first paying customer.

I created Narrate six months ago just to create presentations for my sprint reviews easier and faster, but after a while I decided to make a product out of it. Tbh, I’m really proud of the final product, but I’m struggling to get it out there. This new pro user was just what I needed to continue and get back to working on this project.

The website is narrateview.com. I’d really appreciate any honest feedback if you guys have any

u/realDubDub — 8 days ago
▲ 11 r/Agentic_SEO+4 crossposts

Finally seeing some growth on my app and I haven't done any marketing yet (here is my process)

63 impressions, average position 31.9, zero clicks. 3-4 weeks in, one blog post a week, zero marketing. Already feeling an upward trend.

I built Narrate originally just for myself. I'm a PM and I spend a lot of time on recurring presentations (sprint reviews, project kickoffs, that kind of stuff). I built it so those wouldn't take so much time from me. Wasn't planning to ship it.

A few months in I thought it might have potential so I polished things up and cold launched it. No Product Hunt, no marketing, just put it out there.

The only thing I've been doing is writing one blog post a week. Here is my process:

Finding topics: either from my own experience or by looking at GSC queries with Claude. My first post was sprint review templates, second was about the MCP server feature I added so you can build presentations from your AI agent, latest is a QBR guide.

Research: I have a prompt I use with Claude or GPT to do a deep research pass, built to find good sources, not just whatever's ranking. The output of that becomes the source material for the draft.

Draft: Claude + a custom workflow I've built in Cowork. It starts with a set of questions (topic, audience, goal, tone, length), generates a content brief first for me to approve, then writes the draft against specific requirements: things like question-format headings, a quick answer block at the top, paragraphs capped at 2-3 sentences.

Humanizing: I use the humanizer skill from u/quang-vybe's post. It's useful and speeds things up a lot, but you'll probably need a few iterations to get it where you want it.

Final check: one more Claude pass to make sure the humanizer didn't break anything, then I read it myself, flag what's off, and publish.

Whole thing takes 2–4 hours per week. I try to write actual guides and not make them feel like ads.

Still polishing some things before I start the actual marketing phase. Would love honest feedback if you check it out: narrateview.com

u/realDubDub — 2 months ago