MCI MVP Foundation
Seller Success Command Center
Customer handoff
Launch Decision
Send a customer approval link only after the launch status is clear enough to review.
The customer or approver who will review the launch handoff.
The email address that should receive or open the handoff approval link.
Creates a private approval page for the customer. Use it only when the launch status is ready enough to review.
Launch preparation
Launch Readiness Checklist
Track the remaining work needed before the workspace is ready for real customer use.
Steps
- Refresh to update the checklist.
- Run Restore Drill to prove backups can be restored.
- Review Needs Work and complete each open item.
- Export Evidence for customer and internal signoff.
Updates the launch checklist and shows which areas still need work.
Tests whether backup data can be restored. This proves the workspace can recover if something goes wrong.
Downloads proof of the checklist, backup test, and remaining launch items.
Setup assistant
Production Setup Assistant
Production remediation
Acceptance Queue
Post-launch operations
Success Console
Customer acceptance
Acceptance Ledger
Launch evidence vault
Evidence Vault
Guided setup
Admin Checklist
Production support
Issue Intake
User training
Help Center
Production onboarding
Data Import
Go-live suite
Quality & Launch Lock
Seller intelligence
Priority Sellers
Maria AI
Recommendations
Maria 72
72-Hour Opportunity Review
Ranked opportunity windows, evidence, confidence, and playbook templates for human review.
Seller Opportunity Readiness
Opportunity-to-Seller Match Review
Review which existing MCI sellers are ready for a Maria opportunity. Missing product, inventory, campaign, or performance context is shown as unknown.
Commerce Radar
Operations and Intelligence Workspace
Run the governed Radar flow one step at a time: approved sources, observations, product matching, trends, competitive signals, market gaps, opportunities, Maria 72, and seller matches.
Recommended operator order
- Review Sources to confirm the source is approved, active, and not blocked by governance.
- Collect Observations only from an approved source and policy.
- Rebuild Product Matching before trend, competitive, or opportunity review.
- Rebuild Trends, Competitive Intelligence, and Market Gaps so Maria has current evidence.
- Rebuild Opportunities, Maria 72, and Seller Matches before planning any human-approved action.
Observability
Ops Health Monitoring
Runtime metrics
Requests
Operational inbox
Unified Work Queue
Inbox health
Queue Mix
Workers
Background Scheduler
Worker history
Recent Runs
Workflow automation
Automation Rules Engine
Automation
Execution Logs
Integrations
Webhooks & Event Bus
Event bus
Deliveries
Integration security
API Keys
API access
Usage Log
Launch command
Production Launch Suite
Launch domains
Go/No-Go Controls
SaaS operations
Workspace Management
Isolation
Tenant Controls
Tenant revenue
Billing & Subscriptions
Plan catalog
Entitlements
Tenant setup
Onboarding & Provisioning
Provisioning status
Tenant Controls
Customer experience
Branding & Domain Setup
Domain readiness
DNS & TLS
Customer enablement
Help Center / Knowledge Base
Data adapters
Marketplace Connectors
Production setup
Environment Setup Wizard
Environment validation
Setup Status
Live production verification
Secrets & Provider Checks
Resilience
Backup / Restore Console
Retention
Data Retention Policy
Staging operations
Test Data Control Center
Use this page to prepare or reset demo data. It is for QA, training, and presentation setup; daily seller operations happen in Dashboard, Sellers, CRM Cases, Maria AI, and Campaigns.
Recommended seeding order
- Refresh to load the current counts and cleanup status.
- Create Baseline to save a rollback point before changing demo records.
- Seed Lazada Demo to load the seller incubation story for the presentation.
- Review Dashboard, Sellers, Campaigns, CRM Cases, and Maria AI to confirm the story looks right.
- Export Manifest if you need evidence of what data was loaded for handoff.
Use before reviewing this screen. It only reloads counts and status; it does not change data.
Use before imports or demo changes. It creates restore evidence so you can prove what the workspace looked like before changes.
Use for the Lazada presentation. It loads the synthetic incubation story with sellers, risk cases, campaigns, tasks, and Maria recommendations.
Use for a generic tenant rehearsal. It refreshes the active workspace with standard demo records, not the Lazada-specific story.
Use after QA testing. It removes test artifacts such as generated invoices, delivery attempts, and validation records.
Use for handoff evidence. It downloads current QA data counts, cleanup status, workspace info, and billing/test-data metadata.
Cleanup guardrails
Validation Artifacts
Customer acceptance
UAT Sign-Off Console
Use this page near the end of a pilot or demo cycle to record scenario results, blockers, evidence links, and customer/operator signoff.
Recommended acceptance order
- Confirm customer and owner so the acceptance pack has the right accountable contacts.
- Run each scenario and mark it Passed, Failed, Blocked, or Untested.
- Add evidence such as a screenshot, URL, export pack name, or short proof note.
- Resolve blockers before requesting signoff from Operations, Admin, Customer, and Executive roles.
- Export Acceptance Pack after scenarios and signoffs are complete.
Sign-off roles
Acceptance Gate
Collect final approval only after scenarios are tested and blockers are documented or cleared.
Pilot launch
Customer Pilot Launch Console
Use this to prepare the pilot, confirm the checklist, and export the scale handoff pack.
Steps
- Set the pilot status so the team knows whether it is planned, live, paused, or complete.
- Confirm owner and dates so everyone knows who runs the pilot and when it starts.
- Complete the checklist before moving from pilot to wider rollout.
- Export Scale Pack when the pilot is ready for customer review.
BP-007 Sprint 1
Controlled Pilot Environment
Seed a realistic UAT dataset with 20 fictional sellers, cohort coverage, missing-context cases, poor-fit cases, blocked cases, and sandbox market evidence.
BP-007 Sprint 2
End-to-End Intelligence Journey
Validate the governed path from controlled evidence to Maria 72 and Seller Master matching. This is a UAT proof only: no campaigns, no seller outreach, and no live Shopee/TikTok collection.
BP-007 Sprint 3
Human Operations, Execution, and Outcomes
Validate the human chain from approved Maria opportunity to seller selection, approval, internal task assignment, controlled disposition, outcome capture, learning evidence, and audit traceability.
Operator steps
- Confirm Sprint 2 is PASS so evidence, opportunities, Maria 72, and seller matches already exist.
- Run Operations UAT to approve one eligible fictional seller through the controlled internal workflow.
- Review negative controls to confirm Laguna Beauty, unauthorized roles, and kill switches remain protected.
- Check outcome and learning evidence to confirm missing facts stay unknown and no production rule changed itself.
- Export Operations Report for the BP-007 pilot UAT evidence pack.
BP-007 Sprint 4
Pilot Certification and GO/NO-GO Gate
Certify the whole controlled pilot using Sprint 1 data, Sprint 2 intelligence, Sprint 3 human operations, governance, audit, MySQL/Railway evidence, and explicit human checklist conditions.
Certification steps
- Review Sprint 1, 2, and 3 gates to confirm the controlled pilot evidence is present.
- Check human attestations such as UAT acceptance, notification test, and rollback owner without auto-completing them.
- Review blockers and conditions before accepting GO, CONDITIONAL GO, or NO-GO.
- Run Certification only when the operator is ready to record the current decision.
- Export Certification for the pilot evidence pack.
Success monitoring
Post-Launch Success
Track whether the pilot is being used successfully after launch.
Steps
- Choose the review cadence for checking progress.
- Assign the owner who will watch the pilot after launch.
- Review each success goal to see if adoption, risk, and readiness are on track.
- Save Success after notes or ownership changes.
AI operations
Live AI Provider Controls
Incident response
Operational Runbook Console
Runbooks
Response Playbooks
Production operations
Readiness & Deployment Console
Deployment snapshot
Launch Signals
Admin configuration
Configuration Console
Settings summary
Active Controls
Reports
Data Export Pack
Export coverage
Snapshots
Seller health
CSV / JSON
SLA and workload
CSV / JSON
AI and campaigns
CSV / JSON
Compliance
CSV / JSON
Executive analytics
KPI Dashboard
Use this page to understand where seller success needs attention and what to open next.
How to read this page
1 Check the red or high numbers first.
2 Open the seller or workload signal behind the number.
3 Use CRM, Tasks, Campaigns, or Maria AI to act.
4 Export the report pack when you need launch evidence.
Executive Command Center
Market, Maria 72, gaps, actions, and evidence
A governed leadership layer. Every number shows its meaning, freshness, source, and limitation.
Leadership view
Risk Signals
Open these items first when you need to reduce seller risk or workload pressure.
Admin presentation studio
My Presentation
One controlled place for customer presentation material, user training, marketing notes, sales talk tracks, and technical review content.
2 PDF packs
4 audiences
Admin only
Choose customer demo, sales, technical review, or user training.
Check the included sections before downloading.
Use the approved file for the meeting or training session.
This library is visible only to workspace admins.
Audience guide
Which file should I use?
Pick the material based on the meeting, not based on file name.
Use the presentation pack. Focus on the seller incubation story, business value, proof, and demo flow.
Use the presentation pack. Focus on positioning, pain points, value message, and meeting talk track.
Use the presentation pack. Focus on access control, data saving, providers, exports, and readiness checks.
Use the training tutorial. Teach sign in, dashboard, sellers, cases, Maria AI, campaigns, and reports.
CRM operations
Open Case Queue
Use this list to decide which seller issue needs attention first.
How to work cases
- Start with high priority or cases close to their response target.
- Open the seller to see context, score, risks, and related work.
- Add comments so the next agent knows what happened.
- Create a follow-up task when the issue needs action after the case update.
Follow-up queue
Agent Tasks
Tasks are the daily action list for agents after cases, campaigns, reminders, or Maria suggestions.
How to use tasks
- Open Seller to understand the seller before taking action.
- Start when the agent begins working the task.
- Done only after the follow-up is completed or recorded.
- Watch due dates so urgent work does not slip.
Admin readiness
Workspace Setup Status
Quick checks that show whether the workspace is ready for real users.
Workspace data ready
Ready
Login protection
Ready
User access controls
Ready
Next setup focus
Permanent data storage
Admin
Users
Review who can sign in and what role they have.
User setup steps
- Create real users for the people who will operate the workspace.
- Assign the right role so each person only sees the tools they need.
- Rotate temporary passwords before customer handoff.
- Suspend unused accounts when access is no longer needed.
Identity admin
User & Role Management
Identity operations
Account Recovery & Sessions
Production setup
Demo Cleanup & MySQL
Access model
Role Permissions
Access provisioning
User Invitations
Invite lifecycle
Pending & History
Access control
Permission Matrix
Effective access
User Preview
Notifications
Reminder Center
SLA
Escalation Rules
Security
Password, Session & Secrets Policy
Security posture
Checks
Compliance
Review Console
Review Queue
Open Reviews
Campaign guide
How Campaigns Work
Campaigns turn seller score gaps into a clear action plan for the seller success team.
Use this page when you want to improve a group of sellers, not just view them.
The system finds sellers that match a campaign, enrolls them, creates follow-up tasks, and then tracks whether scores and sales improved.
1 Choose a campaign
2 Find eligible sellers
3 Enroll sellers
4 Complete tasks
5 Export impact proof
Recommended steps
- Run Eligibility to see which sellers fit a campaign.
- Review Targeting & Enrollment to confirm the seller list.
- Enroll + Assign to create the seller action tasks.
- Track task completion and score movement.
- Export Impact for Lazada review or internal reporting.
Campaigns
Campaign Execution
Run a campaign, assign seller tasks, and prove the result with before/after evidence.
Opportunity Approval
Create Campaign Draft from Maria Opportunity
Create a draft only after seller matches have been reviewed and approved. The draft freezes evidence and baselines; it does not enroll sellers, create tasks, or contact anyone.
Altria Execution Workspace
Approved Campaign to Agent Tasks
Generate controlled agent work only after a Maria opportunity campaign draft is approved for planning. Agents receive seller facts, safe talking points, uncertainty, and follow-up controls.
Outcome Measurement
Baseline and Outcome Dashboard
Lock the campaign baseline, then measure current authorized facts against that baseline. Missing commercial data stays visible and is not guessed.
Attribution Review
Attribution and Prediction Quality
Review before/after, selected sellers, similar non-selected sellers, and Maria's original prediction. This is directional evidence, not a causal claim.
Learning and Optimization
Learning Review and Proposal Control
Create model-feedback records, performance reviews, drift reports, and evidence-backed proposals. Production scoring is never changed silently.
Builder
Create Campaign
Eligibility
Targeting & Enrollment
Action Templates
Campaign Task Playbooks
Maria AI
Next Best Actions
Incubation