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.

Solutions are the responses your team is considering, planning, shipping, or validating. They can be product changes, experiments, process changes, content, or service interventions. Custory keeps them connected to the opportunity they are meant to address.

​
What a solution is

A solution answers:
  • What are we going to do about this?
  • What experiment or change should we try?
  • What shipped response should we now validate?

​
Solution types

Custory supports these solution types:
  • Idea
  • Experiment
  • Feature
  • Process
  • Content
  • Service
This is valuable for smaller teams because not every customer problem needs a product feature. Sometimes the right response is support design, onboarding content, or an internal process fix.

​
Solution fields

Solutions support:
  • Description
  • Status
  • Owner
  • Solution type
  • Impact
  • Effort
  • Priority
  • Target date

​
Owner

Use owner when someone is responsible for moving the solution forward.

​
Impact and effort

Use these the same way you would in prioritization work:
  • Impact reflects likely upside
  • Effort reflects cost or complexity

​
Priority

Use priority to sequence solution candidates, especially when several approaches could address the same opportunity.

​
Target date

Use target date when the solution has a real planning horizon. Leave it empty when the item is still too early.

​
Solution statuses

Solutions use these statuses:
  • Idea
  • Proposed
  • Planned
  • In progress
  • Shipped
  • Validated
  • Rejected
Recommended interpretation:
  • Idea: possible response, still early
  • Proposed: concrete enough to discuss seriously
  • Planned: committed into near-term work
  • In progress: actively being delivered
  • Shipped: released or implemented
  • Validated: demonstrated to have solved the intended problem
  • Rejected: intentionally not moving forward

​
How solutions should connect

Solutions link: This matters because “shipped” is not the same as “worked.”

​
Good solution examples

  • Add a guided setup checklist for new workspace admins
  • Run an onboarding email experiment after team creation
  • Rewrite failed-payment copy with a clearer retry path

​
How to leverage solutions inside Custory

​
Keep multiple solution candidates visible

Do not collapse options too early. Custory works well when the team can compare several possible responses to the same opportunity. If success has no visible metric, solution review becomes opinion-heavy later.

​
Use solution type to widen thinking

Founder-led teams often default to features. The solution type field is useful because it reminds the team that content, process, and service can solve real customer problems too.

​
Common mistakes

​
Creating solutions with no linked opportunity

That usually produces feature drift. If the problem is not visible, the solution becomes harder to defend later.

​
Treating shipped as finished

Shipped should usually lead to validation, not closure.

​
Mixing scope decisions into the title

Keep the title clear and actionable. Save the debate about implementation detail for comments, linked tasks, or follow-up discussion.