Technology & Software · Founder story · 10 September 2026
Why I Built 360 Degrees.
Support should revolve around people, not systems.
When people seek support, they can find themselves explaining the same circumstances repeatedly. One organisation holds a referral, another holds an assessment, and another manages the next part of the journey. The person at the centre is left trying to understand who is responsible, what is happening and what comes next.
I believe technology should make that experience easier, not add another layer of complexity. That is why I built 360 Degrees.
360 Degrees is a connected support platform designed for Aotearoa New Zealand. It brings whānau, practitioners and organisations together around a coordinated support journey, with clear responsibilities and consent-led access to information.
The problem is bigger than software
Many organisations already have systems for recording their own work. The difficulty is that people's lives do not fit neatly inside one provider's database. Support can involve housing, health, employment, education, financial circumstances, family relationships and other services. Each organisation has its own responsibilities, but the person receiving support remains the same.
The challenge is to connect the work without assuming that every service should have access to every piece of information. Good coordination requires both continuity and boundaries.
The person should not have to become the administrator of every organisation's disconnected process.
A platform designed around the person
360 Degrees is being developed to give whānau a place to stay involved in their support journey, understand their network and have a clearer say over how their information is shared. Practitioners need tools to manage referrals, assessments, plans, tasks, appointments and evidence. Organisations need oversight of the services they deliver and the outcomes they are responsible for.
The design principle is straightforward: information should be available to the right people, for the right purpose, with appropriate permission and accountability.
That means consent, identity, role-based access and auditability are not optional extras. They are part of the system design. The platform is not intended to replace professional judgement, legal responsibilities or the relationships between whānau and the people supporting them.
Why I am building it
My work through Eden Software focuses on turning complex processes into practical digital systems. I am interested in the point where technology, governance and everyday life meet—particularly where fragmented processes create unnecessary work or leave people without a clear pathway.
360 Degrees is one expression of that work. It is not intended to replace the relationships between whānau and the people supporting them. Its purpose is to give those relationships better tools, clearer information and a more accountable way to coordinate.
The platform will continue to evolve through development, testing and feedback. My priority is to build capabilities that are useful, secure and demonstrably fit for purpose, rather than promise features that have not yet been delivered.
What good coordination should look like
A useful system should make the current state of a support journey clear. A practitioner should be able to understand what has been assigned, what evidence is required and what action comes next. An organisation should be able to distinguish an open referral from an accepted service, work in progress from a completed outcome, and a request for information from an approval.
Whānau should be able to participate without needing to understand the internal machinery of every provider. Access to sensitive information should remain subject to the appropriate permissions and responsibilities. A record should show what happened, who acted and when, rather than relying on someone to reconstruct the process from disconnected messages.
These are design objectives, not a claim that every capability or integration is already live. Each feature needs to be tested against the actual service process before it can be relied upon.
Building for Aotearoa
Software built for New Zealand needs to account for the communities and organisations that will use it. That includes accessible language, practical workflows, appropriate treatment of personal information and the ability to support different organisational responsibilities without treating every provider as identical.
For Māori and whānau-centred services, technology should support relationships and the authority of the people and organisations involved. It should not assume that a generic database can replace whakapapa, tikanga, professional obligations or community decision-making.
The work is to make the digital infrastructure useful while respecting those boundaries.
What comes next
The next stage is to continue strengthening the whānau experience, practitioner workflows and organisation administration, alongside the controls needed for responsible information sharing. I will also publish practical resources explaining how the system works, the service-design principles behind it and what we learn through the build.
360 Degrees is part of a broader commitment to building software that helps people and organisations do more with the resources they already have.
Build the system around the person. Make the work visible. Keep authority and accountability clear.
Explore the work
You can explore the platform at 360degrees.app ↗, or read more about my software and product work on kiricampbell.com ↗.
Kiri Campbell
Founder, 360 Degrees and Eden Software
Aotearoa New Zealand