Retainer or project, choose the form that fits
Not every software question belongs in the same commercial model. That is why we make explicit when a project proposal is the logical choice, when a retainer works better, and when both complement each other.
Project proposal for features and scope variants
Retainer for recurring work per month
Hours can scale up and down, even to zero
Not every question needs the same model
The commercial model should match the work ahead of you
A project proposal fits a clear feature set with Glossary · In briefMoSCoW prioritizationMoSCoW prioritization classifies requirements as Must have, Should have, Could have or Won't have this time, making clear what is essential and what can wait.Read more, hour ranges, and estimate allowances. A Glossary · In briefretainerA retainer is an ongoing agreement in which a client regularly reserves a service provider's capacity for recurring work, such as software maintenance, support or development.Read more fits when you mainly organize ongoing development, support, or maintenance per month.
You can also combine both forms. Then you use a project part for new build or a major extension, and a retainer for recurring work, support, or monthly ongoing development.
When each form fits
A project proposal or monthly capacity
You get a feature-based estimate with priorities, ranges, and explicit assumptions, so you can choose what needs to come first.
A retainer organizes hours per month, invoicing afterwards, and if needed SLA agreements for a collaboration that keeps going.
Before the end of the month, we align how many days are needed for the period that follows. That can rise, fall, or be zero when there is temporarily no development demand.
If you build something new and then want to continue in a stable way, a combination is often more logical than forcing everything into one contract form.
For bounded work
Project proposal for scope and scenarios
You get a feature-based estimate with priorities, ranges, and explicit assumptions, so you can choose what needs to come first.
Roles and result
What to expect from each contract model
We make explicit what each model gives you: feature estimates and scenarios for projects, hour range, invoicing, and if relevant Glossary · In briefSLASLA stands for service level agreement: an agreement between a customer and provider about the service, its agreed level and how that level is measured.Read more agreements for a retainer.
At SGI Compliance, you can see why that difference matters. Monthly ongoing development and support call for a different rhythm than a one-off feature estimate. If you want to sharpen scope first, the conversation starts with scope and estimation.
Maintenance & support
What this gives you
Less chance that contract shape and way of working collide
Clearer choice between bounded and ongoing work
More flexibility without vague agreements
A collaboration that can move with the phase of the work