ACE Framework: b10’s Commercial Transformation Framework
b10 commercial transformation partners

B10 publishes the ACE Framework: a commercial transformation framework for connected commercial engines

Most businesses do not have a sales problem, a marketing problem or a CRM problem in isolation. They have a disconnected commercial engine. b10 has published the ACE Framework to diagnose, design, connect, automate, operate and optimise that engine across the systems that create, capture, convert, fulfil and grow customer value.

What is the ACE commercial transformation framework?

The ACE Framework, the Autonomous Commercial Engine, is b10’s commercial transformation framework for building connected, measurable and increasingly autonomous commercial engines. It is not a slogan, a delivery checklist or a renamed internal process. It is a structured framework for designing, connecting, operating and improving the commercial systems through which organisations turn market attention into retained customer value.

In practical terms, The ACE Framework helps a business move from disconnected commercial activity to a governed commercial operating model. That means the website is not treated as a brochure. The CRM is not treated as a database. Marketing is not treated as a collection of campaigns. Sales is not treated as individual effort. Operations is not treated as a back-office afterthought. Customer growth is not left to goodwill. Automation is not layered onto weak process.

Instead, The ACE Framework asks a harder question: does the commercial engine work as one system from first click to recurring revenue?

The problem the ACE commercial transformation framework is designed to solve.

Many founder-led and MD-led B2B companies are not short of effort. They have a website. They may have a CRM. They may run campaigns, attend events, post on LinkedIn, build partnerships, send proposals, onboard customers and deliver good work. However, the commercial system behind that activity often remains fragmented.

That fragmentation shows up in familiar symptoms. Website enquiries arrive but do not convert cleanly. CRM records exist but do not reflect the real buyer journey. Marketing activity creates attention but does not reliably move into qualified pipeline. Sales follow-up depends on individual discipline rather than process design. Proposals drift. Delivery handoffs are inconsistent. Reporting shows activity but not commercial truth. Customer growth depends on memory, relationships or firefighting rather than a controlled value journey.

It is tempting to solve each symptom separately. Redesign the website. Clean the CRM. Hire a marketing agency. Add automation. Introduce a new dashboard. Replace the sales tool. None of those moves is automatically wrong. The risk is that each fix optimises one part of the system while the wider commercial engine remains disconnected.

The ACE Framework exists because b10’s position is simple: revenue cannot scale efficiently when commercial systems are fragmented, manual, disconnected or commercially underdeveloped.

Why ACE is not just another internal delivery model.

A delivery model describes how a company does the work. The ACE Framework goes further. It defines what must be connected for a commercial engine to work, how those connections should be governed, where diagnosis should happen, how automation should be controlled, and how learning should feed back into system improvement.

This matters because many transformation projects fail at the seams. Strategy is produced but not operationalised. CRM is implemented but not connected to sales behaviour. Marketing reports on leads but not revenue quality. Sales closes work that delivery is not ready to fulfil. Operations delivers but does not feed customer evidence back into positioning, demand capture or sales qualification. Automation reduces manual effort in one place but creates risk somewhere else.

The ACE Framework treats those seams as design points. It is a commercial operating framework, not a list of services. It gives b10 a structured way to assess the engine, define the required future state, build or rebuild the necessary systems, connect the interfaces, automate the right workflows, operate the engine and keep improving it over time.

The seven connected systems inside ACE.

The ACE Framework is built around seven connected commercial systems. Each system has a role, but the value comes from how they work together.
These systems are supported by the ACE Content Engine, the ACE Intelligence Loop and Operating Rhythm. The Content Engine ensures commercial messaging, content logic and conversion assets support the engine. The Intelligence Loop converts signals into learning. Operating Rhythm turns visibility and learning into accountable decisions, actions and system improvements.

What “autonomous” means in ACE.

Autonomous does not mean removing human judgement from commercial decisions. That would be reckless for most businesses. In ACE, autonomy means the governed reduction of avoidable manual intervention. It means clearer rules, cleaner data, better workflows, controlled automation, commercially grounded intelligence and human ownership of material decisions.

A connected commercial engine should not require a founder, MD, sales manager or operations lead to manually chase every update, interpret every signal, trigger every follow-up, reconcile every report or rebuild every process from scratch. Some work should happen because the system is designed to make it happen. Some decisions should be prompted by evidence. Some exceptions should be escalated. Some workflows should run automatically. Some learning should become system change.

That is the difference between random automation and commercial autonomy. Random automation moves tasks. Commercial autonomy improves the engine.

How ACE compares with recognised commercial and operating frameworks.

The ACE Framework is b10’s commercial transformation framework. It sits in the same strategic landscape as RevOps, GTM operating models, target operating models and established organisational alignment frameworks, but it has a more specific purpose.

The ACE Framework focuses on the commercial engine: the connected systems that create, capture, convert, fulfil and grow customer value.

McKinsey 7S Framework vs ACE.

The McKinsey 7S Framework is useful for understanding organisational alignment. It looks at how strategy, structure, systems, shared values, skills, style and staff work together.

The ACE Framework is narrower by design. It does not try to assess the whole organisation equally. Instead, it focuses on the commercial engine: the systems, workflows, data, content, automation and operating rhythm that move value from first click to recurring revenue.

The distinction matters. A business may have broad organisational alignment but still have a weak commercial engine. Its CRM may not reflect the sales process. Its website may not capture demand properly. Its handoff from sales to delivery may be poor. Its customer growth process may be informal.

The ACE Framework exists to diagnose and improve that commercial system directly.

RevOps lifecycle vs ACE.

RevOps is one of the closest adjacent disciplines to ACE. It helps align revenue-facing teams, processes, data and technology across marketing, sales, customer success and reporting.

That is useful. In fact, The ACE Framework includes a significant amount of RevOps logic. CRM structure, pipeline visibility, attribution, forecasting, sales process control, marketing-to-sales handoff and revenue reporting all matter inside ACE.

However, The ACE Framework goes further than a typical RevOps lifecycle. It does not stop at revenue team alignment. It connects market clarity, demand capture, sales conversion, delivery readiness, commercial operations, customer value, retention, expansion, automation and learning.

That is why The ACE Framework is not simply a RevOps model. RevOps helps improve the revenue process. The ACE Framework designs and operates the wider commercial engine that revenue depends on.

GTM operating model vs ACE.

A GTM operating model helps a company define how it takes an offer to market. It usually covers market segmentation, ICP, positioning, routes to market, channels, demand generation, sales motion and customer acquisition.

The ACE Framework includes those areas, especially through Market Clarity, Demand Capture, Marketing Operations and Sales Operations.

The difference is that The ACE Framework does not treat GTM as the end of the commercial journey. Winning a customer is not the finish line. The commercial promise still has to be fulfilled, the customer has to experience value, and the business has to learn from what happened.

The ACE Framework connects GTM to fulfilment, onboarding, customer growth, Revenue Quality and the ACE Intelligence Loop. That makes it more useful for businesses where the real problem is not just going to market, but connecting the whole journey from attention to retained revenue.

Target operating model vs ACE.

A target operating model defines how an organisation should operate to deliver its strategy. It can include structure, roles, governance, processes, systems, data, decision rights and performance management.

The ACE Framework can inform a commercial target operating model, but it is not a generic TOM.

The difference is focus. A TOM may cover the whole business. The ACE Framework focuses specifically on the commercial systems that create, capture, convert, fulfil and grow customer value.

That makes The ACE Framework more practical for founder-led and MD-led B2B companies that do not need a large enterprise transformation programme, but do need stronger commercial control, better visibility and a more connected operating rhythm.

Veeva-style commercial blueprint vs ACE.

Veeva-style commercial blueprints are useful examples of structured commercial execution inside specific verticals, particularly where customer engagement, content, field activity, compliance and omnichannel journeys need to be managed carefully.

They are valuable because they show how commercial execution can be designed as a system rather than a collection of disconnected activities.

However, The ACE Framework is not a vendor blueprint and it is not designed for one industry. It is sector-agnostic. It can apply to consulting firms, technical B2B companies, SaaS businesses, engineering firms and other founder-led or MD-led B2B organisations where the commercial journey needs to become more connected and measurable.

ACE‘s value is not that it copies a vertical blueprint. Its value is that it gives b10 a structured commercial transformation framework that can be applied across different business models while still adapting to the specific commercial route, customer journey and operating complexity of each organisation.

The practical distinction.

The ACE Framework does not replace 7S, RevOps, GTM or target operating model thinking. It uses the commercially relevant parts of those disciplines and applies them to one specific problem:

Most businesses do not have a sales problem, a marketing problem or a CRM problem in isolation. They have a disconnected commercial engine.

The ACE Framework is b10’s commercial transformation framework for diagnosing, designing, connecting, automating, operating and optimising that engine.

How ACE works.

diagnose, design, build, connect, automate, operate, optimise.

The ACE Framework follows a practical delivery cycle:
Diagnose Design Build Connect Automate Operate Optimise.

Diagnose.

b10 starts by identifying where the commercial system is constrained. CTI, the Commercial Transformation Index, supports this diagnostic layer by assessing commercial maturity across 10 domains, 50 criteria and 250 points. The goal is not to produce a vanity score. The goal is to expose where revenue is leaking, where systems are weak and what must be prioritised.

Design.

Once the constraint is understood, The ACE Framework defines the target commercial engine. This includes systems, workflows, data, handoffs, ownership, content requirements, automation opportunities and operating rhythm.

Build.

The required assets and systems are then built or rebuilt. That may involve website architecture, CRM configuration, sales process, content engine, reporting, onboarding workflow, customer growth process or commercial stack changes.

Connect.

The ACE Framework places heavy emphasis on interfaces and handoffs. Demand Capture must connect to Sales Operations. Sales Operations must connect to Commercial Operations. Commercial Operations must activate Customer Growth. Data and learning must move across the engine.

Automate.

Automation comes after process clarity. The ACE Framework distinguishes low-risk administrative automation from more consequential AI-assisted execution or controlled autonomous workflow. The principle is simple: automate the process only when the process is commercially sound.

Operate.

The engine needs ongoing ownership. Managed commercial performance requires reporting, review, decision-making, issue resolution and improvement cadence.

Optimise.

The ACE Intelligence Loop turns outcomes into learning and learning into system improvement. This prevents the commercial engine from becoming a static build that decays after launch.

What a disconnected commercial engine looks like.

A disconnected commercial engine rarely announces itself as one big problem. It appears as several smaller problems that are easy to misdiagnose.
This is why b10 argues that many businesses should not start with a tool, supplier or campaign. They should start with diagnosis.

Why this supports commercial transformation.

Commercial transformation is not simply “more growth activity”. It is the structured diagnosis, redesign, implementation and improvement of the systems, processes, tools, data and operating model that move a business from attention to retained revenue.

The ACE Framework gives that transformation a working architecture. It helps b10 explain what must change, what must connect, what must be controlled and what must improve over time. It also protects the buyer from the common trap of buying isolated fixes that do not solve the system-level problem.

For a founder-led consultancy, ACE may expose that referrals are strong but offer structure, website clarity, CRM discipline and follow-up are weak. For a technical B2B company, ACE may show that capability is high but demand capture, quotation tracking, proposal follow-up and delivery handoff are underdeveloped. For a SaaS business, ACE may reveal that acquisition, onboarding, customer success and expansion data sit in separate tools without a usable operating rhythm.

Different businesses will need different interventions. The common principle is the same: the commercial engine must work as a connected system.

Where the CTI fits.

CTI is B10’s diagnostic authority layer. The ACE Framework is the implementation and operating layer. That distinction matters.

CTI helps answer: where is the commercial engine weak, immature, disconnected or leaking value? The ACE Framework helps answer: how should the commercial engine be designed, connected, operated and improved?

Together, Commercial Transformation Index and The ACE Framework create a clearer path from problem recognition to action. CTI prevents the business from jumping into the wrong fix. ACE prevents the diagnosis from becoming another unused report.

Why this matters now.

Commercial systems are becoming more complex. Buyers research across more channels. CRM stacks are more capable but also more fragmented. AI and automation are becoming easier to deploy, which makes process quality more important, not less. A weak process with more automation is still a weak process. It just moves faster.

For growth-stage B2B companies, the next advantage will not come from adding tools at random. It will come from commercial clarity, clean system design, meaningful data, controlled automation and operating discipline. ACE is B10’s framework for building that advantage.

What to do next.

If your business feels like it has a sales problem, a marketing problem, a CRM problem or a website problem, the sharper question is whether those are symptoms of a disconnected commercial engine.

The next step is not to buy another isolated fix. The next step is to diagnose the commercial system. Start with CTI to understand where revenue is leaking, which domains are constraining performance and whether ACE is the right implementation and operating pathway.

Start with the CTI.

Then use ACE to design, connect, automate, operate and optimise the commercial engine.

Autonomous Commercial Engine Framework FAQs.

What is a commercial transformation framework?

A commercial transformation framework is a structured approach for diagnosing, redesigning, implementing and improving the systems that turn market attention into retained revenue. ACE is b10’s framework for connecting those systems into a measurable commercial engine.

What is the ACE Framework?

ACE, the Autonomous Commercial Engine, is b10’s commercial transformation framework for building connected, measurable and increasingly autonomous commercial engines across market clarity, demand capture, marketing, sales, operations, customer growth, data and automation.

What does autonomous commercial engine mean?

An autonomous commercial engine is a governed commercial system that reduces avoidable manual intervention through clear workflows, data, automation and decision support while keeping humans accountable for material decisions.

How is ACE different from RevOps?

RevOps usually focuses on aligning revenue teams, processes, data and technology. ACE includes that logic but extends across the full commercial engine, including market clarity, demand capture, fulfilment, customer value, Revenue Quality and continuous system improvement.

How is ACE different from a GTM operating model?

A GTM operating model focuses on how a company goes to market and wins customers. ACE connects go-to-market activity to fulfilment, customer value, retention, expansion, operating rhythm and commercial learning.

How does CTI relate to ACE?

CTI diagnoses the maturity and leakage points in the commercial system. ACE then provides the implementation and operating framework for rebuilding, connecting and improving that system.

Who is ACE for?

ACE is designed for commercially accountable B2B organisations with proven demand but fragmented commercial systems that limit revenue efficiency, scalability and control.

Does ACE replace CRM, marketing or sales strategy?

No. ACE does not replace those disciplines. It connects them into one commercial operating model so CRM, marketing, sales, operations, automation and customer growth reinforce each other rather than operating separately.

When should a business use ACE?

A business should use ACE when revenue cannot scale efficiently because the systems behind growth are fragmented, manual, poorly connected or too dependent on individual effort.

What is the first step before implementing ACE?

The first step is diagnosis. b10 recommends starting with CTI to identify where the commercial engine is constrained before deciding what to rebuild, connect, automate or operate.