I am genuinely trying to figure out how other product folks handle this. You run feedback through an AI. You get a summary. Sure. But what are you still doing before that result drives a real product decision? We never know if we are missing some obvious step in our own daily workflow.
When I first started developing MindNote, it took the entire development period to reach around 2,000 authentication requests.
Last month alone, the product received 1,200.
For a solo founder building an AI product, seeing that change in the numbers feels encouraging. But it also raises a question: what does that activity actually tell me?
MindNote is a multimodal AI notetaker. The idea is to help people turn information from meetings, voice notes, videos, images, and text into organized, searchable knowledge they can actually use.
The product is live, and I’m continuing to improve it while figuring out how to turn interest into consistent usage and paying customers.
I know authentication requests don't necessarily mean unique users. They could include repeat attempts, returning users, or other activity. I'm trying to understand the signal rather than celebrate a vanity metric.
For founders who have been through this stage:
I'd love to hear what worked for you, especially if you're building a SaaS or AI product as an indie founder.
Hey everyone,
I’m looking to connect with early-stage, high-growth startups building something genuinely exciting.
3 years of experience. Over the last ~1.5 years, I’ve operated across GTM systems, solutions engineering, and sales pipeline architecture across ~7 technical B2B/SaaS accounts.
Instead of generic manual prospecting, I build automated, signal-driven engines that connect buying intent directly to revenue:
Signal-Based Revenue Outbound: Triggering outreach based on live market signals (tech stack shifts, hiring triggers, executive moves, and intent spikes) using Clay waterfalls, n8n automations, and custom Apify scrapers syncing directly into modern CRMs like Attio and HubSpot.
Hiring & Strategic Channel Outbound: Building outbound sourcing engines for hard-to-hire technical roles, strategic partnerships, and pre-/post-event conference pipelines.
Results: Across my work, this infrastructure has driven a 4.5%–7% positive response rate, influenced $7M+ in qualified pipeline, and directly generated $120k+ in closed revenue.
I thrive in fast-paced, high-agency environments where I can roll up my sleeves and build systems from scratch.
I’m ready to commit fully, bring extreme energy, and would love to work on-site/in-person (open to relocation and looking for teams open to US visa sponsorship).
Comment your company name and what you’re building, if it aligns with what I feel is interesting and I can give my all to, I will DM you.
I’m building a B2B SaaS for a specific niche within field services. I have access to a business owner in that niche who can test it and provide feedback.
I’m keeping the exact niche private for now, but some of the core functionality could also be useful to other service businesses.
Would you focus the product and marketing entirely on that one niche until you get traction, or build for a broader audience from the beginning?
I see the benefit of solving one industry’s problems really well, but I’m wondering whether I’m limiting the potential too early.
For anyone who’s faced this decision, what convinced you to stay narrow or expand? Would love to hear actual experiences.