MVP scope
The MVP should focus on the smallest credible platform that proves Opries can improve documentation, compliance, continuity, and communication evidence for pilot organisations.
MVP capabilities should include:
- organisation setup and user roles;
- document upload, categorisation, ownership, status, and version history;
- policy, best management practice, and standard operating procedure registers;
- review date tracking and basic reminders;
- compliance obligation register;
- project and grant evidence links;
- communication log with audience, channel, approval, and related record fields;
- exportable audit views;
- initial template packs for common Landcare and NRM needs.
Non-MVP scope
The following should be deferred unless pilot evidence shows they are essential:
- full customer relationship management;
- full accounting or grant management replacement;
- advanced workflow automation;
- native email campaign sending;
- complex learning management;
- AI drafting or document interpretation;
- marketplace for consultants or service providers;
- deep integrations with government or funder systems.
Boundaries
Opries should complement existing accounting, email, storage, and project management tools. The first version should not try to replace every system an organisation uses.
The platform should instead become the authoritative place for governed organisational documents, linked obligations, and audit-ready communication records.
Content and templates
Initial templates should be useful starting points, not legal advice. They should include clear disclaimers and encourage each organisation to adapt, approve, and review them under its own governance arrangements.
Security and privacy baseline
The MVP should include role-based access, secure authentication, record-level audit events, backups, and privacy-conscious handling of member, landholder, client, supplier, and volunteer information.