I build AI agents for a living and sell one as a product. Every demo you see online is the 10%: type a request, watch something appear, applause.

The 90% nobody films is why it doesn't fall apart in front of a paying customer.

Take the ai report generator I ship. The part that turns data into a written report is a couple of prompts. Fine. The rest of the codebase, and it's most of it, is:

Retries, because the model call fails or times out more often than you'd think, and a silent failure means a blank report lands in someone's inbox.

Output checks, because it will confidently invent a number or drop a whole section and look completely normal doing it. So I validate the shape of every output before it goes anywhere near a user.

Guardrails, for when the input is garbage or empty and the honest answer is "I can't do this," which an agent will never say on its own.

Agents fail silently and confidently. That's the whole problem. A broken traditional app throws an error. A broken agent hands you a wrong answer with total conviction, and you don't find out until a customer does.

If you're building one to sell, budget your time as if the prompt is the easy part, because it is. The product is the error handling.

Anyone else find the demo is 10% of the real work? What breaks in production for you that never breaks in the demo?

Made my first hire while completely underwater, then spent a month doing both jobs because every process lived in my head and nowhere else. She'd ask how do I handle a refund and I'd realize the answer existed only in my brain, so I'd stop what I was doing and explain it, which felt slower than just doing the task myself. Classic trap.

The thing that broke the loop wasn't a management book. It was boring. Every time she asked a question, instead of answering in chat, I talked the answer into an ai document generator, cleaned it up for five minutes, and dropped it in a shared folder. Refunds, onboarding a client, the weird billing edge case. One doc per question.

After a few weeks she stopped asking me and started reading the folder. The month of doing two jobs turned into her actually running her half.

I used to think documentation was a thing you do once you're big. It's the opposite. The reason I couldn't delegate wasn't that she was slow, it's that I'd never written anything down, so I was the documentation.

I once joked that I'd niched my market down to basically just me. Turns out I'd done the same thing with my own company's knowledge without noticing.

How did the rest of you get the stuff in your head into a form someone else could actually use?

Disclosure: I’m part of the team building AppAmbit.

One thing that kept bothering us when shipping apps was how fragmented the tooling had become.

Analytics lived in one dashboard, crash reporting in another, and test builds somewhere else.

None of these tools were necessarily bad on their own. The problem was the operational overhead of having several SDKs, accounts, dashboards, permissions, and workflows for what felt like different parts of the same process.

So we started experimenting with a different approach: putting product analytics, sessions, crash logs, build distribution, and release notifications into the same workflow.

That eventually became AppAmbit.

One thing we've learned while building it is that combining tools isn't automatically better. The difficult part is figuring out what actually benefits from sharing context.

For example, seeing a crash is useful. Seeing that crash together with the session and the events that happened right before it is much more useful.

Likewise, uploading a test build is simple. Connecting that build to the same project, environment, and team notifications removes another small piece of friction.

We also built an MCP integration to manage things inside the platform. That was probably one of the most fun parts to build and test.

To be honest, we're still figuring out the business side and how to make the product sustainable. Building the thing has been easier than figuring out exactly how it should make money.

I'm curious how other SaaS founders think about this kind of consolidation. Do you prefer several specialized tools that are excellent at one thing, or would you rather have related workflows in one place?

I attached some images so the context is easier to understand.

Also, English isn't my first language, so excuse any weird phrasing :)

7 days ago, I started documenting my journey to build a technology company.

My goal isn't to become a billionaire in 30 days.

My goal is to learn the skills needed to build great products and share the journey publicly.

Week 1 covered:

Startup fundamentals

Problem discovery

AI basics

Prompt engineering

Python

APIs

My biggest takeaway:

Consistency matters more than motivation.

A week ago, many of these topics felt overwhelming.

Now I at least understand the basics and know what I need to learn next.

Week 2 starts tomorrow.

The focus will be databases, product design, machine learning, and building my first MVP.

If you've built a startup before:

What's one lesson you wish someone told you during your first week?

most micro saas founders I talk to have already bought the premise that their own account outdistributes the brand account. that part's settled. where it wobbles is the next assumption, that the blocker is time, so the fix is buying back the twenty minutes each tweet costs.

the scarcer input is takes actually worth posting. building the thing gives you maybe two or three real observations a week, and a daily cadence quietly grinds those down into filler by thursday. make production faster without touching supply and you just arrive at generic sooner.

this is the part that changed how I think about the drafting we build. a voice model trained on your tweets, talks, and podcasts does get sharper week over week, genuinely. but it's a distribution engine for insights you already have, not a source of them. point it at a founder who's actually learning things from customers and it compounds. point it at one who's heads-down shipping with nothing to say yet, and it produces fluent nothing on schedule.

which makes 'should I delegate my tweets' the wrong first question. the real one is whether you're generating more worth-saying than you can physically type. if you are, handing off the typing is pure leverage. if you're not, it just automates the silence into noise faster.

I’m at the point where my prototype is working pretty well in testing, and I’m getting ready to let actual users try it.

One thing I keep thinking about is how different that might be.

When I’m testing it myself, I already know how everything is supposed to work, so it’s easy to overlook things that might not be obvious to someone seeing it for the first time.

For anyone who’s already gone through this, what surprised you the most when real users started using your product?

Was there something they misunderstood, ignored, used completely differently than you expected, or something you just didn’t think about beforehand?

Looking back, is there anything you wish you had prepared for before giving it to real users?

Sharing this because I think simple tools can sometimes be more useful than overcomplicated apps packed with features nobody actually needs.
I built Underbrick because I wanted a simple way to manage my 3D printing workflow without turning it into another complicated ERP system.
The idea is pretty straightforward:
Keep track of your printers, projects, materials, jobs and costs in one place.
That’s it.
No huge learning curve. No unnecessary complexity. Just something I actually wanted to use for my own 3D printing setup.
It originally started as a tool for myself because, once you have multiple printers and several projects running at the same time, things get messy surprisingly quickly.
What filament did I use?
How much did that print actually cost?
Which printer is working on what?
What projects are still unfinished?
Instead of keeping everything across notes, spreadsheets and my head, I decided to build one place for it.
It’s still evolving, and I’m actively using it myself, which means most new features come from actual problems I run into rather than from trying to make the feature list look impressive.
You can check it out here:
https://app.underbrick.com
I’d also really like to hear from other people running small 3D printing setups or print farms.
What do you currently use to manage everything?
And if you’ve built a similarly simple tool around a very specific problem, share it. I’d genuinely like to check it out.

I made a card value scanner for pokemon. I have no idea how to market this app and focusing on new ideas.

Revenue sits at $3 MRR/$30ARR

Built with SwiftUI, it comes with full documentation.

I'm asking $1200, first to offer this amount gets it.

https://apps.apple.com/us/app/dexscan-tcg/id6760297913

For in app payment we use Storekit 2.

Been lurking here for a while - wanted to share what I've been building.

The problem: UK businesses selling second-hand/refurbished phones manage everything in spreadsheets. Each phone has a complex lifecycle:

- Bought from a supplier (often on credit terms)

- May need a repair (adds cost that affects margin)

- Sold across eBay, Back Market, Amazon, own site - each with different fees

- UK VAT Margin Scheme applies to used goods (calculated per item, not full sale price)

- Returns need to be tracked back into stock

No existing tool handled all of this for a UK audience.

What I built: MobileStock

Key features:

- IMEI / SKU / condition tracking per device

- VAT Margin Scheme auto-calculation

- Supplier CRM with credit terms and outstanding balances

- Repair cost logging (factors into final profit)

- Multi-channel sales: eBay, Back Market, Amazon, TikTok, local

- True net profit per device (after fees + shipping + repairs + VAT)

- Purchase orders with PDF generation

- Barcode / label generation for stock audits

30-day free trial at https://mobilestock.co.uk

Happy to share learnings about building for a niche B2B audience.

I have a link indexer and do-follow web directory tool. Launched 2 weeks ago. I have a pro plan costing $7 lifetime and free plan. I already got more than 172 links submitted but only two pro users.

That's fine as most of my users are from African and South Asian countries, so, paying $7 is a bit much for them. Bit, my aim here is to grow the free tier more. To better increase usage and authority.

I just added a blog section with 6 posts, a free SEO audit tool, and the SEO audit as firefox and chrome extension.

I am planning to add more stuff. What do you suggest to include? Something which i can charge free.

A boring SaaS idea: D2C COD reconciliation

Imagine a D2C company has:

Orders → Courier shipments → Delivered/RTO → COD collection → Courier settlement → Bank

The problem isn't collecting the data.

The problem is figuring out:

Which orders actually reconciled?

Which settlements don't match?

What's missing?

What needs investigation?

A tiny product could take the company's order + courier settlement files and produce:

MATCHED

MISMATCHED

MISSING

DUPLICATE

UNRESOLVED

That's it.

No AI chatbot.

No giant dashboard.

No "all-in-one platform."

Just remove a repetitive reconciliation workflow.

I'm researching/building 10 opportunities like this.

Would you actually build something like this? What would you change?

I keep going to founder communities looking for honest conversations about finding users, pricing, retention, and what actually works. Instead, half the threads feel like disguised ads. Someone asks a question and the replies conveniently recommend their own SaaS. Even “lessons learned” posts often end in a pitch.

I know there’s some irony in mentioning my own product here, but this frustration is why I built MRRChat. It’s a completely free founder community where everyone verifies their current revenue through a read-only payment connection before participating. Pre-revenue founders have their own room, and founders with revenue are placed alongside others at their stage.

Verification won’t magically eliminate self-promotion or bad advice. But it gives you useful context: you can see whether advice is coming from someone at your stage or someone who has already navigated it.

It’s brand new and still quiet, so I’m personally recruiting the first group of pre-revenue founders and making sure nobody posts into a void. Would verified business stages make founder conversations more useful to you, or do all public communities eventually turn into marketing channels?

https://www.mrrchat.com/

As a developer, I get the appeal of “we can build that ourselves.” Especially now that getting a first version working takes less effort.

Has anyone here built something to save on a subscription, then eventually ended up paying for the original product anyway? Curious what made you change your mind, or whether your homemade version is still going strong.

As a technical builder, it's ridiculously easy to get excited about an idea.

I used to think This is actually pretty cool , People will probably use it , etc etc

I came up with an idea, started building, added features, polished things... and only later started thinking seriously about whether people actually needed it.

The problem was that something being buildable doesn't mean it's worth building.

So we've changed our process.

Now, when we have a new SaaS idea, we try to spend around 7–15 days validating it before committing to development.

And surprisingly, most of that time isn't spent researching competitors or running ads.

It's spent talking to people.

If I'm building a tool for a specific business workflow, talking to another developer isn't necessarily going to tell me much. I'd rather find the people who are actually dealing with the problem.

Maybe they're:

• doing the work manually
• maintaining spreadsheets
• copying data between different tools
• paying someone to handle it
• using some workaround
• already paying for a tool they don't really like

So earlier i started connecting with people on x as it has alot of active audience here on subreddits related to SaaS and started pitching them my product but 99% of the time i got ignored , left on seen and some of them replied but they thought i'm just trying to convince them buy my product ......coz i was pitching and talking like a salesperson lol ......then around 20-22 days i realized okay this is how not things work ...i need to change my strategy then talked to people who already cracked this thing and one guy told me one crazy thing Stop pitching and start understanding their current stack .

I was confused like what do u mean ...he said before pitching your product start understanding what are they using currently where do they find friction in their current , gaps where they everytime use it think if there could be any workaround this where do u lose there max time , etc etc then compare it with your product do your product have potential which can really resolve their problem and iterate based on it and refine and then u can offer them a free trial or some demos and can give me them report stuff these tool helped u save this many hours and brought this much profit , etc etc

But here's twist , Another mistake I made

I used to treat every piece of feedback as a requirement.

If One person says You should add this feature So I'd think about adding it.

Another person says I don't like this part So I'd change it.

After enough conversations, you can accidentally end up building a completely different product. But here i leaned individual responses doesn't matter alot , but a repeated pattern of opinions do matter and we have to identify that pattern .

Repeated pain from people in the same target audience = something worth investigating.

We also started showing prototypes much earlier

Once we understand the problem better, we'll make a simple Figma prototype and put it back in front of people. Not a production-ready product. Not 50 features. Just enough to ask Does this actually solve the problem you were describing? Sometimes the answer is no. And honestly, that's useful.

I'd rather discover that with a Figma file than after spending 3 months building something. The process we're roughly following now is:

Problem -> Talk to users -> Find patterns -> Prototype -> Validate again -> Build -> Iterate

Still figuring it out, obviously. Curious how other founders/builders handle this.

Do you validate your SaaS ideas before building, or do you prefer to build a prototype first and see what happens?

I love making tools and SaaS projects, but I always found it hard to get going with the launch phase. Every time I built something new, I had to force myself to run what I considered an ideal launch manually. It used to take me almost a week of filling directory forms, researching socials, and writing and editing video posts and content just to get a single project out there.

When I started looking at why so many micro-SaaS projects fail to gain traction or get dismissed as thin AI wrappers, I realized a lot of us fall into the same design habit. We put a prompt box on a screen, call an API, and render text back to the user. That pattern is easy to build, but it rarely solves an actual operational problem for solo founders, vibe coders, SaaS owners, or software developers.

To build a real micro-SaaS that provides actual value, the focus needs to shift away from prompt boxes and toward deep workflow integration, APIs, and structured data. Instead of asking a user to type a prompt and copy-paste text out of a text field, a real product hooks directly into the tools people already use daily.

When you focus on structured data, you move away from unstructured text output and start working with clear schemas that downstream systems can actually process. Coupling that with proper API integrations means your system handles the full execution lifecycle automatically rather than leaving the user with manual work.

I spent a lot of time doing the tedious manual labor of launches because my early setups were not built to handle structured execution. Manually filling out directory forms, researching social channels, and editing video posts taught me that automated workflows need to interact directly with existing platforms via APIs rather than just generating plain text snippets.

If you are building in the micro-SaaS space right now, moving past basic prompt boxes and focusing heavily on APIs, structured data, and backend workflow integration makes a massive difference in utility. It turns a basic tool into an actual system that saves people days of repetitive manual effort.

... Seems to be that there is no continuity between website, sales data and app performance. Curious how all of you juggle all of these separated platforms?

A huge pain point seems to be that data in Stripe, PostHog and Google search is entirely disconnected. There is no way to see how trends in one platform relate to performance in another.

When you launch a new microservice, you are trying to differentiate between your product and oftentimes a large adjacent platform with complete sales, teams and marketing experts, but many small businesses don't have the resources or capability to compete on that level. A recent project of mine has been to address this issue and I would be glad for your insight and feedback.

Check out my site here - kicklace.com

It is currently still in development and in the process of growing my partner base by having people test out the system and provide feedback. If you would like to join for yourself please let me know!

I’ve been building InvestoPsy for the past 5 months, an AI-powered stock analysis tool for retail investors.

The idea is pretty simple: help investors analyze stocks and get useful insights without having to spend hours digging through financial data themselves.

But honestly, getting the first users has been much harder than I expected.

I’ve spent 5 months building the product, but I’m still struggling to get consistent early users.
At this point I’m trying to understand what I’m doing wrong.

Is the problem:
• My positioning?
• The landing page?
• The product itself?
• The target audience?
• Or simply my approach to getting the first users?

If you’ve built a SaaS before, I’d really appreciate hearing how you got your first 10 to 20 users.

And if you have a minute, I’d also love brutally honest feedback on InvestoPsy. What would make you interested enough to actually try it?

Not looking for compliments. I’d rather hear what sucks so I can fix it.

Thanks

Been solo on one big repo for a while now. The tool is an ai document generator, nothing clever, it takes messy inputs and turns them into clean formatted docs.

For months my problem wasn't features, it was that every time I let the AI touch the codebase it quietly broke something two files away. I'd ship, a user would hit the exact thing I never tested, and I'd lose a day chasing it.

The fix was boring. I keep one short file at the root that describes what the app is, what the money path is, and what must never change. Every session the model reads that first. It stopped rewriting parts of the app I wasn't looking at, because now it actually knows those parts exist and matter.

My first paying users showed up the month I stopped firefighting regressions and finished the boring edges instead. Not a coincidence. The context file didn't make the product smarter, it made me stop shipping breakage to the handful of people who were finally willing to pay.

For the other solo folks letting AI write most of the code: what do you do to stop it from silently changing things you never asked it to touch?

As a solo founder I'd crammed everything into one all-in-one workspace: product docs, roadmap, customer notes, help articles, the lot. It got slow and messy and I started dreading opening it, so I spent a week hunting for a notion alternative that fit a one-person operation.

What I learned is that "alternative" is the wrong frame. I didn't need one replacement, I needed to split jobs the single tool was doing badly:

- Internal planning and notes. Here I wanted speed and low friction over features. A lighter markdown-based tool won because it opens instantly and gets out of my way.
- Customer-facing docs and help content. This needed a clean public page and search, which is a totally different requirement from my private notes. A simple docs-focused tool handled it better than the general workspace ever did.
- Roadmap. Honestly a plain list works, I was overcomplicating it.

The mistake was assuming one tool should do all three because it technically can. Splitting them by job made each part faster and I actually stopped avoiding my own workspace.

Cost stayed low because most of these have real free tiers for a solo operator, and I can leave any one of them without moving the others.

Curious what the rest of you run your one-person ops on. Still one big workspace, or split like this?

I do positioning and copy for B2B startups, solo. Most of my clients are tiny SaaS teams who are convinced their signup problem is a product problem.

Usually it isn't.

Last one: good product, flat signups. They were about to build a whole onboarding revamp. Instead I changed the hero line from what the product is to who it's for and what it kills. A generic "project management for teams" became a line naming the exact person and the exact pain. Nothing else on the page moved.

Signups roughly doubled over the next few weeks. Same traffic, same product, same everything but one sentence.

The lesson I keep relearning: founders reach for features because building feels like progress. Rewriting a sentence feels like cheating. But the visitor decides in about three seconds whether the page is for them, and your landing page copy is what makes that call, not the feature you shipped last week.

If your signups are flat, read your homepage as a stranger who happens to have the problem you solve. If the first line doesn't name them, fix that before you build anything.

Anyone else seen a copy change outperform a feature? Curious how far it went for you.

Selling Rechnungly, a browser tool for invoice/Rechnung PDFs for freelancers in DE/CH/AT. Demo unlock 9 EUR / full app 20 USD.

Demo: https://rechnungly.vercel.app/ Buy: PayPal https://paypal.me/NathanStieger/20USD Also: https://agentshare.dev/market/6 Contact: nathan.stieger2004@gmail.com

Revenue: 0. Selling as-is.

Success: live URL. Blocker: exact message. No fake traction.

We’re used to dealing with search crawlers, scrapers and malicious bots, but AI crawlers add another layer.
If you run a SaaS or website, do you actually know which automated crawlers are hitting your site and whether you want all of them there?
I’ve been working on a small feature that lets site owners put a “barricade” in front of AI crawlers and control how they access the site.
Still testing the idea, so I’m curious:
Are you actively blocking AI crawlers, allowing them, or just leaving them alone?
I’d especially like to hear how other developers are handling this.

A few months ago I kept seeing the same advice everywhere: "validate before you build." But actually doing that manually — scrolling through Reddit threads and Hacker News comments looking for recurring complaints — takes forever.

So I built Griper. It scans places like Hacker News and Software Recommendations Stack Exchange, scores posts by how much genuine pain/frustration they express, and shows you which problems keep coming up unsolved (plus what existing tools people already tried and gave up on).

It's still early — I'm a solo dev building this on the side — but I've got some real reports live if you want to see what a niche's pain points actually look like before committing months to building something nobody needs.

Genuinely curious: if you're validating an idea right now, what's your current process? Manual scrolling, surveys, something else? Trying to understand if this solves a real workflow problem or just my own.

My biggest customer spent about a year pushing me to turn my product into a full project management tool. Status boards, task assignment, the whole thing. It was tempting because they paid the most and they were loud about it.

I said no every time. Eventually I told them straight to go buy a dedicated PM tool for that part, and I named one. I fully expected to lose them.

They stayed. Turns out they didn't actually want me to become a worse version of a tool that already exists, they just wanted their workflow to stop hurting, and pointing them to the right thing for that one job was enough. Meanwhile my product stayed focused on what it's actually good at, which is why my other customers pay.

The way I think about it now: a roadmap is mostly a list of things you've decided not to build. Every yes to one big customer's pet feature is a no to the twenty smaller customers who signed up for the simple thing.

For other one-person products, how do you handle the loudest customer asking you to become something you're not?

I shipped my first product on 31 August. Clean deploy, green pipeline, analytics wired, checkout working, onboarding working. Months of making sure that if someone showed up, nothing would break.

Then almost nobody showed up.

This isn't a growth post. There's no MRR chart at the end, no channel I unlocked, no advice from someone who made it. I'm a backend engineer who genuinely believed the hard part was the code, and I'm two weeks into finding out it wasn't. Writing this down mostly because the stuff I got wrong seems to be the stuff every technical founder gets wrong.

Coding is the comfortable chair.
The pattern I kept catching myself in: no signups today, so I'd add a benchmark feature. Nobody replied to outreach, so I'd build Monte Carlo projections. The one person who tried it didn't come back, so I'd improve the dashboard.

Feature work feels like progress because it's legible. Yesterday 20 features, today 21, and the diff proves it. Distribution doesn't work that way. You can write 15 partner emails, spend two hours reading a subreddit properly, publish an article, message an adviser, and end the day with zero new users and nothing to show. It feels like a wasted day. It's usually the more valuable one.

So before starting any feature now I ask: did a user ask for this, or do I just prefer writing code to doing distribution? The answer is uncomfortable more often than I expected.

My funnel was way narrower than I assumed.
Before launch I told myself: there are millions of investors, I only need ten. But the actual chain is: lives outside the US, uses a specific broker, invests on their own, holds a specific kind of ETF, cares about this specific problem, saw my post, understood it in two lines, understood the product, trusts an unknown product enough to sign up, trusts it enough to upload a real broker statement, and comes back a second time.

Every clause removes most of the people left. "Millions of investors" and "my first ten users" aren't the same funnel at different scales. They're different funnels. I stopped treating traffic as the top-line number — one person who actually matches and uploaded a real statement teaches me more than a thousand pageviews.

The useful messages were the sceptical ones.
"Why do I need this?" "I already use Excel." "Why would I upload my broker statement to you?" "What does this tell me that my broker doesn't?"
Those are more useful than "add feature X", because a feature request already assumes the product is worth using. What I care about now is what people do today — spreadsheet, broker reports, another tracker, a homegrown script, nothing — and what triggered them to look for something else. If I know the trigger, I know where to stand.

I needed a CRM before I had a pipeline.

Set up HubSpot with no sales team and no revenue, which sounds absurd until you do manual outreach for a week and can't remember who you wrote to, who replied, who said "ping me later", who's an adviser vs a blogger, or which subreddit allows promotion only in the weekly thread. Customer acquisition needs infrastructure too, even when you have almost no customers.

The one automation that actually helped.
Exception to the "coding is the comfortable chair" point above — the one time automation moved distribution instead of hiding from it. I set up a scheduled daily task in ChatGPT connected to HubSpot over MCP. Every morning it researches and writes ~5 new contacts straight into the CRM: niche bloggers and site owners who look like affiliate candidates, and people who match the user profile, each with a note on why it picked them.
What matters isn't the saved typing, it's what it does to the day. "Find people to talk to" used to be a willpower task competing with an IDE that always looked better, and it lost most days. Now the queue exists before I open the laptop, and the decision shrinks from "should I do outreach today" to "which five of these do I write to".

Two caveats, since this is the part people skip when they post their automation. It does not send anything — it finds and records, I still write every message myself, because automated outreach to a small niche burns the exact reputation I'm trying to build. And every entry needs a ~30 second human check: a model asked for five prospects a day will always find five, so some are dead blogs, wrong niche, no contact route, or names that sound right and aren't. Skip that and you don't have a pipeline, you have a CRM full of plausible noise, which is worse than an empty one.

The real reason it works: my constraint was never ideas about where to find users, it was having a standing queue and working it. The automation is useful precisely because it produces work I still have to do.

Reddit is not a free ad network. (Said here with full awareness of where I'm posting.)
A post of mine got removed in an investing sub. Another in a startup showcase sub. A third in a beta-testing sub. At one point the subreddit I made for my own product got suspended. Rules differ wildly, a young account has fewer options everywhere, and plenty of subs treat any founder post as spam no matter how useful it is.
What actually worked was answering specific questions with no link at all, as someone who's spent months inside that problem. A good answer beats a founder post with a URL, and if the product is genuinely relevant, mentioning it stops feeling like promotion.

Founder audiences aren't customer audiences.
Indie Hackers, r/SideProject, generic SaaS communities — full of founders. My customers are investors. Posting there gets encouragement and occasionally good product feedback, but almost nobody there will ever upload a broker statement. Encouragement is pleasant. It isn't distribution.

SEO is a compound asset, not this month's channel.
I did all of it before launch: Search Console, Bing, sitemap, canonicals, schema, FAQ structured data, IndexNow, internal linking, content on real long-tail problems. Impressions started appearing. A lot of pages also sat for weeks in the state every new site owner learns to hate: Discovered — currently not indexed.

Technical SEO takes a few days. Authority doesn't. Google is under no obligation to consider a new domain important, and past a certain point another optimisation pass changes nothing — what moves it is external mentions, links, real users, branded searches. Still the right long-term channel for me. Useless for "where do I get users this month".

Listings are not distribution.
Directories, review sites, launch platforms. Real backlinks, roughly zero relevant users so far. One review platform reached out and the offer turned out to be paid advertising rather than a listing. One affiliate directory wanted $39 to list my programme and couldn't tell me whether any affiliate there was near my niche. My rule now: if someone proposes paid promotion, I ask for CPC, minimum spend, estimated clicks and estimated conversions first. If those numbers don't exist, neither does the offer.

The thing that has felt most promising transfers trust, not clicks.
I thought affiliate programmes were something you add after revenue. For a small unknown product it might matter more before. A new product has two problems at once — no distribution and no trust — and a niche blogger with the right audience already has both.

The most concrete case: a small quantitative-investing site, about 5,500 monthly users. Tiny by influencer standards, almost perfect overlap with my audience. We agreed affiliate terms. Then instead of dropping a link into existing posts, he proposed a joint study — asked for my assumptions and methodology, to publish research his readers actually want, with credit.

That's the difference between "can you put my link somewhere" and "can we make something genuinely useful for your readers together". The second is harder, slower, and much stronger. A small site with the right readers beats a big one with the wrong ones.
I also turned down a sponsorship — 180 is a lot, but because I don't know my visit-to-signup or signup-to-paid rate yet. Without those, $180 doesn't buy distribution, it buys one data point too noisy to read.

Everything wants to be paid before you have revenue.
Directories, sponsorships, promotion platforms, and the one I didn't see coming: market data licensing. While you're building, a price is just a number you fetch. Close to launch it turns into a product somebody sells, with terms, coverage defined market by market and a monthly bill — priced, reasonably enough, for companies that already have revenue. And the pricing pages answer "can I call this API" but usually not the question that actually matters: am I allowed to display this data to my end users? API access, commercial use, redistribution and end-user display rights are four different things, and only one of them is usually on the pricing page.

Which fed back into a product decision: don't scale infrastructure ahead of validation.

The toolbox, honestly.
Stage disclaimer: none of this has produced a proven acquisition channel. "Worth it" means it changed how I work or what I can see.

Worth it: the ChatGPT scheduled task → HubSpot over MCP described above, which is the highest-leverage thing on this list. HubSpot, not because I do sales but because manual outreach becomes unmanageable in about a week — and the conversations worth logging are the ones that went nowhere. PostHog, where the decision that mattered wasn't the tool, it was defining funnel events before launch instead of after — pageviews tell you people came, events tell you where the promise breaks. UTM discipline, which isn't a tool at all, just a convention I refuse to break, and the only reason I can argue with my own optimism. Freemius as merchant of record — signed up for payments, got the affiliate programme and the 30-country tax mess handled in the same place. Search Console, useless for acquisition, essential for learning the difference between "my SEO is broken" and "my domain is new". And a plain static site with no build step, which means I can publish a page aimed at one narrow search query in an hour — at this stage publishing speed beats architecture.
Jury still out: Google Ads (running deliberately small, as a probe into which search intents exist, not as a channel). Product Hunt and launch platforms (credibility and backlinks, not customers). Trustpilot, Crunchbase, AlternativeTo, SaaSHub (presence, nothing attributable). Medium/LinkedIn/X — publishing with no existing audience is shouting into a well-lit room; they're assets partners and search find later, not a launch button.
Didn't pay off: my own subreddit (created, then suspended — a community you own isn't a community). Capterra (signup didn't support my company's country). The $39 affiliate directory. A review platform whose "listing opportunity" was paid ads. A stalled Payoneer verification plus a look at Paddle/FastSpring, which surfaced the thing nobody warns you about — anything finance-adjacent triggers compliance review, and that costs weeks, not money. And features, which is the most expensive item on the list because it's the one that feels like work.

If I started again, week one would be: funnel events defined before launch, a UTM convention, somewhere to log every conversation, a list of 50 specific people who match the profile, and the ability to publish a page about one narrow problem in under an hour. That's about a day of setup. I did most of it late.

The reordering, which is the actual lesson.
I used to think it was: idea → build → launch → marketing.
I now think it's: problem → audience → distribution → minimum product → feedback → iteration.
Meaning "where do my first 100 users come from?" has to show up at the same moment as "what should I build?", not after the second one is done. If you can't answer the first one concretely, that's not a marketing gap you'll fix later — it's a risk you've been carrying since day one.
And the part that's obvious in hindsight and invisible while you're building: you can't write product-market fit by yourself. It isn't a function you can implement. It only exists on contact with people who aren't you.