Talk to an Expert
← AI Pricing Observatory

// AI PRICING OBSERVATORY

The Observatory · Weekly · Slack

The Observatory in your Slack.

One message a week, in the channel you choose: the pricing moves that cleared verification that week, each with a one-line read.

Mondays, and only in a week where something moved. A quiet week posts nothing. Every move is checked against a primary source before it ships, and the read underneath it is approved by Chris Mele before it goes out.

01 · What arrives

One message a week, and only when the record moved.

The digest is the Observatory’s weekly register, delivered to a Slack channel instead of an inbox. Each Monday it carries the moves verified in the prior week: a dated headline and a one-line read for each, with a link back to the full page. No full reads, no history, no filters in the message; those stay on the Observatory.

A move earns a place in the channel the same way it earns a place on the page. Primary or corroborated sourcing, verified faithful to the vendor’s own statement, and evidenced as a transition: the dated event plus what the terms said before it. A change on a pricing page that cannot clear that bar never reaches the channel, whatever attention it is getting elsewhere.

Cadence Mondays, around 09:05 ET. A week with no verified move posts nothing at all.
The unit One dated headline and one line of read per move, each linking back to the full read on the page.
The gate Primary-source verification and a recorded before-state, the same gate the page itself runs.

02 · Privacy

Three things stored. Nothing else read.

Installing the app grants it one permission: posting into the channel you choose. That is the whole footprint, on Slack’s side and on ours.

What we store Your workspace name, the channel you chose, and one delivery webhook for that channel. The webhook is a posting address, not a key to the workspace.
What we never see Messages, members, files, other channels, or anything else in the workspace. The app holds no read permission and asks for none.
Uninstall

Remove the app in Slack. Deliveries stop and the webhook dies with it; nothing on our side keeps a way back into the workspace.

03 · Other channels

Prefer email. Teams follows.

The same weekly register goes out by email. It is the channel the Observatory has always had, and the one to take if Slack is not where your team reads.

The register also lives on the Observatory page, next to the record it covers.

Microsoft Teams is sequenced after Slack. Until it ships, the email register is the Teams path.

04 · Questions

Questions we get about the digest

One message each Monday listing the pricing moves verified in the prior week: a dated headline and a one-line read per move, each linking back to the full read on the Observatory page. Nothing else is posted, and nothing is posted in a week with no verified move.
Because nothing cleared verification that week. The digest is silent by design when the record has not moved; a quiet Monday is the ledger holding still, not a delivery failure. Slack lists the app under the channel’s integrations for as long as it is installed.
Three things: your workspace name, the channel you chose, and one delivery webhook for that channel. It requests a single permission, posting into that channel, and holds no read access to messages, members, files, or any other channel.
Remove the app in Slack. Deliveries stop and the webhook dies with the removal; nothing on our side keeps a way back into the workspace.
Not yet. Teams is sequenced after Slack. Until it ships, the email register carries the same weekly digest, and it is open now on this page and on the Observatory.

05 · Your own pricing

The digest is the record. Your own pricing still needs its own read.

The Observatory tells you what other software companies did, verified and dated. What your company should do with the same moves depends on your own licensing, packaging, and pricing, and that read does not fit in a Monday message. Bring the situation and a pricing expert reads it with you.