Short answer
Unlimited requests means you can add as much as you like to your queue. Each track works on one task at a time until it’s properly done, so you get a steady flow of finished work. The number of tracks sets the pace. If you need more moving at once, you add a track.
Why one task at a time?
Because half-finished work has no value to your users. A team juggling ten tasks ships none of them this week. A team finishing one at a time ships something every few days, and you can see exactly where things are.
It also keeps quality up. A developer focused on one problem thinks it through, tests it and gets it reviewed. Context switching is where bugs creep in.
How does that keep “unlimited” fair?
There’s no cap on requests and no hours to count, so nobody spends time arguing about whether something was a two-hour or a four-hour job. Delivery is naturally paced by the number of tracks. That’s fair to you, because you’re never rationing ideas, and fair to us, because the workload is predictable.
What is a track?
A track is one stream of work. On our plans, Embedded has one, Embedded Plus has two in parallel, and Partner has three or more. Two tracks means two things in progress at once: perhaps one on the roadmap and one on fixes and customer requests.
What counts as one request?
Anything that can ship as a self-contained piece: a feature, a fix, a design change, an integration. Bigger pieces get broken down into smaller ones that ship one after another.
| You ask for | It becomes |
|---|---|
| Add CSV export to the reports page | One request |
| Fix the date format on invoices | One request |
| Connect our CRM | One or two requests, depending on the sync |
| Rebuild the reporting module | Five or six requests, each shipped and reviewed in turn |
| A whole new product | A run of releases, often after a short discovery sprint |
How fast does each request ship?
Most tasks land within a few working days. We promise a rhythm rather than a number of tasks a month, because a typo fix and a payments integration aren’t the same size, and pretending otherwise leads to padding or corner-cutting.
What about urgent bugs?
If something’s broken in production, it jumps to the front of the queue on every plan. That’s the one exception to strict ordering.
How do you get more done?
- Write clear requests. The fewer questions a request raises, the faster it ships. Here’s a template.
- Review quickly. Work waiting for sign-off isn’t shipping. How to keep reviews moving.
- Keep the queue ordered. The top three items should always be the three you care about most.
- Add a track when the queue is right but the pace isn’t enough.
Questions
Can I change the order of my queue?
Yes, whenever priorities change. The next task picked up is always the one at the top.
Are revisions counted as new requests?
They go into the queue like any other request, at no extra cost. If something isn’t right, it goes back in and gets fixed.