Built in your pilotBuilt in your pilot

Give your customers live numbers inside your own product

Tridan AI does not sell a packaged embedded analytics product. Our engineers build it for you in a 4 to 8 week pilot: the data pipeline, the separation that keeps each customer to their own data, and dashboards you embed in your portal or an API for your own app. Your customers see their usage, orders, service levels and account health. We build and maintain it, you decide what they see.

  • On-prem or hosted
  • Read-only access
  • You approve every action
  • Each customer sees only their own data, enforced on the serverBuilt in your pilot
  • Live views in your portal, or an API for your own screensBuilt in your pilot
  • Runs on your servers or hosted by us, your choiceReady today

The Problem

Your customers want their numbers now. Your team sends them a spreadsheet next week.

Today

Customer reports are built by hand and out of date on arrival.

  • Customers email your account team for order status, usage or service level numbers, and someone puts a spreadsheet together by hand.
  • Reports go out monthly as PDF or Excel files that are already out of date when they are opened.
  • Building customer facing analytics in house pulls your product team away from the roadmap.
  • One wrong filter in a manual export can show one customer another customer's data.

With Tridan AI

Each customer sees their own live numbers inside your portal.

  • Customers open a live view inside your portal and see their own numbers without waiting for anyone.
  • Dashboards refresh on their own, fed by the pipeline our engineers build on your data.
  • Our engineers build the pipeline, the per-customer separation and the embeddable views in the pilot, and maintain them for you.
  • Each customer sees only their own account, enforced on the server and tested with your team before anything goes live.
Example scenario

One customer, one login, their own numbers

An illustrative example of a supplier portal for business customers. No real customer, no numbers.

  1. 1

    Your customer signs in.

    A purchasing manager at one of your business customers logs into your existing portal, with the login you already have.

  2. 2

    The portal asks for their data.

    The embedded dashboard, or your own screen through our API, requests the numbers for that one account. The account comes from the signed-in session on the server, not from anything the browser can change.

  3. 3

    The pipeline has it ready.

    Orders, deliveries and open tickets, joined from your order system and helpdesk through a read-only connection, are prepared in the views we designed with you.

  4. 4

    They see live numbers.

    Open orders, on-time delivery against their agreed service level and this month's usage, in your product's look, refreshing on their own.

  5. 5

    Your account team sees the bigger picture.

    Internally, an account health view shows which customers use less or miss service levels. Your team asks the AI analyst "Which accounts had more late deliveries this month than last?" over a read-only copy of the data.

  6. 6

    A person decides.

    If an account looks at risk, the view suggests a follow-up. Only after your account manager approves does a webhook create the task in your CRM. Nothing is sent to the customer automatically.

Data flow

From your systems to your customers' screens

  1. Sources
    • Your product database or order system(Built in your pilot)
    • Helpdesk, billing or CRM via API or webhook(Built in your pilot)
    • Read-only replica or export you control(Built in your pilot)
  2. Processing
    • Data pipeline(Built in your pilot)
    • Per-customer data separation(Built in your pilot)
    • Metrics for usage, orders, service levels and account health(Built in your pilot)
  3. Delivery
    • Embeddable dashboards in your portal(Built in your pilot)
    • API for your own app screens(Built in your pilot)
    • Sign-in through your existing login(Built in your pilot)
  4. Your team
    • Internal account health view(Built in your pilot)
    • AI analyst over a read-only copy of your data
    • Account manager approves (always a person)
  5. Action
    • Webhook into CRM or ERP after approval (target wired in pilot)
    • Alerts to your account managers(Built in your pilot)
  6. Your teamacts on the results
Built in your pilotExample layout. Items marked with a badge are built for you in the pilot.
Ready vs built

What exists today, and what we build for you

  • Webhooks into CRM/ERPAlready used to push call results into CRM and ERP. In the pilot we point them at your CRM for approved follow-ups.Ready today
  • Dashboards that refresh on their ownOur dashboards already refresh on their own. The customer facing views and metrics are designed with you in the pilot.Ready today
  • Embeddable componentsTridan AI already ships an embeddable AI chat widget for websites. The analytics views for your portal are built in the pilot.Ready today
  • On-prem or hosted deployment, enterprise AI APIs that do not train on your dataAvailable for every Tridan AI deployment, including this pilot.Ready today
  • AI analyst: plain-language questions over a read-only copy of data, with human approval of actionsTry it in the demo. In the pilot we connect it to your data for your own team.Demo ready
  • Connection to your product, order and customer dataWe connect through a read-only replica, export, API or webhook, depending on your systems.Built in your pilot
  • Data pipeline and per-customer data separationBuilt and tested for your data model. There is no ready-made embedded analytics product.Built in your pilot
  • Embeddable dashboards or an API for your appYour choice, styled to match your product and agreed with your product team.Built in your pilot
  • Sign-in through your existing loginYour customers keep the login they already use. We connect to it in the pilot.Built in your pilot
  • Self-serve report builder for your customersYour customers see the views we design with you. New views and metrics are added by our engineers.Not offered
Your Pilot

What you get in 4 to 8 weeks

One data source, a small group of your customers, and live numbers inside your product by the end of the pilot.

Deliverables

  • A read-only connection to one product or order data source, plus the customer list that defines who sees what
  • A pipeline that prepares the first set of customer metrics, such as usage, orders and service levels, agreed with you
  • Per-customer data separation, enforced on the server and tested with your team before any customer sees it
  • Embeddable dashboards for your portal, or an API your developers call from your own screens, styled to match your product
  • One internal account health view for your account team, with the AI analyst on a read-only copy for follow-up questions
  • A results review with your team, and a written recommendation on whether and how to roll out to all customers

Success criteria, defined with you before we start (no numbers promised up front, we agree the targets together)

Data separation
whether every test account sees only its own data, checked together with your team
Freshness
whether the numbers update fast enough for what your customers look at, against the target agreed in scoping
Load time
how quickly the embedded views open inside your portal for your pilot customers
Fewer manual requests
how many report and status requests your team still handles by hand, compared to today
Customer feedback
whether pilot customers find the numbers clear and use them without asking your team
Security

Your customers' data stays separated and under your control

Each customer sees only their own data

The account is taken from the signed-in session on the server, and every query is limited to that account. We test this with your team before any customer sees a dashboard.

On-prem or hosted

We install the pipeline and dashboards on your own servers, or host them for you. With on-prem, customer data does not leave your infrastructure. This supports GDPR and ZZPL aligned processing on your side.

Read-only access

We read from a replica or export you control. Nothing in your product database is changed by Tridan AI.

People decide

Dashboards show and suggest. Only your account manager approves a follow-up, and nothing is sent to a customer or another system without that approval.

Controlled AI processing

Enterprise AI APIs that do not train on your data, or a local model option.

FAQ

Common questions about embedded analytics

Do you have a ready-made embedded analytics product?

No. Tridan AI does not sell a packaged embedded analytics product. Our engineers build it for you in a 4 to 8 week pilot, on top of parts that already work: dashboards that refresh on their own, webhooks into your systems, on-prem or hosted deployment, and the embeddable components we already ship, such as our AI chat widget.

Can our customers build their own reports?

No. This is not a self-serve report builder. Your customers see the views and metrics we design with you. When you need a new view, our engineers add it.

How do you make sure one customer never sees another customer's data?

The separation is built on the server, not only hidden in the browser. The account comes from the signed-in session, and every query is limited to it. Testing this with your team is one of the pilot success criteria, before any customer sees a dashboard.

Embedded dashboard or API, which one do we get?

Your choice. We can deliver dashboards you embed in your portal, or an API your developers call to show the numbers in your own screens. Some teams use both. We agree this with your product team during scoping.

Who maintains it after the pilot?

We do. Our engineers build it and maintain it for you, including new metrics and views. You do not need a data team of your own to keep it running.

How live are the numbers?

Dashboards refresh on their own. How fresh the data needs to be depends on what your customers look at, so we agree the target with you during scoping and measure it in the pilot.

Does our customer data leave our servers?

Not with on-prem. We install everything on your infrastructure and read from a replica or export you control. If you choose AI processing through enterprise APIs, those APIs do not train on your data, and a local model is also an option.

One data source, one customer view, 4 to 8 weeks

No slides. We show it on your data.

Tell us which numbers your customers ask for most. We will show you how they would look inside your product.

  • On-prem or hosted
  • Read-only access
  • You approve every action