Add cloud_spend as required field on ICP for Enterprise tier

Introduce cloud_spend as a required firmographic on ICP objects for the Enterprise segment. 12 accepts, 3 rejects so far.

Voting

Summary

Enterprise ICPs consistently include cloud_spend as a top-3 firmographic. Today it lives as a loose custom attribute across workspaces, so no adapter maps it consistently and no prompt can rely on it.

This proposal promotes cloud_spend to a first-class ICP field for the Enterprise tier, with a canonical unit (USD, annualized) and a documented derivation path when the provider only exposes ranges.

Proposed changes

ICP.cloud_spend

Before

undefined

After

required (number, USD annualized)

ICP.cloud_spend_source

Before

n/a

After

enum(provider|self_reported|derived)

Discussion

4 comments

Sarah Kaur2h ago

Rolled the derivation table into the RFC. Feedback welcome on the AWS→estimated-spend mapping.

Marcus Tan4h ago

Apollo maps to a bucketed range. Suggest a canonical bucketing helper before we require the raw number.

Elena Rossi1d ago

+1 with the bucketing helper. Prompts that use cloud_spend today assume USD annualized, which not every provider gives us.

Nash Delarosa1d ago

Fine to ratify once the derivation table is in. Breaking-change window should be two minor versions.