Features Get Built When
Enough of You Want Them.
Somebody asks for a feature. We scope it properly and publish the whole specification in the open, including the cost. Back On Stage covers half. If enough bandleaders fund the other half, it gets built and it ships to everyone.
Miss the target and every backer is refunded in full. Nothing gets built and we say so publicly.
Your feature is real. It is just not everybody's feature.
Every roadmap has the same problem. A handful of bands hit a specific piece of friction that genuinely costs them hours, and it never gets built, because it will never outrank what the whole customer base needs next. It is not that the request was bad. It is that ten bands cannot outvote a thousand.
The Build Board is how a smaller group moves their thing up the list without waiting for it to become everyone's problem.
And when it ships, it ships to every customer on a qualifying plan, backer or not.
We publish the spec
The full Statement of Work goes public before a penny is taken. What gets built, what is deliberately left out, the technical risks, and the real cost.
You back it, and you shape it
Contribute from $100. For the first fourteen days backers argue with the spec and change it. Then it locks and republishes as final.
It gets built, or you get refunded
Hit the target inside thirty days and development starts. Miss it and every backer is refunded in full.
On the board right now.
One campaign runs at a time, so the board never asks you to choose between two things you want.
One-Tap ForScore Setlist Export
Fully FundedEvery musician pulls their own part, in set order, as one file that opens straight into forScore. You build the set once in Back On Stage and then you are finished. No downloading chart by chart, and nothing for the bandleader to send.
What goes up next
Open for requestsThe board takes one campaign at a time and the next one is not chosen yet. If there is a piece of friction costing your band real hours every week, tell us. The ones that get scoped are specific, and they are the ones several bands hit independently.
- Be specific about the job, not the solution
- Tell us roughly what it costs you in hours
- Tell us if you know other bands with the same problem
All of them, in public,
before you pay anything.
There is no version of this where you find out the terms afterwards. Here is the whole model.
- You are charged upfront. If the target is not met, you are refunded in full. Not credited. Refunded.
- The minimum is $100, and there is no maximum that matters, because a campaign closes the moment it hits target. Overfunding is not possible here.
- A campaign runs thirty days. It funds or it does not.
- A near miss is a miss. There is no ninety percent rule. If a campaign falls short it is published as a failure and everyone is refunded.
- You get a say in the spec. For the first fourteen days backers argue with the Statement of Work and change it. This is not decorative: the ForScore build was rewritten because a backer found a hole in it.
- Then it locks, and you get seven days to leave. When the final spec republishes, every backer to that point can withdraw for a full refund if it is not what they thought they were funding. No reason required.
- What you get for backing is the feature, and credit. Your name in the release notes and on this page. Nothing financial. No account credit, no discount, no portion of your contribution returned. We offered that once, thought better of it, and withdrew it.
- The feature is never split. It ships to every customer on a qualifying plan, backer or not. You are paying to move something up the list, not to own it.
- We only list things we would not otherwise build. If it is already coming in the next six to twelve months, we tell you and build it for free.
- We publish the low end of the estimate. If a build runs over, Back On Stage absorbs it. That is our problem, not yours.
Why show us the cost?
Because asking bandleaders to fund development without showing the number is how you lose their trust once and never get it back. Total build cost, our half, your half, all on the page.
Why publish what you are not building?
Because an out-of-scope list is the honest part of a specification. Nobody should back something expecting a thing it was never going to do, and find out after they paid.
Do I need to be a subscriber to back a campaign?No, but the feature ships to customers on a qualifying plan, so backing something you cannot use is not a good trade. Check the campaign's requirements before you contribute.
When do I get charged?At checkout. The refund is the protection, not a delayed charge.
How long until it is actually built?Development starts once the spec has locked and the withdrawal window has closed. Build time depends on the feature and the Statement of Work gives the phasing.
Can I suggest a feature without funding it?Yes, and most requests arrive that way. Scoping is on us. The campaign only happens if it is something we would not otherwise build.
Your cart
Taxes calculated at checkout. We will be in touch within one business day to schedule and to collect your data.
