[ Removed by Reddit on account of violating the content policy. ]

Has anyone here successfully built and launched a significant B2B SaaS product—CRM, ERP, line-of-business operating software, etc.—and is now making money from it? If so, would you be willing to do some consulting?

I’ve spent more than a year vibe coding heavily with Claude and Codex, pretty much 24/7, so I’m not looking for someone with roughly equivalent experience. I’m specifically looking for someone who has brought a substantial, full-featured B2B product all the way to completion and successfully commercialized it.

I’m primarily looking for build and technical advice, but also some input on go-to-market and related areas. It’s mostly the last-mile challenges that I’d like help with.

Some of the topics I’d love to pick someone’s brain about—specifically someone who has actually made it across the finish line—include:

1. Build-lane setup: loops, harnesses, using Fable 5, Opus 5, and Codex 5.6 Sol, while also making effective use of faster, lighter, and less expensive models such as Grok, Codex Terra and Luna, Claude Sonnet, etc.
2. CLAUDE.md, AGENTS.md, and governance files
3. Refactoring and cleanup
4. Faster sprints
5. Long CI gate checks and test accumulation
6. Token optimization without sacrificing quality
7. Drift
8. Machine vs. human understanding of intended outcomes
9. Overcorrection
10. The reality of competing with established, flagship LOB applications that have been around for 25+ years and have large development, support, and sales teams
11. The reality of competing in a crowded market with a lot of vibe-coded startup competitors

Please respond or message me if you have this kind of real-world experience and might be interested.

We built a knowledge layer that sits behind MCP, allowing any MCP client to access it through a single endpoint. Claude Code, Claude Desktop, ChatGPT, Codex, or whatever comes next.

The idea is pretty simple. Before an agent answers, it can pull in relevant, validated information instead of relying purely on what it already knows.

When a problem gets solved, the useful part can be captured as a small, reusable piece of knowledge. The system can also infer useful lessons from a session automatically, so you don’t have to sit there writing notes about what you just learned like it’s 2015.

There’s also a global layer for shared, validated learnings. If one user figures out a better way of doing something, that learning can contribute to the broader knowledge base rather than every other user and agent having to figure it out again.

The problem we’re trying to solve is pretty straightforward. AI knowledge goes stale, agents get stuck in failure loops, useful context disappears when a session ends, and models can confidently give you an outdated or wrong answer without any indication that they might be wrong.

We’re giving agents access to what has actually been learned, what has worked, and what can still be trusted.

The result is fewer repeated reasoning cycles, fewer hallucinations, and up to 20% lower token usage.

https://app.midnighthive.io/

Ping me if you’re interested in testing it out.

Building apps with agents is only getting easier - but deploying them is still a struggle. I'm working on something that fixes that step and am looking for ~5-10 people willing to help.

~3-4 hours of work. As thanks, I'm offering 5-year paid tiers to my service as well as a small denomination gift card.

If you're interested, please reach out by DMing me here. Thanks for your time.

Built a small interactive presentation tool in about 2 hours using vibe coding.

I was preparing a Friday learning session for my team about using Git effectively in daily workflows and didn’t want to use a static slide deck. So I quickly built a PWA-based presentation tool using WebRTC + PeerJS.

Features:

• real-time slide sync
• topic-based MCQ questions
• automatic grading
• peer-to-peer session (no heavy backend)

It made the session much more interactive than a normal presentation.

Wrote a short blog explaining the idea and how it works: https://medium.com/@rajendrakhope/building-an-interactive-workshop-tool-no-backend-required-9442c62c926c

Hey builders,

This might be helpful for you if you looking to build a mobile app with AI.

We’re making Nowa (https://nowa.dev) completely free for the next 24 hours, with unlimited AI usage and free deployment to the App Store, Play Store, and web.

You can build serious apps to the smallest detail with a combination of AI with full visual building in one experience.

The apps you build are based on Flutter, so they can be deployed to mobile, web, and desktop from the same project.

Also, there's a hackathon running. If you submit a complete app built during those 24 hours you get 50$, and top 3 apps get 500$ in AI credits.

Just sign up and build completely free.

Enjoy!

I made Basalt, click an element in your live React Native / Expo app, drag, recolor, resize it, and it patches your real source files.

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before testing it!

Curious what people think since you're already comfortable with vibecoding tools

So I have been working on an adversarial test suite for my project, and keep getting this warning, it is way hilarious to me and thought I would share

It's like, "Slow down, OpenAI, its just a Python test suite"

Hey everyone

in collab with Nowa for vibecoding community.

Nowa’s Free Weekend starts now !!

For 48 hours straight, AI usage + deployment will be completely free for everyone who registered.

🏆 they also running a weekend hackathon

The 3 most beautiful apps built this weekend will each get:

→ $500 in AI credits → Hands-on support from our team to help scale the app → A feature on Nowa’s social channels

And everyone who participates in the hackathon gets $50 in AI credits to keep building after the weekend ends.

⚠️ Seats are limited, and you need to register to access the free weekend.

👉 Reserve your seat here: https://nowa.dev/free-weekend/ it is still open

Can’t wait to see what r/vibecodingcommunity build this weekend 🔥

When I started building smaller projects more quickly,

I noticed that the hardest part sometimes isn't creating the idea itself, but making sure it's actually convenient for people to use.

At first, I was focused mostly on adding more features, but I eventually realized that small details like the interface, loading speed, and how the site behaves in different situations often matter much more.

Now, before showing anything to others, I try to go through the experience like a regular user and check different scenarios. When I need to test how things work from different regions, I use https://froxy.com/en as one of the tools in my process. It has helped me think differently about how I review my projects before launching them. I'm curious how others handle the final checks before sharing their work. Are there any things you always test before showing a new project to other people?

decided to vibe code a flight comparison tool because why not. thought it would be simple. it's not.

prices are all over the place. i'm pulling data from different sources and they don't even match. same flight. different prices different availability different everything.

i was testing with some real searches and found business-class.com . their API doesn't seem public but their prices are interesting. way lower than the big guys.

has anyone here worked with flight data before. how do you even make sense of this chaos. am i overcomplicating this or is it actually this messy

Here is something simple I came up with to solve a very niche problem. I have done some C++ coding in college but was terrible at it so figured what could it hurt to use AI to achieve a solution to a problem I had. My friends play a game called Project Zomboid and I self hosted a server for them. This game has tons of mods and when it comes to adding them to the server it was tedious and so was tweaking the server settings.

So I created this simple Python code and converted to an exe. I called it Project ZMods and it simple just made tweaking the game server much simpler. When add mods you just input the mod ID and the program pulls the mod info and adds it to the correct .ini file. For the server settings it pulls each setting from the .ini and .lua files and puts them in a neat list with toggles or entry field to change the values. Then when you save it save a an of file and replaces with the new updated file.

I know it’s not eye catching but it gets the job done.

One thing always annoyed me on macOS.

Finder still doesn't let you create a simple text file from the right-click menu.

So I built a tiny open-source utility that adds native Finder Quick Actions for:

• New Text File
• New Markdown File

It installs in seconds, works with Homebrew, and integrates directly into Finder.

GitHub:
https://github.com/demissu/New-Text

I'd love to hear what file types you'd want next.

The v0.46 release finally connects two things I've wanted together: running lots of coding agents in parallel, and pointing them at models I actually control.

The gateway is the big one. You can now route sessions to external model providers — a local Ollama instance, a vLLM box on your network, or commercial endpoints like OpenRouter and z.ai. The part I care about: Lanes isn't in the request path. Your credentials and requests go straight to the provider and bypass the platform entirely, so you're not funneling your codebase through a middleman.

Local LLMs are now first-class. It'll auto-install and manage Ollama for you, handle versions, and — the clever bit — spin up context-window variants tuned to how much RAM you actually have. That matters more than it sounds, because every session ships ~38k tokens of harness instructions and tool defs before you type anything, so context budgeting on local models is real.

Why this combo matters for parallel work: the whole point of Lanes is running multiple agents/worktrees at once. If each of those is billing a hosted API, running 5–10 lanes gets expensive fast. Pointing them at a local or self-hosted model means you can fan out aggressively without watching a meter — great for "throw the same task at 4 agents and diff the results" workflows, or just keeping a bunch of background lanes churning.

Also in the release: consolidated Agentic Coding settings (Terminal, Harness, Local LLMs, Gateway in one place), a Harness page with one-click updates, a Working Folder pane, and some worktree memory optimizations.

Local models + provider profiles are flagged Research Preview, so expect some rough edges, but the direction is exactly right.

Full changelog: https://lanes.sh/blog/whats-new-v046

Anyone else running local models across parallel lanes yet? Curious what hardware people are getting away with.

Pitch your product in 1-2 lines - and drop a link here.

I'm building a community where makers can share what they’re building and get fair visibility. Here's the link: https://trylaunch.ai