A small team with big coordination needs
The client was a community charity in Observatory, Cape Town, with staff and volunteers working from one office, home and outreach sites around the city. Like many non-profit teams, they had grown around personal accounts and informal sharing. Messages were getting missed, calendar invites were scattered, and a few project documents lived on different phones and memory sticks, which made handovers difficult.
The brief was clear. They wanted custom email addresses, shared calendars and a central place for documents without paying for more than they needed. They also wanted something the team could use without long training sessions. Budget mattered, but so did continuity because their work includes donor meetings, beneficiary appointments and transport coordination across the week.
- Client type: neighbourhood charity
- Town: Observatory, Cape Town
- Team size: 9 active users plus volunteers
- Core need: move from personal mail to managed hosting
What had to work and what had to be avoided
The biggest constraint was practical. The organisation could not afford downtime in the middle of fundraising, and they needed to keep old correspondence available for reference. Several users were also on mixed devices, including older Android phones and low-cost laptops, so the setup had to be simple enough to work across a range of screens and connections. Coastal humidity and occasional power interruptions meant they wanted a system that did not depend on one office machine being switched on all day.
We also had to keep the migration tidy. That meant no broken contacts, no duplicated calendars and no confusion about who could see which shared folders. Because the team includes both permanent staff and short-term volunteers, we set up access in layers so each person only saw what they needed. That kept admin lighter and reduced the risk of accidental changes.
- Mixed devices: laptops, Android phones and a few tablets
- Priority: keep old mail and contacts intact
- Access control: separate admin, staff and volunteer access
- Timeline pressure: avoid disruption to donor and field work
The rollout plan over three weeks
We completed the rollout in three weeks. Week one covered planning, mailbox naming, domain linking and a security review. We checked existing addresses, listed who needed shared calendars, and mapped the document structure so the team would not inherit a messy folder tree. Week two was migration and device setup. We moved mail in batches, imported contacts, and configured phones and laptops so the team could keep working while old and new accounts were being aligned.
Week three focused on training, go live support and admin handover. We ran short sessions for daily use, then another session for the people handling the inboxes and calendars. The training was practical, not theory heavy, so they could see how to send from the correct address, share an appointment and recover from a missed invite. A few users needed extra help with their mobile sync settings, which we sorted out one by one.
- Week 1: planning, domain linking, security review
- Week 2: mail migration, contact imports, mobile device setup
- Week 3: training, go live support, admin handover
Services supplied for the charity
The service package was built around the organisation’s daily routine. We set up mailboxes using the charity’s own domain name, then configured shared calendars for staff meetings, outreach visits and venue bookings. Document collaboration was added so policies, funding notes and event plans could be kept in one place instead of being sent around as attachments. That reduced version confusion and made it easier for the team to find the latest file.
We also handled the less visible but important work. Contacts were imported from existing accounts, device settings were checked on mobile phones, and admin access was handed over only after the internal lead was comfortable. Ongoing help was left in place for the first few weeks after go live so the charity had somewhere to turn if a mailbox rule or calendar share needed adjustment.
- Domain Linking
- Mailbox Setup
- Calendar Setup
- Document Space Setup
- Mail Migration and Contact Imports
- Mobile Device Setup, Security Review and Team Training
What changed after go live
The immediate result was clearer communication. Staff no longer had to guess which personal account held a reply, and the shared calendars gave everyone a better view of visits, leave and meetings. The admin team could see who had accepted an invite and who still needed a reminder, which cut down on duplicate messages. They also stopped losing time searching for the latest version of a proposal or donor note.
Another win was confidence. Because the system was set up around the way the charity actually works, not around a generic office pattern, the team adopted it quickly. Volunteers were given limited access where needed and senior staff had the controls they needed for oversight. It made the organisation feel more orderly, and less dependent on one person remembering every detail.
- Better inbox ownership and fewer missed messages
- Shared calendars for meetings, outreach and leave
- Cleaner document handling with less file duplication
- Faster handovers between staff and volunteers
What we would repeat for the next non-profit rollout
If we were doing this again for another charity, we would keep the same sequence: plan first, move in batches, train last. That approach suits non-profit teams because it respects busy schedules and keeps costs down. It also gives space to test device settings properly before everyone switches over, which matters when people are working between the office, home and field visits.
We would also repeat the short role based training format. In our experience, people remember what they practise, not long manuals. A simple setup with clear mailbox names, a shared calendar structure and a document space that reflects the organisation’s daily work is usually enough to get the whole team moving in the same direction, with less admin pressure afterwards.
- Keep migration in small batches
- Train by role, not by theory
- Test mobile access before go live
- Leave a short support window after handover
Key facts
| Location | Observatory, Cape Town |
|---|---|
| Rollout duration | 3 weeks |
| Users supported | 9 active users plus volunteers |
| Core services | Message hosting, shared calendars, document collaboration |
| Migration scope | Mailboxes, contacts, calendar shares and mobile devices |
| Support coverage | Observatory, Cape Town, Johannesburg, Durban, Pretoria and Bloemfontein |
