What is a project add-on?
A project add-on is any additional work, feature, or improvement that is not included in the original Technical Specification. Add-ons are used when both the client and developer agree to extend the scope of the project during development.
An Add-on may include:
- A new feature or interface
- An additional function or integration
- A workflow improvement or UX enhancement
- Extended support or configuration
- Any other enhancement outside of the confirmed scope
It’s often more efficient to develop these additions during the project, rather than waiting until after launch, when setup and team alignment might already be closed.
Add-ons are always created and issued by the seller, based on your request or mutual agreement.
How add-ons work
- You request a change or improvement
- We evaluate the request and create a custom Add-on proposal
- You receive a full description with:
- Scope of the Add-on
- Estimated delivery time
- Cost or quota usage
- Expiration deadline to accept or decline
No work begins until you explicitly confirm the Add-on terms.
Tips for buyers
Before confirming an Add-on, please make sure to:
- Read the Add-on description carefully
It outlines what will be delivered, how it works, and any related technical notes. - Check the delivery time
Some Add-ons may extend your project timeline. - Review the pricing or quota cost
Payment terms are clearly displayed (top right corner of the Add-on proposal).
How much does an add-on cost?
Each Add-on is unique and priced based on the complexity and time required.
There are two ways to cover the cost:
- Paid Add-on – A separate invoice is issued, and development begins after payment confirmation.
- Quota-based Add-on – If you have available quotas, the Add-on may be fully or partially paid using your internal quota balance.
The method of payment will always be clearly defined in the Add-on description.
Delivery time and expiration
- Delivery time: Some Add-ons may affect the global project deadline. If they add significant scope, we may adjust the timeline accordingly.
- Expiration: Add-on proposals are time-sensitive. You are expected to confirm or decline the offer within a specific timeframe. After that, the proposal may be withdrawn or updated.
In summary
- Add-ons cover any work not included in the original scope
- They are optional, custom, and created by the developer upon request
- You must review and confirm the Add-on before work begins
- Add-ons can be paid directly or exchanged for quotas
- Each Add-on may affect the budget, timeline, and delivery