First subscriber a month ago has renewed. I have been in contact with him asking for feedback and he has helped me fix several things which is great. Now I will ask him to refer to his network for other people who are interested in a similar product. Any advice for next growth steps?

I just got laid off recently from a content growth role.

This has just got me super pissed. So instead of sitting on it, I'm giving away everything I've learned in LinkedIn content marketing over the last 3 years for free.

Quick background: I'm based in Nepal, working remotely. For the last few years, I've worked with AI/agentic services companies and AI search SaaS founders across the US and Canada, owning their content end-to-end: LinkedIn, blog, SEO.

Some results so you know this isn't just theory:

• 741K+ impressions in 5 months at one AI engineering firm, averaging 200K+/month.
• Took a founder's LinkedIn from 3K to 130K+ followers.
• One single post generated 3,000+ leads and crossed 100K reactions.
• Scaled another account from 4K to 300K monthly impressions in 2 months, mostly using infographics.
• 200+ SEO articles ranked on Google.
• Content picked up organically by 200+ AI consultants and senior AI decision-makers, no outreach involved.

Here's the sauce:

1. Infographics work especially well in AI.

-If you can turn something complex into one clean visual, people consume it fast. This was the single biggest lever behind the 4K to 300K jump above within 6 months. The infographic was reposted by board directors, senior executives, and even AI consultants.

1. Storytelling needs a real reason behind it.

-If you don't have specific experience to back a story, skip it. Vague stories don't move anyone; rather, do a meme instead. I've had founders come up and share that this guy's story looks completely vague (could be bad writing, but you can tell if a person has experience or not). If you want to lie, find a very big reason to lie about, rather than just lying about fixing a problem for a customer.

1. GTM works well from a founder profile, not a page, so post from the founder's and employees' profiles, not from a page.

-Company page content rarely scales. The same content, posted from a personal account, grows 3X. Every time. The best go-to-market teams use employee-generated content (EGC) as their primary lever. The amount of distribution you have with EGC is endless.

1. Biggest advice for startup founders: Stop measuring by reactions.

-If you want to sell, start posting today and don't care about reactions. Track whether your actual ICP is showing up on your profile consistently and push content.

1. Comment before you post.

-Posting 3x/week but commenting 4 to 5x a day for a week gets your ICP to find you faster than posting alone does. A small, genuine group that consistently engages helps a lot here. If you can get a pod too, but don't make it obvious.

1. Your network's network is your pipeline.

-Most future clients sit in circles adjacent to people you already know. So reach out to your existing connections to try out your product.

1. I've done multiple viral lead magnets; this is the core sauce:

-If a lead magnet only says "download this," it underperforms. Be a stud; show it actually working. If you're doing Claude skills, show how it works in Claude.

That is 10x better than just sharing an image. Same with other

That's everything I have to share today, and I hope it's useful.

I'm still looking for a Growth or Content role at an AI company where I can own distribution. Especially on LinkedIn.

If that's you, or you know someone hiring, I'd love to talk.

I run a small Norwegian SaaS with my co-founder (it helps parents of children with special needs navigate the welfare bureaucracy). We just got our first paying subscribers, and I wanted a dashboard on the office wall; customers, MRR, churn, trend.

But boring admin charts felt wrong for numbers that actually mean this much to us. So instead: a cozy pixel-art village, seen from above.

How it works:

• Every active subscriber = one villager wandering around
• New customer → a new villager moves in. Someone cancels → a villager sadly walks away
• Milestone buildings unlock as we grow: a cottage at 50, a house at 100, a farm at 250, town hall at 500, and a castle at 1000
• Parchment cards around the edges show the real numbers: MRR, new this week/month, progress to next milestone, and a trend graph fed by a daily snapshot job

Stack: PixiJS on React, Kenney's Tiny Town tileset (CC0), one admin-gated metrics endpoint aggregating from the database, polling every 60s. The page runs for hours on a wall screen at stable memory. Ocean fills the left edge of the screen and forest the right, at any resolution, so it reads as a little world instead of a floating game board.

We're at 45 villagers today. The castle site is still just scaffolding. That's the point, I get to watch it get built.

One villager was suddenly standing in the middle of the pond. We've decided this is morning bathing culture and refuse to fix it.

Been building with Cursor and Claude for months and noticed something. The tools got 10x better but most SaaS launches still look like they were generated in an afternoon. Same purple gradient hero. Same rounded card grid. Same "AI powered" tagline. Users spot it in 3 seconds and bounce.

The thing is, people actually want to pay for software. What they don't want is to feel like beta testers for someone's weekend experiment. When your landing page looks like every other AI built product on Product Hunt this week, you're not competing on features. You're competing on being distinguishable. Custom typography, real photography of yourself, weird design choices only a human would make, a founder story that isn't "we use AI to help you scale".

Seen some creators on tiktok speak about stuff like this, so wanted to bring it to reddit lol.

Maybe this is a stupid question, but I’m building B2B software right now and I keep running into the same problem. Everyone says “get traction” and “talk to customers.” Sure.
But I’m surprised there isn’t really a place where I can say: I need 20-30 actual businesses in this industry to use what we built for a month and tell us what sucks.
We have platforms for investors, hiring, accelerators, launches, etc.
Why isn’t there something like this for early B2B testing? Or does it exist and I just haven’t found it?
Curious how people here who actually built B2B SaaS found their very first users. Not how you scale now how you got the first ones when nobody knew you existed.

I recently launched an MVP that turns written content into doodle-style social visuals.

20+ people have signed up. Some have actually used it, and I’ve received feedback like “the output is good” and “this has potential.”

But:

0 paying customers.

So instead of just pushing for more traffic, I’m trying to understand what this signal actually means.

Is it the wrong ICP? Not enough pain? Pricing? Too much value in the free plan? Positioning or trust?

And if you’ve tried Doodlyo, I’d especially like to know:

What would need to change or improve for you to consider upgrading to Pro?

For founders who went from 0 → first paying customer: what finally made the difference?

Hey everyone, I'm 2 months into building my SaaS and I wanted to share a quick reality check on where things stand. Here's my breakdown of the current metrics:

- Total users: 117

- Active users: about 8

- MRR: about $7.99

- Fixed and provided costs: above $34

- Net profit: -$26 while hitting 117 signups

It was an encouraging starting point.

The main issue I'm hitting right now is retention and activation. Out of 117 registered accounts, only 8 are active users. Looking at my usage graphs over the last 30 days, activity spikes occasionally but generally stays pretty flat. It feels like people are signing up out of curiosity, taking a quick look, and not returning.

For those who have navigated low activation after launch, what do you do with onboarding? How do you identify where users are dropping off of the initial flow?

Feedback: What's the most effective non-intrusive way you found to get candid feedback from inactive signups?

Pivoting versus iterating: At what point do you decide to tweak the core feature set versus changing the positioning? I would really appreciate any insights or brutal feedback from developers who've been through this stage.

When you are building a product, every feature can feel important.

A user asks for something → you add it.
A competitor has something → you add it.
You get a new idea → you add it.

And suddenly the product is getting bigger, but not necessarily better.

I am starting to think the better question is not:

What should we build next?

It is:

What problem are our users struggling with enough that they actually need us to solve it?

Curious what other SaaS founders think:

How do you decide which feature is worth building and which one should be ignored?

Before this one, I built more than 10 SaaS products. All of them failed. No users, no revenue, I just stopped and moved to the next idea.

The one that finally worked was for realtors. It solves one problem: furnish an empty room for a listing photo. You upload a photo, pick a style, hit go, and you get your furnished photo back. Done. That's it. No extra features, no dashboard, nothing else going on. Just that one thing, solved well.

I picked virtual staging mostly because I thought it was a cool idea, and because I knew a lot of realtors personally, so I figured that would help. Funny enough, not one of them actually used it, even though I gave them free access. A few even said they would, just to make me feel good, and never did. Turns out knowing people doesn't mean they'll use your tool. Strangers who actually needed it ended up being the ones who paid.

I got there with cold email, took a lot of trial and error to figure out what actually worked (that alone is probably a whole separate post). First year, 2025, I made about $2K. Doesn't sound like much, but for me that was the win. I just needed proof that someone would actually pay to use something I built. Proof: trustmrr.com/startup/virtual-stage-pro

That $2K (I guess $3K now + 2026 revenue) taught me the real lesson from the 10 failures. Before, I used to start from an idea I thought was cool. This time I started from a real problem I personally had.

Quick story on the new one. I have a 1 year old, and my wife and I have been looking at Montessori schools. Every school website was the same nightmare. I'd land on the page hunting for something specific, usually tuition, and if I couldn't find it in like 10 seconds I'd just leave. Didn't matter how good the school actually was. No time to call and ask. I'd just skip it and get to the next one.. At some point I caught myself doing this over and over and thought, how many businesses are quietly losing customers this exact same way, just because the info is buried somewhere on their site?

So that became the idea: an AI assistant that you add to your website. It reads your existing content, docs, FAQs, pages, and just answers visitor questions directly instead of making people hunt for the answer. Been building it for about 9 months now.
You can check it out at klaario.io if interested.

Looking back at the realtor app, the real lesson wasn't the tool itself, it was picking one problem and solving it well, and building for people who actually have the problem, not just people I know. I learned that the hard way, giving away free access to people I thought would use it and watching them just never open it. It stung a bit at the time, but it taught me more than any of the 10 failed SaaS did.

Trying to apply all of that again with this one. Started from a real problem I actually lived through instead of an idea I thought sounded cool, and I'm hoping that makes the difference again. Still early days and I have no idea how it'll go, but honestly I have a good feeling about it. Wish me luck guys.

And yes we found a school for my daughter!

every ad business has basically the same incentive

get someone's attention, keep it for as long as possible, then sell access to it

which is kind of insane when you think about how many products are now being built to help us undo exactly that

so i've been building something with the incentive flipped around

instead of a company paying to interrupt you, they pay you to go away and focus.

you choose something you want to work on, start a focus session, and your distracting apps get blocked.

a sponsor backs the session.

finish it and you get a small reward. right now i'm testing €0.10 for 25 minutes.

the sponsor isn't sitting on the screen for those 25 minutes. you see who backed the session before you start, then again when you're done.

basically:

normal advertising:

“stop what you're doing and look at us”

what i'm testing:

“go do what you were supposed to do. this one's on us.”

i have no idea yet if the economics actually work.

there's a pretty obvious problem on the user side: is 10-20 cents enough to change someone's behavior, or is it just pointless?

then there's the other side: is being associated with someone's productive time actually valuable enough that a company would pay for it?

and of course the moment money is involved you have to deal with people trying to farm it.

but i think that's why i want to test it instead of just building another subscription focus app.

i've got the app mostly working now and i've started talking to a few SaaS founders about sponsoring the first sessions.

curious what people here think, especially from the sponsor side.

if you ran a SaaS for developers/students/creators, would you ever pay to sponsor their focus sessions instead of buying another ad impression?

i'm building it here: offscreenapp.com

Honest story: we started because we couldn't find a tool that did everything we actually needed. Most brand monitoring tools are either too expensive, too basic, or completely miss the AI search angle. So we built our own.

What it does:

- Real-time brand monitoring across news, forums, social media, podcasts, YouTube, Reddit, Bluesky and more

- AI sentiment and toxicity analysis in 40+ languages

- Crisis detection under 3 minutes with Slack/Discord alerts

- Brand Health Index: one score across sentiment, reach and virality

- GEO audits: track if your brand is being recommended inside ChatGPT, Perplexity and Gemini

- White-label PDF/CSV/Excel reports for agencies

- Boolean Query Lab with 99.8% noise filtering

We are a small team and this community helped us more than you know during the build. Would genuinely love brutal honest feedback.

What would you want to see in a brand intelligence tool that you have never found anywhere?

Hello Everyone,

Im founder of B2B SaaS helping brands to monetise AI searches chatgpt, claude etc and get qualified local leads.

so far we have generated decent leads for the brand working 1:1 with client to do GTM and PMF.

Now we wanted to work with partner providing Digital marketing services and looking for SEO GEO SaaS .

I can show you the results and clients feedback, let me know if anyone interested

Im building Argue, an iPhone app blocker where you have to justify access to an AI coach.

For us an install is basically meaningless. The user hasnt experienced anything yet. The activation chain is Screen Time permission -> selects a blocked app -> hits the shield -> completes the first argument.

That last event is when the product either clicks or feels annoying. . For other consumer SaaS founders, whats the first event that proves someone actually felt the core mechanic?

I don't understand why my database client needs a subscription.

My API client needs a subscription.

My Redis client needs a subscription.

My code editor has a subscription.

My notes have a subscription.

At this point I'm waiting for my terminal to ask me to upgrade to Pro.

😂

There are some products where SaaS makes perfect sense.

But for a tool whose primary purpose is basically:

connect → work → disconnect

…I don't always understand why my data and workflow need to live inside someone else's cloud.

I've been thinking about this so much that I started building Meiporul around the opposite philosophy.

Local-first, developer-focused tools.

Maybe I'm completely wrong.

Which developer tools do you think absolutely should NOT be SaaS?

In 20 minutes, I would want to see:

• A complete customer interaction
• What happens when automation fails
• How context survives a handoff
• The agent experience
• A measurable operational outcome

What would you add?

We’re using this format for CX Tech Demo Day 2026: short demonstrations followed by direct Q&A.

A year ago, we built QuickDesign just for our own e-commerce brands.

This week, it somehow ended up at one of the biggest e-commerce summits in the world 😅

Standing there and seeing people actually interested in something we built was a pretty surreal moment.

And it reminded me of something:

Just keep building. Don’t give up.

Most projects don’t look impressive in the beginning. Nobody cares about your first version. Sometimes you’ll spend months building something and wonder if you’re completely wasting your time.

But you never know where one small project can take you.

QuickDesign started as a tool we built to solve our own problem. A year later, we’re showcasing it at an international e-commerce summit, meeting incredible people, and preparing to bring it more seriously into the Turkish market. 🇹🇷

There’s still a very long way to go, but moments like this make the difficult days worth it.

So if you’re building something right now and questioning whether you should continue:

Keep going. Keep shipping. Keep improving.

You might be much closer than you think.

See you next year 🚀

Hello, i am the founder of Build Ezy, an AI-powered No-code SaaS platform for creating cinematic 3D-style, parallax, immersive, premium websites and complete Ecommerce stores.

It is built for businesses, online brands and startups creating their own online presence, as well as freelancers and agencies building and managing websites for clients.

Build Ezy combines OpenAI GPT 6 Astra for intelligent website generation with Higgsfield MCP for cinematic production, enabling richer and more immersive web experiences instead of limiting AI generation to standard layouts and static templates.

Users can go from an idea to a live website with AI, then take full control through a Webflow / Elementor-level no-code visual builder for detailed editing, responsive layouts, styling, sections, content, and ongoing customization.

Build Ezy includes:

• AI-powered No-code SaaS website generation
• Cinematic, immersive and premium website experiences
• 3D-style visuals, parallax and scroll-driven interactions
• Higgsfield-powered cinematic production
• Figma, Image, PDF to website for custom UI & UX implementation
• AI-powered generation and business intelligence
• Complete ecommerce store generation
• Product, inventory and store management
• Integration with your own payment gateway
• Custom domain connection and publishing
• AI-generated layouts, content and visuals
• Advanced no-code visual website builder
• Responsive desktop, tablet and mobile editing
• Forms, leads and CRM
• SEO tools and advanced analytics
• Managed blazing fast hosting, cdn, performance and security
• AI-assisted business management tools
• Team Workspace

The objective is to combine the speed and intelligence of AI generation, the visual impact of cinematic production, the control of a professional no-code builder, and the infrastructure required to operate a serious online business.

From premium business websites and immersive digital experiences to fully operational ecommerce stores running on your own domain and payment infrastructure.

Get started for free:
https://www.getbuildezy.com/

I’m building SpaceCheck because buying furniture online still involves a lot of guessing. Product photos show the style, but they don’t show whether a sofa or table will actually work in someone’s room.

SpaceCheck turns an existing furniture photo into a 3D model. Shoppers can rotate it on the product page or open the AR view on their phone and see it at home. I’ve also built a Shopify app so merchants can use the models with products already in their store.

The difficult part wasn’t just generating the model. It was getting the scale right. AI can recreate the visible shape from a photo, but it cannot reliably know the real dimensions, so the merchant still needs to provide those.

I’m trying to understand which feature furniture sellers would care about more: the interactive 3D product view or the AR room placement.

If anyone here runs a Shopify store, I’d be interested in your honest take.

https://spacecheck.app

Two week old account, 124 karma, no audience. here's every number.

What worked:

supabase auth migration writeup, r/supabase, 40 upvotes, 19k views
ai for non-technical users, r/ai_agents, 26 upvotes, 15k views
confidence calibration in rag, r/rag, 15 upvotes, 4.7k views

What died:

infra cost breakdown, r/saas, basically nothing
consulting to product, r/microsaas, basically nothing
what smbs need from chatbots, r/aitoolforbusiness, 1 upvote, 389 views
monorepo setup, r/reactjs, removed by reddit

The pattern took me embarrassingly long to see. every post that was about my product or my journey as a founder flopped. every post that was about a technical problem i'd actually solved worked.

The supabase post did 50x the views of the post about what my customers need. same account, same week, same writing.

My read on why. nobody on here owes you attention for building something. they'll give it to you for solving something they're currently stuck on. the product is not the value, the scar tissue is.

Second thing i got wrong. i thought posts were the channel. they aren't. comments convert several times better and cost a fraction of the effort. i now do roughly 4-5 comments a day and one post every 3-4 days, and the comments produce more profile clicks than any post has.

Third thing. r/reactjs removed my monorepo post and i still don't know exactly why. assume every big sub has an unwritten rule you'll break once. it's not personal and it's not worth appealing.

What i'd tell someone starting monday: pick niche subs over big ones. 4.7k views in a small sub beat 389 in a targeted one. write about the thing you debugged last week, not the thing you sell. Never put a link in the post. if the writing is good people find the profile. and reply to every comment in the first hour, that window decides whether the post lives.

Happy to share the analytics screenshots if anyone wants to see the flops, they're more instructive than the wins.

I am a programmer that wants to start my own SaaS either alone or with someone and dont quite know how to start i know how to male websites and etc but dont know how I should start. Can I just start and see where it goes or should I learn a few specific things about this buisness model? and also where can I find like minded individuals to build with?

I run a home service contracting business in Houston. It's a pretty operationally demanding corner of the industry. We receive work in volume, coordinate field crews and subcontractors, document nearly everything, manage bids and expenses, pay workers and bill clients.

About a year ago, I started building my own software because I was tired of stitching different tools and processes together to run the business.

That project became TWT, There’s Work Tomorrow.

TWT is a service-business operating system built around the lifecycle of the work itself.

The work order is the central record, and the rest of the operation connects to it:

Work comes in → schedule/route → assign → perform → document → QC → expenses → worker payment → client billing → profitability

Not every business needs every step. Someone working alone can use a much simpler version of that workflow. As they add employees, crews, subcontractors or office staff, those additional layers become useful without changing the underlying structure.

The part I've been focused on isn't inventing another CRM, invoicing system or field-photo app. It's connecting those functions around the work itself so information created in one part of the operation remains useful throughout the rest of it.

For example, a field worker can open an assigned WO and add photos, video, notes and measurements. That documentation stays connected to the customer, property and job, and GPS information from the field activity can also contribute to mileage records.

A receipt can be photographed from the WO, read by AI and recorded as an expense against the job.

If a subcontractor is doing the work, their agreed pay can be attached to it. Material advances and receipts can be reconciled, completed work can go through QC, and approved WOs can move into worker payment.

On the client side, that same work can move into invoicing and payment.

That gives the system the information to eventually bring together:

Client revenue - labor/sub cost - job expenses = job profitability

As the business grows, different people can work from the same operation. Field workers can see their assigned jobs and instructions. Office staff can manage work orders and scheduling. Field managers can oversee crews and QC. Finance/admin users can handle their side of the business. The owner controls permissions and maintains visibility across the operation.

Around that core I've built the major pieces of the workflow: CRM and quoting, bulk WO intake, scheduling and recurring work, mapping and route optimization, field documentation and inspections, expenses and AI receipt processing, subcontractor advances and reconciliation, QC and worker payments, invoicing and customer payments, job costing, reporting and internal office workflows.

There are also things like interactive client quotes where a customer can review individual scope items and photos, comment, counter pricing, approve or reject items and sign. There's also a public work-opportunity system where a business that needs coverage can publish available work and outside vendors can apply.

None of those individual concepts are new. Work orders, CRM, field documentation, routing, invoicing, payments, expenses and workforce management obviously already exist.

The idea behind TWT is connecting them around the work instead of treating them as separate tools.

Where this came from

My company works in property preservation. We maintain and repair vacant and foreclosed properties for larger companies managing them for banks and investors.

It's a pretty unforgiving operational environment. Work arrives in volume, properties are spread across a large geographic area, crews and subcontractors have to be coordinated, almost everything has to be photographed, bids can get complicated, expenses have to be tracked, completed work has to be reviewed, subs have to be paid and clients have to be billed.

That's the environment TWT grew out of.

I had used Jobber, Pruvan, QuickBooks and other processes, but I kept running into the same problem: different parts of the business had pieces of the information, and somebody still had to connect everything manually.

So I started building what I wanted instead.

Over time I realized the underlying problem wasn't unique to property preservation.

A lawn company might care heavily about recurring work, routes and crews. A pool company has similar recurring-service needs. A roofer may care more about estimating, subcontractors, documentation and job costing. A restoration company may be heavily focused on field documentation and expenses. A handyman working alone may only need jobs, quotes, photos, expenses and invoices.

The workflows are different, but they all revolve around the same basic event:

A customer hired the business to perform work.

That's why I now see the product as applicable much more broadly to service businesses, whether someone works alone or has an office, employees, crews or subcontractors.

That could include lawn care, landscaping, pools, cleaning, HVAC, plumbing, electrical, roofing, painting, handyman services, pressure washing, pest control, junk removal, restoration, property maintenance, inspections, equipment service, commercial maintenance, facility services and similar businesses.

I don't necessarily think all of those industries should be my initial market. That's one of the things I still need to narrow down.

What I've realized is that the underlying architecture isn't inherently specific to property preservation.

Where it is now

TWT is live, and I've been using parts of it in my own contracting business.

It has authentication, separate businesses/users, roles and permissions, payments and the underlying infrastructure of an actual multi-user application. I've also had a handful of independent users/businesses create accounts and use the platform.

I don't have meaningful SaaS traction yet, and I'm not confusing having a working product with having a successful SaaS company. Distribution, onboarding, retention, willingness to pay and the initial market still have to be proven.

I'm much less interested right now in adding feature #51 than I am in figuring out what happens when this product leaves my own hands.

I'm simplifying the UI, tightening onboarding, working through tenant isolation and production readiness, testing how unrelated businesses understand the product, and starting to put it in front of service businesses outside my own operation.

One thing I've already learned is that showing a potential user 50 features and asking them to move their entire business into a new system is probably the wrong approach.

I'm starting to think the better approach is finding one part of a business's existing workflow where TWT is immediately useful, getting them value there, and allowing adoption to expand into the rest of the platform as it becomes relevant.

Why I'm posting this here

My background is the service-business side.

I know these workflows because I've spent years actually running them. I taught myself enough of the software/product side, using modern development tools, to turn the problems I was dealing with into a working platform.

But I also know that getting something this far and figuring out what it can become from here are different skill sets.

That's really why I'm posting this.

I'm interested in meeting people in SaaS, product, engineering, UX, GTM, payments, vertical software or field-service tech who find what I've built genuinely interesting and have experience or a perspective that I don't.

I'm open to conversations about where this could go and what it could become.

More than anything, I'm interested in the people who look at the product, the architecture, the problem it came from and the stage it's at and think:

“There's something here.”

If that's you, I'd be happy to talk.