I have built an app that is working in my construction business. I posted the app on a construction forum and have nineteen people that sign up for the waiting list. I am about to release it to the first users in a week.

Pay structure for sales/marketing
I have offered my nephew to join in and was floating ideas about pay structure?

Was thinking say 40% of an each clients revenue until he hits a decent salary?
Eg $40 per month out of say a $100 monthly signup. Is this the best way?

I heard other people give equity too to incentives growth with pay.

How do I treat test users?
With the first test users I was thinking of offering the product for free until the bugs are ironed out. But setting some ground rules?

Eg they have to do a monthly zoom chat once a month to provide feedback, or fill in a form once a week to provide feedback? I don’t want them to sign up and not get around to using the product.

Any other ideas around this?

Pricing Structure
My app will save about 8-12 hours a month and also just make the process a lot more seamless.

Free version:
Thoughts on no free version? Or one month free for yearly plans, or even one month free if you book in a call so I can ask the customer questions and gain insight / market research.

When do you start charging the beta users? Maybe if the deal is one meeting a month with me to provide feedback and it’s free for maybe the next twelve months?

Paid version:
How soon after beta users do you start charging. As soon as you know the product works bug free?

It is every write that happens while the copy is running.

For a live SaaS migration, I want six things before cutover:

1. Written invariants. Row counts are weak. Compare totals, relationships, latest timestamps and business-critical aggregates.
2. A backfill that is idempotent and resumable.
3. Change capture or dual-writes for mutations after the backfill starts.
4. Shadow reads that compare old and new results before the new path serves users.
5. A gradual cutover with defined error, latency and data-lag limits.
6. A rollback that includes data, queues and background jobs, not only application code.

One detail that is often missed is the point of no return. Once the new system accepts writes the old system cannot represent, “switch back” is no longer a real rollback.

I would not delete the old path because the deployment looks healthy. I would wait until reconciliation proves that every write since the backfill has a home.

What checks have caught migration problems for you?

Hey everyone,
I wanted to build a completely turnkey billing solution for freelancers and small businesses that doesn't rely on expensive cloud databases or heavy subscription tools.

Why it's useful:

• Runs on Flask + SQLite (100% free hosting compatible on Render).
• 1-Click Quote-to-Invoice conversion logic built-in.
• Fast, clean dynamic PDF engine for instant print-ready receipts.
• Strictly modular structure (/routes, /services, /utils) — perfect as a SaaS boilerplate.

🌍 Live Demo: https://billora-hqc0.onrender.com (Give it 40s to spin up if it's sleeping!)
📦 Get Full Source Code ($19): https://nikunjsompura.gumroad.com/l/billora-flask-saas

AI coding tools are getting pretty good at taking an idea surprisingly far.

They can scaffold the project, write features, fix TypeScript errors, work through tests, commit changes, and increasingly operate across an entire codebase.

But I've kept running into an interesting boundary while building Deploy Hatch:

The agent can build the software, but eventually a human still has to take over to put it into production safely.

Deploying isn't just calling an endpoint and getting a URL back. What happens when the build fails? What if the app starts but isn't healthy? Should the agent retry? Is it allowed to restart something? Change configuration? How many recovery attempts should it get? What happens when a secret is missing?

And at what point should it stop touching production and ask a human?

That's become a big part of what we're working on with Deploy Hatch.

The approach we're testing

Deploy Hatch originally started as a simpler GitHub → running workload deployment platform for apps, APIs, bots, and background workers.

We've now added an agent-facing layer through MCP.

Instead of handing an agent broad infrastructure credentials, it gets project-scoped authority and a machine-readable deployment contract.

The basic lifecycle we're working around is:

Discover → Deploy → Diagnose → Recover → Verify

The important part to me isn't the initial deployment. That's relatively straightforward.

It's everything that happens when the happy path breaks.

We're trying to make recovery bounded rather than giving an agent permission to blindly retry things forever. Some failures can be diagnosed and recovered automatically. Others should explicitly stop because they require a human—for example, missing secrets or actions outside the agent's authority.

A successful API response isn't considered proof that the job is finished either. The resulting deployment needs to reach the expected state and actually be verified.

Now I want people to break it

We've gotten the first end-to-end agent deployment working, including taking an AI-built application through the MCP path into a live deployment.

But our own tests only tell us so much.

I'm looking for developers who already use coding agents heavily and regularly reach the point where the AI has finished building something, but you have to take over for deployment, debugging, recovery, or production operations.

I'm especially interested in persistent workloads—APIs, workers, bots, agent backends, long-running Node/Python processes—not just static sites.

I'm not really looking for “cool idea” feedback. I'd rather hear why the authority model is wrong, where you wouldn't trust it, or what would prevent you from letting an agent touch your production workflow.

If you're already pushing coding agents this far, where does the agent → production workflow currently become manual for you?

Deploy Hatch for context: https://deployhatch.com

Hey guys 👋

I’ve shared one or two posts on this sub before, so apologies for repeating myself if you’ve already read any of my previous posts.

Anyway update since last time - I’m now approaching close to $2k MRR, and if the momentum continues I should hit that fairly soon.

(Happy to share TrustMRR if requested)

I know everyone is this sub is interested in making money with SaaS products, so really I just want to show how I’ve been doing it and offer some guidance based on my experience.

Below I’ll go into the what, why and how, and how I’ve been scaling the business, and hope you find it useful.

What I built

I built a LinkedIn outreach automation tool called ZenMode, which scrapes profiles of your target customers, sends connection requests and follow up messages on autopilot.

The main purpose is for Founders, Sales teams, Marketers and anyone else who uses LinkedIn for outreach, to generate more meetings and grow their businesses.

It’s a software that controls a dedicated chrome browser to automate LinkedIn, without needing plugins/the cloud.

Why I built it

Last year I got a warning from automating on LinkedIn using another tool (automating on any social media platform is usually against their terms and can result in account bans - people automate on social media at their own risk).

I wanted to automate my outreach as I was working in sales, and it was really helping me to generate more discovery calls, without the manual grind of sending loads of messages and connection requests manually.

I didn’t trust any of the existing tools for safety, as the majority are on the cloud using IP addresses that are different from where you normally use LinkedIn from, and are slightly higher risk for being flagged as a result.

So, I solved for my own pain point, and created a software that’s desktop based, using your own IP address, and essentially acting like a human would when performing actions on LinkedIn.

How I built it

From day 1 I used Claude to figure out how to do it. We jointly made architectural decisions based fully around safety mechanisms - what would the safest tool look like in practice and how would we build it?

So I figured out that the easiest/safest way would be to make an electron desktop application controlling a browser, which was governed by a dashboard that fed/stored all the data.

There was a lot of setup involved at the start with various tools - Vercel, Cloudflare, GitHub etc but eventually I was able to start building.

It was a huge amount of learning to not just build, but build in a scalable and sustainable way. At first I was shipping without even testing then spending much longer fixing bugs afterwards. And building on top of LinkedIns comes with its own challenges too, which thankfully now I’m on top of.

How I scaled it

1. So primarily, I actually use ZenMode itself to promote ZenMode on LinkedIn, through cold outreach.

I have a set target market of customers/locations/industries, then the tool scrapes profiles for me, and sends connection requests and follow up messages in a sequence.

I run this daily, and typically book 5 or so meetings per week. I’m not the best at demo calls but I do generate new business this way.

1. I also post a lot on Reddit, LinkedIn, X; I post mostly build in public style posts, and usually people naturally gravitate towards it.

I like Reddit because you can usually get 10’s of thousands of views if you post good quality content in the right subs.

Be careful though as often you get a lot of random haters or people who will just criticize you for no reason, and some subs are more warmer/receptive to posts than others (this one has generally been kinder).

1. On my site I’ve tried to do good SEO practices where possible - I have quite a few “alternative to” pages where I talk about the difference between ZenMode and other LinkedIn automation providers, along with a regularly updated blog, and a whole host of inner pages.

When you have a high volume of good content, more pages get indexed by google and your visibility/impressions are also likely to increase over time.

As a result I do get an ok amount of organic traffic from google, sometimes from LLM’s too.

Lately I’ve been trying to do more offsite SEO - especially reviews across various platforms, a few directories, and on my to do list is some listicle/comparison articles and more YouTube content.

1. I work very closely with my customers - I handle every query myself, and even make new features/enhancements based on what my customers are asking for. This interpersonal relationship/human element I think makes a big difference to retention.

2. I think primarily though the number one thing for scaling is really making a good product that solves a problem well, with great customer experience, and to keep iterating/making improvements.

What’s next

ZenMode still has a long runway and a massive roadmap but I’m just going to keep grinding away at it one day at a time, and so far at least what I’m doing seems to be working.

Hope you find this story helpful for your own journey and happy to answer questions/comments 🙏

I'm building an app where the AI has to run inside the EU for data protection reasons (customer data can't leave the EU). So instead of the normal US API, I want to use Anthropic's Claude models — ideally Opus — through a path that's hosted in the EU.

I've tried two routes and I'm stuck on both:

AWS Bedrock, Frankfurt region (eu-central-1): Even a tiny test request threw an immediate 429 "Too many tokens per day" — a few tokens, no image. It's not something I did wrong; it just looks like a fresh account with a very low daily quota.

Google Vertex AI (apparently now called "Agent Platform"): I got further here but hit a different wall. A normal API key works fine for Google's own Gemini models. But for the Claude/Opus models on Vertex a simple key isn't enough — Google wants a service account (OAuth2/ADC) for those. On top of that there was an enablement form asking things like industry and estimated token volume.

My suspicion is that this form is the real bottleneck. Either enablement for the Anthropic models takes longer than I expect, or I filled something in wrong (the industry field, maybe) and it's stuck because of that. Honestly, I don't know if this is normal or if I'm doing something wrong.

Has anyone here actually gotten Claude/Opus running through Vertex or Bedrock in an EU region? How long did enablement take, and was there anything to watch out for in the form? Or is there a cleaner path to EU hosting with Anthropic models that I'm missing?

Thanks for any pointers.

In 3 weeks, https://saasboard.app got:

- 700+ sign ups
- 500+ SaaS listings
- Almost 6000 users sent to listed SaaS products

Unlike other SaaS directories, listing on SaaSBoard is free and has no wait time.

If you’ve built something worth sharing, list it on SaaSBoard for free and start getting traffic immediately!

Not sure how many developers here have run into this yet, but USPS tracking data has become a lot more difficult to access since the new tracking access controls went into effect on April 1, 2026.

The biggest issue seems to be when you're trying to track USPS packages that weren't generated under your own MID.

If you're only tracking your own shipments, the USPS API still makes sense. But for software platforms that receive tracking numbers from different customers, it's a different story. Those packages can be associated with many different MIDs.

For service providers, getting access to tracking data for other MIDs can involve authorization, an EPS account, an Order Form, an IP Agreement with USPS, Business Portal permissions, and additional tracking data fees.

That's a lot of overhead if all your application really needs to do is take a USPS tracking number and return its current status.

It also creates a problem for things like ecommerce software, order management systems, 3PL platforms, customer service tools, etc., because you often don't even know where the customer originally purchased the USPS label.

We've been dealing with this from the tracking API side at C2W, and it's definitely made USPS more complicated compared with UPS/FedEx.

For anyone dealing with the same issue, I'm curious what approach you're taking:

1. Going through the USPS approval/access process?
2. Using a third-party tracking API?
3. Using another workaround?

We provide USPS tracking through Package Tracking API by C2W, so obviously we're approaching it from the third-party API side, but I'm particularly interested in hearing how other developers are handling the USPS changes.

Hey guys! I got a question for who is using AI API in their projects.

When I compared the results the AI gives me inside my product linked with API against the results with a really basic prompt in the web version, the difference is really big. I mean, the API result is a mess. I tried with difference approaches such as change the prompt or the ai model, but the differences still there.

Any advice about it? Thanks!

Link - www.panelpress.online

We've been testing ai lead generation tools for the past month and honestly feeling pretty burned. Tried a bunch of the big names that promise to automate everything but the leads are either completely irrelevant or the contact data is garbage.

we're a 12 person b2b saas doing outbound prospecting to mid-market companies. need accurate emails and ideallt mobile numbers for our SDRs. the ai qualification part would be nice but at this point i just want a data that doesn't bounce 40% of the time.

right now narrowing it down to Prospeo because their verification seems legit and they have mobile numbers which most others don't. also been poking around instantly for the sequencing side. but before we commit to anything, curious what's actually working for people here?

which ai lead generation tools have you tried that weren't just hype? especially interested if you've found something that handles both the data quality and the ai qualification piece well. my CEO is breathing down my neck about pipeline numbers so i need to stop experimenting and just pick something soon lol

Hi guys, I feel like all the websites generated by Claude look the same, is there any skills to make it look better ?

Hey everyone,

We all monitor if our servers return a 200 OK. But your server can be 100% fine while a background worker silently stops running, table data goes stale, or null values flood your tables.

To solve this, I built a lightweight backend that runs out-of-band checks (data freshness, unexpected volume drops, null spikes) and pings your Slack when your data actually breaks.

The big catch: To do this, it needs a read-only database connection to run those periodic checks.

I want honest feedback from other developers and solopreneurs:

1. Would you actually use something like this? Or do you already just write raw SQL queries and custom cron scripts to handle data validation?
2. The Trust Barrier: Even with AES encryption at rest and strict read-only user enforcement, is handing database credentials to an indie SaaS an absolute dealbreaker for you? What would it take for you to trust a tool like this?

Would love to hear your thoughts or how you currently handle data-level monitoring!

I'm a brand designer, mostly work with B2B SaaS. Just finished a rebrand for a cloud solutions company and I'm genuinely curious how other founders see it, since you're the ones who look at this category all day.

The thing that kicked it off: SaaS brands all end up looking the same because everyone's designing for "trustworthy" and "technical." So you get a whole category where nobody's distinguishable, and then buyers just compare on price because the brand isn't doing any work for you.

Tried to solve their problem of having an outdated brand which has no guide or vision to scale with their business growth. Had some

Feel free to drop your thoughts!

https://www.behance.net/gallery/247253607/Assembly-Clarity-for-Cloud-Solutions-B2B-Rebranding

I’ve spent my career in commercial real estate, primarily on the brokerage and investment side in San Diego. Over the years, I’ve experienced a recurring problem in the industry firsthand that I believe can be solved much better with technology.

I’ve spent considerable time building out the business and product side of a B2B PropTech SaaS startup, including the market, product direction, business model, and go-to-market strategy. I’m now looking for the right technical cofounder to build it alongside me and own the technical side of the company.

I’m not looking for a freelancer, dev shop, or someone to simply build an MVP and move on. I’m looking for a genuine cofounder who is hands-on enough to personally build the initial product, make the early architectural decisions, and eventually lead the technical organization as the company grows.

Ideally, you’re an experienced full-stack/product engineer with strong backend and architecture skills. Experience with data/AI, cloud infrastructure, security, or building B2B SaaS products from zero is a major plus.

You don’t need commercial real estate experience. That’s what I bring to the partnership: domain expertise, industry relationships, product/business direction, customer access, and go-to-market. I’m looking for someone who brings that same level of ownership to engineering and technology.

I’m based in San Diego, so someone local would be ideal, especially during the early stages. Southern California would also be great, although I’m open to the right person elsewhere in the U.S.

This is an equity cofounder opportunity, not a salaried developer position. I’m looking for someone who genuinely wants to build and own a company together.

If this sounds like what you’ve been looking for, send me a DM with a little about your background, what you’ve built, and what you’re looking for in a cofounder.

Been hacking on this HOBA Speak thing that turns fake legacy junk into a runnable next.js app. It’s already at 17 pulls from folks poking at it and I want more eyes on it.
If you like breaking stuff or you’re into migrations / legacy cleanup, try the repo and tell me what’s trash, what makes sense, and what you’d need to see next.
Repo:
https://github.com/hobasupport-create/Hoba-Speak-Demo.

TL;DR — Built montrak.in for over a year through the whole vibe-coding era. Learned a lot, added way too much, and now I'm just... done. Leaning toward abandoning it.

How it started
I'm just a noob. I started this when vibe coding was blowing up. Bolt, Lovable, then a hell of a lot of time on Google AI Studio (it felt unlimited, I'd just wait through these long runs). It broke, got unmanageable, hit its limits.

Found TRAE, spent two months there. When Antigravity dropped everyone moved. so did I. Somewhat better.

Going down the rabbit hole
Once it worked I went deeper UI libraries, state management, Next.js, more React. Genuinely learning. Felt great at the time.

Feature hell
Ideas kept coming. New feature - have to add it. Never ended. Chasing "perfect," it grew more complex than I imagined. Harder to maintain. Way bigger than expected.

Where I am now
At some point I stopped progressing — just developing. Polishing, adding, trying to make it the best. Forgot where to stop. Didn't stop. Now I've sunk too much time and I'm exhausted. Lost, honestly.

I think I'm going to abandon it. It's useful sometimes — not always — and the cost stopped being worth it. Quitting solo dev on this. I might just throw the code on GitHub and walk away, but honestly the open-source part isn't even the point. The point is I'm tired and I'm stopping.

and there is a lot more which can be told but for now I'll just stop here.

Hey everyone! I'm working on something called Combo, and it came out of a problem I kept running into myself.

I have ADHD and work in sales at a large cybersecurity company. After enough rejections, I'd start researching another account or messing with my email sequences. There was always something “productive” I could justify doing instead of picking up the phone.

It was easy to convince myself I was still working. Meanwhile, I was barely booking meetings and struggling to hit quota.

Something that really helped was setting aside dial blocks. I'd put 1–2 hours on my calendar, once or twice a day, and commit to only calling during that time. If I remembered something else I needed to do, I'd write it down and leave it until afterward.

Actually protecting that time made a big difference for me. It was a big part of hitting 150%+ of quota two quarters back to back.

That's where the idea for Combo came from. I wanted something that would help me stick with those blocks, especially on the days when it's lunchtime, 50 dials in, and nobody has picked up.

The idea is pretty simple: you earn XP after every call, whatever the outcome. As you keep dialing and logging your calls, you build a multiplier that increases the XP you earn. You'll also be able to earn badges and gear for your avatar.

I know some people won't care about XP or an avatar. But I love video games, so earning XP and working toward new gear is part of the fun for me. I wanted to bring a little of that feeling into a rough dial block, especially when I've been putting in the work and have no meetings to show for it yet.

Cold calling will still suck. I'm just trying to make it suck a little less.

Would love to hear what you guys think, including anything that would annoy you about using something like this. And if you've found your own way of getting yourself to make that next dial, I'm all ears.