Strategies for Monetising Trello Power-Ups
|5 min read

Strategies for Monetising Trello Power-Ups

A Power-Up's pricing scope should follow the value it delivers per user. How to choose between per-user, per-board, per-workspace, and per-seat models.

SC

Sean Cooper

Engineering Team Lead at Salable. Building the future of SaaS billing infrastructure.

When a customer subscribes to your Power-Up, how do you determine who gets to use it? The individual user who paid, everyone on the board, or every member of the workspace? Your choice affects your pricing strategy and may cap your earning potential.

There’s no one answer. The right scope follows from how much value each user gets. Trello is a collaborative tool, and a Power-Up lives inside other people's workflows, so every scope decision is also a question of how much value to capture from each person who benefits.

Value Depth Sets the Model

Choose your pricing scope by asking what kind of value your Power-Up delivers and who gets it.

Power-Ups that change how a team works (cross-functional planning, shared analytics, and workflow automation that every teammate touches) sit at the heavy end of per-user value. Each team member gets enough value that charging per head is fair and sustainable. Per-seat pricing also lets you grow with the account: a five-person team paying $10 per seat becomes a fifty-person team paying $500 without any plan change, and your revenue expands with the customer's adoption. For collaboration multipliers, per-seat is the natural model because the price scales with the value each user gets.

At the other end sit lighter team enhancements: a better date picker, a reporting view, or a specific integration. These are useful, but few team members will notice them. For a Power-Up in this band, per-seat billing introduces friction that works against you. Procurement complexity, user tracking, and per-head price justification all become harder to defend when the per-user value is modest. Flat per-board or per-workspace pricing trades per-seat revenue for adoption velocity. One admin makes a single purchase, the whole team gets the feature, and your pricing page can quote "$49 per workspace per month" and move on.

The last category is personal utilities: tools that help one person, regardless of who else is on the board, such as private notes, a personal dashboard, or a timezone helper. These fit individual per-user subscriptions that follow the paying user across every board they touch. While the average revenue per customer is lower than in team-based models, these plans are typically cheaper and can sell in higher numbers thanks to frictionless, self-serve adoption, allowing buyers to complete a purchase without talking to sales.

The more concentrated your per-user value, the more you can charge per user; the more diffuse but broad your team-wide value, the more you should lean on flat scope pricing to maximise reach.

Choosing Your Anchor

Each scope keys to a different Trello identifier and fits a different kind of Power-Up. Per-user, individual pricing keyed to the member ID fits personal utilities where the buyer is the end user and their subscription needs to follow them across every board and workspace they touch. Per-board, keyed to the board ID, fits Power-Ups tied to a specific board's workflow (release trackers, client-specific dashboards, and board-local integrations) where the buyer is a board admin, which matches how people already think about Power-Ups, since they're turned on board by board. The trade-off is that teams with many boards pay many times, which gets annoying as the team grows.

Per-workspace pricing comes in two flavours. Flat per-workspace is where lighter enhancements earn the most: one admin pays, everyone in the workspace gets access, and you price for what the buyer will pay, not the sum of what each user gets out of it. Per-workspace with per-seat pricing charges by the number of people using it, which fits the heavier collaboration tools where every user gets real value. Per-seat is more work to maintain (you need to keep the seat count accurate as people join and leave), but the price grows with the value.

How Salable Fits the Scope You Choose

Salable provides generic billing primitives. Owners scope subscriptions, Groups collect Grantees under an Owner, and Grantees are the individual identities that receive access. Whichever Trello identifier you've anchored your pricing to (member, board, workspace) becomes the Owner in Salable, and your commercial scope decides how the primitives compose.

For per-user pricing, Owner and Grantee are the same: the member ID. Per-board billing makes the board ID the Owner, with board members as the Grantees. Per-workspace makes the workspace ID the Owner and workspace members the Grantees; per-seat pricing caps the Group at the seat count.

Salable's primitives are generic; they don't know about Trello. Your Power-Up owns the mapping: you add Grantees to Groups when Trello members join a workspace, remove them when they leave, and raise seat caps when the team grows. In return, Salable gives you the billing state machine, seat-cap enforcement, proration when you change quantities, and a single-call entitlement check you can make from inside the Power-Up. You keep the commercial decision: which Trello identifier is the Owner, and so what your customer is paying for.

Start from the Value

Start from how much each user gets, and let the scope follow. Deep per-user value earns per-seat pricing; broad but shallow team value earns flat-scope pricing; solo value earns individual subscriptions. Start narrower than you think you need to, and widen as customers pull you there. Adding a workspace tier to a per-user product is easier than rescoping an established per-workspace product when individual users start asking for plans of their own.

Share:

Building a Trello Power-Up?

Connect with other Power-Up developers sharing lessons on building and getting paid.

Join Discord

Related Posts

Try Salable Today

Monetise your Power-Up with flexible pricing—flat-rate, per-seat, or usage-based.