leroy/who it's for/the backlog
// for draining the backlog

Drain the backlog. While you build the next thing.

Hundreds of GitHub issues. A Linear board full of "small" tweaks. Customer requests you keep meaning to get to. Point Leroy at the backlog and it works through it in priority order — shipping what's safe, flagging what's risky.

Get on the waitlist →What it clears
// works from
LinearGitHubSlack
// point it at
a label or a board
// you keep
the final say
−32
issues closed this week
// label: good-first-issue
Empty state for the reports pagemerged
Fix typo in onboarding emailmerged
Add loading spinner to export buttonmerged
Sort team members alphabeticallycoding
Support markdown in project descriptionsqueued
// why backlogs grow

The next big thing always wins.

Every week, the important work crowds out the long tail. The small stuff isn't hard — it just never makes the cut. So it compounds, quietly, until the backlog is a graveyard you're afraid to open.

!
It's not a priority — until it's 200 of themEach item is skippable. The pile isn't.
!
Customers see the gapsThe "small" requests are the ones users actually asked for.
!
Grooming is its own jobTriaging, labeling, and re-prioritizing eats the time you'd spend shipping.
!
Momentum hides rotThe longer it sits, the staler the context — and the scarier the fix.
// the handoff

What Leroy clears

Hand it a label, a board, or a milestone. It works top-down by priority, ships what's safe to auto-merge, and routes the risky calls back to you.

✓
Small feature requestsThe "can you also add…" items customers keep asking for.
✓
UI tweaks & polishSpacing, empty states, loading indicators, alignment nits.
✓
Copy & content changesMicrocopy, error messages, email tweaks, label fixes.
✓
Config & setting changesFlags, defaults, env-driven toggles with tests.
✓
Low-priority bugsThe known issues that never quite earned a sprint.
✓
"Good first issues"The exact work you'd hand a junior — handed to Leroy instead.

Your backlog isn't a someday list.
It's a queue Leroy is already working.

// other angles

Not quite you?

// solo founders
From vibe-coding chaos to shipped features.
For when you're a team of one trying to stay in build mode.
Read the solo-founder angle →
// bug fixing
Sentry error → root cause → PR. While you sleep.
For when production bugs are the thing eating your week.
Read the bug-fixing angle →
// closed beta

Point Leroy at your worst backlog.

Leroy is in closed beta — we're onboarding the first 50 users by hand. Tell us how big the pile is and where it lives.

No spam. No drip. One email when it's your turn.