Custom functions and integrations. Connecting the platform to the systems you already run — your internal API, the legacy database, the vendor portal nobody ever built an integration for. This is what most customers use it for, and it's what turns a capable platform into one that fits how you actually work.

Weight on the roadmap. Points apply to what we build next. Ask about a feature, a user story, or a bug and we'll scope it properly, so you know what it takes before you commit anything.

Apply points and it moves up the queue. Cover its full size and it stops being a priority and becomes a commitment — scheduled for a named release, with a date you can plan against.

Points pool. If other customers want the same thing, their points count toward the same total. Backing part of something is often enough to get it built.

How ownership works. Custom work is jointly owned and reusable. That means it lives in the product rather than in a fork of it — maintained, upgraded, and supported like every other feature, at no ongoing cost to you. It's also why we can include development points at all: the work compounds into the platform instead of fragmenting across it.

Points accrue every month and bank across the year, so you can save toward something larger rather than spending them as they arrive. Whatever's unused at year end doesn't carry into the next one.