Build your first Twin

You do not need to map the whole company before the Twin becomes useful. The best starting point is one recurring question or workflow where shared business meaning would make a real difference.

Start with an outcome

Choose something specific enough to review. For example:

• understand monthly revenue using the finance team’s definition;
• explain which invoices are overdue and why;
• show the current stage of each customer onboarding;
• summarise delivery risk across active projects; or
• prepare a weekly view of sales activity.

“Connect everything” is not a useful first goal. A focused outcome makes it clear which evidence is needed and who should review the result.

Bring in the smallest useful set of sources

Your implementation contact or organisation administrator helps connect the systems that support the chosen outcome. The first version may need only one or two sources.

For monthly revenue, that might be the accounting system plus an approved definition from finance. For customer onboarding, it might be a CRM, a project channel, and a documented process.

Your Twin shows whether a connection has merely been configured or has successfully provided usable evidence. This helps everyone distinguish setup from a connection that has actually been verified.

Review the business meaning

The Twin can do much of the discovery work, but the people who know the business make the important decisions.

Reviewers should be able to answer:

• Does this describe the measure or process we actually use?
• Are the right sources included?
• Are any important exclusions or exceptions missing?
• Is the information fresh enough for the intended use?
• Who should be allowed to use the published result?

Publish and activate a first useful version

Once the result is approved and its required checks pass, it can be published as a stable version. The implementation team then completes the validation and deployment checks required to activate that exact version for its intended use. You can test it with real questions before making it available more widely.

The first version does not need to solve every related problem. It needs to be useful, understood, and reviewable.

Follow the review and publication guide when you are ready to check a proposal in the Twin workspace.

Activation does not automatically make the result available through every AI tool. External connections have their own approval, identity, and access checks.

Grow from real demand

Questions from users reveal what the Twin should learn next. A common unsupported question may point to:

• another source that should be connected;
• a definition that needs clarifying;
• a missing relationship or process stage; or
• an existing piece of knowledge that needs updating.

This lets the Twin grow around actual business needs rather than becoming a large modelling exercise with no clear user.

Who is usually involved