Sample only, not delivered client work or a completion promise.
App Care · 10 changes + 1 micro-feature
An illustrative shared-codebase queue could contain four reproducible bug fixes, three small text or layout changes and three isolated compatible dependency updates. A new filter on an existing list could use the separate micro-feature allowance. Each item needs an agreed scope and acceptance check.
Care Plus · 20 changes + 2 micro-features
A busier illustrative queue could contain eight bug fixes, eight existing-screen changes and four compatible dependency updates. Two separate micro-features might add a sort option and a display toggle using existing data. Your assigned account manager coordinates priorities, weekly updates and the monthly planning call.
Weekly progress updates show work completed, blockers and next steps; the monthly summary records accepted changes and micro-features, agreed checks and release status. One item is active at a time. Tested, approved changes can use the weekly release opportunity; store timing is outside our control. These are example allocations, not a guarantee every item completes that month. Accepted unfinished work carries forward without another slot in its category. Unused allowances expire, so agree new priorities around carryover.