From reports,
to results.
Put your best operators' playbook to work in every store.
Store, member and lead data in one operating data layer.
Issues go to the right store and owner, with an auto re-check after 14 days.
Daily reports, weekly reports and monthly decks write themselves.
Start from Excel · Works with your existing CRM / ERP · Phased rollout
Demo on the right · one day at a sample brand
Review round 1 · every fix re-checked after 14 days
The reports are done.
Nothing gets fixed.
BI tools already turn spreadsheets into dashboards well. PDOS picks up where the dashboard stops: issues go to an owner, work comes back with proof, results get reviewed. One loop a week.
- 20+ sheets to reconcile
- Every level counts differently
- Problems surface at month end
- One set of numbers, live charts
- Any BI tool gets you this far
- But who fixes it, and did it work? A dashboard can't tell you
- Each issue goes to a named owner
- Proof and photos come back automatically
- Auto re-check in two weeks; the next round is sharper
A dashboard ends at a chart.
PDOS ends at a verified action.
Finding: 70% of the lead gap sits in these 3 stores. Slow first response is the first thing to check.
Fix slow first response + "30-min response" lesson
Confirmed by the dealer, sent in their name · 3 stores · to each personOverdue tasks get automatic reminders. Proof includes on-site photos, visible to HQ in real time.
One data layer,
your own operating system.
Metrics, roles and dashboards configured to your business. No build from scratch; delivered on a standard product timeline.
Why not BI, general-purpose AI,
or custom development?
BI stops at seeing. General-purpose AI stops at advice. Custom development is slow and expensive. PDOS gets the work fixed and verified, at standard product cost and speed.
Off-the-shelf SaaS
Cheap, but a loose fit- Cost
- Time to launch
- Business fit
- Responsiveness
- Easy to connect
- Action to owner
- Result re-check
General-purpose AI
Advises, doesn't follow through- Cost
- Time to launch
- Business fit
- Responsiveness
- Easy to connect
- Action to owner
- Result re-check
Custom development
Fits, but slow and costly- Cost
- Time to launch
- Business fit
- Responsiveness
- Easy to connect
- Action to owner
- Result re-check
Standard core + configuration
Standard price, tailored fit- CostStandard price
- Time to launchFirst version in 3 days
- Business fit
- ResponsivenessSame week
- Easy to connectA spreadsheet is enough
- Action to ownerTo store & owner
- Result re-check14-day re-check
Illustrative scores based on typical cases. Longer is better.
metric definitions
Channel, attribution, exclusions, thresholds, holidays. A new brand only changes config
diagnostic rules
Anomalies, laggards, overdue, churn. Problem stores surface automatically
fix playbooks
From issue straight to action: scripts, lessons, displays, rosters
dashboard components
Cockpit, funnel, map, ranking, detail, action center
source types supported
Messaging, Social CRM, Mini-app, POS, ERP, spreadsheets
pre-publish checks
Reconcile, dedupe, freshness. If it doesn't match, it doesn't ship
Every source in one place.
Dashboards update daily.
No data warehouse needed. An exported spreadsheet is enough. Upload one and get a dashboard built for you, free.
Member dashboard
New, visits, active, repeat, by channel and month. See target progress at a glance.
Store & associate dashboard
Scans, leads and orders ranked by region, store and associate. Laggards flagged red.
Lead CRM dashboard
Assignment, first contact, visit, close: the full funnel, with overdue alerts.
Dealer tables
Each dealer gets its own data, distributed by permission.
Weekly & monthly decks
Export an editable deck in one click. Charts, takeaways and next week's focus filled in.
Campaign review
Before/after for promotions, referrals and in-store events, with ROI calculated.
The right chart for every metric,
clear at a glance.
Most tools give you one default chart. PDOS picks the chart by metric type: trends for anomalies, funnels for drop-off, rankings for laggards, targets for gaps. Every chart comes with a takeaway.Charts use demo data. Production uses your metrics and definitions.
One set of facts.
Each level sees its own screen.
Every level opens the system to answer the same three questions: How am I doing? Where's the problem? What do I do now? Data above your level stays hidden.
Decision center
- Sees daily
- Global health score, region rankings, which region is slipping
- Receives
- Morning brief and this week's watch list
- Does
- Sets metric definitions and targets, approves cross-region resources
Region health
This week's watch list
- APAC leads down 2 weeks runningCause: slow first response in 3 stores · assigned
- LatAm: 3,200 dormant membersSuggest a win-back next week
- Europe "night shift" is workingSuggest rolling out to N. America
Regional management
- Sees daily
- Dealer rankings and gap breakdown
- Receives
- Region alert: leads down 2 weeks running
- Does
- Start with the dealers with the biggest gaps; confirm fixes
| dealers | stores | Lead gap | Fix progress | Status |
|---|---|---|---|---|
| Singapore Central | 9 | −44 | Fixing | |
| Kuala Lumpur | 8 | −31 | Fixing | |
| Penang | 7 | −15 | Re-checked | |
| Johor | 6 | −10 | Re-checked | |
| Bangkok | 5 | +6 | OK | |
| Jakarta | 4 | +3 | OK |
70% of the lead gap is in the top two. Prioritize them this week.
Dealer operations
- Sees daily
- Comparison across their own stores
- Receives
- Fix tasks waiting for confirmation
- Does
- Confirm in one click and send to stores in their own name. Tasks from the owner get done.
Tasks sent by the dealer owner get done 23 points more often than tasks sent by HQ (illustrative).
Store growth
- Sees daily
- Store diagnosis: which step is the problem
- Receives
- Fix tasks and matching lessons
- Does
- Who does it, by what time today, with proof
Today's timeline
- 10:20First-response fix assigned to 3 associates
- 11:00Run the "30-min response" lesson
- 15:40Reply to 12 pending customers
- 18:00Submit fix proof + on-site photos
Associates
Frontline execution
- Sees daily
- One morning message on their phone
- Receives
- Which customers to follow up, which task to finish
- Does
- Just three things: follow up, do the task, mark done
Sort the stores first,
then match the action.
Stores and figures are demo data.
Biggest opportunity: traffic comes in, sales don't
Split stores into four groups by traffic × conversion. Fix this group first; it pays off fastest.
A customer messaged. No reply for an hour
First-response time by store and associate. Over the limit triggers a fix task.
Watch the first 90 days
Compared with similar stores' ramp-up curves. Falling behind triggers an alert.
Will we hit the month?
Projects month-end from current pace and flags gaps two weeks early.
Notes, follow-ups, social posts
Standard-action completion ranked by person. Top associates' playbooks become lessons.
What shouldn't count, doesn't
Closed stores leave the ranking but stay in totals. Transferred associates merge by employee ID.
Reports in one click
Weekly and monthly reports and tables, exported by region and dealer.
If it doesn't match, it doesn't ship
Reconciled before every publish. Metric versions locked.
Ask the data: "Why is APAC down?"
Answers on controlled definitions, with charts and sources. Every number is traceable.
Send us a spreadsheet.
Within 3 business days, we'll build you a dashboard, free.
No contract, no IT work. See what PDOS can do with your own data. Talk about working together only if you like it.
- 01Email usPut "Free pilot" in the subject
- 02Attach a spreadsheetAny operating sheet works. Mask it first if you like
- 03Get your dashboard linkWithin 3 business days, on phone or desktop
The free pilot includes 1 use case, 1 spreadsheet and 1 dashboard (online). Not included: system integrations, task dispatch to staff, complex permissions. Those come in the paid pilot.
Prefer a form? Apply here →Pick your stage:
pilot first, then scale.
No per-seat pricing. After the pilot, an annual subscription can fully credit the pilot fee (per contract). Every quote is based on your store count and data scope.Quotes exclude tax.
Your data is in spreadsheets; you need dashboards first
- 1 use-case dashboard
- Updates on spreadsheet import
- 3 role views
- Online dashboard + downloadable reports
- 30 days of onboarding support
HQ + 1 region, or 2–4 cities
- Multi-use-case dashboards
- Detect · Diagnose · Assign · Verify loop
- Associate mobile app
- Daily / weekly reports and monthly decks, auto-generated
- Weekly operating support
- Acceptance criteria in the contract
Company-wide rollout, continuous iteration
- Full org structure, five permission levels
- Automated data sync via API
- PDOS Assistant
- Dedicated advisor, ongoing iteration
- Data isolation audit + named watermarks
You have an IT team, or data can't leave your network
- On-premise deployment
- Code and metric documentation handed over
- Team training and certification
- Annual technical support (optional)
Not just software.
We help you run it, too.
The system finds issues, assigns them and re-checks. Our advisors turn what works into rules and training. Mix and match; no need to buy everything at once.
Run your data through 90+ diagnostic rules. Get a list of problem stores, ranked causes and fix recommendations.
Custom quote · credited toward a pilotAnonymous peer benchmarks: percentile levels for store health, first response, repeat purchase and more.
Published quarterlyDashboards, diagnosis, assignment, re-checks and automated reports. Delivered as Starter / Pilot / Enterprise / On-premise.
See pricing aboveA weekly deck generated automatically, then annotated by an advisor with takeaways and next week's focus. Ready for your weekly meeting.
Monthly subscription3 / 6 / 12 months: weekly reviews, fix follow-up and campaign reviews, so the system gets used and delivers results.
Quoted per termBenchmark stores' practices and diagnostic rules turned into courses and assessments, with certification.
Quoted per sessionAsk for an industry template →Request the 30-rule store checklist →
- Free pilot1 spreadsheet · 3 business days
- Health checkFind problem stores and causes
- 3-month pilotLoop running · accepted per contract
- Annual + supportScale it out
Every number
traces back to its source.
Deploy the way you want
The standard edition is cloud-hosted and isolated per brand. Enterprises can deploy on-premise and keep data in their own environment. Phase one can run on exported sheets alone, without touching any system.
Five permission levels
HQ, region, dealer, store manager and associate each see their own data. Nothing above their level.
Traceable, line by line
Every number traces to its data source, field and metric version. Not "the model said so."
Named watermarks & audit
Email-verified sign-in, per-person watermarks, and a data isolation audit before role-based exports.
If it doesn't match, it doesn't ship
Checked and reconciled with your system totals before every publish. Metric versions locked: same question, same answer.
The people building this system
spent five years on the brand front line.
"I sat at HQ but did delivery work. So I could see what HQ decided, what actually happened in stores, and the gap between them."
- 2021Into social CRM operationsSocial CRM projects for tech, lubricants and other brands
- 2022–2026Consumer brand, China front lineLed the annual social CRM plan, renewed yearly; coordinated 1,100+ associates and 40+ dealers
- 2025Method repeated across brandsBuilt a three-tier messaging setup from zero for another brand; customer base grew 100× in a year
- 2026PDOS is bornThe method became a system: first dashboard for a new brand in 3 business days
No inflated ROI · acceptance in the contract · data security first
From procurement and business leads:
the questions we hear most.
Is the data accurate?
Every publish runs pre-publish checks and reconciles with your system totals. If it doesn't match, it doesn't ship. Every number traces to its data source, field and metric version.
How is this different from our BI / CRM / Social CRM?
BI shows you the problem, CRM records the process, Social CRM reaches the customer. PDOS sits on top of them: it assigns issues to people, follows up until they're fixed, and re-checks two weeks later. It doesn't replace them; your data can come straight from them.
What if associates won't use it?
The associate view has just three things: which customers to follow up, which task to finish, and a done button. Fixes go out in the dealer owner's name, and pilot users' weekly activity is part of the acceptance criteria.
How fast can we start? How much IT do we need?
Send a spreadsheet and get a first dashboard in 3 business days; the pilot produces its first review in 14 days. The first month needs almost no IT: it runs in a browser, on manually exported sheets.
What if the pilot doesn't work?
Acceptance criteria go into the contract before the pilot: how many met to roll out, how many to extend, how many to stop. We don't promise multiples. We commit to process metrics.
Can it run alongside our ERP / CRM?
Yes. PDOS reads exported data or open APIs from those systems. It never replaces or rewrites their data. Phase one can run on manual exports alone.
Is the re-check always 14 days?
No. The re-check cycle follows your business rhythm. Default is 14 days; 7, 30 days or per campaign also work.
What happens to our data when the contract ends?
You can export all dashboard data, detail tables and metric docs. After that, data is deleted within the contracted period, with written confirmation.
Our structure is different. Will it work?
Any chain with an HQ → region → dealer → store → associate structure (home furnishing, building materials, bath, appliances, jewelry, eyewear) shares the same underlying shape. Brands with only member KPI sheets can start with Starter.
Your numbers,
one full loop.
- 01Run Detect, Diagnose, Assign, Verify on your store structure
- 02What each of the five roles sees, and what tasks they get
- 03What your data can support, and what to prepare
- 04How to set pilot scope, timeline and acceptance criteria