LogoLogo
  • Introduction
    • 🥳Welcome to the playbook
    • đź“’Project background
    • What is co-operative care?
    • 🛠️How to use the playbook
    • A word from...
      • Equal Care
      • Clapton Care Commons
  • Start and Grow
    • đźš Overview
    • 🌍Foundation
      • Founders
      • Find the others
      • Feasibility
      • Formation
    • Have a go
    • Find (more) money
    • Share the power
    • 🎋Grow
      • Recruit workers
      • Start teams
    • Sustain
  • Technology
    • Equal Care's Platform
    • Equal Care's technology journey
    • Choosing technologies
      • Social Care Platform Vendors
  • Fundraising
    • Fundraising options
    • Community Share Offers
      • Financial Conduct Authority (FCA)
    • Commons Contribution
    • Restrictions on investment
  • Equal Care's Model
    • Our Purpose
    • How we work
    • Sociocracy
    • Circles
      • Long term decisions
      • Everyday decisions
      • Circle records
      • Consent
      • Proposals
    • Teams
      • Why we use the Teams model
      • Who's in?
      • Team Starting
        • The role of a Team Starter
        • 1. Starting a Team: The First Contact
        • 2. Beginning the Relationship
        • 3. Finding the Right Match
        • 4. Supportive Conversation & Trust Assessment
          • 4a. Example of a Supportive Conversation
          • 4b. Example of a Trust Assessment
        • 5. Profiles and promises
          • 5a. The Getting Support Promise
          • 5b. The Getting Support Profile
          • 5c. Worker and team member profiles
        • 6. Building a team
          • 6a. Finding and welcoming new members
          • 6b. Trialling new team members
        • 7. Getting Organised: Roles and Hats
        • 8. Stepping Back: Team Independence
      • Dealing with conflict and change
        • Conflict support
        • How to leave a team well
    • Hats
      • Team Hats
      • Circle Hats - Process
      • Circle Hats - Operational
        • Care Commons Organiser
        • Peer supervisor
    • Platform
    • Co-production
      • Implementing co-production
      • Context of co-production in social care
      • Governance for co-production
      • Ownership for co-production
    • Care Commons
    • Radical Candour
  • Evaluation framework
    • Introduction
    • Commons-based Care: the Context
    • Scope
      • Three Domains of Care Outcomes: Process, Change, and Maintenance.
      • Three Domains of Outcomes in Equal Care
      • Mapping Equal Care Outputs to Outcomes Domains
      • Social Climate as a Key Evaluative Lens
    • Evaluation Challenges
    • Methods
      • Social Climate Survey
      • Community Mapping
      • Interviews and workshops
      • Group activities
      • Community needs assessment
        • Locality analysis
    • Data Analysis
      • Interviews Outcome Domains
        • Growth Outcomes
        • Well-being, Relationships & Belonging Outcomes
        • Systems Maintenaince & Co-production Outcomes
      • Community Network Map: Analysis & Overview
        • Who’s in the Network?
        • Bridging the Gap Between Formal and Informal Care
        • Mapping Care Wealth
        • What We Learned from the Teams
        • The Role of Teams in the Community Care Network
        • Reflections and Future Directions
      • Reflections from the Ground: Insights from Key Circle Leads
        • Circle Outputs: Experiences & Learnings from the Clapton Circle.
        • Teams Outputs: Experiences & Learnings from the Clapton Circle.
        • Platform Outputs: Experiences & Learnings from the Clapton Circle.
        • Commons Outputs: Experiences & Learnings from the Clapton Circle.
          • Care Commons Organiser Role Description
    • The Toolbox
      • Theory of Change
        • What is a Theory of Change?
          • Using a Theory of Change
        • Co-producing our Theory of Change
        • Observations about ToC Outcomes
        • How to use our interactive ToC
          • Orientation to ToC Tool: The Kumu Platform
            • Using the focus function in Kumu
            • Using Basic Control Functions
            • Toggling Between views
          • 1. Outputs Dimensions and Outcome Domains
          • 2. Coop Output Dimensions - a deeper dive.
          • 3. Coop Outcomes Domains. A deeper dive.
        • Using ToC tool to understand our model of care: Key Outputs.
        • Using ToC tool to understand our model of care: Key Outcomes
        • Using ToC tool to see how we measure outcomes
        • Using ToC tool to understand the impact of specific features of the coop
          • Circle ToC
          • Platform ToC
          • Teams ToC
          • Commons ToC
        • Using this tool for Strategy and Planning
      • Equal Care Coop's Social Climate Survey
        • About Equal Care's Social Climate
          • Why Measure Social Climate?
        • Interpreting Growth Measures
          • Low Score Interpretation
          • Medium Score Interpretation
          • High Score Interpretation
        • Interpreting Systems Maintenance and Co-production Measures
          • Low Score Interpretation
          • Medium Score Interpretation
          • High Score Interpretation
        • Interpreting Well-being, Relationships & Belonging Measures
          • Low Score Interpretation
          • Medium Score Interpretation
          • High Score Interpretation
        • Using the Social Climate Survey: Resources and Challenges.
        • List of Survey Items for all Stake Holders
      • Community Care Mapping Tool
      • Interview Templates
      • Atlas Care Maps
      • Co-Production Capacity Assessment Tool
        • 10 capacities for co-production
        • Using the tool
  • Service Specification
    • Care as a common pool resource
    • Service Spec
    • Service Map
  • Cost Model
    • Introduction
    • Resources
    • Fair wages
    • Cost Models in Social Care
  • Resources
    • Co-op operations
      • Communications
        • Roles
        • Tone of Voice
        • Digital Inclusion
        • Social Media
      • Learning
        • What you need to know
        • Peer to peer learning
    • Documentation
    • Care and Support Rates
    • Co-op rules & bylaws
    • Care Mapping with Atlas of Care
      • Care Mapping for Relationship-Centred Care
      • Care Mapping for new Teams
      • Care Mapping for Evaluation
    • Glossary
Powered by GitBook

© Equal Care Co-op Ltd 2025

On this page
  • The Beginning of the Journey
  • The Decision
  • Building the Roadmap
  • Incremental, Rapid Releases
  • Lessons

Was this helpful?

Export as PDF
  1. Technology

Equal Care's technology journey

From the outset, Equal Care was designed to be a platform co-operative: a democratically owned and governed digital platform business that combines the principles of traditional co-ops with the infrastructure and reach of modern online platforms.

From the beginning, the goal was to use technology to support the act of care - enhancing autonomy and equity while reducing administrative overhead, so that more time could be spent where it matters most: on the relationships within our Teams.


The Beginning of the Journey

Early on, the founding team faced a strategic decision: Should we develop our digital infrastructure in-house or buy in a ready-made service?

Each option had its own trade-offs:

Pros
Cons

In-house (Custom Development):

âś… The product can be tailored to fit the needs and values of the co-op.

âś… The co-op retains ownership of the platform.

❌ Requires time, funding, and a dedicated development team.

❌ Long-term support and management needed.

Bought-in service (Full Service)

âś… Lower up-front costs.

âś… Can be deployed quickly, accelerating growth.

âś… Maintenance, updates and customer service are included.

❌ Hard to find a product that fits the co-op's needs without compromise.

❌ No ownership — reliant on the provider for improvements and support.


The Decision

The team opted to develop in-house. This path aligned more closely with Equal Care’s values and long-term aims - particularly our commitment to autonomy, co-production, and ownership.

With the pilot fast approaching, we launched two workstreams in parallel:

  1. Low-code/No-code “Frankenstein’s Monster” A temporary digital setup using off-the-shelf tools to get the pilot underway.

  2. Custom Platform Discovery Requirements were gathered and several agencies were approached to scope the build. When none could fully meet the brief within budget and timeframe, we made the decision to build the platform ourselves, in-house using Agile methods.


Building the Roadmap

The first step was assembling a core platform team - a project manager and technical architect - to work with Equal Care’s founders to define a clear Product Roadmap.

This roadmap:

  • Articulated the vision and outcomes for the platform.

  • Prioritised work based on member needs, not just features.

  • Created a structured backlog for the development team.

A designer and developer were then recruited to begin delivery.


Incremental, Rapid Releases

The low-code 'Frankenstein’s Monster' setup allowed us to start quickly, but it was never meant to last. Each service in that setup came with a cost - both financial and operational.

To replace it, we released new platform features incrementally:

  • Gradually phasing out paid tools

  • Testing with real users in real-time

  • Reducing time to market

  • Increasing adoption and feedback

  • Responding directly to what our members need


Lessons

Technical capacity is vital

Most social care founders aren’t experienced in product development. Hiring experienced technologists or upskilling internally is key.

It’s hard to attract tech talent

Developers and designers are in high demand. Competing with commercial tech salaries is a challenge, especially in a social care context.

You can’t plan for everything

Even the best-designed systems will face bugs, outages, and unexpected issues. Developing strong quality assurance and testing practices is essential to build resilience into the product.

PreviousEqual Care's PlatformNextChoosing technologies

Last updated 14 days ago

Was this helpful?