MBOVerse CRM Workflow Guide

What is the CRM workflow?

It is an interactive website guide showing how MBOVerse CRM moves from lead capture through sales execution, commercial approval, client management, forecasting and reporting.

Is it one giant process?

No. The workflow is divided by persona: Sales Team, Company Admin and Platform Owner.

How does a typical sales journey work?

Lead → Qualify/Score → Assign → Follow-up → Pipeline → Quotation/Proposal → Approval when required → Client → Forecast/Analytics.

Can a lead be created only manually?

No. Leads can also enter through import, public lead forms, API/webhooks and configured integrations.

What does lead scoring do?

It prioritizes opportunities using configured scoring rules and Hot/Warm/Cold classification.

What is automatic assignment?

The CRM can use configured assignment rules, including round-robin behavior, to assign ownership.

Is quotation approval always required?

No. Approval is conditional on the configured commercial approval policy.

What happens after a deal is won?

The business can be maintained as a Client with contract value, recurring revenue, billing cycle, renewal and account manager information.

How does forecasting work?

Open opportunities use pipeline/stage probability and forecast category to calculate weighted sales forecasts and target coverage.

Can recurring reports be configured?

Yes. Scheduled reports can generate recurring management snapshots and notify the selected user in-app.

Can lead data be imported?

Yes. The Import Center supports CSV/XLSX with preview, mapping, duplicate handling and import history. A sample template should be downloadable from the workflow page.

What integration areas exist?

Channels, Templates, Calendar, API, Webhooks and Public Forms are presented as separate tabs.

Is there an Owner Console?

Yes. The Platform Owner manages customer companies, plans, subscriptions/billing, monitoring, SaaS analytics, backups and legal/commercial pages.

Is the workflow itself allowed to change CRM data?

No. The public website workflow is an educational guide. It should use screenshots, hotspots and explanations rather than modifying production data.

Should internal release numbers appear?

No. Labels such as V7/V8/V9/V10/V11/V15 are development history and should not appear in the public workflow experience.