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?
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.
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.
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.
| ACE System | Commercial role | Typical failure when disconnected |
|---|---|---|
| Market Clarity | Defines the buyer, problem, value, positioning, offer logic and market focus. | The business attracts the wrong audience, explains value poorly or builds commercial activity around weak assumptions. |
| Demand Capture | Owns the conversion infrastructure that captures commercially meaningful demand. | The website, landing pages, forms, CTAs and tracking create attention but not qualified commercial movement. |
| Marketing Operations | Operationalises demand generation, nurture, attribution and marketing-to-sales movement. | Campaigns create activity without clear connection to pipeline, conversion, sales readiness or customer quality. |
| Sales Operations | Converts qualified demand into committed revenue through structured CRM, qualification, pipeline, proposals and handoff readiness. | Sales depends on individuals, CRM data cannot be trusted, forecasts drift and revenue quality is weak. |
| Commercial Operations | Converts committed revenue into controlled, visible and commercially responsible delivery. | Sales promises are not translated into operational readiness, delivery risk or margin visibility. |
| Customer Growth | Owns post-commitment value realisation, continuation, retention, expansion and advocacy. | The business wins customers but fails to systemise value, renewal, account growth and learning. |
| Automation and Intelligence | Connects data, workflows, automation and decision support across the engine. | Tools multiply, data fragments and automation scales unclear process rather than improving commercial control. |
What “autonomous” means in ACE.
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 focuses on the commercial engine: the connected systems that create, capture, convert, fulfil and grow customer value.
| Framework or model | Best used for | Where ACE goes further |
|---|---|---|
| McKinsey 7S Framework | Organisational alignment | ACE focuses specifically on the commercial engine. |
| RevOps lifecycle | Revenue process alignment | ACE connects revenue operations to fulfilment, customer growth and Revenue Quality. |
| GTM operating model | Taking an offer to market | ACE connects GTM to delivery, retention and commercial learning. |
| Target operating model | Organisational design and governance | ACE is a commercial operating framework, not a whole-business TOM. |
| Veeva-style commercial blueprint | Vertical commercial execution | ACE is sector-agnostic and not vendor-specific. |
McKinsey 7S Framework vs ACE.
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.
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.
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.
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.
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.
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.
Diagnose → Design → Build → Connect → Automate → Operate → Optimise.
Diagnose.
Design.
Build.
Connect.
Automate.
Operate.
Optimise.
What a disconnected commercial engine looks like.
| Visible symptom | Common assumption | ACE diagnosis question |
|---|---|---|
| “We need more leads.” | Marketing is underperforming. | Are existing leads being captured, qualified, routed, followed up and converted properly? |
| “Our CRM is a mess.” | The tool needs cleaning. | Does the CRM reflect the real sales process, buyer journey, qualification logic and reporting need? |
| “The website is not converting.” | The design or traffic source is the problem. | Is the buyer clear, is the offer clear, is the CTA commercially appropriate and does the handoff work? |
| “Sales is inconsistent.” | The team needs to work harder. | Is there a codified sales operating model, pipeline structure, next-step discipline and proposal workflow? |
| “Everything is manual.” | The business needs automation. | Which workflows are mature enough to automate without scaling confusion? |
| “Customers do not expand.” | Customer success needs more activity. | Is value realisation, continuation, renewal, expansion and advocacy designed into the engine? |
Why this supports commercial transformation.
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 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.
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.
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.
Autonomous Commercial Engine Framework FAQs.
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.
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.
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.
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.
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.
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.
ACE is designed for commercially accountable B2B organisations with proven demand but fragmented commercial systems that limit revenue efficiency, scalability and control.
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.
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.
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.



