Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

Opportunities are the problems, improvement areas, or leverage points your team may want to act on. They sit between learning and delivery:
  • More actionable than an insight
  • More problem-focused than a solution

​
What an opportunity is

An opportunity answers:
  • What is worth improving here?
  • What customer problem should we solve?
  • Where is there leverage if we act?
Good opportunities are still problem-led. They do not assume the solution too early.

​
Opportunity fields

Opportunities support:
  • Description
  • Status
  • Owner
  • Impact
  • Effort
  • Priority
  • Confidence

​
Impact

Impact uses a 1 to 5 scale. Use it to estimate the upside if the opportunity is addressed well.

​
Effort

Effort uses a 1 to 5 scale. Use it to estimate how hard it may be to address, considering product, engineering, design, support, or operational change.

​
Priority

Priority is the team’s current ranking:
  • High
  • Medium
  • Low
Priority is most useful after some comparison, not immediately on capture.

​
Confidence

Use confidence when the problem framing is still uncertain, even if the customer signal feels real.

​
Opportunity statuses

Opportunities use these statuses:
  • New
  • Framed
  • Prioritized
  • Parked
  • Closed
Recommended interpretation:
  • New: captured, but still rough
  • Framed: clear enough to discuss or compare
  • Prioritized: actively selected for attention
  • Parked: intentionally not active right now
  • Closed: resolved, no longer relevant, or intentionally retired

​
How opportunities should connect

Opportunities can link: This makes them the central bridge between customer learning and action.

​
Good opportunity examples

  • Reduce confusion before first integration
  • Shorten the time between signup and first teammate invite
  • Clarify billing recovery after failed payment
Weak opportunity examples:
  • Build setup wizard
  • Add button
  • Rewrite docs
Those are solutions, not opportunities.

​
How to leverage opportunities inside Custory

​
Prioritize with context, not ticket volume

Impact, effort, confidence, and linked insights help teams compare opportunities with more discipline.

​
Assign owners only when follow-through matters

For lean teams, owner fields work best when they represent real responsibility, not generic visibility. One problem can have several responses:
  • A product change
  • A docs change
  • A service workaround
  • A short-term experiment
Custory supports that without collapsing the problem framing.

​
Common mistakes

​
Turning every idea into an opportunity

If the item already assumes the answer, write it as a solution instead.

​
Using opportunity titles that are too broad

Improve onboarding is usually too large. Frame the actual leverage point.

​
Prioritizing without linked evidence

High priority means more when the reasoning is visible. Link the opportunity back to the insight that created it.