Google, Microsoft or Nextcloud for your co-op?

The right collaboration platform is the one your co-op can use, govern and sustain. Google Workspace, Microsoft 365 and Nextcloud can each form part of a useful setup, but their operating arrangements differ. A feature checklist alone cannot tell you which will work for your members.

Begin with what already exists. Familiar templates, spreadsheets with complex behaviour, accessible working methods and established support relationships all have value. Moving away from them creates work. Equally, a familiar system may have permission or ownership problems worth resolving. Compare the current setup with realistic alternatives, including the option to improve it.

Write requirements as tasks

Ask representatives of the actual users to describe five recurring tasks. Include someone who is less confident with technology and someone who works primarily on a phone. A committee that collaborates occasionally has different needs from a worker co-op editing client documents every day.

• Two people edit the annual report and find the approved version later.
• A new committee member gets board papers without seeing personnel records.
• A volunteer receives a role inbox message without sharing a password.
• An external accountant receives a restricted set of files.
• An administrator removes a departing person while preserving organisational records.

Add constraints: unreliable broadband, required desktop applications, supported devices, accessibility needs, available administrator time and the file formats used by partners. Classify each need as essential or useful. Do this before watching sales demonstrations.

Compare the delivery model as well as the product

For Google Workspace, investigate shared drives, account administration, external collaboration and the exact features available in the proposed edition. Google's shared-drive documentation explains organisational ownership of those files. Check how that differs from files left in individuals' storage.

For Microsoft 365, test the documents and workflows your co-op already depends on, including desktop requirements. Ask the supplier to demonstrate team file ownership, guest access and role email. Microsoft documents a delegated shared-mailbox model; confirm that your proposed licensing and setup meet your needs.

For Nextcloud, identify who provides the hosting and who maintains each component. The administration manual describes upgrade prerequisites and compatibility checks. A managed Nextcloud service and a server maintained by a volunteer are materially different support arrangements, even if the interface looks similar.

Do not assume a platform supplies every part of your stack. Ask explicitly about email hosting, video meetings, collaborative document editing, backup, support hours and recovery. Obtain current terms and eligibility decisions directly; being a co-op does not automatically establish entitlement to charitable discounts.

Run a trial with real acceptance criteria

1. Create fictional board, worker and general-member accounts or equivalent test roles.
2. Upload copies of representative documents without confidential information.
3. Ask users to complete the five tasks without coaching them through every click.
4. Record access failures, confusing steps, formatting changes and support time.
5. Remove a test user and check where their files and responsibilities remain.
6. Export a useful sample and open it outside the platform.

Score each task as “works unaided”, “works with support” or “does not meet the requirement”. Give a serious accessibility or confidentiality failure more weight than a cosmetic preference. Agree any workaround explicitly, including the person responsible for maintaining it.

Make the decision explainable

An illustrative eight-person design co-op might retain Microsoft because its client spreadsheets and desktop workflows are expensive to change. A new community project might choose Google after a successful browser-based trial. A co-op with reliable technical support and a strong requirement for its chosen hosting arrangement might choose managed Nextcloud. None of these examples establishes a universal winner.

Write down the reason for the decision, the tradeoffs accepted and the review date. Include migration, training, backup and exit work in the technology budget. Name an owner for permission reviews and induction; the procurement decision is only the start of operating the service.

Compare a full year of costs with the technology budget tool before approving a move.