---
title: "Talk to People Tech Revolution about VR, AR and AI training"
description: "Start with one situation your team wants handled better. Reach People Tech Revolution by chat, voice, the on-screen avatar, a booked call or the contact form."
canonical: https://peopletechrevolution.com/talk-to-us
---

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

# Talk to us.

One situation your team wants handled better is enough to start. Here is what the conversation looks like, from the first call to the day the build ships.

Try a demo before you talk to us: [practise a conversation with an AI](https://labs.peopletechrevolution.com/practice), or [talk to Simon's twin](https://studio.peopletechrevolution.com/connect).

Ask Simon’s Digital Twin a question
Open the contact form

Simon's Twin, here to start the conversation.

## Talk with Simon's Twin about PTR.

Ask about [VR training](https://peopletechrevolution.com/xr), AI roleplay or [a twin for your business](https://peopletechrevolution.com/ai/digital-twins).

[Explore digital twins →](https://peopletechrevolution.com/ai/digital-twins)[Learn about Didymo →](https://peopletechrevolution.com/ai/didymo)

Chat

Voice

Avatar

Book

An open door with the light on.

### Getting in touch is the easy part

No supplier panel, no specification, no quarter of lead time. The message goes to a person and it comes back from one, usually with a question about the situation rather than a menu of products.

What that first exchange is trying to settle is straightforward: whether the thing you want practised is worth building at all.

Telling us the situation, not the solution.

### What to bring

Tell us who has the conversation, where it happens and what goes wrong when it is unrehearsed. That is the whole first brief.

If you have a program already, bring it. Mater Education brought an existing culture program; Google brought real incidents from its own workplace. Both were built on, not replaced.

## The first call

A video call that ends with a yes, a no, or a question we need answered before anything is built.

The first call, with the people who will use the build.

### A yes, a no, or a question

We ask whether practising this in real life is dangerous, impossible, counterproductive or expensive. If it is none of those, we say so and stop there, including when that means telling you not to buy VR, AR or AI from us.

If it is, you leave the call knowing which technology fits, roughly how long the work takes, and who needs to be in the first workshop.

[How we decide the work is real](https://peopletechrevolution.com/about/approach)

## Five stages, from the first workshop to the years after launch

The same five stages run every PTR project. Each has a room it happens in and a thing you hold at the end of it.

Across the table at the first consultation.

Stage one, weeks one to four

### Discovery and consultation

We start with your goals, the people who will use the build and the technology that fits them.

You hold: a clear answer on whether XR or AI earns its place, and a scope for the workshops.

A co-design workshop at the whiteboard.

Stage two, weekly with your team

### Co-design workshops

Your practitioners shape the scenarios in their own language: an alignment session, a concept, scripts, storyboards and agreed constraints. Lived experience sits at the table as an equal.

You hold: signed-off scripts and storyboards that your own people wrote.

Two builders, one floating panel between their screens.

Stage three, months two to six

### Prototyping and development

Environments, characters and features are built and rebuilt: draft builds, two to three feedback rounds and short fortnightly check-ins so nothing drifts from the brief.

You hold: a draft build in your hands at the end of each round.

A tester in the headset while a builder adjusts the screen.

Stage four, before launch

### Testing and deployment

The build goes to the people it is for, on the platforms they use, with the accessibility check done first. Then it ships with analytics and support built in.

You hold: a build your own people have used, and the record of what they said.

The handover: a build in someone else's hand.

Stage five, after launch

### Ongoing support

Guides and workbooks, a high-level review, and a team that stays with the experience as it changes, with clear approval and content-oversight accountability rather than a one-off sign-off.

You hold: a program your own facilitators run, the way Mater Education runs its own.

> "Our ethos from the beginning has been about co-designing solutions alongside people with lived experiences."

Simon Lowe
Co-founder and joint CEO, People Tech Revolution. [SAE Insights](https://sae.edu.au/insights/brisbane-studio-redefines-conversation-on-ageism/)

## What you leave with

Not a deck, not a proposal, not a quote for a quarter of work: a working build your own people have already used, and a clear answer on whether to go further.

A working build on a screen, ready to hand to a colleague.

A web experience that runs in a browser.

An AI practice partner on a screen, no headset in the room.

### And a build that changes with you

The first version is a starting point, not the final word. It keeps changing while your people use it.

A prototype on the table, and a client in the headset.

### Decisions get made on the build, not on a slide about it

For a Fast Build, two weeks in you have something to open on a phone or put in front of a customer.

For a custom program, every feedback round ends with a draft your practitioners have tried, and the next workshop starts from what they said.

[What a Fast Build is](https://peopletechrevolution.com/fast-builds)

## It ends in a conversation

Every route through this page arrives at the same place: two people, one situation, and an honest answer about what can be done with it.

Two chairs, both taken, mid conversation.

### Two chairs, both taken

The first call, the co-design workshop and every review round are the same shape: someone who lives the situation, someone who builds the rehearsal for it, and an hour spent agreeing what actually happens in the room.

Nothing on this page replaces that hour. The rest of it is how the hour gets arranged.

## If the question will not wait

Arranging a first call takes a week. A question does not always give you a week.

A question asked long after hours.

### Ask now, book the call for later

Simon's twin answers from material PTR has approved, at whatever hour you are reading this, and books time with a person when the answer needs one.

[How the twin works](https://peopletechrevolution.com/ai/didymo)

## Where to go next

The approach in full, the three things PTR builds, and the work clients have already run.

[Our approach. Five stages, from the first conversation to the years after launch. The DICE test, co-design with lived experience, and how governance is built in.](https://peopletechrevolution.com/about/approach)
[XR. Virtual, augmented and mixed reality, built to practise the hard human moments. Immersive training, the PTR VR Library, and the devices that run them.](https://peopletechrevolution.com/xr)
[AI. Digital twins and AI practice partners on a screen, a phone or a call. No headset required.](https://peopletechrevolution.com/ai)

### And more places to look

What a Fast Build ships in two weeks, the case studies clients have already run, and Didymo, PTR's own digital twin product.

[Fast Builds. A working build in two weeks: web, mobile, games, events and custom. Brief, build, test, refine, ship.](https://peopletechrevolution.com/fast-builds)
[Case studies. Client by client, what was built and what happened. Mater Education, Mayo Clinic, Google, Central Coast Council and more.](https://peopletechrevolution.com/work/case-studies)
[Didymo. PTR's own digital twin: chat, voice, an on-screen avatar or a booked meeting, answering from a professional's approved material.](https://peopletechrevolution.com/ai/didymo)
