Design Partner Program

Three steps from a first look to your organisation modelled.

Explore the running demo. Validate Nodwise against your own metadata, identity and security landscape. Then adopt what the validation already built. Nothing is thrown away between the steps.

Apply to the program Open the demo first

The demo is open to anyone with a work account. The program is a limited cohort in this phase.

How adoption works

Explore, validate, adopt.

One path, three commitments, each one answering a question the last one raised. You decide at every boundary whether the next step is worth taking.

Design Partner Program

Sits across the whole path: a limited number of organisations in this phase, with enhanced access and preferential terms at every step.

Step 01

Explore

A running Nodwise tenant modelling Adventure Works, a simulated bicycle manufacturer, dense enough to ask it real questions.

You get
The live demo environment, fictional data, guided sessions and architecture discussion.
Cost
Free — sign in and go
Duration
Immediate — the environment is already running.
Answers
What is Nodwise, and could it carry our use cases?
Next when
The fit looks real enough to test on your own data.

Step 02

Validate

A scoped engineering engagement that puts Nodwise inside your real metadata, identity and security landscape.

You get
A dedicated environment, import of the in-scope metadata, one enterprise source integration, Entra sign-on, reconciliation and a validation report.
Cost
Scoped per engagement — talk to us
Duration
Weeks of engineering — the calendar is set by your security, network and procurement reviews.
Answers
Can Nodwise operate with our data, systems, identities and constraints?
Next when
The success criteria agreed up front are met.

Step 03

Adopt

The validated environment keeps running. Adoption continues from where the validation stopped.

You get
A one- or two-year subscription, the import approach already proven, and an adoption roadmap written from evidence.
Cost
Recurring subscription
Duration
One or two years, then continuous.
Answers
How do we move from a validated environment into sustained use?
Next when
Continuous — new dimensions, sources and teams enter the model.
Step 02 ends on an explicit decision GOCONDITIONAL GONO-GO The criteria are written and signed before the work starts, so the decision is read off evidence rather than argued. NO-GO ends the engagement with no obligation to subscribe.

Step 01 · Explore

See it working before anyone signs anything.

The demo is a Nodwise tenant like any other — the platform we ship, with Adventure Works modelled end to end. It needs nothing from your side: no systems, no network, no identities, no metadata.

Included

  • A functional environment with preloaded fictional data.
  • Graph exploration and relationship traversal.
  • Representative governance use cases.
  • AI-assisted capabilities as shipped.

Not included — and deliberately so

  • Your data, your connectors, your integrations.
  • Microsoft Entra or enterprise network configuration.
  • Import from an existing catalogue.
  • Dedicated infrastructure or production readiness.

Everything on this side is what Step 02 exists to do. Keeping it out of the demo is what keeps the demo free and immediate.

Open the demo environment

Step 02 · Enterprise Validation

Not a proof of concept. The first phase of the deployment.

A disposable POC answers a question and is deleted. The Enterprise Validation is built to be kept: where it is technically and commercially sensible, the environment, the import tooling, the integration and the configuration become the foundation of what you run afterwards.

A dedicated environment

Provisioned for the engagement: application infrastructure, database, storage, networking, secrets, logging and monitoring. Nodwise carries that cost for the agreed validation period.

Import of your metadata

Extraction from your existing catalogue, asset, attribute and relationship mapping, transformation into the Nodwise model, import, and reconciliation you can audit. The inventory is agreed and bounded before extraction.

One enterprise source, connected

Connector configuration or development, authentication, discovery, ingestion, mapping, incremental updates, error handling and monitoring — on one agreed source, validated end to end. Lineage is named in or out explicitly.

Your identity, your rules

Microsoft Entra single sign-on, application registration, user, group and role mapping, provisioning where agreed, and the identity lifecycle tested rather than assumed.

Why the validation is a paid engagement

You are not paying to see the product — the demo does that, free, today. You are paying for enterprise engineering: import, integration, dedicated infrastructure, provisioning, security and networking support, workshops, reconciliation. What you buy is evidence and reduced risk, and a foundation that survives the decision.

Scoped per engagement · pricing on a scoping call

What the fixed scope assumes

A fixed fee needs a fixed frame. Ours assumes timely access to your stakeholders, credentials, environments, network and security approvals, plus an agreed allowance of architecture and security sessions, one identity tenant, one source, one extraction baseline and a defined number of import and reconciliation runs.

Anything materially beyond that is handled as a change request, in the open, before the work happens. No silent overruns, in either direction.

Step 03 · Adopt

Adoption starts from a running system.

On a GO, the subscription continues what the validation already stood up. On a CONDITIONAL GO, the open items become a remediation plan inside the agreement instead of a surprise after signature.

Term

One or two years. A two-year commitment earns a commercial incentive and price protection for the committed term.

What carries over

The imported metadata, the working source integration, single sign-on, the import approach and the security requirements you discovered — all already in place.

What comes next

Further dimensions, further sources, further teams. The roadmap is written from what the validation actually showed, not from a template.

What Design Partner status adds

Early costs you something. It should also buy you something.

Design Partners are not test subjects and this is not a beta. It is a limited group of organisations adopting Nodwise while it is young — and being compensated for that in access, influence and terms. Nodwise is built for your teams to model and integrate on their own; where something is not yet self-serve, partners get first say on what we build next.

Direct engineering access

A line to the people who build the product, for the duration of the validation and the first period of use.

Higher-touch support

Enhanced technical support through the first enterprise deployment, when the questions are hardest.

Roadmap influence

A structured channel into prioritisation. Influence, not control — we say so plainly.

Priority on the connector queue

Design Partners choose which ones we build first — and the connector is yours to run and extend without us. For systems only you run, the documented API means no queue at all.

Early access

Selected capabilities before general availability, with the context to use them well.

Preferential validation terms

Design Partner conditions on the Enterprise Validation, against the standard engagement price.

Subscription price protection

A price lock for an agreed initial term — usually worth more than a one-off discount.

Validation credit

A portion of the validation fee credited against the first subscription when signed within the agreed window.

Multi-year incentive

A two-year commitment carries a commercial incentive on top of the Design Partner terms.

A named counterpart

A solutions architect who knows your model, from the first workshop through to production.

The other side of it

What we ask in return.

The program only works if it runs both ways. None of this is onerous, and all of it is written down before you commit.

Expected

  • Timely access to the stakeholders the work depends on.
  • Structured product feedback, on a rhythm we agree.
  • Participation in the validation workshops.
  • Early engagement from security and architecture.
  • Feedback on enterprise usability and operations.
  • Agreement on measurable success criteria before we start.

Optional — never assumed

  • An anonymous case study.
  • Reference calls.
  • A named public reference.
  • A joint industry presentation, or a quote.

Each of these is a separate, explicit agreement. Nothing on this list is a condition of the program or of the pricing.

Asked before procurement gets involved

Questions this program raises

Is this a beta?

No. You run the product we ship, in an environment provisioned for you, with a signed scope and agreed success criteria. What is early is the company, not the deployment.

Why isn't the validation free?

Because it is real work. Free work gets deprioritised on both sides — a scoped, paid engagement gets staffed, tracked and finished. The free step is the demo, and it is genuinely free.

What happens on a NO-GO?

The engagement ends. You keep the validation report, the import inventory and the security findings, and you are under no obligation to subscribe. The environment is torn down and your data returned or deleted, evidenced.

How long does Step 02 take?

The engineering is measured in weeks. The calendar is usually set by your side: vendor onboarding, security and architecture review, firewall and network changes, service accounts, API approvals, change boards. We plan around those explicitly rather than pretending they take no time.

Do we have to import everything?

No — and "everything" is never the contract. The scope is the in-scope assets and relationships existing at an agreed extraction baseline date, covered by an approved inventory. Anything not named is out until a change request names it.

How many partners are you taking?

A small number in this phase. When the cohort is full, the standard path stays open.

Who is this not for?

Organisations that need a finished vendor with a decade of certifications behind it, or that want no involvement at all from their own architecture and security teams.

Does this make us dependent on your consultants?

No — the opposite is the design goal. What the validation buys is the first mile. Everything built during it is yours to extend, and we would rather you never needed us for the second one.

Apply

Tell us what you'd want modelled first.

Every application is read by a person. If there is a fit, the next thing that happens is a scoping conversation — not a sales sequence.

01

You apply

Four fields. Every application is read by a person, and we come back as soon as we can.

02

Scoping conversation

We define the success criteria, the extraction baseline, the one source, and what your security review will need. That is what the validation is priced against.

03

Validation, then the decision

Work runs to the agreed scope and ends on GO, CONDITIONAL GO or NO-GO.

Apply to the program

0 / 5

We review every application personally and reply within a few business days. Required fields are marked *.

Optional, and the most useful thing you can tell us.

5 required fields left.

You can withdraw your consent at any time by writing to privacy@nodwise.com. No marketing spam.

Received

Thank you. A person reads every application — we will come back to you within a few business days.

Meanwhile, the demo is open right now to anyone with a work account.

Open the demo