A SharePoint retainer vs project decision usually appears after a familiar moment: the new intranet, workflow or migration is live, but the business immediately has a list of sensible next improvements. A form needs another approval stage. Teams cannot find a policy. A site owner needs help. The question is not simply how to pay for support. It is how to keep Microsoft 365 useful without committing to more consultancy than you need.
For small and mid-sized businesses, the right answer depends on the certainty of the work, the pace of change and who will own the platform after delivery. Fixed-price projects and monthly retainers solve different problems. Treating one as a substitute for the other can create either unnecessary cost or a system that slowly loses relevance.
When a SharePoint project is the right choice
A project works best when there is a defined outcome, a clear deadline and enough information to agree what “done” looks like. Examples include moving content from a legacy file share to SharePoint, building a new department site, replacing a paper-based approval process with Power Automate, or developing a specific Power App.
The commercial benefit is clarity. You agree the scope, delivery approach, timescale and price before work starts. That makes a project particularly suitable where budget approval depends on a business case, such as reducing manual data entry, improving document control or meeting an audit requirement.
A well-scoped SharePoint project also creates useful decision points. Before building, the consultant can establish what content should move, which permissions are required, how records will be managed and whether existing processes are worth replicating. This avoids the common mistake of moving old clutter into a newer system.
Projects do have boundaries, though. A fixed scope needs change control when priorities move. That is not a flaw – it protects both parties from an undefined brief – but it can feel restrictive where the business is learning as it goes. If each new requirement requires a separate quote, small improvements may be delayed until they become a larger, more expensive problem.
Signs your work is project-shaped
Your requirement is likely best handled as a project if the business can describe a specific result, needs it by a particular date and can nominate people to make timely decisions. A migration before an office move, a new intranet ahead of a merger, or an approval workflow needed for a compliance deadline all fit this pattern.
It also helps if the work has a natural handover point. Once the sites are built, content is migrated and users are trained, an internal owner may be able to manage routine updates. They may only need occasional specialist help afterwards.
When a SharePoint retainer earns its keep
A monthly retainer suits organisations whose SharePoint environment needs steady attention rather than one large intervention. It provides planned access to senior Microsoft expertise for a predictable monthly cost, without employing a full-time SharePoint specialist.
That matters because a digital workplace is not static. Teams change, policies are revised, new reporting needs emerge and users find gaps that were not visible during initial design. A retainer lets the business make useful changes while they are still small: refining permissions, improving page layouts, building a simple Power Automate flow, resolving adoption issues or reviewing whether a site is still being used as intended.
The value is not only in completed tasks. It is in continuity. A consultant who understands your tenant, information architecture, governance rules and previous decisions can give quicker, more practical advice than someone starting from scratch for every request. This is particularly useful where there is no in-house SharePoint lead, or where an IT manager is already responsible for security, devices, suppliers and day-to-day support.
Retainers are also a sensible route for continuous intranet improvement. Rather than commissioning a major rebuild every few years, a business can add capability in stages. A custom SPFx web part for clearer news, navigation or knowledge search may be deployed first; further improvements can follow as usage data and user feedback show what matters most.
What a good retainer should include
A retainer should not be an open-ended promise of “support”. It needs a defined monthly allocation, clear priorities and a straightforward way to decide what is worked on next. Typical activity includes user and site-owner support, governance checks, small enhancements, workflow improvements, testing, release planning and advice on Microsoft 365 changes.
The best arrangements also make unused time and larger pieces of work visible. A complex migration, a substantial Power App or a new intranet phase may still need its own scoped project. Trying to squeeze a major build into a small monthly allocation often creates a slow delivery cycle and unclear expectations.
SharePoint retainer vs project: compare the trade-offs
The choice becomes clearer when you compare the operational need rather than the label on the contract.
| Consideration | Fixed-price project | Monthly retainer | | — | — | — | | Best for | Defined build, migration or deadline | Ongoing improvements and support | | Budgeting | One agreed cost for a known scope | Predictable monthly spend | | Change requests | Usually assessed and priced separately | Prioritised within the monthly allocation | | Platform knowledge | May end at handover | Builds over time | | Delivery pace | Concentrated around a defined plan | Steady, flexible progress |
A project offers stronger certainty when the destination is known. A retainer offers more flexibility when the route will change as users engage with the system. Neither is automatically cheaper. The expensive option is often the one that does not match the way your organisation makes decisions.
For example, an operations team may initially ask for a SharePoint document library with approval. During workshops, it becomes clear that the real problem is inconsistent request data, not storage. A project can still work if the team can agree the revised process quickly. If several departments have related issues and priorities are likely to shift, a retainer may give more room to improve the process in sensible increments.
The blended model is often the practical answer
For many SMEs, the strongest arrangement is a project followed by a retainer. The project handles the defined transformation work: a migration, intranet launch, workflow build or initial governance design. The retainer then supports adoption, resolves issues and develops the next set of improvements.
This approach avoids two unhelpful extremes. You do not need to hold a monthly commitment for work that can be clearly delivered as a fixed project. Equally, you do not need to restart procurement every time a site needs a meaningful improvement.
It also gives users time to influence the roadmap. Real usage often reveals where navigation is unclear, which approval steps cause delay and what information people repeatedly search for. Those findings are more valuable than assumptions made before launch. A retained consultant can turn them into manageable pieces of work rather than letting them sit in a backlog.
At ThePoint, this can mean delivering a fixed-scope SharePoint build or migration first, then providing ongoing senior support as priorities develop. The aim is not to keep clients dependent on consultancy. It is to make sure their Microsoft 365 investment continues to solve real operational problems after go-live.
Questions to ask before you choose
Start with the work, not the contract type. Can you define the required outcome, scope and deadline with reasonable confidence? If so, request a fixed-price project proposal. If your list is a mix of support requests, small improvements and emerging ideas, ask what a monthly allocation would realistically cover.
Be honest about internal capacity too. A project still needs stakeholder decisions, content owners and testing. A retainer still needs someone to prioritise requests. Without that involvement, either model can lose momentum.
Finally, consider the cost of leaving small issues unresolved. An unclear library structure, a manual approval chase or a neglected intranet page may seem minor alone. Across a year, they can waste time, weaken adoption and encourage staff back to spreadsheets and shared drives. Choose the engagement model that lets your team deal with those problems while they are still easy to fix.