How do I get started with Pilea?

Welcome to Pilea

This guide shows you how to get your first actionable insight from Pilea in 15 minutes, what success actually looks like (hint: it's not perfect organization), and how to avoid the common setup mistakes that make people give up before they see value.

The short version

Pick one feedback source (Slack, support tickets, or interview notes)
Connect it to Pilea and ask "What are users asking for most?"
Share that insight with one teammate
That's your successful first day

Why feedback gets overwhelming (and why it's not your fault).

You became a product manager to build great products, not to spend weekends sorting through spreadsheets of customer comments. But somehow that's where you ended up. The problem isn't that you're bad at organizing feedback—it's that feedback comes from everywhere and nowhere has taught you how to handle it at scale.

The 3 things you need before touching any settings.

Before you start connecting tools or uploading files, answer these questions:

Where does most of your customer feedback currently live? (Slack, support tickets, interview notes)
Who on your team actually makes decisions based on customer input?
What's one product decision you're trying to make right now?

Having clear answers prevents you from importing everything and getting overwhelmed on day one.

Your first 15 minutes: One source, one insight.

Pick your biggest source of feedback and start there. If your team talks about customers in Slack, connect Slack. If you have a folder of interview transcripts, upload those. Don't try to connect everything—just pick one.

Upload or connect your chosen source, then ask Pilea: "What are users asking for most?" You'll get an answer in about 30 seconds. That's your first real insight.

What success looks like.

You know you're on the right track when you can answer: "Based on customer feedback, what should we work on next?" without opening five different tools or asking around the office.

Success isn't having perfect data organization. It's having enough clarity to make your next product decision with confidence.

Common "did I break something?" moments

Upload taking longer than expected? Normal for large files.
Not seeing feedback immediately after connecting Slack? Check that you're looking at the right time range.
AI suggestions seem off? It needs a few examples to understand your product context.

Simple next step

Take the insight you just found and share it with one person on your team. Ask them: "Does this match what you're hearing too?"

That conversation is more valuable than connecting three more data sources.