2026 Q2 in review: MRR-weighted prioritisation
It would let us retire an internal tool nobody wants to maintain. The workaround breaks as soon as a second person is involved.
Before you start
This has come up in three separate customer calls this month. It is the single biggest reason our team still keeps a second tool open.
Before you start
Right now this costs us roughly two hours a week. We would stop exporting to a spreadsheet every Friday. Customers ask about this on nearly every onboarding call.
How it works
It was the first thing our new hires tripped over. We raised this during the pilot and it is still the main gap. It would pay for itself in the first month.
- Enable keyboard shortcuts.
- Enable a Linear two-way sync.
- Enable custom domains.
- Enable internal notes.
curl -sS https://api.example.test/v2/posts \
-H "Authorization: Bearer $BULLETIN_API_KEY"
Next steps
Two people on the team have independently asked for this. We would stop exporting to a spreadsheet every Friday.
What changes
The workaround breaks as soon as a second person is involved. This blocks the quarterly report we send to the exec team.
- beta