01
Workflows & use cases
The decisions, actions, and applications you want to support, starting with a defined operational need.
Pricing / Built around your organization
Start with what matters.
Build the right scope.
Your workflows, systems, and operating requirements shape the proposal. Define the scope first, with a clear view of the costs and responsibilities.
See nondro in actionA tailored engagement
Custom proposal. Clear scope.
A proposal for the work you want to make possible, from the first connected workflow to your deployment and operating needs.
Plan your proposal Pricing is provided after a scope discussion.What we'll define together
01
Platform & deployment
The environment, access requirements, and capabilities your organization needs.
02
Connections & implementation
The source integrations, ontology, and initial workflows to configure.
03
Usage & ongoing support
AI usage, operating responsibilities, and the support arrangements for your scope.
Inclusions, fees, and service terms are specified in your proposal.
01 / What shapes the proposal
A few practical inputs.
These help us understand the work involved and scope an appropriate deployment.
02
Sources & integrations
The systems to connect, how they can be accessed, and the work needed to model their relationships.
03
Teams & access
Who will use nondro, the roles they need, and the permission boundaries across your organization.
04
Deployment requirements
Infrastructure, networking, security requirements, and the environment where your instance will operate.
05
AI models & usage
The model providers and expected workload, with usage costs and any limits made explicit in the proposal.
06
Implementation & support
Configuration, onboarding, and ongoing assistance, with responsibilities and service terms agreed in advance.
02 / From conversation to scope
Make the first step concrete.
- 01
Share the workflow
Walk through the operational problem, the people involved, and the systems they use.
- 02
Define a focused starting point
Identify the connections, configuration, and deployment requirements for the initial use case.
- 03
Review the proposal
Agree on deliverables, pricing, usage terms, and responsibilities before implementation begins.
A few useful answers
Before we talk.
Are there published plans or fixed prices?
Nondro currently uses tailored proposals. We do not publish fixed plan prices; the proposal sets out the fees and scope for your organization.
Can we start with one workflow?
A focused workflow is a useful starting point for the scope discussion. Its sources, users, and decisions help define the implementation and what success would look like.
How are AI costs handled?
Model choice and workload affect AI costs. Your proposal should specify the charging arrangement, any included usage, limits, and how additional usage is handled.
Do we need to move our source data?
Nondro connects to supported sources in place. The platform stores metadata, knowledge, and audit history. Connectivity and any integration work are assessed during scoping.
What support is included?
Support coverage, response expectations, onboarding, and operating responsibilities are defined in the agreed proposal. They are not assumed to be the same for every deployment.
Plan your proposal
One useful workflow.
A clear starting point.
Tell us what your team needs to accomplish. We'll use that context to begin a scope discussion.
See nondro in actionStart the conversation
A little context goes a long way.
- The workflow or operational challenge.
- Your organization and the teams involved.
- The systems and deployment requirements.
Proposal requests will open here soon. Explore the walkthrough to see how nondro approaches a connected workflow.
See nondro in action