Sales Development survived the Domain restructure and grew a sibling, but the "under Marketing" half of the finding dissolved rather than moved

Acronyms, expanded once: eTOM = Enhanced Telecom Operations Map, TM Forum's business process framework, published as document suite GB921. SIP = eTOM's pre-restructure "Strategy, Infrastructure and Product" process area. L2 / L3 = Level 2 / Level 3 process element. CPQ = configure-price-quote. DLPM = Digital Lead and Prospect Manager (a Tecnotree product).

The question

Verbatim, from the Notion Research Backlog:

"Does GB921 v24/v25 still contain a 'Sales development' equivalent (eTOM 1.2.1.6), and did the Domain restructure move channel development out of Marketing?"

Context: this is a currency check on the single most useful positive finding of [[2026-08-23-etom-per-function-motion-catalog]], which read 1.2.1.6 Sales development out of ITU-T M.3050.2 (03/2007) — frozen at eTOM Release 7, nineteen years stale. The finding at risk: eTOM models the act of choosing channels as a standing process with three children, carrying sales targets and performance indicators per channel, and places it under Marketing rather than Sales.

Answer, up front, in two parts because the two halves resolve differently.

Part 1 — the process survived, and it is no longer a 2007 artifact. A Level-2 process element named Sales Development is present in the Market & Sales Domain of eTOM v21.0 (read from a TM Forum-published conformance footprint diagram, © TM Forum 2022) and of GB921D L3 R18.5.0 (read from a TM Forum-published domain decomposition figure, © TM Forum 2018). The restructure also added a second, separate L2 named Sales Channel Management, which did not exist in 2007. So the axis got more structure, not less. I could not confirm it at v24 or v25 specifically — see the honest-failure statement below — but the finding's vintage moves from 2007 to 2022, and the intervening restructure is now documented rather than assumed.

Part 2 — "out of Marketing" is the wrong shape of question, and that is itself the finding. The restructure did not move channel development out of Marketing. It abolished Marketing as a container. eTOM's post-restructure Level-1 is a set of seven Domains — Market/Sales, Product, Customer, Service, Resource, Business Partner, Enterprise — in which Marketing and Sales are one domain, not two. Market Strategy & Policy, Marketing Campaign Management, Marketing Communications and Advertising and Brand Management sit in the same Domain row as Selling, Sales Forecasting, Sales Development and Sales Channel Management. The 2007 observation "it sits under Marketing, not Sales" is therefore not falsified. It is rendered undiscriminating: in the current framework there is no Marketing/Sales boundary for the node to fall on either side of.

The honest failure, stated plainly

No v24 or v25 artifact I obtained reproduces the Market/Sales Domain's Level-2 list. Everything at v24 that I could read is domain-scoped to Customer. The string "Sales Development" is absent from both v24.0 documents I hold, and that absence is not evidence of removal — each document is explicitly "an extract of the text of the Business Process Framework" for one domain, so it could not contain a Market/Sales process even if one existed.

The artifact that would settle it: a GB921 v24.x or v25.x conformance self-assessment mapping template scoped to the Market/Sales Domain, or the full GB921D guidebook for v24/v25. The R18.5 Deloitte/STC document below is exactly this artifact one release family too early, which is why it is the template to hunt for. Where I looked, and what happened, is in the blocked list at the end of Sources.

Source tiers (read this before quoting anything below)

What we already know (from the vault)

• The finding under test, and its stated weakness. [[2026-08-23-etom-per-function-motion-catalog]] read 1.2.1.6 Sales development and its three children (monitor sales and channel best practice / develop sales and channel proposals / develop new sales channels and processes) from ITU-T M.3050.2 (03/2007), and flagged the gap itself: "the 2025 material I could fetch is a 48-page excerpt covering four Domains and never reaches the SIP area." This brief is that follow-up.
• Why it matters operationally. The same brief argued that if channel mix is the output of a standing process rather than a static fact, then "every client map we produce is a snapshot of a variable somebody in the org is paid to move, and the map does not currently record who that person is." It named FN.MARKETING at Kwik Trip — one of three departments that resisted motion assignment — as the candidate test case.
• The sibling verifications held, and the pattern is now four-deep. [[2026-08-21-apqc-pcf-80-channel-motion-leaves]] confirmed APQC left its channel leaves childless across two major versions. [[2026-08-22-scor-digital-standard-level2-process-types]] confirmed the decompose-at-L1 / choose-at-L2 shape while killing the specific codes. [[2026-08-26-apqc-retail-pcf-store-channel-decomposition]] found the one exception, an industry PCF that does decompose store-channel execution deeply.
• The schema decision this feeds is still open. spec/00-template-decisions.md deferred the axis: field pending re-verification, and [[2026-08-26-org-map-sibling-homogeneity-scope-test]] has since put pressure on the imported decomposition rules from the other direction.

What the web says

All items below are Tier A or B primary text or figures unless explicitly labelled otherwise.

1. The Market & Sales Domain L2 roster, read off the v21.0 conformance footprint (Tier A1)

The diagram lays the Domain out as a row crossed by seven lifecycle columns. Reading the Market & Sales row:

Two things to notice. Sales Development sits in Lifecycle Management, the column for building and retiring things. Sales Channel Management sits in Operations Readiness & Support, the column for keeping things runnable. eTOM has split the channel axis into build the channel and run the channel, and given each its own L2 element with its own owner.

2. The same roster, one release family earlier, as an explicit parent-child tree (Tier A2)

The R18.5.0 figure is a plain decomposition tree — Market_Sales Domain at the root, fifteen L2 boxes beneath it. Verbatim box labels, in figure order:

Market Strategy & Policy · Sales Strategy & Planning · Sales Forecasting · Sales Development · Market Sales Support & Readiness · Sales Channel Management · Selling · Loyalty Program Management · Contact/Lead/Prospect Management · Market Performance Management · Sales Performance Management · Marketing Communications and Advertising · Marketing Campaign Management · Brand Management · Market Research

Two independent TM Forum-published documents, two different diagram conventions, five years apart, same two nodes. That is the core positive result.

3. Marketing is not a container any more (Tier A1 + A3 + B)

The v24.0 extract states the domain list in running prose (© TM Forum 2025):

"The focus of the Business Process Framework is on the business processes used by service providers, the linkages between these processes, and the use of Market, Product, Customer, Service, Resource, Business Partner, and Enterprise Management related information by multiple processes."

And gives the numbering scheme:

".b.x.c.d.e where … x: Digit representing Domain … c: Digit representing Level 2 process"

The Salesforce v22.0 scoping table names domain 1 outright as "1.1 - Market & Sales Domain", and the Windup and 6D Tech templates name "1.2 Product Domain" and "1.3 Customer Domain". So the container that holds Sales Development is intact at v24.0; what I cannot read at v24.0 is its contents. In 2007 the node lived at 1.2.1.6, i.e. SIP area → Marketing and offer management → Sales development. That grandparent no longer exists. Marketing processes and Sales processes are now peers inside one Domain.

4. The pipeline-stage decomposition of Selling survives, with one process promoted out (Tier A3)

2007 1.1.1.4 Selling had five children. Current 1.1.9 Selling, read verbatim from two independent conformance scoping tables:

1.1.1.4.1 Manage prospect — the 2007 element carrying the "prospects are assigned to the appropriate sales channel" sentence — was promoted to its own L2, 1.1.11 Contact/Lead/Prospect Management, with children 1.1.11.1 Manage Sales Contact / .2 Manage Sales Lead / .3 Manage Sales Prospect. The parent brief's contradiction stands unchanged: eTOM still decomposes Selling by pipeline stage while our tree decomposes Sales by channel.

5. The Enterprise back office is still a Level-2 row (Tier A1, and weak)

The v21.0 footprint shows Enterprise as a single un-columned strip: Strategic & Enterprise Planning · Enterprise Risk Management · Enterprise Effectiveness Management · Knowledge & Research Management · Financial & Asset Management · Stakeholder & External Relations Mgt · Human Resources Management · Enterprise Data Management · Business Assurance. That is 2007's seven groupings plus two new ones. Caveat: a footprint poster shows L2 only by construction, so it cannot tell you whether L3 depth was added underneath. The parent brief's "do not cite eTOM for Finance, HR, Legal & Risk" guidance stands, but it now stands on 2007 evidence plus an uninformative poster, not on anything current.

6. The process ID is inference, not a read (Tier C — do not quote as fact)

I never read an ID next to Sales Development. Known-good sibling IDs from Tier A3 are 1.1.7 Market Sales Support & Readiness, 1.1.9 Selling, 1.1.11 Contact/Lead/Prospect Management, 1.1.14 Marketing Communications and Advertising, 1.1.15 Marketing Campaign Management. Mapping those onto the R18.5 figure's left-to-right box order gives a consistent position + 2 offset at every one of the five anchor points, which would put Sales Development at 1.1.6 and Sales Channel Management at 1.1.8, with two L2 elements not drawn in that figure. Plausible, arithmetically clean, and unverified. Cite the names, not the numbers.

Convergences and contradictions

• Convergence with the parent brief, strengthened. The 2007 claim was that eTOM models channel selection as a standing process. The current framework does that and then some: it separates channel construction (Sales Development, in the build-and-retire column) from channel operation (Sales Channel Management, in the keep-it-runnable column). Eighteen years of committee revision made the channel-as-a-thing-you-decide idea more structurally explicit, not less. Whatever else is true, this is not a concept eTOM was quietly walking away from.
• A contradiction with the question's own premise, and it is the more interesting half. The backlog item asked whether channel development moved out of Marketing. It could not have, because Marketing stopped being a place. The interesting consequence is that eTOM's answer to "does channel development report to Marketing or to Sales?" is now neither, and the question is malformed — the framework merged the two into one Domain and then re-cut that Domain by lifecycle stage (strategy / capability / lifecycle / readiness / fulfilment / assurance / billing) instead. The org-chart question our Organizational Map wants to ask has been architecturally dissolved by the framework rather than answered by it.
• A gap that neither converges nor contradicts. The v24.0 primary text I hold confirms the seven-domain skeleton and the numbering scheme but is scoped to the Customer Domain. Between R18.5 (2018) and v24.0 (2024) there are roughly a dozen releases. Nothing I read suggests churn in the Market/Sales L2 roster across v21 → v22 — 1.1.9 Selling keeps the same ID and the same children across both — which makes a silent deletion of Sales Development in that window unlikely. Unlikely is not verified, and this brief does not claim it as verified.

Synthesis for RDCO

The parent brief's most useful finding is no longer resting on 2007 text, and its two halves should now be cited separately. The half that survives cleanly, and that should go into the Organizational Platform's argument, is: a major process standards body models the construction and the operation of sales channels as two distinct standing processes with distinct owners, and has done so continuously from at least 2018 through at least 2022. That is a stronger, more specific claim than the one the parent brief made, because the 2007 text had one node and the current framework has two. The half that must be retired is the placement claim. "It sits under Marketing, not Sales" was doing real rhetorical work in the parent brief — it implied a testable prediction about where a channel-development owner sits on a real org chart — and the current framework cannot support it, because the framework no longer has a Marketing box. Anyone re-using that line should be pointed here.

The two-node split changes what the Org Map is missing, and makes the gap bigger rather than smaller. The parent brief concluded that the Map needs "a node and a seat for an owner of motion mix." The current eTOM says that is one seat too few. Building a new motion — standing up a partner channel, opening a direct-to-consumer storefront — is a lifecycle activity with a project shape and an end date. Running the portfolio of live channels, keeping each one staffed and hitting its per-channel targets, is a readiness activity with no end date. These are routinely different people, and in a mapped organization they are routinely in different reporting lines. If the Org Map is going to carry a channel-development concept at all, it should carry both, and the cheapest version of that is two role slots rather than one field. This also sharpens the Kwik Trip test in the parent brief's second follow-up: instead of asking "does anyone own channel development, and do they sit in Sales or Marketing" — a question the framework has just told us is malformed — ask "who decided to open the last new channel, and who is accountable for the per-channel numbers today, and are those the same person." Those are answerable from an org chart and a set of scorecards.

On the axis: decision, this brief is neutral-to-mildly-supporting and should not be over-read. It supplies a fourth independent body distinguishing a structural build-vs-run split, which is adjacent to but not the same as the alternative-vs-lane distinction the deferred field would encode. It does not re-verify the quarantined 2-of-10 count and makes no attempt to. What it does do is remove one stated objection to citing eTOM at all: the "verified-but-stale" label on the 1.2.1.6 row can come off for the existence and shape of the process, while a new and narrower caveat goes on — confirmed through v21.0/v22.0, not confirmed at v24.0/v25.0 — with the specific artifact that would close it named in the follow-ups below. That is a materially better epistemic position than the one this brief started from, and it is short of the one the question asked for.

On method, for the next person who hits a TM Forum gate. The parent brief's route generalizes further than it claimed. Not only does tmforum.org/wp-content/uploads/ serve clean while listings 403 — every other HTML path on the host is behind the same Cloudflare interstitial, including the WordPress REST API and both sitemap conventions, and WebFetch is challenged identically to curl, so there is no point trying the other tool. The productive move is that vendor conformance certification reports are a back door into the framework itself. They are published as static assets, they reproduce framework diagrams and scoping tables verbatim under TM Forum copyright, and the full-framework "conformance footprint" poster that some of them include is the single densest artifact available: one page carrying every Domain and every Level-2 element in the release. The catch is that these diagrams are raster images, so pdftotext returns nothing and the text has to be recovered by rendering the page and reading it. Any future eTOM currency check should start by finding a recent-release conformance report with a footprint poster, not by hunting for the guidebook.

Why this is in the vault

It resolves the first of the three open follow-ups on [[2026-08-23-etom-per-function-motion-catalog]] — partially, with the residual gap named — and it retires a specific sentence ("it sits under Marketing, not Sales") that was about to be carried into the Organizational Platform's motion-layer argument and into the Kwik Trip FN.MARKETING diagnosis, where it would have produced a malformed interview question. It also upgrades the recommendation from one missing Org Map seat to two, before the 36-motion vocabulary locks in organizational-platform/03-motions/.

Open follow-ups

• Does a GB921 v24.x or v25.x conformance self-assessment mapping template scoped to the Market/Sales Domain exist as a static asset under tmforum.org/wp-content/uploads/? That single file would close the residual gap in this brief outright — it would reproduce the Market/Sales L2 roster and the Sales Development extended description verbatim at the current release. The R18.5 Deloitte/STC document is exactly this artifact, one release family too early.
• Is there an eTOM v24.0 or v25.0 conformance footprint poster in any vendor certification report published in 2025 or 2026? The v21.0 poster carried every Domain and every L2 on one page and was the highest-yield artifact in this run by a wide margin. Finding the current equivalent would also settle the Enterprise-domain depth question that §5 leaves open.
• Did Sales Development retain its three 2007 children (monitor sales and channel best practice / develop sales and channel proposals / develop new sales channels and processes), and specifically did it retain the per-channel sales-target and performance-indicator language? That language is what made the 2007 finding load-bearing for the Org Map, and no artifact in this run reached the L3 layer under Sales Development.
• Does the new Sales Channel Management L2 decompose into channel types, or into channel-lifecycle stages? If types, eTOM has quietly published the channel catalog that four reference bodies have so far refused to publish, and the "nobody with a standards committee will name the motions" convergence in [[2026-08-23-etom-per-function-motion-catalog]] needs a stated exception.
• Reframed from the parent brief's second follow-up, now that the Marketing/Sales boundary is known to be dissolved: in a mapped client organization, is the person who authorized the most recent new channel the same person accountable for today's per-channel targets? Testable against the Kwik Trip org map, and it bears on why FN.MARKETING resisted motion assignment.
• eTOM re-cut its Domains by lifecycle stage (strategy / capability delivery / lifecycle management / operations readiness / fulfilment / assurance / billing) rather than by department. Is that second axis a better spine for the Organizational Map than function-then-motion, and has any vault brief tested the Map against a lifecycle-first decomposition at all?

Related

• [[2026-08-23-etom-per-function-motion-catalog]]
• [[2026-08-17-gtm-motion-origins-industry-reference-models]]
• [[2026-08-21-apqc-pcf-80-channel-motion-leaves]]
• [[2026-08-22-scor-digital-standard-level2-process-types]]
• [[2026-08-26-apqc-retail-pcf-store-channel-decomposition]]
• [[2026-08-26-org-map-sibling-homogeneity-scope-test]]
• [[2026-08-17-apqc-pcf-function-motion-mapping]]
• [[2026-08-22-cstore-fuel-retail-reference-models]]

Sources

Tier A — TM Forum primary documents and figures, fetched and read

• Open Digital Architecture — eTOM 21.0 Product Conformance Certification Report: Tecnotree DLPM (Digital Lead and Prospect Manager) v5.0, © TM Forum 2022. Figure 6 "eTOM DLPM Scope" (p.12 of the PDF) is the full v21.0 framework conformance footprint; the Level-2 scoping table is on p.11. https://www.tmforum.org/wp-content/uploads/2022/01/TMF-eTOM-21.0-CertificationReport_Tecnotree-DLPM-V-5.0-v1.0.pdf
• Business Process Framework (eTOM) — TM Forum Frameworx 18.5 Conformance Certification, Deloitte PLM Digital Transformation for STC CBU, Self-Assessment Process Mapping Report, Market/Sales Domain, © TM Forum 2018, header "GB921D L3 Business Process Framework (eTOM) R18.5.0". Figure 1 "Market/Sales Domain" (p.4) is the L2 decomposition tree. https://tmforum-resources.s3.amazonaws.com/Conformance+Certifications+/Deloite_PLM_STC/Deloitte+PLM_STC_Conformance_Mappings_R18.5_eTOM_MarketSales_Domain_V3RF.pdf
• Salesforce CPQ Conformance Certification Report — TM Forum eTOM & SID v22.0, © TM Forum 2022. Figure 9, "TM Forum Assessment Scoping Document — Business Process Framework (eTOM) v22.0", gives 1.1 - Market & Sales Domain and the children of 1.1.9 Selling. https://www.tmforum.org/wp-content/uploads/2023/02/Salesforce-CPQ-eTOMSID-22.0_Conformance_Certification_Report_v1.0.pdf

Tier B — GB921 v24.0 primary excerpts, wrong domain for this question

• Business Process Framework (eTOM) Conformance — GB921 Process Decompositions v24.0, 6D Technologies self-assessment mapping template, 58 pp, © TM Forum 2025. Source of the seven-domain sentence and the b.x.c.d.e numbering scheme. Scoped to the Customer Domain. https://www.tmforum.org/wp-content/uploads/2025/07/eTOM-24.0_Conformance_Mapping_Template-6D_Tech-VFRF.pdf
• GB921 Process Decompositions v24.0 — JioChargeIT Additional Processes self-assessment mapping template, © TM Forum 2025. Carried over from the parent brief; re-checked here for any Market/Sales reference (none). https://www.tmforum.org/wp-content/uploads/2025/06/eTOM-24.0_Conformance_Mapping_Template-JioChargeIT-AdditionalProcesses-VFRF-1.pdf
• WindUp Software self-assessment mapping report for eTOM certification, EW Billing System Solution, © TM Forum. Consulted only to corroborate the Domain numbering (1.2 Product Domain, 1.3 Customer Domain). https://www.tmforum.org/wp-content/uploads/2023/04/Windup-eTOM-Conformance-Mapping-V2RF.pdf

Blocked — flagged, not retried

• https://www.tmforum.org/resources/suite/gb921-business-process-framework-etom-suite-v24-0/ — HTTP 403, Cloudflare interstitial, to both WebFetch and curl with a browser User-Agent
• https://www.tmforum.org/oda/conformance/etom — HTTP 403, same interstitial
• https://www.tmforum.org/wp-json/wp/v2/search, /wp-json/wp/v2/media, /sitemap_index.xml, /wp-sitemap.xml — all HTTP 403, same interstitial. No asset-discovery path exists on the host
• https://tmforum-resources.s3.amazonaws.com/?list-type=2 — AccessDenied. The bucket serves known keys but will not enumerate
• Member-gated GB921 guidebook downloads on tmforum.org — not attempted, per standing policy on member-gated material

Vault

• [[2026-08-23-etom-per-function-motion-catalog]] — ~/rdco-vault/06-reference/research/2026-08-23-etom-per-function-motion-catalog.md
• [[2026-08-17-gtm-motion-origins-industry-reference-models]] — ~/rdco-vault/06-reference/research/2026-08-17-gtm-motion-origins-industry-reference-models.md
• [[2026-08-21-apqc-pcf-80-channel-motion-leaves]] — ~/rdco-vault/06-reference/research/2026-08-21-apqc-pcf-80-channel-motion-leaves.md
• [[2026-08-22-scor-digital-standard-level2-process-types]] — ~/rdco-vault/06-reference/research/2026-08-22-scor-digital-standard-level2-process-types.md
• [[2026-08-26-apqc-retail-pcf-store-channel-decomposition]] — ~/rdco-vault/06-reference/research/2026-08-26-apqc-retail-pcf-store-channel-decomposition.md
• [[2026-08-26-org-map-sibling-homogeneity-scope-test]] — ~/rdco-vault/06-reference/research/2026-08-26-org-map-sibling-homogeneity-scope-test.md
• [[2026-08-17-apqc-pcf-function-motion-mapping]] — ~/rdco-vault/06-reference/research/2026-08-17-apqc-pcf-function-motion-mapping.md
• [[2026-08-22-cstore-fuel-retail-reference-models]] — ~/rdco-vault/06-reference/research/2026-08-22-cstore-fuel-retail-reference-models.md
• Organizational Platform artifacts (not vault, phData project): ~/Documents/phdata-projects/organizational-intelligence/spec/00-template-decisions.md, ~/Documents/phdata-projects/organizational-intelligence/organizational-platform/03-motions/