Every Custom M3 client gets The M3 AI Core™: a continuously evolving business operating system powered by automation, AI, customer management, communication, marketing, sales, payments, events, reporting and more. Choose your level based on how much you want M3 involved.
The M3 Core keeps getting more powerful. Your level determines what M3 does for you.
One connected business operating environment. It continuously evolves as new technology becomes available.
Every level includes The M3 AI Core™. The Core contains the capability. Your level decides whether M3 operates it.
Same Core. Different responsibility. One build fee installs it. One monthly plan keeps it running at your level.
We build it. You run it.
For businesses that want the M3 Operating System and have the people or ability to operate it internally.
"Give us the machine. We'll drive."
We build it and keep it healthy.
For businesses that run their own operation but want M3 proactively maintaining and optimizing the systems underneath it.
"We'll run the business. Keep the machine healthy."
We help operate it and keep building what comes next.
For businesses that want M3 actively helping execute, improve and expand the operating system.
"Help us use it, grow it and keep building more leverage."
M3 becomes your AI and technology partner.
For businesses that want M3 deeply embedded in AI, systems, software, infrastructure and technology decisions. Blueprint or paid discovery first.
"We want M3 at the table helping lead our technology function."
| M3 responsibility | 01 Configured | 02 Managed | 03 Developer | 04 Operator |
|---|---|---|---|---|
| M3 Core | Included | Included | Included | Included |
| Initial build | Yes | Yes | Yes | Yes |
| Support | Yes | Yes | Yes | Priority |
| Proactive maintenance | No | Yes | Yes | Yes |
| Proactive optimization | No | Yes | Yes | Yes |
| Recurring execution | No | No | Yes | Yes |
| Continuous development | No | No | Yes | Yes |
| Custom software | No | No | No | Yes |
| Dedicated infrastructure | No | No | No | Yes |
| Technology leadership | No | No | Strategic | Yes |
Software capability is not M3 labor. The Core contains the capability. Your level determines M3 responsibility.
Most software is purchased based on what it can do today. M3 Core keeps evolving. As new AI, automation, communication, commerce, reporting and business applications become available, M3 can incorporate them into the Core. Your operating system gets materially more powerful without rebuilding the business around a new stack every year.
You are not buying frozen software. You are entering an operating system that keeps evolving.
Run events. Sell tickets. Accept RSVPs. Manage attendees. Build schedules. Send notifications. Check guests in. Another business system brought inside M3 Core.
Specific setup and implementation depend on client architecture and purchased level. Event tools are in Core. M3 running your events is Developer.One Core. An entire business stack. M3 brings capabilities businesses often assemble across a whole collection of software into one connected operating environment that keeps evolving.
Everything below explains what the M3 Core can do, what each level includes, and where the boundaries are.
M3 creates the initial operating environment and supports the installed system. You and your team use and operate it day to day. M3 is not providing ongoing marketing execution or active system management.
Everything in Configured plus proactive M3 stewardship of agreed systems. Managed does not mean M3 runs your company. You run the business. M3 keeps the machine underneath it clean, tuned, and reported on every month.
Reasonable bounded modifications to existing M3-built components within plan capacity.
A small change does not create an entirely new system, a major new agent, a new architecture, a new integration family, a new department, or a bundle of changes that is actually development.
Everything in Managed plus active execution and continuous development. M3 helps use the system, grow it, and build what comes next. You are buying leverage and forward progress, not hours.
Operator is not a larger Developer package. The relationship changes. M3 participates in deciding what should be built, how systems should connect, where automation belongs, what AI should own, what humans should own, what software should exist, and how technology creates leverage across the company.
Having the capability is different from having M3 operate it. A Configured client may have AI, Booster, social publishing, email infrastructure, Event OS, automation, funnels and payment tools. That does not mean M3 manually performs those activities.
The Core contains the capability. The service level determines M3 responsibility. Software access does not imply M3 labor.
Contacts, companies, opportunities, pipelines, lead management, lifecycle tracking, custom fields, segmentation, tasks, customer history, sales activity, and custom business records. Advanced architecture may use custom objects for projects, policies, properties, assets, subscriptions, vehicles, cases, departments and other entities.
Email, text, phone, voicemail, social conversations, unified inbox, history, automated responses, routing and notifications.
Lead response, follow-up, nurture, reminders, no-show recovery, missed-call response, routing, task creation, pipeline movement, internal notifications, lifecycle automation, operational workflows and connected system actions.
AI configured around approved business context may help with conversations, qualification, appointment support, follow-up, service, routing, phone conversations, internal assistance, CRM activity, campaign support, workflow decisions and connected systems.
AI automatically performing work is part of the M3 Core. It does not mean M3 staff are manually performing that work.
Review requests, follow-up, reputation workflows, feedback routing and review-response support. The automated system can perform this work even at lower service levels when configured. Managed and higher determine how much M3 maintains that architecture.
Sites, funnels, landing pages, forms, surveys, booking, calendars, invoices, payment links, subscriptions, products, checkout and commerce automation. Metered usage or transaction fees may be separate.
RSVP and ticketed events, ticket sales, registration, public event pages, schedules, speakers, notifications, attendee management and check-in, connected to the larger M3 environment.
Capabilities that once required another standalone platform can now become part of M3 Core.
Social scheduling and publishing, content calendars, email and text infrastructure, templates, approvals, customer portals, communities, courses, memberships, dashboards, native integrations, APIs, webhooks, connectors and Model Context Protocol connections.
The distinction is whether M3 is producing and managing content, not how many supported channels the technology can publish to.
Public description is conceptual. Exact counts live in the Order Form.
Get the business onto M3 correctly: CRM, lead capture, pipeline, booking, foundational website or funnel, core automation, AI, portal, reporting, users, training.
Enough operational depth for M3 to maintain the environment: deeper journeys, expanded automation, additional pipelines, scheduling architecture, integrations, reporting, AI configurations, content infrastructure, expanded users, training.
An operating system worth continuously developing: multiple departments, advanced workflows, custom objects, leadership views, deeper integrations, role-based environments.
The technological operating layer of the company. Signed addendum governs department redesign, AI workforce architecture, custom development, infrastructure, dedicated machine deployment, change management and executive technology leadership.
Configuration: populate and connect capabilities that already exist.
Customization: modify an existing M3 system within a bounded written scope.
Development: create meaningful net-new capability, architecture, integration, AI system, workflow system, application or operating function.
Management: M3 proactively maintains and optimizes specifically agreed systems.
Support: help with documented functionality and defect correction appropriate to the purchased level.
Small change: a reasonable bounded modification to an existing M3-built component that does not create a materially new system.
Development capacity: recurring capacity at Developer and Operator for meaningful forward development. M3 determines what reasonably fits.
Implementation fees are paid before work begins. Monthly plans bill in advance. Usage for text, email, voice, AI compute and other metered infrastructure is separate. Cancellation requires 30 days written notice. Plans cannot be paused unless agreed in writing. Upgrades are available. Downgrades require active scope to fit the lower level. Substantial new businesses, brands, locations or organizational scope require additional scope. M3 does not guarantee leads, sales, revenue or specific business outcomes.
Review the M3 Terms and Conditions.
"I want M3, and my team can operate it."
Start Configured Level 02Managed"I want to operate my business while M3 keeps the system healthy."
Start Managed Level 03Developer"I want M3 actively helping execute and continuously build more leverage."
Start Developer Level 04Operator"I want M3 helping lead our AI and technology function."
Apply for OperatorConfigured, Managed, Developer, Operator. The M3 Core keeps evolving. Your level determines how far M3 goes.
Implementation billed before work begins. Monthly plans bill in advance. Usage is separate. Cancellation requires 30 days written notice. Need a written plan first? Start with a Personal Leverage Plan. Review the M3 Terms and Conditions. Formal acceptance is recorded on the Order Form.
Learn how to turn simple conversations into real revenue inside the M3 Setter Program—powered by AI, built for winners.
Copyright 2026. M3 Projects. All Rights Reserved.