1 min read

Why we called it "Guides"

A dashboard is something you glance at. A snapshot is a moment in time. But a guide has a job. It's useful, it's intentional, it meets you where you are and shows you what matters.

Screenshot of a custom Guide built in Kerdora
Screenshot of a custom Guide built in Kerdora

We didn't start with the name. We started with a question: what does this feature actually do?

It helps advisors do the two things Kerdora exists to do, help clients:

  1. Understand their financial life, and
  2. Know what to do next.

A guide does that. Not a dashboard. Not a snapshot. A guide.

A dashboard is something you glance at. A snapshot is a moment in time. But a guide has a job. It's useful, it's intentional, it meets you where you are and shows you what matters.

It's also flexible enough to match the feature itself. A guide can be an explainer. A step-by-step plan. A visual overview. A tactical checklist. That range matters because every client needs something different.

The name also works in conversation, specifically, in conversation with your clients.

  • "Check your main guide"
  • "Go to your liquidity guide"
  • "Take a look at your Q4 review guide"

It fits. It's natural. It tells the client exactly what they're looking at and what it's for.

So that's why we called it Guides. Not because it sounded good in a product meeting, but because it sounds right when you're sitting across from a client.

Subscribe to my newsletter

Subscribe to my newsletter to get the latest updates and news

Member discussion