---
title: "Custom AI experiences built around your own knowledge"
description: "Custom AI builds shaped around an organisation's own knowledge and workflow, from digital twins and conversational agents to co-design and support."
canonical: https://peopletechrevolution.com/ai/custom-ai-experiences
---

<!-- Machine-readable copy of https://peopletechrevolution.com/ai/custom-ai-experiences. The HTML at that URL is the
     canonical document; this file is the same words without the markup. -->

[AI](https://peopletechrevolution.com/ai)

# Custom AI experiences

A build shaped around your organisation’s own knowledge and workflow, answering the way your own people do.

The moment

## The question that arrives at eleven at night

A carer in a regional town types a question into your website after a long shift: what the new medication means for her mother’s morning routine. The answer sits in a folder on your shared drive. Your desk reopens at nine. By then she has rung the after-hours line twice.

Your policies, handbooks and recorded briefings become the material the build answers from.

Your answer reaches her at eleven at night, drawn from the same material a daytime answer uses.

One build reaches every site: in writing, by voice, or on a call.

What the build does

## It answers from your material and hands over when it should

Retrieval draws on your approved knowledge, so the answer sounds like your organisation. Guardrails hold it inside what you agreed. Anything that needs a person is queued for one.

Your approved documents are the shelf the build reaches for, and nothing else.

Your safety team reviews what the build may and may not say before anyone outside sees it.

Your visitors who cannot use a keyboard get a control they can.

Bring us the custom AI problem your team has.

[Open the contact form](https://peopletechrevolution.com/ai/custom-ai-experiences#contact)
Ask our CEO Simon Lowe’s Digital Twin a question

Before we build

## What we agree with you before a line of code

Three things are settled before the first line of code is written.

A secure safety net. A protected environment for sensitive conversations, so people get support on difficult topics.

Data ownership and domain expertise. Named vendors under their agreements, data handling you agree before we build, and your subject experts guiding what it can say.

Your clinicians are coached through a session before the build reaches a patient conversation.

Your team maps the workflow the build will sit inside, tile by tile, in the co-design workshop.

Our commitment, after it ships

## What stays true once it is in your people’s hands

Tools that extend the reach of the people already doing the work, for one person or a whole organisation. Approved knowledge, human oversight, configurable boundaries and auditability stay in place.

Your team adjusts the character’s look and voice until it fits the people it serves.

Your reviewers get a working prototype to try, not a slide deck about one.

Your specialists refine the model’s output until the edge cases are clean.

How a build comes together

## From the discovery call to the day after launch

Discovery sets the goal. Co-design workshops shape it with your team. Prototyping builds it, testing readies it for your platforms, support carries it past launch. See [our approach](https://peopletechrevolution.com/about/approach).

Your testers put the build through its paces, and the skeleton shows what it saw.

Your booking calendar sits beside the chat, so a conversation can end in an appointment.

Your reviewer watches a conversation with the approval controls in view.

Where a person stays responsible

## When the knowledge has to be yours and the call has to be human

A custom build needs curated, approved knowledge about your own policy and practice. Licensed professionals stay responsible for clinical and crisis care; the build extends the people already doing that work. [Map where AI fits](https://studio.peopletechrevolution.com/consult) on AI Studio, answer a short set of questions and download the opportunity map, or start on the [AI overview page](https://peopletechrevolution.com/ai).

Your people in a protected space see the companion, and the exit to a human, from inside the headset.

Your mentors run a session inside the headset with the same guardrails as the desk version.

Your support line hands a caller to a person the moment the build reaches its limit.

Inside a headset

## The same build, in the room where the job happens

VR needs a headset. A custom AI build does not, but it can run inside one when the headset is already part of the job: a clinician in the staff room, a lounge host greeting a traveller, an AI presence beside the equipment. Same knowledge, same boundaries, same handover to a person.

Your AI presence appears inside the headset session your staff already run.

Your clinicians practise the patient conversation in the staff room, headset on, between shifts.

Your lounge hosts rehearse the welcome with a traveller who arrives tired and late.

> "AI plays a crucial role here as well, especially now, helping to script and gamify scenarios that provide a more realistic experience. It enables us to craft narratives that adapt in real-time, making the experience progressively more challenging and thus more effective."

Simon Lowe
CEO, People Tech Revolution, on AI inside PTR’s scenarios. [The Cusp of a Revolution, Global Best Practice Group, October 2024](https://globalbestpracticegroup.com/airevolution/)

Bring us the custom AI problem your team has.

[Open the contact form](https://peopletechrevolution.com/ai/custom-ai-experiences#contact)
Ask our CEO Simon Lowe’s Digital Twin a question

### Building a custom experience on top of this

Your developers build on the same pieces through the PTR API and SDK, under an enterprise agreement.

[Developers. What the agreement provides, and what your team can start with today.](https://peopletechrevolution.com/developers)

Your team tells us what it is building, and we arrange the agreement.[Request API and SDK access](https://peopletechrevolution.com/talk-to-us?interest=API%20and%20SDK%20access%20%28enterprise%20agreement%29#contact)

## Related PTR work and further reading

Where digital twins, AI roleplay and PTR’s approach fit alongside a custom build.

[Digital twins. A twin that talks to clients and connects into everyday workflows.](https://peopletechrevolution.com/ai/digital-twins)
[AI roleplay and practice. A practice partner for a hard conversation, no headset needed.](https://peopletechrevolution.com/ai/ai-roleplay-practice)
[Our approach. The process behind every PTR build, from discovery to support.](https://peopletechrevolution.com/about/approach)

## Sources and further reading

NIST guidance on AI risk management and Australian Government policy on responsible AI use.

### [AI Risk Management Framework (AI RMF 1.0)](https://www.nist.gov/itl/ai-risk-management-framework)

National Institute of Standards and Technology · 2023

The framework behind the approved-knowledge and human-oversight commitments above.

### [Policy for the responsible use of AI in government (v2.0)](https://www.dta.gov.au/articles/ai-policy-update-strengthening-responsible-use-across-government)

Australian Digital Transformation Agency · 2025

The government guardrail language the build commitments draw on.
