See what your customers do while the campaign is still running
Tridan AI does not sell a ready-made e-commerce or customer analytics product. Our engineers build it on your own data and infrastructure, in a 4 to 8 week pilot: orders, carts, conversions, prices, stock and campaign response in one view, flags for the changes you care about, and an AI analyst that explains them in plain language. AI suggests, your people decide.
- On-prem available
- Read-only access
- You approve every action
- Orders, carts, stock and campaigns joined on your data, not a generic templateBuilt in your pilot
- Every flag explains what changed, and no price or campaign changes without a personBuilt in your pilot
- Runs on your servers, customer data stays with youReady today
The Problem
Customers react in hours. Reports often arrive next week.
Today
The team learns what customers did from last week's report.
- Orders sit in the shop, stock in the ERP, campaign results in the ad accounts, and someone joins them in a spreadsheet.
- A campaign underperforms or a promoted product runs out, and the team finds out from the weekly report.
- Reviews, comments and mentions are read by hand, if at all, so the mood around a launch is a guess.
- Every question about sales by store, channel or campaign becomes a request to the analyst and a wait.
With Tridan AI
Orders, stock, campaigns and feedback in one view that refreshes on its own.
- Our engineers connect your sources into one pipeline, so orders, carts, prices, stock and campaigns are in one view.
- Dashboards refresh on their own during the day, and flags for the changes you defined reach the people who can act.
- Written feedback from the sources you choose is grouped by topic and sentiment, so you see what customers say next to what they buy.
- An AI analyst answers follow-up questions in plain language over a read-only copy of your data.
One campaign day, from launch to decision
An illustrative example for an online shop. No customer, no numbers, only the steps we build in a pilot.
- 1
The campaign goes live.
A newsletter and a paid social campaign start in the morning. Orders, carts and campaign clicks flow from your shop and ad accounts into the pipeline our engineers built, through read-only feeds you control.
- 2
Everything lands in one view.
The pipeline joins orders and carts with current prices and stock from your ERP, by campaign, channel and product, the way your team chose in the pilot.
- 3
Something does not add up.
Many carts contain the promoted product, but few of them reach checkout, and stock of the most popular size is running low. Both match rules you defined with us, so the product is flagged.
- 4
The flag explains itself.
The manager sees the campaign, the product, carts against orders compared to a normal day, the stock left, and a short summary of what customers write about the offer in comments and reviews.
- 5
The manager asks a follow-up.
"Did the delivery price for this product change today?" The AI analyst answers from the read-only copy of your data.
- 6
A person decides.
The manager decides to fix the delivery price and pause ads for the size that is running out. Only after that approval does a webhook send the change to your shop, ERP or marketing tool, and the decision is logged so we can tune the rules together.
From your shop, stores and campaigns to your team
- Sources
- Online shop or order system (orders, carts)(Built in your pilot)
- ERP or POS: prices, stock and sales by store (read-only replica or export)(Built in your pilot)
- Campaign, ad and social data via API or export(Built in your pilot)
- Customer calls from an Asterisk based PBX (works today)
- Processing
- Customer and order pipeline(Built in your pilot)
- Joining orders, carts, prices, stock and campaigns(Built in your pilot)
- Rules for drops, spikes and low stock(Built in your pilot)
- AI
- Flag summary in plain language(Built in your pilot)
- Topics and sentiment of reviews and mentions(Built in your pilot)
- AI analyst over a read-only copy of your data
- Human review
- Flags for your team to review(Built in your pilot)
- Manager approves or dismisses (always a person)
- Action
- Customer analytics dashboard(Built in your pilot)
- Webhook into shop, ERP, CRM or marketing tool after approval (target wired in pilot)
- Decision log for rule tuning(Built in your pilot)
- Your teamacts on the results
What exists today, and what we build for you
- CapabilityStatus
- AI analyst: plain-language questions over a read-only copy of data, with human approval of actionsTry it in the demo, we connect it to your data in the pilot.Demo ready
- Webhooks into CRM/ERPAlready used to push call results into CRM and ERP. In the pilot we point it at your shop, ERP, CRM or marketing tool, for approved actions only.Ready today
- DashboardsOur dashboards refresh on their own. The views for orders, carts, stock, campaigns and stores are designed with you in the pilot.Ready today
- On-prem deployment, enterprise AI APIs that do not train on your dataAvailable for every Tridan AI deployment, including this pilot.Ready today
- Customer calls from an Asterisk based PBXCalls are transcribed by speaker within minutes, and AI analysis runs on the calls you choose. See our contact center analytics page.Ready today
- Connection to your shop, ERP, POS, ad and social dataWe connect through a read-only replica, export, API or webhook, depending on your systems. There are no one-click connectors.Built in your pilot
- Pipeline joining orders, carts, prices, stock and campaignsBuilt for your data, your volumes and the speed your case needs. There is no ready-made e-commerce or retail engine.Built in your pilot
- Topics and sentiment of reviews, comments and mentionsSentiment works today for calls. For written feedback we set it up on the sources you choose.Built in your pilot
- Flags and alerts to your teamRules, channel and routing agreed with you.Built in your pilot
What you get in 4 to 8 weeks
One sales channel or one group of stores, one question your team asks every week, and a working answer on your own data.
Deliverables
- A read-only connection to one sales source, such as your shop or POS, plus the price, stock and campaign data you choose
- A pipeline that joins orders, carts, stock and campaigns and checks them against the first set of rules, defined with your team
- Flags for drops, spikes and low stock, each with a plain-language reason, waiting for a person to decide
- The AI analyst connected to a read-only copy of the pilot data, for follow-up questions
- One live dashboard for sales, carts, stock and campaign response, by channel or by store
- A results review with your team, and a written recommendation on whether and how to go to production
Success criteria, defined with you before we start (no numbers promised up front, we agree the targets together)
- Numbers you trust
- whether the dashboard matches your shop and finance reports for the same period
- Useful flags
- how many flags your team considers worth acting on, compared to the noise they dismiss
- Time to notice
- how long it takes from a change in carts, stock or campaign response until your team sees it, compared to today
- Time to answer
- how long a manager needs to answer a typical question, such as why orders dropped yesterday, compared to today
- Team feedback
- whether the views and explanations are clear enough to act on without opening other systems
Customer data stays with you
On-prem
We install the pipeline, dashboard and AI analyst on your own servers, so customer and order data does not leave your infrastructure. We agree which personal fields enter the pilot at all. This supports GDPR and ZZPL aligned processing on your side.
Read-only access
We read from a replica, export or API you control. Nothing in your shop, ERP or POS is changed by Tridan AI.
People decide
AI flags, summarizes and suggests. Only a person on your team approves a price, stock or campaign change, and nothing is sent to another system without that approval.
Controlled AI processing
Enterprise AI APIs that do not train on your data, or a local model option.
Common questions about customer and e-commerce analytics
Do you have a ready-made e-commerce or customer analytics product?
No. Tridan AI does not sell a customer analytics product today. Our engineers build it for you in a 4 to 8 week pilot, on top of parts that already work: webhooks into your systems, dashboards that refresh on their own and on-prem deployment, plus the AI analyst you can try in our demo, connected to a read-only copy of your data.
Does the AI change prices or campaigns on its own?
No. The AI flags changes, explains them and can suggest a next step. A person on your team decides, and nothing is sent or changed without that approval.
Which shop, POS and marketing systems can you connect?
There are no one-click connectors. Our engineers connect your systems through a read-only replica, an export, an API or a webhook, and we agree the first source with you during scoping.
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.
How fresh are the numbers?
That depends on your systems and the decision you need to make. We agree the target freshness with you during scoping, build the pipeline to meet it, then measure it as one of the pilot success criteria.
Can we include customer calls?
Yes. If you run an Asterisk based PBX, customer calls are a stream that works today: recordings are transcribed by speaker within minutes and AI analysis runs on the calls you choose. See our contact center analytics page, and in the pilot we can place call topics next to orders and campaigns.
One sales channel, one customer question, 4 to 8 weeks
No slides. We show it on your data.
Tell us what you want to see before the day is over. We will show you whether your data can answer it.
- On-prem available
- Read-only access
- You approve every action