Engagement · SharePoint Online · India
SharePoint Online applications maintained for more than two years
2+ years
Situation
The client ran its work on SharePoint Online. The applications and custom features on that tenant were how people got things done, so they could not sit still. New needs showed up as new add-ins. Existing add-ins needed changes as the business changed. The same estate also needed someone who would keep it running and answer when something broke.
That is a different job from a one-time build. The value is continuity across the life of the product: the team that adds a feature is the team that later changes it and supports it.
What we took on
Temiio maintained this SharePoint Online estate continuously for more than two years. The work had four parts, and all four stayed in scope until the product was discontinued.
- New add-ins, when the client needed a capability that was not there yet.
- Enhancements to add-ins already in use, so existing features kept up with how the client actually worked.
- Maintenance of the applications and custom features, so the estate did not drift.
- Support, so issues had a team that already knew the applications.
Each addition became part of the estate under the same engagement.
How it ended
The engagement ended in 2025, when the customer discontinued the product. Up to that point the same team had been on the SharePoint Online applications for more than two years: adding add-ins, changing the ones already in use, maintaining the estate, and supporting it.
What this shows
A SharePoint Online estate stays useful when the same team stays with it. New add-ins, changes to old ones, maintenance, and support were one engagement for more than two years. The work stopped in 2025, when the customer discontinued the product.
