Technical Documentation

{{branding.parent}} · {{product.nameUpper}}

Welcome to the employee page.

Everything you need to get up to speed on {{product.name}} and take it into a client conversation, in one place. Pick the path that matches what you are here to do; you can switch at any time with the tabs above.

Path 1 · Learn

I want to know more about {{product.name}}

Get up to speed on the problem it solves, how it works and who it is for, at your own pace.

A 3-minute introduction tour
Three-level learning path
Searchable FAQ knowledge base

Start learning →

Path 2 · Sell

I want to sell {{product.name}}

Tailor your pitch, handle objections, qualify the opportunity and keep the pipeline up to date.

Conversation guide and elevator pitch
Positioning, objections, qualification
The shared deal tracker

Start selling →

Path 3 · Demo

I want to demo {{product.name}}

Show the product: play the recording, or prepare a live demo with a tested script.

Demo video and intro deck
Demo scripts by format and audience
Shared demo hub

Start demoing →

Path 4 · Build

I want to build with {{product.name}}

See where the product is heading and find the technical documentation for engineers and architects.

The release roadmap
Technical enablement portal

Start building →

LEARN {{product.nameUpper}} IN 3 MINUTES

The {{product.name}} introduction tour

Swipe through six slides: the problem, the solution, how it works, who it is for, proof and how to start. Edit the slide copy below to make it yours.

01 / 06 — The problem

The problem our clients face

[Replace: two or three sentences describing the client pain point {{product.name}} addresses, in the client's language, and what it costs them today in time, money or risk.]

[Replace: pain point 1] [Replace: pain point 2]

02 / 06 — The solution

{{product.category}} [Replace: key differentiator]

03 / 06 — How it works

Three layers, one outcome

Layer 1: [Replace: name] — [Replace: what it does, one line]
Layer 2: [Replace: name] — [Replace: what it does, one line]
Layer 3: [Replace: name] — [Replace: what it does, one line]

See the Platform page

04 / 06 — Who it is for

Buyers, users and sponsors

Economic buyer — [Replace: role and what they care about]
Day-to-day users — [Replace: role and what changes for them]
Technical stakeholders — [Replace: role and their typical concerns]
Best-fit sectors — [Replace: sectors or client profiles]

05 / 06 — Proof

What good looks like

[Replace: metric] — [Replace: measured outcome and how it was measured]
[Replace: metric] — [Replace: measured outcome and how it was measured]
Only quote figures and references that have been approved for external use; check with your account lead.

06 / 06 — How to start

From first conversation to scale

1. Explore — discovery conversation and demo
2. Prove — a time-boxed pilot on real client data
3. Scale — roll out, then run as a service or hand over
[Replace: typical duration of each step]

Request a session

Level 1 · Foundations

I can explain it

Understand the problem, the value and the vocabulary well enough to hold a first conversation.

Do this: take the introduction tour above; read the Platform page; skim the FAQ below; [Replace: link to intro recording or e-learning].

Suggested effort: about 1 hour · Outcome: give a 2-minute explanation to a colleague

Level 2 · Practitioner

I can pitch and demo it

Run a discovery conversation, qualify the opportunity and deliver a standard demo.

Do this: work through the Sell tab guide and objection handling; shadow one live demo; deliver the 5-minute demo script to a peer; [Replace: link to practitioner workshop].

Suggested effort: 1–2 days · Outcome: lead a first client call with a peer observing

Level 3 · Expert

I can design and deliver it

Shape a solution, scope an engagement and guide implementation.

Do this: read the enablement portal (architecture, deployment, integrations); complete a hands-on lab; support one live engagement; [Replace: link to certification or expert programme].

Suggested effort: 1–2 weeks · Outcome: own a solution design review

Who to ask: [Replace: product owner, enablement lead and Teams channel]. Support link, if configured: support channel.

🔍

No matching questions found. Try a different search term.

CONVERSATION GUIDE

How to sell {{product.name}}.

Answer two questions about the client. Get a tailored recommendation with talking points. The themes and engagement options are editable in the SELL_GUIDE block at the bottom of this page.

VALUE — Which theme?

What value do they need most?

ENGAGEMENT — Which approach?

What is their appetite for change?

Select options on both sides to see your recommendation

Theme

Approach

VALUE THEME

How it adds value

Use cases

Typical client questions

Tech & data foundation

Best-fit customers

Indicative timeline

ENGAGEMENT APPROACH

Commercial shape

Cost drivers

What is included

PLAYBOOK

Pitch, position, handle, qualify.

Starter scaffolds. Fill them in with your agreed messaging, then keep them current.

ELEVATOR PITCH

Say it in 30 seconds.

30-second template

"For [Replace: target buyer] who struggle with [Replace: problem], {{product.name}} is a {{product.category}} that [Replace: what it does]. Unlike [Replace: the alternative they use today], we [Replace: key differentiator]. Clients typically see [Replace: approved proof point]."

Tips

Lead with the client's problem, not the technology.
One proof point, not five.
End with a question or a next step.

Two-minute version: structure

Context — what is changing in the client's world? [Replace: one line]
Problem — what does that cost them? [Replace: one line]
Solution — what {{product.name}} does about it. [Replace: tagline-level statement]
Proof — an approved result or reference. [Replace: proof point]
Next step — the specific ask: a demo, a workshop or a pilot scoping call.

POSITIONING

Where {{product.name}} fits.

We are the right choice when

[Replace: client situation 1]
[Replace: client situation 2]
[Replace: client situation 3]

Alternatives clients consider

Do nothing / status quo — [Replace: why this is costly]
Build in-house — [Replace: trade-offs]
Competing product or vendor — [Replace: how we differ, factually]

Not a fit when

[Replace: out-of-scope scenario]
[Replace: prerequisite the client lacks]

Saying "not yet" early protects credibility and pipeline quality.

OBJECTION HANDLING

Hear it, acknowledge it, answer it.

"We already have something for that."

Acknowledge: that is common, and it is a good starting point.
Answer: [Replace: how {{product.name}} complements or improves on the existing tool]
Ask: "What would you change about it today?"

"How do we know it is secure and compliant?"

Answer: describe the approved security posture, [Replace: link to approved security summary].
Do not make compliance or certification claims yourself; involve Security and the Data Privacy Officer early.

"It is too expensive / not budgeted."

Answer: reframe on outcome and cost of inaction; offer a smaller, time-boxed first step.
Do not quote prices from this page; use your commercial lead and the approved price book.

"We do not have the people or time."

Answer: [Replace: what the team provides vs. what the client must provide]
Show the lightest-touch engagement option.

"Prove it works for us."

Answer: propose a proof of value with success criteria agreed up front.
Use only references approved for external use.

Your own

[Replace: objection heard in the field and the agreed response]
[Replace: objection heard in the field and the agreed response]

QUALIFICATION

Is this a real opportunity?

Need

What problem are you trying to solve, and why now?
What happens if nothing changes?
[Replace: product-specific discovery question]

Authority & budget

Who owns this decision, and who else is involved?
Is there budget, or a route to it? Over what period?
How have similar decisions been made here?

Readiness & timing

What systems and data would we need to connect?
Are security and procurement requirements known?
What is the target start date and what drives it?

⚠

Qualified? Log it in the deal tracker (when enabled) with an honest stage and probability. Keep client-confidential details out of free-text fields, and out of this site entirely.

Pitch deck

The current introduction deck: the story, the model and proof points. Use it to brief, or leave it behind (check the client may receive it first).

Open the deck

Team tool

Deal tracker

The team pipeline: log new conversations, tag hot deals and services, and see where the weighted value sits.

Open the deal tracker →

Show it

Demo video & scripts

The recorded walkthrough and live-demo scripts are on the Demo path.

Go to Demo {{product.name}} →

Demo video

{{product.name}} product demo

A short, self-running walkthrough: the fastest way to make the product concrete in a conversation.

Watch the demo

Pitch deck

The current introduction deck, to talk over or leave behind.

Open the deck

Team tool

Demo hub

Find, book and track the shared demo environments, and see who has which one and until when.

Open the demo hub →

Choose a format

Three standard formats cover most situations.

5 min

Lightning demo

One problem, one moment of value. For corridor conversations, events and executive intros.

Environment: recording or sandbox

20 min

Standard walkthrough

Three or four scenarios tied to the client's stated needs, with time for questions.

Environment: shared demo environment

60 min

Working session

Interactive workshop where the client's team drives. For late-stage and technical audiences.

Environment: dedicated demo environment

Choose an environment

Recording no setup

Plays the same every time and cannot fail live. Best for first conversations and remote audiences. Less convincing for specific questions.

Shared sandbox minutes

A common environment with generic sample data. Good for the standard walkthrough. Check nobody else is using or resetting it. [Replace: environment URL or how to request access; do not publish credentials on this page]

Dedicated, themed environment plan ahead

An environment loaded with synthetic data in the client's sector. Most convincing in the room. Allow lead time and confirm the expiry date. [Replace: how to request one, who approves, typical lead time]

⚠

Use synthetic or approved data only. Never load real client data, credentials or personal data into a shared or demo environment. Make clear that demo figures are illustrative and not the client's actual performance. If you are unsure whether data is permitted, ask the Data Privacy Officer first.

Prepare: know your audience

Find out who will attend, their roles, what they have seen before and the one or two problems they care about. Agree the length and format in advance. Write down the three things you want them to remember.

Rule of thumb. If you cannot state the client's problem in one sentence, you are not ready to demo yet. Go back to discovery.

Set up the environment the day before

Reserve the environment (use the demo hub if enabled), log in, check the data looks right and walk the whole script once. Confirm the expiry date, close unrelated tabs and notifications, and have the recording ready as a fallback.

Fallback. Keep the demo video open in a tab. If the live environment fails, switch without apology and carry on.

Open (first 2 minutes)

Restate the client's problem in their words, say what you will show and how long it takes, and invite interruptions. Do not start with a tour of the interface.

Script

"You told us that [client problem]. In the next [N] minutes I'll show how {{product.name}} deals with that, using [scenario]. Stop me any time."

Core storyline: three scenarios

Show the product doing work, not the menu. For each scenario use the same rhythm: situation, action in the product, result, and "so what" for the client.

Scenario 1: [Replace: name] about 5 min

[Replace: situation, the clicks or prompts to show, the expected result, and the business takeaway.]

Scenario 2: [Replace: name] about 5 min

[Replace: situation, the clicks or prompts to show, the expected result, and the business takeaway.]

Scenario 3: [Replace: name] about 5 min

[Replace: situation, the clicks or prompts to show, the expected result, and the business takeaway.]

Handle questions and "can it do X?"

Answer what you know. For what you do not know or what is on the roadmap, say so and promise a follow-up. Never demonstrate or promise an unreleased feature as available. Park deep technical questions for a dedicated session with an architect.

Close and follow up

Recap the three things you wanted them to remember, agree one concrete next step (pilot scoping, technical workshop, stakeholder intro), and send a short follow-up within 24 hours. Update the deal tracker if it is enabled.

Clean up

Release or reset the environment, remove any client-specific content you added, and note what worked and what did not so the next presenter benefits. Anything worth keeping should be copied into a document: environments can expire without notice.

Open the demo hub →

Now · Live

Release {{product.version}}

What clients can use today

Live capabilities

[Replace: capability 1]
[Replace: capability 2]
[Replace: capability 3]

Next · [Replace: quarter] · preliminary scope

Next release

What we are building now

New & evolving capabilities

[Replace: capability 4]
[Replace: capability 5]

Platform themes

[Replace: quality, performance or governance theme]
[Replace: UX or integration theme]

Later · On the horizon

Direction of travel

Where we want to go

Candidates

[Replace: capability 6]
[Replace: market or technology bet]

Roadmap items are indicative and may change. "Next" scope is preliminary; "Later" is direction, not a committed delivery date. Do not present unreleased items to clients as available. Release notes: enablement portal.

01 · Architecture

Architecture overview

System context, major components, request lifecycle and data tiers.

02 · Components

Components & capabilities

A catalogue of the building blocks and what each one can do.

03 · Features

Feature reference

Every feature: what it does, how it works, how it is configured and how it links to others.

04 · Operations

Operations

Run-time operation: monitoring, support, administration and troubleshooting.