Questions to ask any Business OS vendor

Source · CMS snapshot (seed) — this blog body is served from content/generated/cms-snapshot.json, not the code catalog alone. Staff path: Content Studio (:3030 /experience/sites) → Blog tab → publish → MCV_CONSOLE_URL=http://localhost:3030 pnpm --filter @mcv-tech/marketing-shell content:seed → rebuild :3050. Offline: MCV_CMS_SNAPSHOT_FILE=… pnpm content:seed.

Ask us these. Ask everyone these.

If you are evaluating a shared operating platform for a multi-brand business, the demo will look good. Demos always look good. These are the questions that separate platforms built for operators from platforms built for procurement:

Data and boundaries

1. Where exactly is the boundary between my brands' data — application code, or the database itself? Application-level filtering fails silently. Database-level enforcement fails closed. (Our answer, in depth: how per-brand data isolation works.)
2. If I sell or spin off a brand, how does its data leave? A clean exit path is the strongest evidence that isolation is real.
3. Which of my existing systems stay authoritative during rollout, and who decides when that changes?

Control and evidence

1. What actions require human approval, and can I change that list myself?
2. Can I reconstruct who did what, on which brand, through which approval — a year later?
3. What do your AI features see, and is it more than the invoking operator is authorized to see?

Honesty checks

1. Show me your status page. Are the numbers on it real or decorative?
2. Which of your public case studies can I call? "None yet, approvals pending" is an acceptable answer. Vague logos are not.
3. What does the smallest credible pilot look like, and what does it cost?
4. What happens to my pricing when the pilot works and I expand?

We publish this list because we are comfortable answering every question on it — and because a market where buyers ask them is a market we win.