Skip to main content

Company

Built at the point where systems collide

Technic began inside support coordination, where the practical difficulty of connecting participants, providers, plan managers, government, health, housing, family, funding and service systems is a daily problem rather than a strategy slide.

Our story

From one hard problem to the layer underneath it

Support coordination sits between everything. A coordinator holds the relationships that no single system holds: the participant and their family, the providers delivering support, the plan manager paying for it, the health service treating them, the housing provider, the government scheme funding the plan.

Technic started by structuring that work. Making practice consistent, capturing evidence as it happened, and giving providers a defensible account of what they did and why.

It became clear that the structure being built was not specific to support coordination, or to the NDIS. The same problem exists wherever a person crosses organisational boundaries in a regulated care system, and the same structure solves it.

Technic is now expanding that insight into broader human-services infrastructure, while the products that proved it keep running in production.

How we work

What Technic optimises for

  • Industry-led

    Built from operating inside the sector, not from a technology theory applied to it from outside.

  • Structural, not superficial

    We look for the structural problem underneath a workflow complaint, because that is the one worth solving once.

  • Safe by construction

    Security, privacy, governance and risk are design inputs. In this sector they are not features you add later.

  • Human-centred

    Technology exists to improve continuity, decisions and outcomes around people. Everything else is implementation detail.

Leadership

The people behind Technic

Technic is led by people who have built and run services inside the systems the company is now connecting.

  • Nic Farman

    Nic Farman

    Technology & Innovation

  • Deon Metcalf

    Deon Metcalf

    Technology Operations & Security

  • Sid Raje

    Sid Raje

    Lead Development

Security and governance

Enterprise expectations, met by design

Technic works with sensitive information in regulated settings. The statements below reflect current status and are reviewed before every release.

  • Secure by design

    Security is a design principle rather than a later addition. Access, evidence and data handling are considered when a workflow is specified, not after it ships.

  • Encryption in transit and at rest

    Technic systems use encryption in transit and at rest where supported by the current production architecture.

  • Role-based access control

    Role-based access, multi-factor authentication and least-privilege controls are applied where applicable to the product and its users.

  • Documented incident response

    Documented incident response, backup and recovery processes sit behind the platform, with governance reviewed as the business grows.

  • Australian hosting

    Technic runs on Google Cloud with Cloudflare, hosted in Australia for the products where that claim is current.

  • Privacy and data handling

    Technic works with sensitive information in regulated settings. Data handling, retention and disclosure follow documented policy rather than case-by-case judgement.

For a copy of Technic's current security documentation, contact us and we will route your request to the right person.

Traction

Where the model has been proven

Technic built and tested this model inside the NDIS, one of the most complex regulated human-services environments in the world.

  • 1,000+

    professionals in the proving environment

  • 16,000+

    people represented in real-world journeys

  • Millions

    of workflow records informing the architecture

Investors

Open to strategic and financial partners

Technic is open to strategic and financial partners who can contribute industry leverage as well as capital, particularly where a partner can accelerate adoption, distribution or integration.

  • The market shift

    Care systems are increasingly expected to work around the whole person rather than around a single sector, provider or software boundary. That direction creates demand for shared foundations, data continuity, safety and evidence.

  • The infrastructure thesis

    The opportunity is not another vertical platform. It is the layer that lets specialised systems keep their specialisation while sharing context.

  • Proven in a hard environment

    Technic built and operates production software inside the NDIS. The regulatory and commercial constraints there are a reasonable proxy for other regulated care systems.

  • Cross-sector expansion

    A new sector is a standards pack and a workflow context rather than a new platform, which is what makes expansion a configuration problem rather than a rebuild.

Detailed commercial material is shared directly rather than published. Request investor information and we will respond with what is appropriate to your interest.

Investor enquiry

Request investor information

Tell us who you are and what you would like to understand. Your enquiry goes to the Technic business team.

A few lines on what you have in mind is enough to start a conversation.

Technic uses these details to respond to your enquiry. Please do not include participant, client or health information in this form.