Perspio™ Partner Programme — Embedded Partners
Inauro | Partner Programme
Track A Partner programme

Perspio inside
your product.
Your customer. Your deal.

Embedded Partners integrate Perspio directly into their own product — extending what their platform does without rebuilding it. You own the customer relationship end-to-end. Inauro provides the platform capability and technical support behind the scenes.

Configurable scope Embed only what your product needs — nothing more
Fully white-labelable Perspio branding is always customer-configurable
You own the relationship Inauro operates as your technical support layer
How it works
Perspio as a configurable layer

There is no fixed embedded scope. What Perspio does inside your product is defined by what your customers need and where the upsell to deeper capability makes commercial sense. Inauro works with each embedded partner to scope the integration, agree the commercial model, and define the upsell path.

Scoped to your use case
Perspio can be configured to expose only the connectors, data views, and capabilities relevant to your product. You define the scope in collaboration with Inauro.
Branded how you need it
The embedded experience can carry your product brand, a co-branded identity, or the full Perspio brand. Branding is agreed as part of the embedded partner setup and is always customer-configurable.
Built for upsell
The embedded scope is a starting point. As customers see value and their needs grow, the path to deeper Perspio capability is already inside the product they're using.
Illustrative patterns
What embedding can look like

No two embedded partnerships are identical. These patterns illustrate the range — from a focused data layer to a broad integration capability embedded within a host platform.

Pattern 1
A targeted data layer within an existing product
Perspio is scoped to deliver a specific, bounded capability within the partner's product — surfacing a particular category of asset data or resolving a focused integration problem. The embedded experience is contained and purpose-built for the partner's customer base.
Upsell path: Once customers see value from the embedded scope, the conversation opens naturally toward broader Perspio capability — connecting more systems, covering more asset types, or moving up the maturity ladder.
Pattern 2
Perspio as the integration backbone of the host platform
Perspio sits at the core of the partner's product as the layer that normalises and routes asset data into the host platform's workflows. The partner's customers experience Perspio as a native capability of the product they already use.
Upsell path: As customers' operational complexity grows — more systems to connect, deeper automation needs, enterprise-scale workflows — additional Perspio capability layers in without disrupting the existing integration.
Upsell recognition
Signals that a customer is ready for more

The upsell from embedded scope to deeper Perspio capability is a maturity conversation. Customers signal readiness through the questions they ask and the outcomes they start describing. Listen for these.

L1 L2
Visibility → Suggestion
They want to act on what they're seeing
Can it alert us when this threshold is crossed?
We want someone notified automatically when this happens
Is there a way to flag this to the right team without us checking every day?
L2 L3
Suggestion → Control
They want Perspio to act, not just recommend
Can it update our system automatically rather than us doing it manually?
We want the job created in our maintenance platform when this triggers
Is there a way to push this data directly into our ERP?
L3 L4
Control → Automation
They want end-to-end workflows with no human steps
We want this to run without anyone having to approve it each time
Can it handle the whole process — from signal to outcome — automatically?
We're looking at removing the manual step entirely
Platform signals
Outgrowing the embedded scope
They're asking about use cases your embedded scope doesn't cover
They're referencing operational problems in systems Perspio isn't currently connected to
They're asking whether Perspio can integrate with their ERP, CMMS, or billing platform
Their fleet or operations have grown beyond the original embedded use case
The upsell conversation
How to move the conversation forward

When a signal appears, you don't need a new sales pitch. The customer is already using Perspio — they're asking whether it can do more. The answer is yes. Your job is to open that door.

When a customer signals readiness
"What you're describing is exactly where Perspio can take this further. What you've got now gives you [current embedded capability]. The next step connects that to [the system or outcome they described] — which means [specific result]. That's a conversation worth having. I can bring the right people in to scope it with you."
The customer is already in your product. The upsell is a natural extension of something they've already decided works — not a new sale. You stay in the room. Inauro provides the technical depth to scope and close it.
Making it land
1
Mirror their language. Use the outcome they described, not Perspio feature names. They said "push data into our ERP" — say that back, not "L3 write-back."
2
Don't over-promise scope. The upsell path is defined per partner. If you're unsure what deeper capability looks like for your embedded setup, bring Inauro in to scope it rather than committing to specifics.
3
You stay in the deal. Inauro comes in as technical support and implementation — not as a replacement for your customer relationship. The commercial outcome is still yours to structure.
4
Flag the signal early. The sooner Inauro knows an upsell is in play, the better the scoping conversation will be. Don't wait until the customer has already decided what they want.
Your commercial model
You own the customer. Inauro backs you.

The embedded partner model is built on the same principle as the reseller track — you own the customer relationship and the commercial outcome. Inauro operates as your technical support layer, not as a competing presence in the account.

What you own
The customer relationship — from embedded product through to expanded capability
The commercial structure — what you charge, how you package it, and what sits on top
The upsell motion — Inauro supports, but the deal is yours to run
Your consulting and services margin — implementation, configuration, managed service
What Inauro provides
Platform access at agreed embedded partner terms
Technical scoping and implementation support for expanded deployments
Product depth in customer conversations when you need it
Ongoing platform development — new connectors, new capability, roadmap access
Upsell process
Bringing Inauro into an expanded opportunity

When a customer signals readiness to go further, a simple handoff to Inauro gets the scoping started — without disrupting your customer relationship.

1
Flag the signal to your Inauro partner lead
Share what the customer said, what embedded scope they're on, and what they're asking about. A brief message is enough — Inauro will come back with questions.
2
Inauro scopes the expanded capability
Inauro will identify which use cases apply, what systems need connecting, and what the implementation looks like. They'll come back to you with a position before any customer conversation.
3
Joint customer conversation — you in the lead
Where a customer meeting is needed, you lead it. Inauro provides technical depth. The customer's experience is of their existing partner bringing in specialist support — not a new vendor.
4
You close, Inauro implements
The expanded commercial is yours to close. Inauro handles implementation and technical onboarding. Your customer relationship is intact and extended — not transferred.
Get started
Interested in embedding Perspio?
The setup is scoped individually with Inauro. The starting point is a conversation about your product, your customer base, and where a Perspio integration layer adds the most value.
Talk to Inauro