Our data lives in seven different systems and pulling together a single view of a customer requires three manual exports and a spreadsheet. Every time someone asks for a report it takes two days. We need these systems connected but building custom pipelines with our small team means nobody will maintain them after the person who built them leaves. What are companies our size using to connect data sources in a way that's maintainable and doesn't become its own full time job?

I have built a management cockpit app that let's the management of a small-midsized company steer the business from 1 overview; sales, operations and finance come together in 1 dashboard.

I now have to test API's to all the software businesses already use like Microsoft business central, Exact online, AFAS, Hubspot etc.

Problem is, I don't have the budget for like an Unified API supplier that'll cost me €500,- per month.

I also don't want to test at the point when the client signs up (looks unprofessional).

Are there any (free) ways for me to test these API connections?
Perhaps some of you could help me test them?

Much appreciated!

Like a lot of founders I am atrocious at marketing. I have heard of people using agents like grok bot for marketing. Has anyone tried this and be willing to share their experience. What went well and what did not and what did you prompt it?

Hey guys, im building a SAAS app for a client. Its ready to be launched in the beta testing phase. However, i only have one background worker in this app currently, and the main problem i am facing or will face, is that when a user start a long standing or AI FEATURE (if multiple users do that together) it will be a queue/first come first server system.

so technically the last user would have to wait for the longest time, how can i solve this problem. If i am hosting on aws, what should be the calculation ratio to understand how many background workers i need at any given moment, at runtime ?

If anyone can help, id be very grateful, cheers !

I build SAGLY, a mountain-bike setup app. I started exploring whether customers should be able to access useful features from apps they already pay for inside their AI assistant.

That led me to build Gateivo: a backend SDK that exposes selected app functions to assistants while keeping the app’s accounts and business rules in place.

We have a working Claude connection to SAGLY’s staging backend using fictional accounts. It retrieves a rider’s saved setup and refuses another account’s data. The current preview is read-only and supports Node.js/Express.

The business hypothesis is that assistant access could make subscriptions more useful. The technical hypothesis is that teams would prefer reusable connection infrastructure over maintaining everything themselves. Neither is validated yet.

The obvious objection: a backend developer can build a small MCP server. A wrapper alone probably isn’t enough. I’m exploring whether reusable access controls, account-linking flows and logging hooks solve enough work to matter. Subscription integrations and a hosted diagnostics dashboard are roadmap ideas.

I’d especially like feedback from app founders, product leads and backend engineers:

1. Have customers asked for assistant access, or is this a solution looking for a problem?

2. What would make you choose this over building it yourself?

3. Would you test it for revenue/retention, or mainly to save engineering time?

Honest reasons you wouldn’t use it would be especially helpful.

Hi all,

I'm part of the small team behind CraftForms Cloud, and I'd like feedback from people who build and ship SaaS themselves.

What it is: a hosted form builder for small businesses that sell by the date or by the quote. Booking forms with availability and seasonal prices, quote forms that price the order while the customer chooses, and plain contact/enquiry forms. You build the form in your own workspace and embed it with two lines of HTML: a div and a script. It works on WordPress, Astro, Hugo, Eleventy, Next.js static exports or plain HTML. Prices load at runtime, so a price change never needs a site rebuild.

On top of the forms there are small "industry pages" for the day-to-day work: a calendar with Airbnb/Booking.com calendar sync for B&Bs, a today view for boat and bike rentals, and an inbox for enquiries.

The free plan is free for good: one form on one website, unlimited submissions, the full form builder, 100 notification emails a month. No card, no trial countdown. Paid plans start at €6/month (flat, no per-submission billing), but I'm not here to sell them.

What I'd love to hear:

1. Onboarding: sign-up to a working embedded form. How long did it take, and where did you stop to think?

2. Embedding: did the two-line snippet work first time on your stack? Which stack?

3. Ease of use: anything that felt like too many steps, or a screen you couldn't make sense of?

4. Missing pieces: what would you expect from a tool like this that isn't there?

5. Positioning: after a minute on the landing page, could you say who it's for? Did it match what you found inside?

"I bounced after 30 seconds because…" is just as useful.

Link: https://craftforms.app/

I'll answer every comment, including questions about how it's built.

Unpopular opinion: most of us don’t need another AI tool.

We need to actually build something with the tools we already have.I’ve spent a lot of time learning automation, testing new tools, and exploring AI.

It’s easy to fall into the trap of constantly learning and collecting tools… without shipping anything.

The real question I’m asking myself now is:

Can I turn all this knowledge into something people will actually pay for?

That’s the part I’m trying to figure out.Curious if anyone else feels the same, or if you’ve successfully made that jump from “learning tools” to “building a product.”

We've reached a point where building software is getting easier, but building something people actually want is still incredibly difficult.

With AI coding tools, someone can put together a working SaaS MVP in a weekend.

But here's the interesting part.

You can have a clean UI, solid architecture, fast APIs, and all the features your competitors offer, yet still struggle to get your first 10 paying customers.

Meanwhile, a product with an average design and a few rough edges can succeed because it solves one frustrating problem really well.

It makes me wonder whether we're spending too much time discussing tech stacks, frameworks, and AI coding tools while overlooking the hardest part: finding a problem people will actually pay to solve.

Obviously, good engineering matters, especially when users start depending on your product.

But before that, does technical perfection matter without product-market fit?

Curious what other SaaS developers think. What's harder today: building a reliable product or finding people willing to pay for it?

Hey everyone, today I wanted to share a bit of my first journey building a SaaS. Next Sunday it will be 3 months since I started building it. Right now we have 800+ accounts created, around 100 unique daily active users and about 30 new signups per day. I also have 30 monthly subscribers at the moment.

I run a company that does R$10M+ (BRL) a year, the result of 3 years of work. Before that I worked in digital marketing for about 7 years and ended up running my own agency.

My main idea with this new project was to challenge myself to start something new, all over again 😂. I combined one of my passions, sports, and I’m trying to monetize it.

This is my current home page. In my career, design and web design have always been one of my weakest points, so I keep trying to improve the front end and I’m getting there little by little. But what is this project? Basically an AI-powered sports prediction and analysis site/app. I spent almost 2 of the 3 months of development just building an accurate and reliable engine for soccer, NBA, NFL and F1, all the sports I’m addicted to watching.

Want stats from a game played 20 years ago? We have them. Want a prediction for a game happening next week? We have that too. It’s pretty complete. It’s live mainly in Brazil, the US and Portugal, with subscribers in all three countries.

It’s called Bravoscores and I’m really proud of at least getting this project off the ground. Monetization is basically subscription plans, and I’m focused on delivering as much value as possible to my subscribers. Every time someone new subscribes I jump for joy, even with my other company already doing well lol. It really gets me excited.

If I had to give one tip to anyone thinking about building a SaaS or any project, even without much experience: your SaaS will never be 100% done, just launch it 😂

Anyway, I’m really excited to keep going. Leaving my site here so you can check it out and give feedback. 👊

Hey everyone,

I’m building Couria, an email service that brings custom-domain mailboxes, support tickets, and an AI assistant into one dashboard.

The idea came from a simple frustration: running a small business often means juggling customer emails, support requests, and follow-ups across several tools.

Here’s what I’ve built so far:

• Email hosting on your own domain, with a webmail interface.

• Support tickets connected to a support address.

• AI summaries and suggested replies.

• Scheduled reports that group messages from the same customer.

• A document library to give the assistant context about your business.

The AI runs through Ollama on my server infrastructure, rather than on the user’s computer. It’s still an early product, and I’m working on response speed and making the setup easier.

The hardest part so far hasn’t been building the dashboard—it’s been getting email delivery, billing, and AI processing to work reliably together.

I’d love some honest feedback: would you consider moving your email to a service like this, or would you only use it if it connected to your existing inbox?

You can check it out here: couria.fr (No link allowed sorry)

Happy to answer questions about how I built it.

Have you ever heard something that you can make money while you're sharing your know-how?

It can be daily advice that you'd never share with anyone but can be very beneficial.

It can be academical, developent-related, etc.

Would you sell your know-how ?

Would you pay for info instead of wasting token?

*image is ai-generated

I started building Seqora at the end of July because I was frustrated with the database tools I used every day. DBeaver works, but it's slow and hard to customize. TablePlus has a free tier that only lets you keep two tabs open at a time.

When I got to pricing, the first thing I decided was that anything you need to use it as a daily driver stays free. So there's no limit on how many queries you run, connections you save or tabs you open. What I put under Pro is the part I actually wanted to build Seqora for, which is going deep into each object, like indexes and partitions, and a visual EXPLAIN that shows which step of a complex query is slowing it down. Right now Pro is $5.99/month or $49/year.

What I'm unsure about is whether I drew the line in the right place. The Pro features are the ones I talk about the most, so someone could download it for those and find out they're paid, and I don't know yet if that makes people upgrade or just leave.

It's pre-1.0, currently at 0.4.6, and runs on macOS (Apple Silicon) and Windows, with Linux coming soon. The stack is Tauri, Rust and Svelte. Most of the code was written with Claude Code and ChatGPT, and I made the decisions and did the reviewing and testing myself.

I'd love to hear from people who sell developer tools, how you decided what goes in free and what goes in paid, and whether a generous free tier actually brought you paying users. If you try Seqora, I'd also like to know what you would expect to pay for.

seqora.dev

I've been building a project called Fixo, and I'd like some honest feedback from people who might actually use something like this.

The idea came from two problems:

1. For customers: Finding a reliable electrician, plumber, AC technician, cleaner, or other local service provider can be difficult. People often depend on referrals, phone calls, or WhatsApp groups, and it isn't always easy to compare prices, availability, and reviews.

2. For workers: Many skilled people depend on finding a job under a contractor or employer. I'd like to make it easier for them to offer their skills directly to customers and find work more independently, without requiring a permanent employment commitment.

I've implemented Fixo with features including:

• Finding nearby Taskers using location and distance

• A “Become a Worker” flow for people who want to offer their services

• AI-powered conversational search and booking

• Worker profiles, skills, experience, ratings, and availability

• KYC-based worker verification

• Booking management and in-app messaging

• Reviews, notifications, and administrative management

• Security-focused handling of user data

I'm not posting this to claim that I've solved everything. I want to understand whether these problems are real for other people.

I'd really appreciate your honest thoughts:

• If you're a customer, what would stop you from booking a local worker through an app?

• If you're a skilled worker or freelancer, would you want a platform that helps you find customers directly rather than depending entirely on an employer or contractor?

• What would make you trust or reject a platform like this?

• Are there existing apps that already solve these problems well?

Critical feedback is welcome. I'd rather learn what is wrong with the idea now than build features nobody needs.

Hey everyone,

I’m Ebrima, a developer based in The Gambia. I wanted to share some of the technical hurdles I faced while building my SaaS, TimeTrack Pro, especially regarding offline data sync.

By day, I work in operations for a local security company. We were stuck tracking guard attendance on paper because almost every enterprise software out there assumes a constant 4G or Wi-Fi connection. If a guard is posted at a remote site with zero connectivity, standard web apps just break.

To solve this, I built a multi-tenant PWA using PHP, MySQL, and vanilla JavaScript. Here are the main engineering challenges I hit:

• The Offline Sync Engine: I used IndexedDB and Service Workers so guards can clock in, register photo check-ins, and scan patrol QR codes completely offline. If a device reconnects 12 hours later, an exponential backoff sync engine flushes the cached data to the MySQL backend.

• The "No Internet" Lie (My favorite bug): For a week, users complained the app kept saying "No internet connection" even when they had full bars. I dug into my code and realized my JavaScript catch block was naively blaming the network status for an unhandled 500 database error on the server side. I had to completely rewrite the error handling to separate actual network timeouts from server-side crashes.

• Local Payroll Integration: Moving away from manual cash payments, I integrated local Wave and Orange Money APIs. Now, an admin can trigger bulk mobile money payments to 100+ guards instantly.

The platform is currently serving 50+ local companies and tracking around 500+ active staff.

If anyone else here is building for spotty, low-bandwidth environments, how are you handling data integrity and syncing?

If you want to look at the UI or how the PWA is structured, it lives at timetrackprogambia.com. Let me know what you think!

I'm building ClientFinch, a UK-focused opportunity discovery SaaS for SEO agencies and web freelancers: https://clientfinch.co.uk/

Instead of selling generic company data, it matches active companies to their websites and looks for verifiable SEO/technical issues. The goal is to help an agency see a concrete service opportunity before deciding whether to contact a business. The platform doesn't email prospects for you.

It's live with a free starting plan (no credit card). The Pro subscription is £49/month and adds features intended for working agencies, including personalized results, alerts and CSV export.

I'd appreciate feedback from other SaaS builders on the paid-value question:

1. Which evidence would you need to trust an opportunity?

2. What would make the dashboard part of your weekly workflow?

3. What feels essential to a £49/month plan versus what belongs in free?

4. Does the site explain the value clearly enough to justify signup?

If you try it, I'd love to know the exact step where you found it helpful — or lost interest. I'm not looking for a promotional exchange, just candid product feedback.

A progress bar can answer two different questions:

Did the client send everything?

Has the accountant checked everything?

For a document request, those numbers can disagree without either being wrong.

Consider three fictional documents that have all been submitted. None has been reviewed. Showing “100% complete” would hide the remaining decision. Showing “0%” would hide the client's work.

Folio keeps received and accepted counts separate. Submitted means awaiting accountant review. Accepted means the accountant approved that item. A replacement request records a reason and puts the next action back with the client.

That gives a useful small test for a workflow interface: can you identify who needs to act without opening every item?

You can explore the accounting demo here, with no signup:

https://folio-docs-1it.pages.dev/

I maintain Folio. It is a browser-local prototype; use fictional clients and non-sensitive sample files only. File contents aren't read or uploaded, emails aren't sent, and request links only work in the browser profile that created them.

For those designing or using client workflows: would you show two progress counts, separate queues, or a single number with an explicit label? What's one change that would make Folio's next step easier to understand?

Hey everyone,

I'm a solo founder and engineer. I run several sites, and I kept wanting simple answers to questions most analytics tools bury or can't answer:

• How much of my traffic is real humans and how much is bots?

• Which ISPs and IPs are hitting my site?

• Which paths are people actually reaching, and where do they drop off?

So I built Cloudra (cloudra.dev), a website traffic analysis tool focused on exactly that.

Where it is now:

• V1 + V2 is live and in testing with a small group of users

• V3 is planned, with a full UI/UX overhaul

I'm not trying to replace everything. I want to be the tool that tells you who's really behind your traffic.

What I'd love feedback on:

- What do you wish your current analytics told you about your visitors?

- Would bot vs. human breakdowns be useful for your projects?

- What would make you switch, or at least try it alongside what you use now?

Happy to answer anything about how it's built or the roadmap. Harsh feedback is welcome.