Start with what your team actually uses
Before you compare prices, count the people who really need a mailbox, shared calendar or document access. A small NPO in Observatory may only need 6 active users, while a team with offices in Cape Town, Johannesburg and Durban might need 25 or more. The biggest budgeting mistake is paying for features no one uses, or leaving staff to share one inbox and then losing time on follow-ups.
List the daily tasks first. Who sends programme updates, who books meetings, who signs off documents, and who needs mobile access while travelling between schools, clinics or community sites. If your team works in the Eastern Cape or the Northern Cape as well, note the people who only need read access instead of full editing rights. That simple split can cut your monthly spend quite a bit.
- Count active users, not just names on a staff list
- Separate full users from read-only or occasional users
- Record who needs mail, calendar, file access, or all three
- Check which mobile phones and tablets need setup
Build a budget around setup and monthly use
Hosted message budgeting has two sides: once-off setup and ongoing monthly costs. Once-off items usually include domain linking, mailbox setup, calendar setup, document space setup, contact imports, mobile device setup and admin handover. Monthly costs cover the hosting itself plus any ongoing admin help or support you may need. If your organisation has a busy fundraising calendar or field teams that change often, plan for more support in the first few months.
It helps to separate the budgt into neat lines so trustees or finance staff can approve it faster. For example, one line for migration, one for user setup, one for training, and one for support after go live. That way you can see what is essential now and what can wait until the next quarter.
- Once-off setup: linking, migration, imports, device setup and handover
- Monthly running cost: mailboxes, collaboration tools and admin support
- Project cost: training, go live support and a security review
- Reserve fund: a small amount for extra users or changes mid-year
Plan for migration so your budget is not stretched later
Moving old mail into a new system can be the part that catches non-profits off guard. If records, donor messages or committee threads are spread across several accounts, the migration takes longer and needs more checking. A proper mail migration should include a clear plan for folders, contacts, shared calendars and shared documents. That is especially important if the team is moving from personal accounts to a central setup.
Ask upfront how much time is needed for each stage. A small team in Pretoria with clean data may finish quickly, while a larger office in Bloemfontein with years of archived correspondence may need more preparation. Keep a little budget space for failed logins, old phones, password resets and staff who need a second round of help after go live.
- Check how many accounts need migration
- Confirm whether contacts and calendars are included
- Ask about old device compatibility before rollout
- Set aside time for follow-up fixes after launch
Do not underbudget for training and handover
Many non-profits spend on setup then forget the real cost of getting staff comfortable with the new system. If people are used to WhatsApp or personal message, they may need guidance on shared folders, calendar invites and replying from the correct mailbox. Training also reduces admin mistakes, which matters when one person handles multiple projects and reports.
Include a handover session for the administrator or office manager and a separate team training session for ordinary users. If your organisation has branch support in Bellville, Stellenbosch or other local areas, make sure each group knows who approves access and who to call when a mailbox stops syncing. In summer, when offices are hot and power cuts are more frequent, mobile setup becomes even more important.
- Train the admin first, then the wider team
- Cover login, shared calendars, documents and mobile access
- Include practical examples from your own programmes
- Keep a short written guide for new staff and volunteers
Budget for security and steady admin help
Non-profits often hold donor details, beneficiary data and internal reports, so security should be part of the budget not an afterthought. A security review helps check mailbox access, password control, shared document permissions and whether departing staff still have access. If your team works from multiple towns, this is even more important because one weak account can expose the whole organisation.
Ongoing admin help can save money over time. Instead of asking a volunteer or project officer to figure out every new setup, you can have support for new mailboxes, user changes and access reviews. For smaller organisations, that is often cheaper than dealing with lost time and confused staff. It also helps when load-shedding interrupts work and people need to reconnect quickly.
- Review who has access to each mailbox and folder
- Set rules for leavers, joiners and temporary staff
- Check password and recovery details regularly
- Keep admin support in the budget for the full year
Use a simple annual budget checklist
A practical annual checklist keeps message and collaboration costs visible. Start with the number of active users, then add setup fees, support, training and a small contingency. Review it before the financial year starts, and again after the first quarter if your team has grown or changed. This keeps your spend linked to real activity, not assumptions.
For many non-profits, the best approach is to budget conservatively at first, then adjust once the system is in daily use. If your organisation serves Cape Town, Johannesburg, Durban, Pretoria and Bloemfontein from one central admin team, make sure each office understands its own needs. Small changes like fewer shared passwords, better calendar use and cleaner contact lists can save time every week.
- Active users and mailbox count
- Migration and import costs
- Training and go live support
- Ongoing admin help and security reviews
- Contingency for staff changes or extra storage
