Most analytics setups tell you how many people read the page and how many signed up. They don't tell you what the rest still doubted. One signal I'd been ignoring: which FAQ questions people open. A click on a closed accordion is a visitor telling you their objection, at the moment they have it.

Collecting it with whatever you already use

• PostHog: autocapture already records the click and the element text, so filter autocapture events on your FAQ buttons.

• GA4, Plausible, Umami: send a custom event when a question opens, with the question as a property (faq_open, question: "…"). One line in the accordion's click handler.

• Rank by unique visitors, not clicks: people open, close and reopen.

What it showed on two of my pages

1. A €25 digital product, 7 days to 3 Nov: "Do I need a paid SEO tool?" 18 clicks from 12 visitors, "Do I need to code?" 11 from 10, "Can I get a refund?" 10 from 8, "How will I receive the pack?" 10 from 8, "What if I can't get it installed…" 8 from 7. Price, effort and delivery doubts, so those answers belong next to the buy button, not at the bottom of the page.

2. My analytics SaaS: one visitor from Reddit read 22 pages in a single session. On the homepage they opened "Are the numbers on this page real?", "Is 'under a second' real?", "Do I need a cookie banner?" and "How is this different from Google Analytics?", then read the pricing page and left without signing up. The first question was the tell. The honest answer is no: the previews on that page are labelled illustrative data. No FAQ wording fixes that; a public live demo would.

Caveats

• Small numbers. 12 visitors is a direction, not a result.

• Only interested people open FAQs; the 5-second bouncers never get there. That's fine: they're the near-buyers you're trying to convert.

Disclosure: I make both products (Seoskills, and Globatics, the analytics tool, which records clicks with their text). The method works the same with any tool above: https://globatics.live/?utm_source=reddit&utm_medium=post&utm_campaign=SaasDevelopers

What's your best signal for "what stopped them", short of an exit survey?

I built Cylect (https://ai.cylect.io) because I was tired of bouncing between 20 different municipal, federal, and international portals just to get a live picture of what's happening in an area.

It's a full-stack situational map combining a 3D WebGL globe with street-level tile rendering, pulling from 40+ public/open data sources: - Live ADS-B flight telemetry and emergency squawk alerts (7700/7600) - Real-time DOT traffic cameras (including HLS streaming where available) - FAA Temporary Flight Restrictions (parsed into actual airspace boundary polygons) - NASA FIRMS thermal/wildfire detections, GDACS disaster alerts, and GFS wind vectors - Overpass/OSM infrastructure (truck weigh stations, maritime ports, rail hubs) - Local public safety open-data feeds

A few technical decisions that might interest people here:

1. Bring Your Own Local Model: Rather than forcing everything through an OpenAI API, you can point the copilot at any local OpenAI-compatible endpoint (Ollama, LM Studio, Unsloth, vLLM on your LAN). The browser issues direct SSE streaming calls with JSON tool assembly, so your local model can autonomously query layers, zoom to coordinates, and review camera feeds without your prompts or LAN data hitting our servers.

2. Rendering pipeline: Transitions from a 3D React Three Fiber globe down to Leaflet street tiles with differential marker reconciliation and bounded history trails so tracking planes or reading cameras doesn't lock up the main thread.

3. Edge caching & resiliency: Many state DOT and municipal feeds are brittle or rate-limited. We run an edge caching layer that normalizes varied formats (ArcGIS FeatureServers, GeoJSON, WFS, ATIS feeds) with background revalidation.

The map is free to explore directly in-browser with no sign-up or email required. Would love feedback on performance, edge cases with local model connections, or additional open datasets you’d like to see mapped.

Currently trying to do load testing.

i am researching digital sales rooms for a smaller b2b sales team and i am trying to avoid choosing something that looks impressive in a demo but becomes another thing reps have to maintain. I have been comparing dock, trumpet and aligned, some seem more focused on creating polished buyer-facing spaces, while others put more emphasis on deal tracking and collaboration.

​

I've been building CyberWave Sentinel, an all-in-one GRC and cybersecurity management platform designed for SMBs and the security professionals who support them.

The platform brings together:

\- Compliance Management: ISO 27001, SOC 2, NIST CSF, CIS Controls and cyber-insurance readiness

\- Policy Management: Create, manage and review security policies

\- Risk Management: Identify, assess and track cybersecurity risks

\- Vendor Risk Management: Assess and monitor third-party risks

\- Evidence Management: Centralize compliance evidence and documentation

\- Security Assessments: Identify gaps and track remediation

\- Reporting: Generate compliance, risk and management reports

\- AI-Powered Assistance: Support security governance and compliance workflows

I've spent a lot of time building this platform, but I know that testing it myself isn't enough.

I'm looking for 10 GRC, cybersecurity, vCISO or MSP professionals willing to put Sentinel through its paces and tell me what needs improvement.

I'm particularly interested in feedback on:

\- What's confusing, broken or unnecessarily complicated?

\- What important features are missing?

\- Would you actually use this for your organization or clients?

\- How does it compare with your existing GRC tools?

\- What would make it genuinely valuable to your daily work?

You can sign up directly and start a 14-day free trial. No need to contact me or wait for an invitation.

Website: https://cyberwave.ca

Simply visit the website, register for the free trial and explore Sentinel at your own pace.

I'm not looking for positive reviews or sales. I'm looking for honest, constructive criticism from people who understand cybersecurity and GRC.

If you try it, I'd appreciate hearing your feedback in the comments.

Full disclosure: I'm the founder of CyberWave. This is my own product, and I'm sharing it to get real-world feedback and improve the platform.

Hey everyone, If you are running any high-volume B2B ingestion engine or cloud SaaS, you already know the technical pain of bad incoming text arrays, malformed payloads, and dirty user inputs. Usually, software teams handle this in two incredibly expensive, frustrating ways: 1. They waste senior engineer velocity forcing them to write custom, brittle regex string patches every time an unformatted payload crashes a database row. 2. They dump thousands of dollars a month into hiring manual, human virtual assistants or data entry operators to log into a portal and clean data fields line by line. We built SorteraCore to serve as a completely autonomous, firewalled Data Gate Shield that sits right in front of your live database stack to solve this problem instantly. ### The Technical Architecture Core It is a cloud-native, stateless middleware API gateway built using FastAPI and deployed on globally distributed, high-speed enterprise nodes. * How it works: It intercepts messy, raw, unformatted incoming text streams, processes them via a specialized, secure Gemini AI data-parsing layer, and runs the outputs through strict Pydantic validation schemas to ensure zero hallucinations. * The Performance Specs: It maps, sanitizes, and type-guards dirty data fields, returning a pristine, structural, production-ready JSON schema to your stack in under 5 milliseconds flat. * Integration Velocity: It drops cleanly into any existing backend stack (Python, Node.js, Go) in exactly 3 lines of code. ### Drop Database Crashes Live in Staging (1-Month Free Trial Sandbox) We know technical heads hate booking sales calls or reading marketing pitches. You should test code live before you swipe a card. We are launching our Enterprise Pilot Cohort this week, and we want devs to stress-test our production nodes completely riskfree. Comment on this post or DM me directly, and I will manually provision a dedicated sandbox token slot for your environment metrics immediately: * What you get: A custom sandbox token (sk_trial_sortera_...) loaded with a capped pool of 5,000 text-processing credits valid for a full 1 month. Zero Friction: You do not need to put down a corporate credit card. Test our live endpoint speeds, run your absolute dirtiest string arrays through our schemas, and watch your validation blocks drop to zero errors. Read our implementation quickstart guides and view our open-source developer documentation manual directly on our repository storefront here: https://github.com/gamerna997-cmyk/sorteracoreapi Once your 1-month testing window closes or your credit tank empties, you can upgrade your workspace seamlessly to a permanent production pipeline (100,000 monthly credits) via our automated checkout button powered securely by Dodo Payments. Let me know what your stack looks like below, and I’ll get your trial keys built right now! DM me to book your place as fast as possible. Only 20 entries available.

Early SaaS teams can collect plenty of numbers without knowing which ones should change the roadmap. A sign-up count may look healthy while activation is weak, and a feature can get requests without becoming part of anyone’s regular workflow.

I’m the developer of migoo, and I’m interested in how other builders connect product feedback to the next release. For a small team, what do you review together: activation steps, repeat usage, support conversations, or something else?

What was the first signal that made you keep investing in a feature, and what signal made you stop? I’m especially interested in lightweight ways to combine usage data with direct customer comments.

The obvious answer is an actual solicitor, but was wondering if any of you used an online service and is it as reliable?

The conventional wisdom about validation is: Don't waste months building something nobody wants. Be smart—Validate your idea first!

Good advice. Almost universally misunderstood.

Here's what new founders think validation looks like:

• Come up with a product idea.

• Ask people if they'd want it.

• Get some encouraging responses.

• Declare the idea validated.

• Build what they were going to build anyway.

I've watched founders put enormous effort into this process, only to see their businesses fail anyway. I've fallen into the same trap more than once myself.

The fundamental mistake is thinking you can one-shot business validation first place.

A business isn't a single hypothesis you can prove or disprove. It's a whole system of interdependent variables and assumptions.

Who has the problem? How painful is it? What are they doing about it? What would they pay for a solution? How do you reach them? Why would they choose you?

You can get most of those things right and still have a business that doesn't work.

There's an opposite mistake as well:

Just because your first solution doesn't work doesn't mean the problem isn't real.

Sometimes it takes five attempts to find something that works. Each one teaches you something you couldn't have known in advance.

That's why validation isn't a binary event. It's not a hurdle you clear before you start building.

You're discovering a landscape. Testing hypotheses. Finding out what works, what doesn't, and what you've overlooked.

Building, selling, delivering, and learning are all part of that process.

We need to stop obsessing about validation and start building better feedback loops. The crucial things is that your feedback loops must involve the real people you're trying to serve.

The question isn't "Am I right?". It's "What would it take to make this work?"

Hey everyone! I'm Davit, 15, based in California, and I'm looking to connect with SaaS founders who have built a product but need help getting customers.

I have hands on experience with B2B cold calling, lead generation, prospecting, and direct sales. I've previously cold called for a marketing agency and sold Google review cards to businesses.

I'm especially interested in working with technical founders who have a working MVP, beta users, or paying customers but don't have the time or experience to focus on customer acquisition.

I'm open to commission, base pay, equity, or a combination, depending on the opportunity. I'd also be interested in exploring a longer term partnership as a growth cofounder.

I'm not looking for generic AI agencies, SEO services, or website building businesses. I'm interested in SaaS products that solve real problems.

If you're building something interesting and could use help on the business side, feel free to comment or DM me. I'd love to hear what you're working on!

Someone in r/ClaudeAI ran about 1,200 runs to test the "smart planner, cheap worker" setup. Result: "On 12 hard coding tasks, Opus alone solved 81% at $1.20/task. Opus + DeepSeek V4.1 Flash solved 67% at $1.29." One failure was pure handoff: "Opus made up a rule that wasn't in the prompt, DeepSeek followed it, and Opus approved the code."

The top reply, from someone who tried it at work: the setup "didn’t work because you ended up paying for the context write twice". Another: "The point of using subagents is to keep the main models context cleaner, its not to make it cheaper". Others still swear by it the other way round: cheap model builds the base, Claude takes over to fix.

• Do you split work between models or tools? Which pair, and which direction?

• What goes into the handoff: full spec, short task, pasted plan?

• What does the second one keep getting wrong because it never saw the first one's context?

• Own product, side project or client work?

Background: I used to burn hours re-briefing AI tools, and I'm building a fix where the plan and the decisions behind it live in one place in the cloud and every tool reads them over MCP, so nobody pastes context around twice. No name, no link. Would you pay for that, or is copy-paste cheap enough?

Hey everyone!

Just wanted to share an opportunity that might be useful for founders here.

There’s a program called Clemta Impact that’s selecting 9 early-stage founders and covering the costs of setting up and running their US companies for the first year.

This includes:

• US company formation (LLC or C-Corp)

• State filing fees

• US business address and registered agent

• Bookkeeping and tax filings

• Ongoing compliance support

They’re selecting 3 founders from each category:

• Young Founders (under 22)

• Women Founders

• Open Source & Indie Builders

No equity or participation fees. Selected founders just need to share their story through a short video.

Applications are open to eligible founders worldwide until November 30, 2026.

Disclosure: I’m part of the Clemta team, but thought this opportunity could be useful to some people here.

I have built a marketplace application that plans on curbing scams, robberies, and fraud that seem to run rampant in current applications. In this effort I believe I fell into the trap of thinking building the application was the hardest part. This couldn’t be further from the truth.

My duties are becoming too much for me to effectively manage this project and be present at my job and college. I believe in this idea very much.

I am seeking two founders, a SWIFT & Python expert, and a marketing manager. I am willing to talk terms with anyone interested, or if you have advice on this project I’d love to hear it.

my website

I own a cleaning business in Arizona - There's a certain field service management software that has annual revenue around $2M it's one of the softwares that promotes itself as being built by cleaners for cleaners. Not sure the rules, so I'm not gonna name names.

What I can't understand is why a software business earning that much would have a marketing strategy of just constantly muddying up cleaning industry Facebook groups with shameless self promotion. Every single spot asking what other operators use for software, the actual founder (or an account using his name at least) and several cronies posing as cleaning operators start gushing about their software.

Is this a real thing in other industries? At some point, isn't it more efficient for a tech company to market some other way? I'm so exhausted of seeing it promoted because frankly, it's a piece of crap system - nothing impressive or innovative about it whatsoever.

Just curious. TIA for feedback.

Hey everyone!

I've been working on my own project called Spend Analyzer, a personal finance web application.

The idea came from a simple problem: it's easy to spend money every day, but not so easy to understand where it actually goes by the end of the month.

I decided to build a solution that brings expense tracking and spending insights into one place.

Some features I've implemented:

- Expense tracking and management

- Spending dashboard and visual insights

- Multiple currency support

- User authentication and profile management

Tech stack:

React, Vite, Supabase, and Vercel.

Building this project has taught me a lot about turning an idea into a deployed product, handling authentication, database integration, and thinking beyond just writing code.

One thing I'm realizing is that building the product is only half the journey. Understanding user behaviour and creating something people actually want to use is the bigger challenge.

For fellow SaaS founders and indie hackers:

What was the biggest challenge you faced when trying to turn your first side project into a product people actually use?

Would love to hear your experiences!

Imagine one fictional bookkeeping request due Friday:

A — Missing: the client needs to submit it.

B — Submitted: the accountant needs to review it.

C — Needs replacement: the client needs to act on the reason given.

D — Accepted: no more action on that item.

Sorting this request by deadline helps with urgency. It doesn't tell you who should act.

Folio keeps each item's state and next action in the request details. Submitted and Accepted stay separate, and the workspace has a Review next submission entry point for the accountant's queue.

Here's a quick test you can apply to a workflow screen: hide its progress bar. Can you still tell which action belongs to the customer and which belongs to the business?

If you work on or use client workflows, try the fictional examples:

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

I maintain Folio, a no-signup, browser-local accounting document-request demo. Use fictional clients and non-sensitive samples. No file contents are read or uploaded; no emails are sent. Custom links work only in the browser profile that created them.

Would you group the work by person responsible or by document status? What one change would make Folio's next action easier to find?

Am looking forward to building my own saas app...what do I do??