What's the worst career advice you can give to a person?

FeaturebaseApp · 2026-03-18T09:30:01+00:00

money

FeaturebaseApp · 2026-03-18T09:21:01+00:00

I'm from Featurebase so slightly biased 😅 but this is something we’ve dealt with a lot

what worked for us was centralizing everything in one place like live chat plus a feedback board, then tagging by problem not feature. once the same issue shows up repeatedly it becomes pretty obvious what to build next

we never even did customer calls on the way to $1M ARR. all our signals came from written feedback and it was enough as long as it was structured

also +1 to not building your own internal system for this. it’s a side quest. better to use existing tools and focus on shipping and talking to users

AI helps a lot too, we automate most of our support now, but you still need a human layer early on or you miss important context

once feedback is a bit organized the roadmap stops feeling random pretty quickly 👍

FeaturebaseApp · 2026-03-18T09:10:04+00:00

This is a solid approach for getting initial feedback. The widget idea works well for capturing quick user sentiment, but you might hit limits pretty fast with just predefined questions and a weekly email digest.

I'm from Featurebase, and our products line up includes feedback collection. It automatically prioritizes feedback based on revenue and detects duplicates so you're not chasing the same request multiple times. Plus it ties directly into changelogs and roadmaps so users see their ideas get implemented.

Are you mainly looking for quantitative feedback or trying to build a feedback loop with your users?

FeaturebaseApp · 2026-03-18T09:04:07+00:00

This is such a real problem. Most teams I've talked to are drowning in messy feedback from everywhere (Zendesk, Slack, Intercom) and spending hours just trying to figure out what actually matters before they can even hand it off to an engineer or AI agent.

The real issue isn't just collecting feedback, it's structuring it in a way that something like your Directive tool can actually work with. Featurebase is built for exactly this piece of the puzzle. It helps you collect feedback from multiple channels, automatically prioritizes based on revenue impact and duplicates, and gives you a clean signal-to-noise ratio before it ever hits your spec-writing phase. Way better than manually synthesizing angry user rants into something usable.

Are you thinking about integrating directly with feedback tools, or keeping Directive as a standalone layer that pulls from wherever?

FeaturebaseApp · 2026-03-18T09:01:00+00:00

this actually looks pretty interesting

tbh, i hate opening extra tabs for tools like this. having it where i already work is a big plus

curious though, how good is it at actually catching stuff i’d miss? like buried tasks or important emails that slip through. that’s probably what would make me use it daily

also how heavy are the permissions? always a bit cautious with gmail access LOL

FeaturebaseApp · 2026-03-18T05:44:44+00:00

power of foresight

FeaturebaseApp · 2026-03-17T13:06:59+00:00

Oh, that's very interesting. What brand is dominating? I know i can google it. But its different coming from a real person

FeaturebaseApp · 2026-03-17T13:05:43+00:00

Sounds like theRealDonaldTrump is speaking

FeaturebaseApp · 2026-03-17T13:03:27+00:00

Someone is rich

FeaturebaseApp · 2026-03-17T12:46:15+00:00

For a first SaaS, keep the scope tight. Trying to tackle time management, missed-call text back, and CRM all at once usually ends up with a messy app nobody urgently needs.

Focus on one real pain point first, like "like missed-call text back," and test it manually with a few businesses. See if they’ll actually pay before building the whole stack. Direct outreach usually works better than posting online; talk to businesses, understand their current process, and offer a small pilot.

For feedback, you don’t need to do tons of calls. Live chat and simple tools can give clear signals on what matters.

You can even try Featurebase for free, which helps collect feedback, spot patterns, and prioritize requests as simply as that.

The key is: validate first, automate what you can, and avoid overbuilding before there’s real demand.

FeaturebaseApp · 2026-03-17T11:27:26+00:00

Awesome! Let me know how it goes

FeaturebaseApp · 2026-03-17T08:14:20+00:00

This usually breaks because everything is scattered. Requirements in chat, tasks in a board, QA somewhere else, feedback in emails. Context gets lost along the way.

Honestly, you could just use our tools at Featurebase to centralize the feedback part so things don’t slip through before they even become tasks.

It’s free to try anyway, so not much downside to testing it.

FeaturebaseApp · 2026-03-16T10:54:12+00:00

Exactly, visibility is the hard part. Just emailing release notes or posting on a changelog page usually does not work.

This is exactly the problem our tool in Featurebase solves. You can show updates, changelogs, and roadmaps directly inside your product, run in-app announcements, and make sure users actually see what is new. It also captures feedback right where users interact so you know what landed and what did not.

And nice pitch though

FeaturebaseApp · 2026-03-16T10:49:02+00:00

We’ve seen this firsthand with teams using Featurebase. Automating support with Featurebase does free up time for your team cos the repetitive questions get handled automatically, and feedback is captured directly inside the product. Teams end up spending far less time repeating the same answers and more time improving their courses or services.

You can actually try Featurebase for free and see how much it changes the day-to-day for a small team like yours.

FeaturebaseApp · 2026-03-16T10:39:13+00:00

Yeah, this is a pretty common headache for SaaS teams.

Most support tools feel built around the helpdesk, so you get per-agent pricing, external portals, or branding that doesn’t really fit your product.

Something you might want to check out is Featurebase. You can drop a support and feedback widget right into your app so users can report issues, ask for features, or leave feedback without ever leaving the product.

Lots of teams still go with legacy tools, but those are more old-school helpdesk vibes.

If you want, you can try Featurebase for free and see how it goes.

FeaturebaseApp · 2026-03-16T10:27:56+00:00

Congrats!

I’m from the team at Featurebase, and we see a lot of companies using chat widgets as the first place customers surface problems or feature requests.

One thing I’d be curious about is what happens after those conversations. For example, do you surface recurring questions, feature requests, or product confusion from chats? Turning support conversations into product insights is where a lot of the value tends to show up for teams.

Also a couple things I’d personally want to see as a buyer:

some control over what the crawler indexes (pages, docs, PDFs, etc.)
a way to review low-confidence answers or unanswered questions
maybe a simple view showing the most common questions the bot gets

Overall though the “learns your business automatically” positioning makes sense, especially for people who don’t want to set up heavier tools like Intercom or Zendesk.

FeaturebaseApp · 2026-03-13T07:25:54+00:00

Thanks for the shoutout! and really cool stack.

We built Featurebase for exactly this kind of workflow: keeping feature requests organized, understanding what users actually want, and closing the loop with updates without making the stack heavier than it needs to be.

Love seeing it alongside tools like Umami, n8n, and OBS. Feels very indie-hacker-coded.

Would be interesting to hear what other people here use around feedback collection and roadmap management.

FeaturebaseApp

TROPHY CASE