Skip to main content

Platform

Context is the thing that keeps getting lost

Human-services systems lose context every time a person crosses an organisation, a piece of software or a funding boundary. Technic is the layer that holds it.

Why context is lost

Every system is complete on its own terms

A care platform, a clinical system, a finance platform and a funding portal each hold a true and partial account of the same person. None of them is wrong. None of them is enough.

  • Boundaries are where meaning drops

    A referral carries a record. It rarely carries the reasoning, the risk history or the agreements that made the record make sense.

  • Migration is not the answer

    Replacing every operational system in a sector is neither practical nor desirable. The systems are not the problem; the space between them is.

  • Human journeys outlast systems

    Providers change, software changes, funding changes and organisations evolve. The person's history, context and progress should continue with them.

Architecture

The Technic context and intelligence layer

The person at the centre. The systems they move between around them. Context preserved across every interaction.

A person sits at the centre of the Technic context and intelligence layer, which holds human context, business context, intelligence, evidence, connectivity and compliance. Around it sit the systems a person crosses: disability, aged care, health, families, providers, business systems, government, and funders and insurers. Technic preserves context between those systems rather than replacing them.

Technic infrastructure

  • Human context
  • AI Intelligence
  • Connectivity
  • Disability

    Supports and outcomes

  • Aged care

    Quality and wellbeing

  • Families

    Continuity and peace of mind

  • Business systems

    Client systems and operations

  • Government

    Policy, funding and commissioning

  • Funders and insurers

    Utilisation, risk and outcomes

  • Providers

    Programs and service delivery

  • Health

    Clinical and community care

AI personas

Nelly

Supports the person and their families, and the coordination work that surrounds them.

Grace

Helps businesses understand the person, identify gaps and evidence decisions.

The four pillars

What the layer actually does

Human Context

Longitudinal goals, needs, supports, relationships, decisions, risks, budgets, preferences and outcomes, held as a continuous record of a person rather than as one organisation's file.

  • Goals and needs tracked over years, not service periods
  • Relationships and supports as first-class information
  • Decisions and their reasoning, kept together
  • Risk and preference history that travels with the person

Business Intelligence

Grace gives authorised organisations the context and decision evidence relevant to the person they support, helping them identify gaps, risks, changes and next steps.

  • Relevant human context available to authorised teams
  • Decision evidence and reasoning kept together
  • Risks, gaps and changes surfaced as they emerge
  • Suggested next steps and improvements

Intelligence

AI that understands the context around the person and their connected journey, so what it surfaces is relevant, timely and explainable.

  • Understands the role, situation and point in the journey
  • Surfaces patterns, risks, gaps and next-best actions
  • Supports people to make decisions rather than making decisions for them
  • Retains the context and reasoning behind important recommendations

Connectivity

APIs and integration services that let Technic sit alongside existing systems. Nobody is asked to migrate in order to participate.

  • API-first design across the platform
  • Integration rather than platform replacement
  • Authorised context exchanged with existing systems
  • Clear role boundaries between participating organisations

Intelligence

Two assistants, two jobs

Technic does not claim that AI makes decisions on anyone's behalf. Both assistants work with structured context to help people make better-informed decisions.

Nelly

Person-facing intelligence

Supports the plan owner across their support journey, helping surface what matters, what has changed and what may need attention.

Grace

Business-facing intelligence

Helps businesses understand the person, identify gaps and evidence decisions.

Keeping the person-facing and business-facing assistants separate is a design decision, not a packaging one. They serve different people, hold different context and answer to different obligations.

Architecture detail

For the technical reader

One infrastructure layer, built for all human services.

Technic Compliance Engine
The core infrastructure that connects and structures human context, business context, evidence, standards and intelligence.
Human Context Layer
Preserves the person's goals, risks, supports, decisions and journey across systems, organisations and funding changes.
Business Context Layer
Preserves the operational, compliance and decision context organisations need to govern work and demonstrate why decisions were made.
Sonic Connect
Connects Technic to existing systems through APIs, integrations and browser-assisted workflows without requiring platform replacement.
Standards Packs
Configure Technic around the regulatory rules, workflows and data requirements of a particular sector.

Future portability

Built to adapt across sectors

Disability, aged care, health, veterans and other human-service systems have different rules, workflows and terminology. Technic is designed so those differences can be configured without rebuilding the underlying platform.

  • New standards, same foundation

    Sector-specific obligations, evidence requirements and terminology are applied through configurable Standards Packs.

  • Different workflows, common structure

    Each sector works differently, but the need to understand actions, decisions, risks, evidence and outcomes is shared.

  • Human context that can continue

    People often move across services, providers and funding systems. Their goals, history and context should be able to continue with them rather than starting again.

Partnership

Talk to us about integration

If you run a platform, a service network or a funding programme, there is usually a defined first use case worth testing.