We hear a lot of good ideas. A church wants a feature TheRehoboth does not have yet. A business wants 247BrandHQ to support one more platform. Someone wants an app for a completely new audience we have never built for. Most of these ideas are genuinely good. Very few of them become something we build.
The filter is not "can we build it." With enough time, most things are buildable. The real question is whether we can support it for years, not just ship a first version. Every product on this site is still maintained, still getting fixes and updates, still answering support email. Saying yes to a new idea means saying yes to that commitment indefinitely, and that changes how we evaluate a pitch.
So before a new idea gets real engineering time, we ask a small set of blunt questions: who exactly is this for, and can we name them specifically rather than describing a vague audience. Does it fit the stack we already know how to run reliably, or does it require us to learn and maintain an entirely new kind of infrastructure. And critically, is there a small, specific version of this we could ship in weeks to see if the idea holds up in someone's actual daily use, rather than a large version we would have to guess about for months before finding out.
That last question kills more ideas than any of the others. A lot of pitches only make sense as a big, complete product — there is no small version that proves anything. Those ideas usually go on a list rather than into a sprint, because we would rather learn we were wrong in two weeks than in six months.
We also weigh ideas against what we would have to stop doing. A small studio has a fixed amount of attention, and every yes to something new is quietly a no to giving more attention to Koinonia, Edify, TheRehoboth, 247BrandHQ or MyChurchApp PRO. An idea has to be good enough to justify that trade, not just good enough to be worth building in isolation.
None of this makes us immune to bad decisions — we have started things that did not go anywhere, same as anyone building software. But having an explicit filter, and being willing to say no even to genuinely good ideas, is a big part of why the products we do ship stay supported instead of quietly abandoned a year later.