Hi IndieHackers. I'm a solo founder from Italy shipping Scrivix, an AI newsletter SaaS. We're at the beta stage and I'm documenting the journey here. Looking for 5 testers but also wanted to share the validation process and see what resonates.
The Problem I Noticed
I started keeping a simple spreadsheet in mid-2025: tracking why newsletter creators I knew kept abandoning their newsletters.
The data was striking:
- 15 people said they wanted to run a newsletter
- 12 started in Q4 2025
- 3 were still active by January 2026
Common theme in the dropouts: "It's just 6-9 hours a week and I can't sustain it."
Then I did some desk research and found something interesting: 350+ AI-generated newsletters launched in 2025. Why? Because there's clearly massive demand for newsletters in every niche, but creating them is a time suck.
Hypothesis: If I can automate the most painful part (research + writing first drafts), people will actually maintain newsletters.
My Research Phase (2 weeks)
I didn't build immediately. Spent two weeks talking to:
- 8 newsletter creators (different niches: tech, marketing, finance, fitness)
- 4 agency owners who manage newsletters for clients
- 2 B2B companies running internal newsletters
Key findings:
- Time is the #1 blocker, not quality or reach
- Most want to write a newsletter but outsourcing it costs €800-2000/month
- Existing tools (Substack, Ghost, Beehiiv) are publishing platforms, not research automation
- Nobody had heard of a tool that specifically handles the research + drafting part
This validated my hypothesis. Not perfectly, but enough to justify a build.
The Build (4 months)
Timeline:
- January: Designed the core flow and wireframes
- February-March: Focused on the research engine (web scraping + semantic ranking)
- April-early May: Built the UI, connected to AI, created the approval workflow
- Mid-May: Shipped MVP with basic analytics
Tech stack: Python (FastAPI), React + TypeScript, PostgreSQL + Redis, DigitalOcean (€15/month)
Biggest challenge: Getting the ranking algorithm right. Finding articles is easy; ranking them by relevance to YOUR niche and tone required a lot of iteration.
Cost to date: ~€200 (domain + hosting + API credits)
Early Validation (3 users, 6 weeks)
Shipped the MVP to 3 friends in late May:
- Friend A: Tech newsletter, 500 subscribers
- Friend B: Marketing newsletter, 200 subscribers
- Friend C: Fitness/health newsletter, 100 subscribers
Metrics after 6 weeks:
- Retention: 100% (all 3 still active)
- Weekly login rate: 71%
- Newsletter output: 12 newsletters sent through Scrivix so far
- Time savings: Friend A reported going from 5 hours to 45 minutes per week
Qualitative feedback:
- "I was about to pause my newsletter. This makes it fun again."
- "The AI suggestions aren't perfect, but 70% are spot-on and that saves me hours."
- "I want to add custom sources."
Sample size is tiny, but the retention and engagement signals are encouraging.
Where I Am Now
What's working: the core concept (research automation saves time), simple UX, useful AI suggestions ~70% of the time.
What's unclear: pricing, B2B vs consumer, churn rate (only 6 weeks in).
What's broken: source customization is weak, no reader analytics, mobile experience is rough, onboarding assumes they know their niche.
What I'm Asking For Now
I'm looking for 5 beta testers to:
- Validate that this solves a real problem
- Get feedback on what's actually broken
- Collect testimonials for the public launch
- Learn if there's a B2B market
Who I'm looking for:
- Creators/solopreneurs running newsletters (any niche)
- Agencies managing 2+ client newsletters
- B2B companies with internal or external newsletters
- Anyone actively writing for an audience
What they get:
- 3 months free access (would normally be $29-49/month)
- Direct Slack channel with me
- Input on what ships next
- Early bird pricing locked in forever
The Business Side
Revenue model: Freemium SaaS
- Free: 1 newsletter, basic features
- Pro: €29/month (unlimited newsletters, custom sources, analytics)
- Agency: €99/month (client management, branding)
Revenue target: €1k MRR by Q3 2026 (33 paying customers). Seems conservative but realistic for a bootstrap.
Key Learnings So Far
- Talk to users before building. I almost shipped a 10x more complex product.
- Launch with constraints. €0 budget forced me to build simple and focus ruthlessly.
- Retention > growth. 100% retention after 6 weeks is a strong signal.
- The landing page shouldn't be fancy. Just be clear about the problem and solution.
Invite
If you're interested in testing Scrivix, head to scrivix.it and apply for the beta.
If you're building something similar or have feedback on the approach, drop a comment. Would love to hear from other founders building in the newsletter/AI space.
Have you faced the "6-9 hours/week" problem with content creation? What would make you trust an AI newsletter tool? Would you pay €29/month for this vs. €1000+ for a freelancer?
The dropout data you collected is genuinely interesting — tracking 15 people from intent to abandonment is exactly the kind of qualitative research that most solo founders skip. That "6-9 hours a week" quote is a real insight because it frames the problem in time, not quality, which changes what the solution needs to be.
One thing worth pressure-testing: the 350+ AI newsletters that launched in 2025 — were those abandoned because of the same time constraint, or because AI-generated content isn't differentiating enough to build an audience? The failure mode might matter for how you position Scrivix. If it's "AI helps you save time," you're competing on efficiency. If it's "AI helps you be consistent," that's a different emotional hook and probably stickier.
Happy to be a beta tester if you're still looking — I run a niche tool for indie game developers so I understand the "small but passionate audience" distribution challenge from the creator side.
That consistency vs. efficiency framing is sharp and I've been sitting with it.
From what I tracked, the 350+ AI newsletters that died mostly collapsed in weeks 3 to 6 before audience feedback could accumulate. They didn't get far enough to test whether the content was differentiating. Time was the chokepoint, not quality.
But you're right that the hook matters. 'Save 5 hours a week' is a feature. 'Actually ship every Thursday for 6 months' is the outcome people actually want. I should probably lead with that.
Your indie game dev niche context is exactly the kind of use case I want to stress-test. Drop me a line at [email protected] and I'll get you in.
I wanna test it
Love it! Drop me a message at [email protected] and I'll get you set up.
Quick question: are you running a newsletter now, or planning to start one? Helps me make sure the beta fits your situation.
We are looking for someone who can lend our holding company 200,000 US dollars.
We are looking for an investor who can lend our holding company 200,000 US dollars.
We are looking for an investor who can invest 200,000 US dollars in our holding company.
With the 200,000 US dollars you will lend to our holding company, our finance team will invest the money in the stock market and some business sectors, thus making a significant profit for both of us.
With your 200,000 US dollars investment in our holding company, our finance team will invest it in the stock market and 4 different business sectors, significantly increasing our profits within a few months.
Your 200,000 US dollars investment in our holding company will be invested by our finance team in the stock market and several business sectors.
The 200,000 US dollars you will invest in our holding company will be used by our finance team in the stock market and in 4 different business areas.
Which business sectors will be invested in?
Money will be increased by investing in major sectors such as cybersecurity, software, furniture, and e-commerce.
With the 200,000 US dollars you have invested in our holding company, we will invest in major sectors such as cybersecurity, software, furniture, and e-commerce.
With the $200,000 USD budget you've invested in our holding company, we will significantly increase our profits within just a few months by investing in high-market sectors such as cybersecurity, software, furniture, and e-commerce.
If we use the 200,000 US dollars you invested in our holding company across four different business sectors, our earnings will increase rapidly.
By dividing the 200,000 US dollars into different business areas, we will reduce the loss rate to zero.
By investing the 200,000 US dollars you lent to our holding company in the stock market and four different business areas, we will rapidly increase the rate of return on investment.
We will use the 200,000 US dollars you lent to our holding company to rapidly increase our profits by investing in sectors such as stock market and cybersecurity, software, furniture, and e-commerce.
Our finance team will use the 200,000 US dollars you lent to our holding company to invest in the stock market and in high-market sectors such as cybersecurity, software, furniture, and e-commerce.
By using 200,000 US dollars in 4 different business sectors, we will generate a significant amount of income within a few months.
So how will we market the products we produce?
Thanks to our strong advertising network, we will be able to sell the products we produce quickly.
Thanks to our strong advertising network, we will quickly find customers for the products and projects we will produce.
Thanks to our strong advertising network, we will attract a large audience to our projects, which means we will quickly generate significant revenue.
By using WhatsApp groups, Twitter, Instagram, Facebook groups, TikTok, Telegram groups, LinkedIn, and many other high-traffic social media platforms for advertising, we will be able to conduct large-scale advertising.
By using various advertising tactics such as Facebook ads, YouTube ads, Google ads, and email advertising, we will be able to rapidly increase our customer base.
We will also try to attract an audience by using social media applications and websites from different countries.
We have 170 social media accounts, and by simply running ads on these platforms, we can reach an audience of 300,000 people within a week.
We are able to announce our projects to 300,000 people in just one week.
What will your earnings be?
If you invest 200,000 US dollars in our holding company, you will receive your money back as 750,000 US dollars on December 30, 2026.
If you lend our holding company 200,000 US dollars, I will return your money as 750,000 US dollars on 30/12/2026.
You will lend our holding company 200,000 US dollars, and I will return your money as 750,000 US dollars on December 30, 2026.
If you invest 200,000 US dollars in our holding company, you will receive your money back as 750,000 US dollars on December 30, 2026.
I will return your money to you as 750,000 US dollars on December 30, 2026.
You will receive your 200,000 US dollars, which you lent to our holding company, back as 750,000 US dollars on December 30, 2026.
If you lend our holding company 200,000 US dollars, I will return your money as 750,000 US dollars on 30/12/2026.
Your investment of 200,000 US dollars in our holding company will be evaluated by our finance team, and I will return your money to you as 750,000 US dollars on December 30, 2026.
I will refund your money as 750,000 US dollars on 30/12/2026.
By investing 200,000 US dollars in our holding company, you will generate significant returns within a few months.
Thanks to our financial project, you will significantly multiply your money within a few months.
How can you contact us?
To learn how you can lend our holding company 200,000 US dollars, you can get detailed information by sending a message to the WhatsApp number, Telegram username, or Signal number below.
For detailed information, please send a message to the WhatsApp number, Telegram username, or Signal number below. I will provide you with detailed information.
To learn how you can increase your money by investing 200,000 US dollars in our holding company, send a message to the WhatsApp number, Telegram username, or Signal number below. I will provide you with detailed information.
To learn how you can invest 200,000 US dollars in our holding company and to get detailed information about our project, please send a message to the WhatsApp number, Telegram username, or Signal number below.
You can get detailed information by sending a message to the following WhatsApp number, Telegram username, or Signal number.
To learn how you can increase your money and get detailed information, send a message to our WhatsApp number, Telegram username, or Signal number below. We will provide you with detailed information.
My WhatsApp contact number:
+212 619-202847
my telegram username:
@adenholding
Signal contact number:
+447842572711
Signal username:
adenholding.88
Mostly evolved — started with the abandonment problem as the anchor and built backwards from there.
The first version had a more rigid flow: context prompt → generate draft → edit → send. But watching early testers use it showed the real blocking step is earlier than I assumed. The "what do I even write about this week" problem is upstream of the draft. So the flow shifted to lean harder into the setup phase — context scaffolding before generation ever starts.
Some things were fixed from day one (async-first, no requirement to be 'good at prompting', no blank page). But the specific sequencing came from watching where people got stuck.
Did you go through a similar process with whatever you're building, or did you find upfront definition actually held up?
Feels like most of these issues come from figuring things out while building instead of before.
Did you define your flow clearly upfront or did it evolve during development?
Same situation with a platform last year. AI SaaS, solo, zero budget. Reddit threads where your exact user was already venting gave better feedback than any launch page. For Scrivix that's probably r/newsletters or wherever newsletter creators are already complaining about their tools.
That's a good tip. r/newsletters is somewhere I haven't gone yet — the build phase felt more urgent than distribution research. But reading complaints before you have a solution is probably more useful than after.
Did you find that Reddit feedback aligned with what your actual users told you later, or was it a different set of problems?
This is actually quite good-when you first look at it, maybe not so much, but-if people are coming back and re-using it, that is the only true signal this early on; most things like this, you use once and they are forgotten. ~
One thing I would be interested to monitor though is that saving time is good-it’s usually not enough of a pull. One thing in there felt more compelling, when users are saying that they want to write again.
If I were you, I’d lean into that one more-like-not quite so much "research tool" and more "thing that helps you just stay consistent without overthinking it."
And also, I would avoid expanding too rapidly right now; things like this very easily become a suite of features rather than a really tight focused thing for one kind of user. Getting three people that use it every week religiously is way more powerful than building features for it.
Honestly, though, this is where I would want to be at this stage.
The 'I want to write again' line is the one I keep coming back to. You're right that it's a stronger pull than time savings. Time savings is a feature. Wanting to write again is the reason someone started a newsletter in the first place.
The better frame might be: the thing that removes the Sunday dread of 'I have to do my newsletter this week.' That's more honest about what it actually does.
On feature sprawl: fully agree. The impulse to add features for every possible user type is real. Resisting it is the actual discipline right now.
I have the same problem and excellent product but I can't find testers, they say yes and then just disappear some of them it's avoiding me, why they yes!!! And a product with a few visits and growing really slow but let me tell when a saw a fist revenue OMG was such a rush. So let's keep going just that, keep doing what you doing and the results will be soon.
The ghosting is real. What helped me was being very specific upfront — 15 minutes a week on Slack, async, nothing more. When people know exactly what they're committing to, drop-off is lower.
And yes, that first revenue moment is something else. Keep going.
The spreadsheet-first approach before building is the part most people skip — and it shows in the quality of what you built. 100% retention after 6 weeks with 3 users is a real signal, not just a vanity number.
I'm in a similar phase with Autoreport (Stripe analytics by email every Monday) — also solo, also €0 budget, also learning that the first few users teach you more than any amount of traffic.
One thing that's helped me: the "6-9 hours/week" framing you discovered is already a conversion argument. That's exactly the number that justifies €29/month when you put it side by side. €29 vs 6 hours of your time is almost a no-brainer for anyone who values their time.
Happy to swap notes on early validation if useful. What's your current acquisition channel for the 5 beta testers?
Autoreport sounds solid — 'Stripe analytics by email every Monday' is tight positioning. Recurring, dead simple, no dashboard to remember to check.
On your question: the 5 testers came 100% from people I already knew or had spoken to during the research phase. No cold outreach, no ads. This IH post is the first time I've gone beyond my own network.
The €29 vs 6 hours point is sharp and I'm going to use it more directly. I lead with time savings but haven't done the explicit math side by side. Good nudge.
Happy to swap notes. What phase are you at with Autoreport — pre-revenue or already charging?
Charging from day one — €19/month via Paddle, launched a month ago. Pre-revenue so far, but the positioning is getting sharper through conversations like this one. The "30 minutes every Monday" framing is something I'm testing too.
Interesting that all your testers came from people you already knew. That's consistent with what I'm hearing everywhere — the first users almost always come from existing relationships, not channels. The IH post extending beyond your network is exactly the right next step.
What's your read on B2B vs consumer for Scrivix? The agency tier at €99 feels like it could be the real business.
Good move charging from day one — even pre-revenue it sets the right expectation that this isn't a hobby project.
On B2B vs consumer: honestly I don't know yet. The €99 agency tier exists because a few agency owners I spoke to during research seemed genuinely interested, but I haven't properly validated it. Forze made the same point earlier in this thread — agencies have lower churn and higher willingness to pay. That's probably where the real business is once the product is tighter.
For now I'm staying consumer-focused because feedback loops are faster. One beta tester a week tells you more than one agency deal a month at this stage.
Really like how you validated before building — that 5h → 45min result is a strong signal. I’ve seen the same problem with consistency, if you nail custom sources + tone control, this could stick long-term.
Thanks bhavin. Custom sources and tone control are exactly what I'm building next. The current version pulls from RSS and Hacker News — useful but generic.
The long-term value is when it learns that your newsletter about React development cares about certain authors and topics that no generic feed would surface. That's the version I want to get to. Still a few weeks out but it's the next big milestone.
The positioning is sharp. “We’re not a publishing platform, we’re what happens before publishing.” That’s a clear line that Substack and Beehiiv can’t easily cross because their whole product is built around the sending side. Your ranking algorithm is both your biggest challenge and your biggest moat, like Forze said.
That framing came out of a conversation with a potential user actually. They asked 'so it's like Beehiiv but smarter?' and I said no — it's what you do before you even open Beehiiv. That's when the positioning clicked.
You're right that Substack and Beehiiv can't easily cross that line without rebuilding from scratch. Their flywheel is the publishing side. Ours is the research side. Different starting points.
The dropout data is the strongest part of this whole post - 12 started, 3 still active by january. That's not a motivation problem, That's a time problem, and you identified it before building which is the right order.
The 5 hours to 45 minutes signal from friend A is the number you should put everywhere. That's a before and after that anyone running a newsletter understands immediately.
One thing worth thinking through - the 70% accuracy on AI suggestions is honest but it might be the thing that kills retention at scale. Friends tolerate rough edges, strangers don't.
what does the 30% failure look like - wrong tone, wrong sources, wrong angle? knowing which failure mode is most common tells you exactly what to fix first.
The 70% is the thing I think about most. To answer your question directly: the main failure mode is wrong angle, not wrong sources. The sources are usually relevant. But the draft sometimes frames a topic in a way that doesn't match the creator's voice or what their readers expect.
That's why the approval step exists — nothing goes out without the writer reviewing it. But you're right that at scale with paying strangers, 70% won't be good enough. Knowing it's an angle problem and not a sourcing problem tells me exactly what to work on next.
Good push.
This sounds like a solid idea, especially with how fast AI content is growing. I’d be interested in testing it out and giving feedback. What makes your platform different from existing newsletter tools?
Hey arrangill. The short answer: Substack, Ghost, Beehiiv are publishing platforms. They help you send. Scrivix does the work that happens before that.
It finds relevant articles from across the web for your specific niche, ranks them by relevance, and drafts a newsletter around them. You still edit and approve everything — but the 5+ hours of research and first draft are mostly handled.
If you want to test it, head to scrivix.it and apply for the beta. Still have spots open.
Really appreciate you sharing the whole process here, not just the "here's my product, please test it" pitch. The spreadsheet tracking why people abandon newsletters is a clever low-tech way to find signal before writing a single line of code — that's the kind of research that actually holds up.
The retention stat (100% over 6 weeks) is genuinely interesting, even with a tiny sample. With 3 users you can't read too much into it statistically, but the qualitative feedback tells a real story. "I was about to pause my newsletter. This makes it fun again." That's the kind of thing you can't fake.
One thing I'd push on: you mentioned the ranking algorithm was the biggest technical challenge. That's probably also your biggest moat if you nail it. Every AI writing tool can draft content — but surfacing the right sources, tuned to a specific creator's niche and voice, is much harder to copy. Worth doubling down there.
On the B2B vs consumer question — have any of the 4 agencies you talked to during research followed up since you launched? Agencies tend to have more predictable churn and higher willingness to pay, which could make that path more capital-efficient even if it's slower to acquire. Just something to weigh.
Good luck with the beta. The €29 price point feels right for early adopters — low enough not to be a blocker, high enough to signal you're serious.
Thanks Forze. This is exactly the kind of feedback I was hoping this post would generate.
On the ranking algorithm as moat: you're right, and it's where most of my engineering time goes. The draft is the easy part. Getting the tool to understand that a fintech newsletter cares more about regulatory shifts than generic VC funding news — that's the actual hard problem. Still a lot of iteration left there, but it's the thing I'm most excited about.
On the agency question: I haven't followed up with the 4 from research yet. Honestly sitting on it. Your point about predictable churn and higher willingness to pay is a good nudge to prioritize those conversations this month.
Appreciate you reading the whole thing and pushing on the real questions.
Nice, early stage here too 🙌
Out of curiosity — how are you planning to handle support / user messages as people start testing?
I’m starting to get a few and it already feels messy between emails and random feedback. Trying to keep it simple without using heavy tools.
Hey Kilenta. Keeping it dead simple on my end: one Slack channel per beta tester, fully async. I told them 15 minutes a week is all I need from them.
No ticketing system, no forms. At this stage I want conversations, not bug reports. The messy, unstructured feedback is actually the most useful part.
What kind of feedback are you getting? More product direction or mostly bugs?
Yeah that makes a lot of sense.
I’ve been seeing the same — early on, unstructured feedback is actually super valuable.
The only thing I’m starting to notice is that after a bit of volume, it becomes harder to keep track of patterns (same issues, priorities, etc.)
Right now for me it’s a mix — some product direction, some small bugs.
Have you started feeling that yet or still manageable on your side?
Still manageable with 3 testers. I keep a simple doc: one row per piece of feedback, tagged by problem area. Takes 5 minutes after each Slack conversation.
The thing that helps most is asking specific questions. 'What did you struggle with this week?' gets way better data than 'any feedback?' Much easier to spot patterns when the input is already scoped.
At what point does it start feeling like too much for you? How many users are you at now?
Still very early — just a handful of users so far, so it's manageable for now.
But I can already feel what you’re describing — things start to slip through the cracks pretty quickly once there’s a bit of volume.
Your approach with the doc + tagging makes a lot of sense actually.
What I’m trying to build is basically a way to keep that simplicity, but automatically group feedback and surface patterns without needing to maintain it manually.
Out of curiosity, what part feels the most annoying for you right now — collecting the feedback or making sense of it after?
Definitely making sense of it after. Collecting is easy when you're asking specific questions over Slack. The hard part is sitting down and asking: is this a one-off or a pattern?
Sounds like you're building something interesting on that side. Is it designed to plug into existing channels like Slack or more standalone?
Yeah that’s exactly the part I’m focusing on — making sense of it after without adding more manual work.
Right now it’s more standalone, but designed to plug into existing channels like Slack/email rather than replace them.
The idea is: you keep your current workflow, but everything gets centralized and patterns start surfacing automatically.
Still pretty early, but I have a rough version working.
If you're up for it, I’d love to show it to you — feels like you're exactly at the stage I’m building for.
That sounds exactly like the gap I'm feeling. Centralized, patterns surfacing automatically, no added manual overhead. That's the thing I'd actually use.
Yeah, I'd love to see it. How do you want to share? Happy to give you real feedback from the 'actively running beta with 3 testers' angle — that seems to be exactly the stage you're building for.
Awesome — that’s actually perfect timing then.
Since you're already running a small beta, your feedback would be super valuable.
It’s still pretty early but usable — I can give you access and you can try it in your current workflow.
If you're up for it, I’d also be happy to show you quickly how I’m using it on my side.
What works best for you?
Got it — just checked and I'll look for your message. Talk soon.
Ah yeah good point — Indie Hackers isn’t great for DMs 😄
i send you a message on [email protected]
That works great. Happy to test it in my current workflow and give you real feedback from the beta-running side.
Easiest way to connect is a DM here or through scrivix.it — either works. What's your preferred channel?
Scrivix looks like a lifesaver—that '6-9 hours a week' wall is exactly why most newsletters die!
Since you’re looking for validation right now, you should definitely check out the Validation Arena.
It’s a $19 challenge where founders compete to get their first paid customers. The winner gets a trip to Tokyo. >
It’s a great way to see if people will actually pay that €29/month before you spend more time on it. Plus, the prize pool just opened at $0, so the odds are huge
Thanks Tokyolore. That wall is real. It's exactly why 9 out of 12 people I tracked quit their newsletters within a few months.
The bet with Scrivix is that if you cut the weekly time from 5 hours to 45 minutes, most people will actually stick with it. Retention > growth is the whole philosophy at this stage.
Dropping the discussion prompts here to get the conversation going:
Have you run a newsletter and hit the "I don't have 6 hours this week" wall? What did you do — push through, hire, or pause?
What would actually make you trust an AI tool with something as personal as your newsletter voice? For me the key signal was whether the suggestions felt curated or just scraped — there's a big difference.
The €29/month vs. €1000+ freelancer comparison feels obvious on paper, but in practice most people don't make that comparison consciously. What's the real decision you're making when you choose DIY vs. tool vs. outsource?
Genuinely curious — especially from anyone who's tried to monetize a newsletter audience. Is the time savings argument enough, or do you need something more to justify paying for tooling?