Product Feature Requests

Every Monday at 8am, review the customer calls and emails from the
last 14 days. Identify the features and capability gaps customers asked
about or said were missing. Group them, and for each one list the accounts
that raised it and the open deal or renewal value behind those accounts.
Rank by total value. Post the report to the #product channel.

Feature Requests — Aug 1 to Aug 14
48 calls and 74 email threads reviewed · 17 accounts

Ranked by revenue behind the request

1. Scheduled report delivery to a distribution list — $296K
   4 accounts. Raised as a blocker in 2 of them. The pattern is consistent:
   buyers want a weekly report a VP reads without an analyst rebuilding it,
   and per-user delivery is what breaks that.
   Already tracked: yes, one open issue.

2. SSO and SCIM provisioning — $210K
   3 accounts, all enterprise. In one deal it is a procurement requirement
   rather than a preference, and that deal is in commit.
   Already tracked: yes.

3. Run without email access — $155K
   3 accounts, all regulated. New in this window. Framed as a compliance
   constraint, not a feature preference, which means a workaround may
   matter more than a roadmap item.
   Already tracked: no.

4. Historical backfill beyond the current window — $84K
   2 accounts. Both raised it during evaluation, neither called it a
   blocker.
   Already tracked: yes.

Raised once, no revenue attached yet
Custom field mapping on import (1 account, no open deal). Bulk export
(1 account, renewal in Q1).

Worth noticing
Requests 1 and 3 both come from the same underlying constraint: customers
wanting the output to reach people who are not users of the product.

Using the Clearskies Context Graph, review the feature requests and gaps
customers raised in the last 90 days.

For each one:
- What they asked for, in their words
- Which accounts raised it, and the open deal or renewal value behind them
- Whether it was framed as a blocker or a preference
- Whether it came up before or after they saw the product

Rank by total revenue behind the request. Separate blockers from
preferences.

Quote customers directly. Do not translate a request into our roadmap
vocabulary, because that hides whether two accounts asked for the same
thing or two different things.