Opportunities are the entry point of the Kowalah funnel. Anyone in your organization can capture one, in their own words, through the channel they already use. Each Opportunity is scored on Impact, Confidence, and Ease, triaged by your Kowalah team, and then either promoted into a Deliverable inside a project, raised as an Expert Request, or set aside for later.Documentation Index
Fetch the complete documentation index at: https://docs.kowalah.com/llms.txt
Use this file to discover all available pages before exploring further.
Where Opportunities come from
A Discovery
The structured way: Kowalah invites a cohort, and ideas come in through the enabled channels during the Discovery window.
The Kowalah Agent in chat
Anyone can
@Kowalah in Slack, Microsoft Teams, or Google Chat and describe an idea — it lands as an Opportunity in the platform.Directly in the platform
Capture an idea straight from the web — useful when you’re already in the platform and want to log it before you forget.
Created on your behalf
Your Kowalah partner can capture an Opportunity on your behalf, for example after a phone conversation or an inbound email. The Opportunity records who it was raised for and who raised it.
Opportunities don’t have to belong to a Discovery. Free-floating Opportunities — ones raised outside any active Discovery — are just as valid, and follow the same triage and promotion path.
What an Opportunity contains
Each Opportunity captures:| Field | What it’s for |
|---|---|
| Title | A short, plain-English headline |
| Content | The fuller description, in the submitter’s own words |
| Source | Where it came from — Discovery, agent (Slack / Teams / Google Chat), office hours, training, email, manual, or other |
| Department | Optional, helps with later filtering and rollups |
| Discovery | The Discovery this Opportunity came from, if any |
| Submitter | The person who raised it (or the customer it was raised on behalf of) |
| Score | An ICE score — Impact, Confidence, Ease, plus rationale |
| Status | Where the Opportunity is in the triage flow |
| Owners | A customer owner and optionally a Kowalah owner |
Triage flow
Opportunities move through a small number of states. Most of the work happens in the first two.| Status | What’s happening |
|---|---|
| New | Just arrived; not yet reviewed |
| In review | Your Kowalah team is triaging — refining the score, asking clarifying questions, deciding the right next step |
| Promoted | Promoted into a Deliverable or an Expert Request — the Opportunity now has a child entity it points to |
| Declined | Reviewed and explicitly set aside, with a reason recorded |
| Merged | Merged into another Opportunity that’s substantively the same idea |
Scoring
Every Opportunity carries a single live ICE score — three numbers (Impact, Confidence, Ease), each on a 1 to 10 scale, with a composite that’s their sum. Unlike Deliverables and Expert Requests, Opportunities don’t have an estimated-vs-final pair. The work hasn’t started yet, so the score is just the current best read on whether the idea is worth promoting.Kowalah’s AI takes the first pass on most Opportunities — particularly ones submitted through Slack, Teams, Google Chat, or email — so the triage queue is never empty when your Kowalah team logs in. Humans then refine.
Promoting an Opportunity
Promotion is the moment an idea becomes committed work. There are two paths.Promote to a Deliverable
For ideas that need design, build, or rollout work inside a Kowalah-managed project. The new Deliverable carries a back-link to the Opportunity.
Promote to an Expert Request
For scoped, standalone pieces of work — a single Claude skill, a workshop, a one-off audit. The Expert Request carries the same back-link.
- Promoted at — the timestamp
- Promoted by — who made the call
- Promoted to type —
deliverableorexpert_request - Promoted to ID — the child entity it became
Customer-requested promotion
Customers can flag an Opportunity for promotion themselves, without needing to wait for triage. This shows up as a requested promotion: the Opportunity records what the customer asked for (deliverable or expert request), and into which project — but the actual promotion still happens through Kowalah’s triage flow, so the score and scope can be sanity-checked first.This pattern keeps customers in the driver’s seat without bypassing the quality bar: you can always say “this one, please, into this project,” and Kowalah handles the rest.
Merging duplicates
When the same idea arrives from two different people — the same hour saved, the same workflow automated — you can merge one Opportunity into another. The merged Opportunity recordsmerged_into_opportunity_id so the trail is preserved, and the surviving Opportunity gets the combined context.
Identifier
Every Opportunity gets an ID likeOPP-0001, scoped to your organization. You’ll see this on the Opportunity page, on any Deliverable or Expert Request promoted from it, and in any chat or email referring to it.
What’s next
ICE Scoring
How Opportunities (and Deliverables and Expert Requests) are scored
Discoveries
Time-bounded campaigns that surface 20-30 Opportunities at once
Deliverables
What Opportunities become when they’re promoted into project work
Expert Requests
What Opportunities become when they’re promoted into standalone expert work