Product teams
A first release, an AI pilot with a review step, and capacity when the backlog keeps moving.
Product teams
Product teams come to Aarvix Services when a feature is real but not bounded, or when support replies need a draft that cites the help centre. A SaaS MVP and an AI pilot are different hour blocks. You can buy one and decline the other.
When the queue does not end, monthly capacity is the engagement. It is not a substitute for a written scope on a new product surface.
Lanes that tend to fit
| Custom software | Internal tools and a first product release, with discovery priced before product code starts. |
|---|---|
| AI software | Pilots, application sprints, and agent workflows with a person still responsible for what gets sent. |
| Capacity | Prepaid hours and monthly blocks for work that is real, but does not fit a single fixed scope. |
A roadmap item with no edge is discovery, not a sprint.
Product teams arrive with a feature that is real and unbounded, or with support replies that should cite the help centre and currently do not. A SaaS MVP and an AI pilot are different hour blocks. You can take one and decline the other. The pilot ends in continue, narrow, or stop.
When the queue does not end, monthly capacity is the engagement. It is not a way to avoid writing a scope for a new surface. If the backlog is a single release, name the release. If it is a week of varied tasks, name the week.
We will ask who sends the customer-facing text. If the answer is “the model”, the engagement does not start. Someone on your side remains responsible.