A key that can only read

A revenue goal is only as good as the number behind it. To follow your real revenue, goalmrr connects to your payment provider. This post explains how that connection is kept small and safe.

Create a restricted key#

In the Stripe dashboard, you create a restricted key and give it read access only to balance, balance transactions and subscriptions. You paste it on the Revenue page of goalmrr. That is the whole setup.

Secret keys are refused#

If you paste a secret key, one that can write, goalmrr refuses it. The point is that the key you hand over can look but never change anything. A connection that cannot move money is a connection you can keep without worrying.

Stored encrypted, shown once#

The key is stored encrypted and is never shown again. One Stripe account connects to one workspace, so it is always clear which revenue belongs to which goal.

Fresh numbers, honest labels#

Your revenue refreshes every hour. If a number is older than 48 hours, goalmrr labels it stale instead of presenting it as current. A goal that follows real revenue should also tell you when it has lost sight of it.

Leaving is simple#

Disconnecting deletes the key. There is nothing to clean up afterwards.

Your own AI, with limits#

goalmrr is Bring your own AI on every plan. If you use an AI assistant, you connect it over MCP through the agent door of your workspace, and it acts with your permissions. It can read your goals and write updates. It cannot enter revenue, change a key or delete your data, and a change that makes something public needs your explicit confirmation.

From one sentence to a goal#

You start by writing your goal in one sentence, for example "10k MRR by 31 December". goalmrr reads the kind, the amount and the date, you choose the currency, and you get milestone steps and a prefilled first update. Connecting Stripe is the step after that, so the goal follows your real revenue.

To try it, request access.