Pricing model
Subscription-based with plans confirmed per engagement. Self-serve team tiers, sales-led engagement for enterprise procurement. Pricing is transparent within one /contact reply — fees do not float with your SaaS spend line.
Where Blissfully lands — Concierge / per-vendor SaaS management fee model. Pricing scales with the SaaS spend under management rather than a flat platform fee — the bill grows with the spend base, not with a fixed license.
Why it matters — A per-vendor fee on top of your SaaS spend is a tax on growth — every vendor finance adds increases the cost of Reclamp. A flat platform subscription lets you run the reclaim loop without paying the platform an additional percentage on the spend under management.
AI-native vendor coverage
The benchmark corpus is built for the AI-vendor tail by design — model APIs, inference, vector DB, eval tooling, agent frameworks. The benchmark feed tracks AI-vendor pricing percentile data so a price drop surfaces in a finding before the next renewal lands.
Where Blissfully lands — Coverage centers on traditional SaaS categories — collaboration, marketing, security, infrastructure. The long-tail AI-native stack (per-token model API spend, inference, embedding, agent tooling) is not a primary corpus; deals flow through human analysts.
Why it matters — The highest-growth line item in most SaaS bills in 2026 is the AI-vendor tail — model APIs, inference, eval, and agent tooling billed by token or by seat. A tool that does not track this category reads most of the new spend as a flat invoice line, not as a benchmarked concession lever.
Autonomous renegotiation
AI-drafted, tone-matched counter-offers written from in-corpus benchmark concessions. The agent drafts; a named human on your team signs off in the /app/approvals queue before anything reaches a vendor. The full chain — draft, sign-off row, vendor reply, dollar landed — is a counter-signed record, not a dashboard aggregate.
Where Blissfully lands — Human-analyst-led renegotiation. Blissfully assigns a named account manager who reviews the stack, flags savings, and handles vendor outreach manually. The loop runs on analyst time and a procurement queue behind a calm UI.
Why it matters — A human-analyst loop is implementation-by-procurement — the speed of the draft is bounded by the size of the team behind the UI. An autonomous agent loop runs on a continuous cadence: the draft lands in the approvals queue whether your analyst had bandwidth this quarter or not, and the human sign-off row is the audit trail.
Dashboarding
Findings ranked by reclaim dollar against implementation effort. Audit log generated from the same Postgres the agent writes to — no separate system of record, no event-stream export outside the workspace. Audit exports ready for the next quarterly review.
Where Blissfully lands — A polished SaaS-management dashboard with spend visualization, vendor inventory, and renewal calendar features. Visibility is the strong suit; the dashboard is a read view over a stack the analyst team runs the loop on.
Why it matters — A dashboard that visualizes spend is a visibility tool — finance still negotiates by hand. A dashboard that is one view over the same Postgres the agent writes to is what supports the audit claim (the procurement review asks "show me the dollar landed on the next invoice").
Time-to-value
Connectors land on day one — directory (Okta / Azure AD / Google Workspace) plus one spend source. First surfaced savings typically arrive inside 30 days, usually duplicate-license and dormant-seat finds. First priced-out renewal renegotiation usually lands within the first 60–90 days.
Where Blissfully lands — Implementation is gated by the engagement shape. Concierge SaaS-management onboarding typically runs on a longer arc — analyst review of the stack, vendor consolidation, and a renewal cycle — before named savings are visible on a named contract rather than an aggregate.
Why it matters — A buyer-evaluation horizon is rarely longer than two quarters. A tool that needs an entire fiscal year to land "named savings on a named contract" is not a tool a CFO can defend at the procurement review — it is an engagement one.