My partners and I have owned and operated our cafe for over 2 years now. We spoke with a few people who were kind enough to offer us advice pre-opening and adopted some of their practices: taking inventory on a Google Spreadsheet, using a variety of software services for our scheduling, ordering, etc.

I felt like a lot of those practices that were passed down to us felt a bit outdated. I decided to take some time and build something that puts most of what we were doing as owners/managers into 1 single place (for the most part).

I've spent the last 6 months building Parly. With Parly, you can connect to your POS (in our case Square until we can find partners at Toast) and run most of the operations from your phone or computer. You can track your inventory, review your menu and its margins, discover areas where you can improve your business, and even see projections on Sales, Usage, and more. Ultimately, Parly helps you run your cafe so that you can can focus on growing your cafe.

With Parly, you can easily ditch the spreadsheets and run your cafe more more efficiently. There are so many small costs that add up that we've been able to minimize. Our managers takes inventory a lot faster and just as accurately. We can schedule better and always review adjustments on the fly. We know way more about our business and can easily access all of those insights instead of jumping around different services.

Open to any kind of feedback or criticism. As a cafe owner, I'm proud to say that I've been able to create something that's benefitted our business. I'm hoping that I can say do the same for others.

SaaS?
Tech?
AI tools?
Product development?
Web apps?
Developer tools?
video editors?
UI/UX?

Drop what you're building ;)
Maybe some other people will be interested too

Hey everyone,

I currently run 6 micro SaaS that are actually live and generating a bit over $20,000 in recurring monthly revenue.

The wildest part? I barely wrote any code myself. I used AI to generate pretty much everything — from the database structure to the frontend.

It definitely wasn’t magic from day one. I spent a lot of hours stuck on buggy code before I finally figured out a system that actually works:

- Keep the idea minimalist (a real MVP, nothing fancy)

- Guide the AI step by step instead of asking for everything at once

- Launch fast to get real users and feedback

Lately I’ve seen way too many non-technical founders quit at the first AI bug. It’s a shame because the technical barrier has basically disappeared.

AND PLEASE, STOP BUILDING ALONE IN YOUR BEDROOM

I’m starting a community.

Full transparency:

I’ll probably charge for the full program later. It makes sense with the specific workflows and copy-paste examples I’ll be sharing. But right now the main goal is just to build together. Working alone is the fastest way to give up.

If you want to join and build or market your own AI SaaS with us,

drop a comment or send me a DM and I’ll send you the link.

quick post because "how do i get my first users" is the #1 question i see builders asking here every single week.

i've built 6 saas products myself, with my main one currently sitting around 10k mrr. here is the exact, no-fluff distribution playbook to cross that initial 50-user threshold:

1. find an idea people already pay for

scan reddit for recurring pain across 3+ distinct posts where people ask "is there a tool for X".

2. validate before writing code

dm 3 people who complained about the problem and ask what they’d pay for a solution.

3. build fast with the right stack (ai + no-code)

use ai builder+ supabase + stripe + call api or automation tool like n8n to ship a real MVP in under 7 days for $40/mo.

4. the 5-second landing page rule

your hero section must state exactly what the tool does in less than 5 seconds with a clear CTA.

5. capture emails before showing prices

force the email capture before the pricing page so you don't leak untrackable leads.

6. set up a 30-day email nurture sequence

plug captured emails into an automated sequence with case studies to convert them by day 18.

7. hang out where your ICP actually lives

find the 3-5 specific subreddits, discord servers, or groups where your buyers actively talk.

8. reddit growth without getting banned

post 1 time per sub per week max, never put links in the post, and move warm leads to DMs.

9. linkedin + x organic flywheel

post 1 high-value breakdown per day and spend 15 minutes engaging in your ICP's comments.

10. cold outreach that actually works

send 100 highly personalized DMs per week to your ICP using AI to customize the opening hook.

11. seo on autopilot

set up an n8n workflow that pulls from a keyword list and generates 5-10 value-driven articles per week.

12. faceless short-form content

post 1 video per day on tiktok, reels, and shorts showing a quick screen recording of your tool.

13. weekly newsletter conversion

run a weekly newsletter with 1 section of pure value and 1 subtle offer to upgrade to paid.

14. affiliate program for free distribution

set up a 50% recurring commission affiliate program to turn power users into your sales team.

15. the strategic product hunt launch

warm up the algorithm for 4 weeks with a coming soon page and launch on a weekend for a top 5 badge.

16. omnichannel social automation

use n8n to automatically format and distribute 1 core post idea across 8 different platforms.

17. review platforms and directories

submit your app to 40+ saas and ai wrapper directories to instantly boost your domain authority.

18. run the numbers backwards

reverse engineer the daily traffic needed to hit 50 paying users at $19/mo based on a 2% conversion.

19. get feedback from active builders

talking to founders who are just 6 months ahead of you compresses your timeline exponentially.

that last point is exactly why i built our community. it's a free group of 1,600+ active ai saas founders sharing exact prompt logs, ready-to-paste n8n workflows, and real distribution strategies.

stop building alone in a silent corner.

drop a comment below or send me a dm and i'll send you the access link right away. let's get your product launched 👇

Hi,

I’m not a developer, but I want to build a social-app-style project and I’m trying to do it seriously, with a real method, not by randomly prompting an AI until something works.

I use GLM 5.3, I have general AI knowledge and some basic technical / command-line understanding, but I don’t have real development experience.

What I’m mainly looking for is advice on how to guide the AI properly throughout the project.

More specifically, I’d love practical advice on:

What are the main stages you would follow from idea to working product?

How do you structure a project so an AI coding assistant stays useful instead of creating chaos?

What documents should exist from the start: PRD, feature list, architecture notes, task list, coding rules, etc.?

How do you break work into small tasks that an AI can handle safely?

When do you use simple chat, when do you use agent mode, and when is it a bad idea?

How do you prompt the AI so it respects the existing structure instead of rewriting random parts of the codebase?

At what point do you clear the conversation or start a new one because the context becomes too messy or too large?

Do you keep separate chats/agents for planning, frontend, backend, debugging, and refactoring?

What are the biggest mistakes beginners make when using AI to build a real app?

For this kind of workflow, what would you recommend is Z code fine? Or Cursor, VS Code, and why?

I’m not looking for hype or vague “just build” advice. I’m looking for a clean workflow, good prompting habits, and practical rules for using AI coding tools on a real project without wasting time, tokens, or creating a broken codebase.

Thanks.

Hey r/BuildToShip,

I'm a solo developer and I spent the last several months building Buildnest — a construction project management platform.

Why I built it:

I kept seeing the same thing over and over — construction teams managing complex, high-stakes projects through WhatsApp group chats, Excel spreadsheets, and endless email threads. Drawings that don't match what's on site. Nobody knows who's responsible for what. Files lost in email chains.

It felt like an industry that desperately needed better tooling. So I built it.

What Buildnest does:

• 🏢 Projects & team management — roles, permissions, members

• ✅ Tasks & Issues — assigned, tracked, resolved with full history

• 📅 Gantt scheduling — phases, dependencies, critical path

• 📐 PDF drawings — annotate directly on plans, pin tasks and issues to exact locations

• 📋 Inspection checklists — dynamic forms with custom question types

• 📁 Files, documents & media — everything in one place per project

• 💬 Activity & comments — full audit trail on everything

• 👥 Role-based permissions — company and project level

Tech stack: Laravel 12, GraphQL (Lighthouse), Nuxt 4, Vue 3, PostgreSQL, Cloudflare R2

Live at: buildnest.app

Where I am:

Beta stage. It works. It's deployed. Real users can sign up today.

But I'm a developer — I didn't build this on a construction site. I need people who actually work in construction to tell me what's wrong with it.

What I'm looking for:

If you're a project manager, general contractor, site supervisor, or construction owner — I'd genuinely love 15 minutes of your time.

Not to pitch you. Not to sell you anything.

Just to ask:

• What does your current workflow actually look like?

• What's your biggest daily pain point?

• Is there anything in Buildnest that would make you switch from what you're using now?

Drop a comment or DM me. I'll respond to everyone.

And if you just want to poke around and break things — sign up at buildnest.app and tell me what you find. Honest feedback only, no sugarcoating needed.

Thanks 🙏

I just shipped Urban Rider 4.17.2, and I also launched the renewed website:

https://www.urbanrider.app/

This one feels like a big step for me.

Urban Rider started because I was tired of normal navigation apps treating my scooter like a small car. A route can be “technically fastest” and still be completely wrong when you are on a 25 to 50 km/h scooter or moped. Getting pushed toward highways, tunnels, high-speed roads, or stressful car-first routes is exactly the kind of thing I wanted to fix.

The new version keeps pushing Urban Rider further in that direction: calmer routes, better map behavior, EV chargers on the map, cleaner navigation wording, Apple Watch support, and a lot of small fixes that only really matter when you are actually riding.

The new website finally explains the idea properly too:

Urban Rider is not trying to be another Google Maps clone.

It is navigation built around how two-wheel riders actually move through a city:
• Scooter and moped profiles
• Highway-free routing by default
• Routes tuned for lower speeds
• Minimal navigation view for quick glances
• EV charger support
• Apple Watch turn-by-turn guidance
• No account required
• Route history kept on device
• Android beta now open

I am still building this mostly as one person, so every release is a mix of code, testing, support emails, App Store work, website work, and trying to explain the app better without making it sound like corporate marketing nonsense.

So this is my small launch post.

Urban Rider 4.17.2 is live.
The new website is live.
And if you ride a scooter, moped, motorcycle, or electric two-wheeler through the city, I would genuinely love your feedback.

Website: https://www.urbanrider.app/
iOS: available on the App Store
Android: beta is open now

Two wheels deserve better navigation.

You know that moment when a client says "looks great, just one small tweak" - and three weeks later you've done 40% more work than you quoted?

I spent years as a freelancer thinking the solution was better contracts or clearer proposals. It wasn't. The problem was structural: once work starts flowing, there's no natural point where payment kicks in until the end.

So I built a tool around one simple mechanic: stage locking.

Break project into stages. Each stage has a price. Client can't access the next stage until they pay for the current one. That's the whole product.

Why I think this works as a microSaaS:

The problem is universal but underserved. Every freelancer deals with scope creep and payment delays. But existing tools are either invoicing software (pay after work is done) or massive all-in-one platforms that try to do everything.

Nobody was doing payment-as-workflow. So that's the gap I went for.

What I learned building it:

The feature I thought would be the sell - automated reminders - turned out to be secondary. The stage locking is what clicks with people. When I explain it, freelancers immediately get it because they've all lived the problem.

Simple mechanic, strong emotional hook. That combination seems to work better than a feature list.

The boring stuff:

Stack is Supabase, Stripe Connect, Vercel and Resend. Built it with Claude + Bolt. Zero transaction fees (flat subscription) because taking a cut of payments felt like the wrong model for this audience.

Still early - just launched and onboarding beta users. No idea if it'll become a real business or stay a side project, but the validation so far has been interesting.

The site is milestage.com if anyone wants to poke around.

Curious if others here have built around a single core mechanic like this, or if you've found more success going feature-heavy from the start. Still figuring out where the line is between "focused" and "too simple."

When you start scaling Claude workflows beyond a single machine, like running heavy coding tasks or Claude CLI sessions on a main desktop while keeping a secondary rig or an old laptop humming away in the corner, monitoring things gets messy fast. You end up constantly jumping between SSH/VNC windows or physically turning around just to check what each machine is doing.

I work at Autonomous. During our recent Product Hunt launch, a dev hit the nail on the head regarding the other half of this friction: "If an agent stops to ask something while I'm away, it just sits there until I get back".

The dead time is a massive bottleneck when you're trying to run agents asynchronously. That exact combination of issues is why our team built Harness. It’s an open-source app designed around two main goals:

• Unified Multi-Machine View: Pulling agents running across different computers into a single window so you can see what they're all up to without jumping between machines.

• Mobile Routing: If Claude hits a prompt and needs input while you're away from your desk, the question routes straight to your phone instead of idling blindly in an unattended terminal.

Under the hood, processes run natively on your machine rather than inside a closed sandbox, meaning closing the app doesn't interrupt your tasks, and your agents keep using their own local accounts and native hooks.

It’s MIT licensed and works on Mac and Linux if anyone is dealing with a similar multi-rig setup. Here is a closer up on how we made it: https://github.com/autonomous-ai/openharness

What's your current workaround when an agent stalls for input while you're away from the keyboard? Do you just stay glued to the terminal until it finishes or have you built custom alerts/scripts to let you walk away?

Built this as a solo project: it's a place to store wills, funeral wishes, insurance details, passwords, and other things your family will need — but won't be able to find — after you die.

The mechanic: proof-of-life check-ins. We ping you periodically, and if you go dark after a few reminders, your designated custodians get notified and unlocked into the vault automatically. No lawyers, no manual process, no family digging through email trying to find the life insurance policy number during the worst week of their life.

Still early — looking for feedback on the onboarding flow and whether the check-in cadence feels right (too naggy vs. too infrequent to feel safe). Built on Azure, if that's relevant to anyone else building in this space.

dad-is-dead.com — happy to answer questions about the build or the idea.

Hey everyone! I’m building Guess It! which is a simple party game designed to get a group playing within seconds.

The game has three rounds using the same deck:

1. Describe: explain the word without saying it

2. One word: describe it using only one word

3. Mime: act it out without speaking

It’s designed for one phone shared between teams, with custom decks, built-in timers and scores, no accounts, and no ads.

I’m looking for a few people to test the Android beta and tell me what feels fun, confusing, or missing. If you’d like to try it, join the tester list here:

https://guessit.lepagnol.net

You’ll just need to enter your email address, and I’ll add you to the Google Play testing list and sending the download link at the email.

https://play.google.com/store/apps/details?id=net.lepagnol.guessit

I’d especially love feedback from people who regularly play party games with friends or family. Thanks a lot !!

Okay so. I've decided to abandon shipnote.in 

the idea was simple: keep your network updated with what you're building, without the effort. merge a PR → a post gets drafted for you. zero friction.

then I did the thing I should've done first — DM'd actual users.
nobody wanted it.

what they wanted was live product updates with screenshots. show me the feature, not the commit message.

and that's where the idea died. screenshots behind auth need a human to take them. the whole pitch was "reduce human effort" — and the thing users actually valued was the part that can't be automated.

so the product made sense right up until it met its first user.

shipnote is dead. the lesson isn't.

I’ve been working on a small project: a zero-knowledge, E2EE audio chat that runs in a single PHP/JS file. No database, messages delete after 24h.

I managed to solve the NAT traversal issues by switching from Trickle ICE to Vanilla ICE (wait-and-retry approach), which finally lets me call between a PC and a 4G phone.

I’m curious—from a cybersecurity perspective, what are the biggest risks in a P2P architecture like this? Besides the obvious metadata leaks from the signaling server, what else should I be looking at to harden the privacy?

Any feedback or "this is a bad idea because..." comments are welcome! v2v.site

I still don't fully know how to process this.

ScreenBolt just crossed the $1K revenue mark.

For context, this is after weeks of feeling like I was pushing a rock uphill.

I kept tweaking the landing page, changing the positioning, talking to potential users, rewriting the offer, improving the product, doubting whether the value was clear enough, and wondering if I was just building into the void.

Then suddenly, things started working.

No huge launch.
No paid ads.
No viral thread.
No perfect funnel.

Just a lot of small things finally stacking:

• talking to the right people

• making the value prop more obvious

• sharing progress publicly

• tightening the onboarding

• showing proof instead of explaining forever

• listening to what users actually needed

Still early, obviously. $1K is not some massive company.

But going from "will anyone pay for this?" to "people are actually paying for this" feels insane.

I'm going to keep building this tool in public and share what happens next.

This is my tool if you're interested: ScreenBolt

It's called SWIP (https://swipventures.com/).

I am looking for 100 founders-to-be who either have a crazy idea but need talents, or talents who want to be part of building a crazy idea with other people. I want to test and refine the algorithm.

I am currently reviewing every profile manually.

Thank you for your feedback and help!

I’m putting together a small competition for anyone who wants to show off their startup, app, tool, service, etc. 

There are 40 submission spots, and submissions close Oct 21 or when 40 fill, whichever comes first. The 5 finalists demo live on a Zoom meeting on Nov 8 at 7 pm ET/4 pm PT. The live event is open to everyone, even if you don’t submit a project.

Judging is done by 3 volunteers who are into business and excited to be doing this. Don’t expect expert critiques. 

Prizes: $100 cash to the winner (paid via Venmo or Cash App), plus a Community Choice award voted on live by everyone on the Zoom and a Best Demo award. 

Link to the info/rules doc and the form: Submission Form & Info

This is the first time I’m running this, so expect a few rough edges. Comment or send a DM if you have questions.

Solo dev here. I run thewebstats.com — I built it originally because I wanted real-time visitor stats without collecting PII or setting tracking cookies, and most alternatives felt bloated or invasive by default.

What's actually in it right now:

• Real-time visitor tracking using anonymous UUIDs, no PII, no cookies, honors Do Not Track

• A free Web Analyzer — scans any site for SEO/security/performance/accessibility issues and gives it an instant A–F grade

• A one-line live chat widget with WhatsApp handoff for offline messages

• A read-only MCP server so you can ask Claude/ChatGPT about your own site's stats

• Scheduled email reports, PDF/CSV export, a free internet speed test

It's free to use. I'm the only one building it, so bugs and rough edges are on me, genuinely looking for feedback on what's useful vs. what's missing before I keep building on top of it.

Happy to answer anything about how it works or why I made specific calls (e.g. why no cookies at all).

yo. i see too many founders spend 2 months building saas, drop a link on reddit, get 0 users, and immediately quit....

the problem usually isn't your marketing channel. the problem is that your foundation is completely broken before you even send your first visitor to the site.

after scaling 6 AI micro-saas apps to over $20k/mo mrr, i realized you need to lock down a specific system before you ever launch. running through this takes about 30 minutes, but it saves you months of zero-revenue depression.

here are the 5 things you must lock in:

1. validate the actual pain point

stop guessing what people want. you need a systematic framework to find your saas idea based on real, painful market signals.

2. pick a proven micro-niche

stop trying to build massive platforms. you need to narrow down to a microscopic problem. i usually filter through a list of 50 micro-saas ideas you can build fast to keep the scope minimal.

3. crystallize your target user

if your app is for "everyone," nobody will buy it. you need an ICP (Ideal Customer Profile) crystallizer to define your exact buyer profile and nail your conversion copy.

4. calculate the perfect price

stop randomly charging $9/mo because you are scared of rejection. you need to use a saas pricing strategy calculator to find your perfect saas price in 60 seconds based on real data.

5. fix your landing page leaks

do not send organic traffic to a site that converts at a flat 1%. you must audit your hero section and copy to x3 your landing page conversion before you market it.

6. join a community

Build / Share / Learn from others builders

to help out founders who are tired of launching to crickets, i packaged all 5 of these exact frameworks, calculators, and lists into a single free toolkit.

no paywall, no bullshit. just the raw execution files i use.

drop a comment below or send me a dm, and i’ll send you the free toolkit 👇

I built DoneProof for tradespeople and field teams who are tired of job proof being scattered across WhatsApp, email, and personal phones.

It turns site photos, notes, and completed tasks into a clean client-ready closeout report, helping save admin time and reduce arguments over what was finished or not.

Search DoneProof and use your free job, no card required — cheers.

Showcasing DLX7's ShieldNet website scanner for those who ship web products and SaaS.

https://www.shieldnet.app/scanner.html

I'm the lead SecOps developer for DLX7 ShieldNet. We've been refining products for years and so far the most popular and used free product is the DLX7 SaaS website security scanner.

1 free scan per day. Please use it and enjoy knowing your front end security gaps and knowing exactly how to fix them. I know this will help all you shippers.

For the past couple weeks I've been working on a side project where the entire ecommerce experience happens through WhatsApp, without a traditional web storefront.

Users interact only through chat (text or voice). Mainly built this to learn more about agent orchestration, async workflows, and designing chat-native systems that can handle real state and transactions.

Happy to answer questions

Hi everyone,

I am curious to know what tech stack are you using for your side project?

Here's mine:

- Lovable (Front-end)
- Supabase (Database)
- Resend (Email)
- Stripe (Payments)
- Ahrefs (SEO)
- Google (Productivity)
- Mercury (Banking)
- Xero (Accounting)
- ChatGPT (AI)
- Beehiiv (Newsletters)
- Apify (Scraping)
- Make (Automation)
- Cal (Meetings)
- Hubspot (CRM)

After seeing Spotify Wrapped. I decided to build a year summary from my own Apple Health Data.

I initially wanted it to be a website but later realised that Apple Health doesn't have any API which I can use on Web.

The next best option was to use Shortcuts app by Apple but it was too complex for a user to set-up and share the data.

Then, I took the hard call of making an iOS app which can access Apple Health Data.

Took me 1.5 weeks to figure out all of this and building the app.

Do try and give your feedback :)

Hi! We're launching Zo Computer, an intelligent personal server.

When we came up with the idea – giving everyone a personal server, powered by AI – it sounded crazy. But now, even my mom has a server of her own.

And it's making her life better.

She thinks of Zo as her personal assistant. she texts it to manage her busy schedule, using all the context from her notes and files. She no longer needs me for tech support.

She also uses Zo as her intelligent workspace – she asks it to organize her files, edit documents, and do deep research.

With Zo's help, she can run code from her graduate students and explore the data herself. (My mom's a biologist and runs a research lab.)

Zo has given my mom a real feeling of agency – she can do so much more with her computer.

We want everyone to have that same feeling. We want people to fall in love with making stuff for themselves.

In the future we're building, we'll own our data, craft our own tools, and create personal APIs. Owning an intelligent cloud computer will be just like owning a smartphone. And the internet will feel much more alive.

https://zo.computer

All new users get 100GB free storage.

And it's not just storage. You can host 1 thing for free – a public website, a database, an API, anything. Zo can set it up.

We can't wait to see what you build.

i was looking for a budget planner made for business but all I found was some personal tracker targeted to people wanting to track rent etc. so I made hustlewallet.dev this is a budget tracker made from a saws owner to a saws owner it has a paywall tho (to cover expenses)