Our internal platform for managing development requests, church onboarding, and team workflows. Here's how to get started.
Use the Submit Portal to send in bugs, feature ideas, improvements, or special requests. Include as much detail as possible — screenshots help!
Ember reads your request and suggests an ICE score (Impact, Confidence, Ease), a category, effort estimate, and tags.
The dev team reviews the AI suggestions, adjusts scores if needed, sets priority, and assigns the work to a sprint.
Items move through In Progress and Testing. You'll get notified when your request ships.
Not sure which to pick? Is it broken? → Bug. Something new? → Feature. Make it better? → Improvement.
Something is broken or not working as expected
Something entirely new that doesn't exist today
Something exists but needs to work better
Webhooks, integrations, custom work
Every request moves through these stages from left to right.
Inbox
Received, not yet reviewed
Backlog
Reviewed, waiting for sprint
In Progress
Actively being worked on
Testing
Built, being verified
Done
Shipped and verified
We use ICE scores to prioritize objectively instead of relying on gut feelings. Each request gets three scores (1-10) that multiply together.
How many people does this affect? How much does it matter?
How well-defined is the request? Do we know what to build?
How straightforward is it to implement? Less effort = higher score.
We work in 2-week sprint cycles, Monday to Friday. Each sprint has a capacity target of 80 hours across the team.
During triage, requests get assigned to upcoming sprints based on priority, ICE score, and available capacity. If a sprint is full, your request moves to the next one.
Items that aren't completed by sprint end automatically return to the backlog for re-prioritization.
Nothing ships until all five checks are complete. This keeps quality high.
Be specific. “The calendar page is broken” is hard to act on. “Calendar booking page shows a blank white screen after clicking Submit on Chrome” is perfect.
Attach screenshots. A picture of the problem is worth a thousand words in a bug report.
Explain the “why”. Help us understand the problem you're solving, not just the solution you're imagining. Sometimes there's a simpler path.
Mark blockers. If something is actively preventing you or a church from doing their work, check “This is blocking critical work” and it auto-escalates to critical priority.
Church Fuel Labs