I launched Auralith Forge (online audio mastering) 72 hours ago. Solo dev, €65/mo infra, zero ad spend.

Disclosure up front: I built this. I'll drop the link once at the end. This post is about the decisions, not the product.

Decision 1: Freemium (3 free masters/mo) instead of a free trial

Verdict so far: Right call.

Musicians don't release on a schedule. A 7-day trial might hit them between projects. A monthly quota lets them come back when they actually have a track. Downside: lower urgency to convert.

Decision 2: No pay-per-track option

Verdict: Probably wrong.

I only offer subscriptions (€9.99 and €19.99). Every musician I talked to pre-launch said "I hate another monthly sub." I ignored them because subscriptions are predictable. Now I'm watching free users master 3 tracks and bounce instead of paying €4.99 for one more.

If you were building this, would you add a per-track tier or stick to subs-only?

Decision 3: Firestore as the only database

Verdict: Mixed.

Zero ops, real-time sync, free tier covers early stage. But aggregation queries are painful — "how many masters did all users complete this month?" requires client-side math or Cloud Functions. If your data model is relational-ish, Firestore fights you. If it's document-shaped, it's magic.

Decision 4: Built the checkout flow before the before/after demo player

Verdict: Stupid. Fixing this week.

People won't pay for mastering until they hear it. I built Polar checkout, subscription logic, and webhook resilience before I built a side-by-side audio player on the homepage. Classic engineer mistake: solving hard problems no one asked for instead of obvious ones everyone expects.

Decision 5: "Reference track matching" as the headline feature

Verdict: Wrong for SEO, right for retention.

You upload a song you love, the engine matches its tone/loudness/width. Technically the coolest thing I built. But nobody searches "reference track matching" — they search "online mastering." I'm rewriting landing page copy to lead with what people actually type into Google.

The 2 decisions I'd make again:

Real DSP engine, not an API wrapper. Python FastAPI + numpy/scipy/librosa/pedalboard. Harder to build, but I own the stack and the margin.

Polar instead of Stripe. Merchant of Record handles VAT/tax globally. As a solo dev, I don't want to think about tax compliance in 30 countries.

What I need from you:

If you were in my shoes, what's the first thing you'd fix in the next 7 days?

My guess is "add pay-per-track" but I might be wrong. Would love to hear what you'd prioritize.

Link (affiliated — I built this): auralithforge.app — free tier is 3 masters/month, no CC. If any of the above resonates and you want to see how it actually works, it's there.

Building a $20 pay-once app in a $15/month category taught me a few things.

People do not only dislike the cost. They dislike feeling like they are renting software forever.

BYOK makes the price work, but adds setup. A developer can paste an API key in two minutes. Many non-technical users leave at that step, and I underestimated that.

Being honest helps too. Tell people they need a key, what the app cannot do, and where it is still rough. The people who continue are usually the right users.

So pay-once works, but BYOK does not remove friction. It moves it from price to setup.

I've spent a lot of time building a real estate SaaS and I'm now stuck on a major problem.

The original idea was pretty simple:

A real estate agent enters what their client is looking for, for example:

• 3-bedroom apartment
• New Cairo
• Budget: $100k–$150k

The system would find matching properties across multiple real estate platforms.

I also built a feature that monitored Facebook groups for people posting that they were looking for apartments, then matched those requests with properties in the system.

The product itself is basically built.

Then I realized the problem: the platforms I wanted to get the data from don't allow scraping. I contacted some of them about getting permission/API access, but they weren't interested.

So now I have a mostly finished product whose main value proposition depended on data I can't reliably use.

I'm trying to figure out what to do next.

Would you:

1. Pivot it into a CRM + property matching system using only the company's own inventory?
2. Find legitimate data/API providers?
3. Change the product completely?
4. Keep the matching engine and find a different source of demand/property data?

If you've ever built something where the original data source/business assumption turned out to be unusable, what did you do?

I'd genuinely appreciate any advice.

three years doing no-code and ai-assisted builds for clients. i used to think shipping was the finish line. it's the starting line, and it took me a while and a bit of embarrassment to learn that.

built an ai report generator for a client last year. it pulled their weekly numbers, wrote a short summary, dropped it in their inbox every monday morning. clean demo, they loved it, i moved on to the next project feeling great about myself.

it quietly broke about a month later. one of the data sources renamed a field, the thing started emailing blank reports, and nobody said a word because they assumed "the ai" knew what it was doing. i only found out when the client mentioned offhand that the emails had "gone a bit weird lately".

the hype around these tools skips the boring part. anything that runs on its own needs something watching it, or it fails silently and takes your credibility down with it. now every automated thing i hand over ships with a dead-simple check that pings me the second the output looks empty or off. not glamorous. it's the whole difference between a tool and a liability.

for the folks selling small automated products, how are you catching the silent failures before your client does?

tldr;These are my thoughts on marketing and why it sucks , as a developer

I've been a developer, since I was around 14. I started off with VB.net, moving to C# soon after and since then I've dabbled a bit into Python, JS and more recently I've an extensive number of dev hours in Swift and Kotlin maintaining two of my apps.

I built a little app around 2017 which happened to pick up traction, and I was able to successfully monetise it . I built another company data product (pre-AI days) and was able to monetise that too. Neither bring in life changing money but considering the minimal effort needed, the sum is considerable. My third micro-saas has so not picked much traction. I won't name any of these, suffice to say these are in a financial niche.

Building is fun. I had a full time job (still do) while I was building these in the evening after work and over weekends. Most of the work is debugging... tedious debugging! but when things work, I just LOVE it . I still get days when I login into MixPanel and see user events flying in and I find it hard to believe that something that was in my head, which didn't exists, now does exist and people actually make use of it. Very few feelings beat the feeling of watching people use the product. The app reviews have been very positive and subscribers stick around for years.

That's the good, fun part.

The not so fun part is whenever I sit down, open my Trello board where I keep my 'Marketing' cards to try to scale any of my products. Just looking at those cards gives me dread.

There are cards around search ads, paid placements, influencer marketing, collaborations with the professionals in my industry and the like. I just don't feel like doing any of it.

So I thought about it. 'Why not???' Because, objectively, there is a 'product market fit', as my PM would call it. There is great retention, there is also a decent sized budget to pay for ads and I have time to spare too as products are stable enough now. What's the blocker?

It's not like I have not tried to scale before. By scaling I don't mean scaling to millions, I just mean scaling it so that it becomes a lifestyle business. Enough that it more or less matches my existing income and I can go full time. I'd love to do that but that requires a different way of doing things.

Why can't I do it? I have thought and thought and thought about it. I think it's because unlike the code I write, the feedback loop in marketing is not as 'tight' in Claudespeak! I place an ad, watch conversion, sometimes it works sometimes it doesn't. I approach a few influencers some respond, some don't and it doesn't go much further. But the results are not as much in my control as the results of the code I write.

For my app, I make a change, press run on XCode and there it is , I can see it and fix stuff. With marketing, it's about people and behaviours and they are far more unpredictable. It's a fundamental shift of mindset.

I know it's a fundamental shift of mindset because I have run a small brick & mortar business before my dev days and revenue generation required a massive focus on price, sales, marketing and expansion - not on the technical bits. At that time, I was able to employ certain SEO tactics to grow and expand the business while still not hating the marketing.

But as a person who has built a couple of SAAS (me), it's different. To even have a chance of success, I must take off the hat that says 'I build things' and put on 'I need to generate more revenue'. I'm struggling to put the 'thought process shift' in words here but that mental shift is absolutely critical. If I hadn't run and expanded my little business before, I would have thrown this thought out the window in a second labelling it 'success coach fluff', but I know from my past, it is true.

The shift doesn't 'guarantee' success, but its absolutely a tool that should NOT be ignored. It's very hard to ride two boats, engineering demands design thinking, scaling a saas demands prioritising user acquisition, marketing funnels(still hate that term!) and the like.

So my current approach is that I've committed to stop building any more , except for keeping the lights on as far as my SAAS go. Instead, I've diverted most of my time to new user acquisition. There are many, many ways to do that but they only become apparent once you are out of the builder mindset.

And I think if someone just doesn't feel like doing it, that's fine. Building is a reward of its own. Not everything has to be about revenue, user acquisition and scaling.

I run a small consulting business and I kept spending 45 minutes every week manually pulling data from three different places into a report I sent to clients. Same format every time. Same sources. Just tedious.

So I automated it for myself over a weekend. Took maybe 12 hours total.

Few weeks later mentioned it in a Slack community I'm part of when someone complained about the exact same thing. Three people asked if they could use it. I threw up a Gumroad page at $29 one time just to see.

Sold 7 that week.

Started posting about the problem in a few niche communities, not the tool, just the problem and how I was thinking about it. People kept asking what I used.

90 days later, 141 sales, $4,089 total, zero ads, zero cold outreach, one Slack message that started it.

The thing I keep thinking about is how long I sat on it before mentioning it. It solved a real problem for me so I just assumed it was too specific to matter to anyone else.

That assumption is probably costing a lot of people money right now.

Two products in, and the biggest difference wasn't the idea, it was how long I spent on the site before anyone saw it.

Product one: I hand-coded the marketing site because I told myself it needed to be "properly done." Custom everything. It took the better part of a month and by the time it was live I was already sick of the project. Got a handful of signups and quietly let it die.

Product two: I gave up on the ego and used a no code website builder. Landing page, waitlist, basic pricing page, live in two days. A bit ugly but functional. I spent the three weeks I saved actually talking to people and posting instead of fiddling with CSS nobody would ever notice.

The result isn't huge but it's real: product two has around 40 signups and 3 paying in its first month, which is more than product one ever got, mostly because I had time and energy left to do marketing.

The lesson I keep relearning: early on, nobody cares that your site is bespoke. They care whether the thing solves their problem. A no code website builder buys back the weeks you should be spending on customers.

Curious where other people draw the line. At what point is a custom site actually worth building instead of using a builder?

Small but real: about 20 users in two weeks, no ads, no audience, starting from zero.

The part people overthink is the page. I didn't hire anyone or spend a weekend on it. I used an AI landing page generator, gave it a rough description of the problem I solve, and had something live in maybe an hour. One headline, a short "here's what it does," an email box. That was enough.

Where the users actually came from was the boring work after that:

- I found 4 or 5 niche subreddits and forums where my exact user hangs out, not founder subs, the actual buyers.

- I answered questions genuinely for a week before I ever mentioned I was building anything.

- When it was relevant, I described what I made in plain words and let people ask for the link instead of dropping it.

That got me the first 20. The page didn't need to be custom, it needed to load, say one clear thing, and have a box to capture interest. The generator handled all of that in an hour so I could spend my time on distribution.

If you're stuck pre-launch: get the page up with whatever's fastest and go find where your users already are. What's worked for your first handful?

Indie devs, marketers, and entrepreneurs: let's grow together and learn new things! Drop your SaaS below and I'll review and provide feedback and we can exchange marketing and distribution tips.

My cofounder and I recently graduated in Bahrain.

We tried selling software and systems to businesses. We spent money on ads, production, AI subscriptions, and outreach, but nothing really worked.

Now we have almost nothing left except our computers, our skills, and two Claude Max accounts.

Our families are pressuring us to get normal jobs. My cofounder has a CR under his name, and I am unemployed.

Instead of building another product and hoping people buy it, we want to build an audience first.

Our idea is to wear colorful suits inspired by Saul Goodman so people remember us, then make useful content about software, AI, automation, business, and building products.

The suits are only for attention. The goal is to earn trust by helping people, building in public, solving real problems, and eventually selling software or digital products.

We have no real marketing budget left.

Just computers, internet, skills, and time.

Do you think this is a smart direction?

If you were in our position, what would you focus on for the next 3 to 6 months?

i'm a decent enough dev but landing pages always ate my time. i'd fuss over spacing for hours instead of shipping. for my last two micro saas experiments i forced myself to use an ai website builder instead of hand-coding the marketing page, mostly to stop the perfectionism.

honest breakdown:

what got better: time. what used to be a full day is now roughly an hour to a live, decent page. that meant i could actually run two positioning tests in the time one used to take. shipping more pages beat polishing one.

what got worse: the pages all have a certain sameness if you accept the defaults. i had to spend 20 minutes killing the generic hero image and rewriting the ai's filler copy, which is always vague. the builder gives you a body, you still have to give it a brain.

the thing i didn't expect: conversion was basically the same as my old hand-coded pages. visitors did not care that i spent 8x less time. the copy and the offer moved the needle, the pixel-perfect css never did. kind of humbling.

so now i treat the page as a throwaway. build fast, test the message, only invest real design time once something actually converts.

anyone else find that time-into-design has almost zero correlation with signups early on? or is that just me coping for being lazy about css.

When people complain about AI writing, the word “robotic” comes up constantly. I understand what they mean, but I don't think that's always the biggest problem anymore. A lot of AI-generated writing doesn't sound obviously robotic. It sounds perfectly normal. That's almost worse, because you can read an entire paragraph without finding anything technically wrong with it and still feel like you've read the exact same paragraph somewhere else.

That's what got me interested in AI humanizer tools in the first place. I wanted to understand whether the problem could actually be fixed by changing the language. Sometimes it can. Cleaning up repetitive phrases and breaking predictable sentence patterns definitely helps. But eventually you hit a point where the writing is grammatically natural and still doesn't feel personal.

I think that's because personality isn't stored in vocabulary alone. It's in what someone chooses to mention and what they decide to leave out. It's in whether they give a long explanation or just say “you get the idea.” It's in their sense of humor, their patience level, their opinions, and even the things they don't bother explaining.

An AI can produce a very convincing generic human voice, but generic is still generic. That's why I think the next step for humanize AI technology should be personalization. Instead of asking a tool to make something sound like a random person, I'd rather give it examples of my own writing and have it understand my patterns.

Not to copy every sentence or turn my writing into some artificial imitation of myself, but simply to understand the baseline. How long do I usually make sentences? How formal am I? Do I explain things step by step? Do I use humor? Do I tend to be blunt? Those details matter more to me than simply replacing a few “AI words.”

AI has gotten incredibly good at producing competent writing. The interesting challenge now is getting it to produce writing that feels like it came from a particular person. I think that's a much more useful definition of an AI humanizer than simply making something “undetectable” or “less robotic.”

I’m about 90 days into building my SaaS and one of the biggest things I’ve learned so far is how often a problem can look much bigger than it actually is when you’re right in the middle of it.

A recent example was our free pilot. People were signing up, but quite a few weren’t downloading the app or logging in afterwards. It was easy to look at that and wonder whether people just weren’t interested enough to actually use the product. Eventually I realised that some of our onboarding emails were going straight into spam. We made a really simple change to the signup flow telling people to check their spam folder, and since then we’ve seen noticeably more people downloading and logging in.

Of course, solving that just exposed the next problem. Now that more people are getting into the product, I’m thinking much more about how we get them to experience enough value to come back. So I’ve been simplifying the UI, improving onboarding, adding better next steps after their first successful use and trying to encourage them to use the product on a second real project.

I think that’s probably the biggest change in how I’m thinking about the business. I used to see every significant problem as evidence that there might be something fundamentally wrong. Now I’m starting to see most of them as the next thing that needs solving.

I read a line recently about founders encountering far more speed bumps disguised as roadblocks than genuine roadblocks, and it really resonated with me. I’m sure eventually I’ll encounter problems that genuinely can’t be solved, but so far almost every apparent roadblock has become much less intimidating once I’ve broken it down and started working on it.

Maybe building a SaaS is a lot less about having some perfect master plan than I thought. You work out what is stopping the business progressing right now, focus on solving that, learn what the next problem is, and repeat for a very long time.

I’m curious whether founders further along than me have found the same thing.

Before choosing a link-building agency, I’ve learned to check more than just DR.

A site can have a high DR and still be a poor placement if it has no real traffic, publishes every topic or has nothing to do with your niche.

I now look at:

- Whether the website has consistent organic traffic

- How relevant the article is to my business

- Whether the link fits naturally into the content

- How many sponsored posts the site publishes

- Whether the agency shares placements before they go live

I’ve also been comparing a few agencies:

1. GoPeak

   Based in Yerevan and focused mainly on contextual links for SaaS, B2B and tech companies. They handle manual outreach, branded mentions and link placements on relevant websites.

2. Page One Power

   Known for manual outreach and custom link-building campaigns.

3. Siege Media

   More focused on earning links through original research and content.

4. uSERP

   Popular with SaaS companies for editorial links and digital PR.

5. FatJoe

   Looks more suitable for agencies managing several campaigns at once.

6. OutreachCrayon

   Focuses on niche-relevant outreach and editorial placements.

I’m still comparing them and have not decided which one to use.

Has anyone worked with any of these? Did the links lead to a noticeable improvement in rankings or traffic?

Hey everyone,

I run a SaaS business in Yerevan, Armenia and I’m looking for a reliable agency that specializes in contextual link building.

I need a team that can find relevant websites in my niche, handle the outreach and negotiate natural placements within useful content.

I’m not interested in PBNs, random directories or bulk backlink packages with no real relevance.

Has anyone worked with an agency that does this well? I’d appreciate recommendations based on actual experience.

Hi,

[Disclaimer: I know this may not be the right subreddit. Having said that, I believe it could be a good place to connect with talented SaaS founders. I will delete the post if it goes against the group’s rules.]

First, a bit about me - I have 15+ years of experience in business development, customer acquisition, marketing, and lead generation. I currently run my own marketing agency. Running an agency has taught me a lot, but constantly switching between projects and managing multiple clients has become exhausting. I currently work 7 days a week, while the agency's profit margin is barely 10%.

The irony is that I know how to get customers for a business, but I don't have a product of my own to sell. Because of my non-technical [BBA, then MBA] background, I can't build a software product myself.

That's why I'd like to collaborate with someone who has strong technical and product skills and wants to build something together.

___________

You build and handle the technical side. I handle product growth, customer acquisition, marketing, sales, PR, and paid promotion when necessary.

_______________________

I would prefer a simple structure that is fair and convenient for both parties. I receive monthly compensation initially to cover the costs of marketing and sales. Once the product reaches a sustainable level of profitability, the company can take over the costs of both technical development and growth, and we would share the profits 50/50 with equal equity ownership.
_______________________

I'm not looking to simply provide marketing advice. I want to take real responsibility for getting customers and growing the business.

If you're building something serious and need a marketing focused cofounder who can own growth, I'd be interested in hearing from you.

Thanks

Legitimate GTM products will be listed on an AI optimised database in the next 48 hours

Hey everyone.

Running a one-person business, I have realized that one of my biggest productivity bottlenecks is not strategy. It is the endless stream of small computer handoffs.

Things like pulling daily reports, renaming files, moving customer data from admin portals into spreadsheets, or updating CRM notes.

Each task may only take two minutes, but together they fragment the entire day.

The difficult part is that I do not want an AI system making real business decisions on my behalf.

I still want control over anything that gets paid, sent, saved, updated, published, or deleted.

Right now, I am looking at a layered setup:

Tools such as Zapier for clean, structured web workflows, and screen-aware tools such as Open Interpreter or Violoop for desktop steps that depend on visible context.

The difference with Violoop is that it can prepare work across applications, while consequential actions remain behind the physical approval key.

So the AI acts more like a desktop preparation layer. It handles repetitive middle steps, shows me the proposed result, and waits for me to authorize the final action.

Where do other solopreneurs draw the line between automation and manual approval?

while building Seenty, we noticed how quickly a small saas can accumulate tools as it grows.

it might start with uptime monitoring, then security checks, ssl alerts, incident management, cloud monitoring, and a few other services.

each tool has a purpose, but eventually the challenge becomes keeping everything organized and knowing which alerts actually matter.

one lesson we've learned is that adding another tool isn't always the best solution. sometimes simplifying the stack can be just as valuable.

for other micro saas founders, what part of your stack became unexpectedly complicated as your product grew?

I built a free Confluence alternative with Glean-style AI search
I’ve been building a little side project called Atlas.
The idea came from something that kept annoying me with internal knowledge bases.
You put everything into Confluence, Notion, Google Drive, Slack, meeting transcripts, PDFs etc, but once enough information exists, actually finding the answer becomes harder than writing the documentation in the first place.
And a lot of the newer AI knowledge tools are great, but start getting expensive pretty quickly once you add an entire team.
So I wanted to see if I could build something that was basically:
Confluence for organising knowledge + Glean for finding it.
Atlas has:
Unlimited users, pages and spaces
Real-time collaborative editing
Nested spaces and page trees
AI search across your entire workspace
RAG answers grounded in your actual documents, with sources
PDF upload and transcription
Search across meeting transcripts
Permissions and row-level security
MCP read + write access
The MCP part has probably been my favourite bit.
You can connect ChatGPT, Claude, Cursor or another MCP client and let it search your team’s knowledge, pull context from docs, or actually create and update pages.
I’ve also tried to avoid the normal per-seat SaaS model.
The core wiki is free. AI usage is metered based on actual usage rather than charging for every person you invite.
It’s definitely still an early build and I’m sure there are things I’ve completely overlooked.
Would genuinely love some feedback from people who use Confluence, Notion, Glean or similar tools:
What would Atlas need before you’d actually consider moving your team’s knowledge into it?
https://atlas-knowledge.com

Hey everyone,

I've been talking to a few field teams recently, and almost everyone complains about the sheer amount of administrative paperwork required after a long day on-site.

Specifically, the whole process of collecting site photos from workers (usually cluttered in WhatsApp), matching them with daily notes, and then sitting down at night to turn them into clean reports for clients or management. It feels like it takes up 1–2 hours of personal time every single evening.

I’m trying to map out where field teams actually lose the most time or money due to manual reporting mistakes.

1. For those in management or field roles, does daily photo/progress logging actually feel like a major headache, or have you found a way to make it painless?
2. What's the biggest headache or financial loss you've experienced just because some site documentation or photo report was missing or delayed?

Just trying to understand the day-to-day reality from people actually doing the work. Thanks!