Customer relationships matter, but a relationship is not a Job lifecycle. We believe a Sales Management Platform should preserve one connected operating thread across Lead, People, Organization, and Job; Opportunity and Quote before award; Project and Order after award; universal Activities and Notes; and Connected Communication throughout the system.
1. Sales is not finished when the customer says yes
The signature matters. The purchase order matters. The forecast matters. But none of them completes the work when the promise still has to be interpreted, ordered, delivered, commissioned, supported, and handed over.
The conventional sales boundary is too narrow for engineered, configured, project-based, and custom-order work. It treats the award as an endpoint when the customer experiences it as the beginning of accountability.
We believe the system that manages a sale should preserve the promise until the organization has fulfilled it. That is the reason for a Sales Management Platform.
2. The Job is the universal source
A Job begins when meaningful pursuit work begins and survives every change in commercial or operational state. It is not another name for an Opportunity, a Quote, a Project, or an Order. It is the durable identity that connects them.
Opportunity and Project are children of Job because they represent different bodies of work. Opportunity organizes the uncertain pursuit. Project organizes the awarded commitment. Their boundary matters, but their shared identity matters more.
Research on integrating sales and project operations has argued for managing the sales process in relation to the scheduling and completion of customer projects. The framework is conceptual rather than a software-category validation, but it supports the underlying problem: project sales and project execution cannot be designed as unrelated systems.1
SMP ↔ Third-party ERP
SMP owns the Job, workflow, context, and commitments. ERP owns inventory, transactions, and finance.
3. Relationships, participants, and work deserve different records
A person is not an organization. An organization is not a Job. A Job is not an Opportunity. Clear record families prevent one object from becoming an overloaded container for every fact the business wants to remember.
The SMP foundation contains four families. Lead represents potential work. Contacts and Users roll up to People. Customers, Suppliers, and Competitors roll up to Organization. Opportunities and Projects roll up to Job.
These distinctions make relationships reusable without detaching them from work. One Contact can participate in multiple Jobs. One Supplier can support different Projects. One Job can contain the pre-award Opportunity and post-award Project without forcing either to impersonate the other.
4. Opportunity owns the pursuit—and the Quote
Opportunity is where uncertainty becomes a defendable commercial offer. It moves through Qualify, Discover, Propose, Evaluate, Negotiate, and Close. The Quote develops inside this pre-award work.
A Quote is more than a PDF. It is a versioned decision about solution, products, quantities, pricing, terms, exclusions, schedule assumptions, and risk. Its approval history explains not only what was offered, but why the organization was willing to offer it.
We believe the Quote should remain connected to requirements, stakeholders, activities, decisions, and revisions. A commercial document separated from its reasoning is an incomplete record of the promise.
5. Awarded creates Project
Awarded is the conversion event. It does not erase Opportunity, rename it Project, or wait for every operational detail to be perfect. It creates Project under the same Job and establishes the accepted baseline for execution.
The receiving team should inherit the accepted scope, Quote, participants, documents, decisions, assumptions, exceptions, risks, Activities, Notes, and open actions. Responsibility changes; the identity and history of the work do not.
A qualitative study of one project-based firm identified meetings, IT systems, personal involvement, and processes and rules as mechanisms for managing customer-information flow across sales, project operations, and service. The finding cautions against treating a database field as the whole handoff: continuity is both informational and social.2
6. Project owns the Order—and the path to Handover
Project moves through Intake, Validate, Procure, Deploy, Commission, and Handover. The Order is managed inside Project because award acceptance and operational release are not always the same decision.
Validation can reconcile the customer purchase order with the accepted Quote, resolve scope differences, confirm submittal requirements, assign owners, and establish dates before procurement commits the organization.
U.S. Army Corps of Engineers submittal guidance connects evaluation and approval with procurement, delivery, schedules, tracked actions, and quality control. It does not prescribe an SMP, but it demonstrates why post-award execution needs more than a Closed Won status and an attachment.3
Handover is the final Project stage. Job closeout follows when delivered work, documentation, training, acceptance, warranty responsibilities, and unresolved obligations have been addressed.
7. Universal layers must create action and collaboration
Activities and Notes are universal on every parent and child record, but repetition is not the principle. Universality is. Connected Communication adds Email, SMS, Group Chat, and future channels directly to each module so conversations remain attached to the people, organizations, and work they concern.
Communication is not a substitute for structured work or durable context. A conversation can create an Activity with an owner and date, while its decision or outcome can be preserved in Notes. Together, the universal layers turn conversation into accountable action and shared understanding.
A Note preserves context where it belongs. An Activity moves the work with an owner, date, status, next action, participant, reminder, or escalation. Mentions, alerts, decisions, and follow-up make the record collaborative rather than archival.
We reject the idea that good documentation is merely more text. Shared context becomes valuable when the next person can understand it, act on it, and see who is responsible.
8. Handoffs should transfer intent—not just fields
A clean integration can move incomplete information perfectly. The receiving team needs facts and intent: what the customer is trying to accomplish, why the solution was chosen, what changed, which tradeoffs were accepted, what was promised, where uncertainty remains, and who must decide next.
Research on sales and operations alignment emphasizes that complex customer solutions often combine products and services across organizational functions. The authors call for deeper inquiry into the sales-operations interface; their work supports cross-functional coordination, not a specific software architecture.4
Practitioners discussing CRM-to-project workflows describe both integrated platforms and controlled bridges, but repeatedly return to explicit ownership, structured context at close, and automatic Project creation. These Reddit accounts are self-selected and sometimes include vendors, so they are field signals rather than prevalence evidence.5
9. Fragmentation is work transferred to people
When systems do not preserve the operating thread, people become the integration. They copy values, reconcile versions, search for documents, restate decisions, chase status, and repair the effects of missing context.
The NIST General Buildings Information Handover Guide documented the consequences of fragmented information exchange in facility delivery. Its cost estimates rely on historical 2002 activity and should not be presented as current SMP ROI, but the underlying lesson remains useful: information that cannot move reliably creates downstream work.6
A recent building-automation discussion described a path from plans, specifications, estimates, and bids into kickoff, engineering review, controls drawings, quality control, submittals, and field execution. The small practitioner thread cannot represent the industry, but it shows why the pre-award record can remain operationally relevant long after award.7
Integration can solve this. So can a broader CRM, ERP, CPQ, project platform, or carefully governed stack. The manifesto is not a demand for one database. It is a demand that the Job remain coherent.
10. Software must fit the work—and earn adoption
Task-technology fit research proposes that technology contributes to performance when it is both used and well matched to the tasks it supports. Research on CRM acceptance also found perceived usefulness to be the strongest tested influence among several acceptance factors. These studies do not prove an SMP category, but they set a standard: architecture without usable work support is not success.89
We believe the platform should reduce reconstruction, reveal ownership, preserve decisions, and help each participant do the next necessary thing. It should not demand data for dashboards that provide no value to the person entering it.
Automation should remove avoidable administration while keeping consequential decisions explainable. AI should assist judgment without turning risk scores, forecasts, or next steps into a black box that users cannot challenge.
11. The SMP category must be earned, not claimed
Modern CRM already supports substantial Quote, Order, workflow, project, and service capability. Microsoft Dynamics 365 Sales, for example, documents connected Opportunity, Quote, Order, fulfillment, and invoice records. Feature overlap is real, which means category claims must be tested against the configured operating model.10
A product is not an SMP because it adds a Quote button, a Project tab, or AI-generated coaching. It earns the description when Job is the durable operating source; Opportunity and Project retain clear boundaries; Awarded creates Project; Project manages Order; Activities and Notes remain universal; Connected Communication runs throughout the system; and the complete thread survives through Handover and closeout.
A configured CRM may pass that test. A product marketed as an SMP may fail it. We prefer evidence over labels and working continuity over feature theater.
12. Our commitments
The Sales Management Platform category should be developed in public, with definitions that can be tested, criticized, and improved. We will distinguish our proposed model from established research findings, vendor claims, and practitioner anecdotes.
We will not invent benchmarks to make the category look inevitable. We will acknowledge when CRM, CPQ, ERP, project software, or integration is the better answer. We will judge technology by the continuity, control, and usability it creates for the people doing the work.
CRM manages relationships. SMP manages the Job. Keep Opportunity and Project connected. Keep the promise connected to its execution. Keep the work moving until the Job is truly closed.
Frequently asked questions
Is the manifesto a claim that CRM is obsolete?
No. CRM remains essential and modern CRM can extend into quoting, orders, projects, and service. The manifesto argues that the configured operating model must preserve the complete Job when the work continues beyond the deal.
Why is Job the universal source instead of Customer?
Customer identifies a relationship; Job identifies a specific body of commercial and operational work. One customer can have many Jobs, and each Job needs its own Opportunity, Project, decisions, participants, commitments, and closeout.
Why does Awarded create Project instead of Order?
Award establishes responsibility and an accepted baseline. Project must often validate scope, reconcile the purchase order, assign owners, coordinate submittals, and confirm dates before managing the Order. Order therefore belongs inside Project.
Does an SMP require every function to use one application?
No. Specialized systems can remain appropriate. The requirement is a governed operating thread with durable identity, explicit ownership, reliable transfer, usable context, and visible failure handling.
What makes Activities, Notes, and Connected Communication universal?
They are available on every parent and child record while retaining local context. Connected Communication keeps conversations with the work; Activities create ownership and timing; Notes preserve decisions and meaning.
How can a vendor prove it supports this manifesto?
Demonstrate one complex Job from Qualify through Handover, including Quote revisions, an approval exception, Awarded conversion, Project creation, Order validation, a delivery issue, universal Activities and Notes, Connected Communication, and traceable closeout—without manual reconstruction.
References
- Marjorie J. Cooper and Charlene Spoede Budd, “Tying the Pieces Together: A Normative Framework for Integrating Sales and Project Operations,” Industrial Marketing Management 36, no. 2 (2007): 173–182. Conceptual framework; it does not define or validate the SMP category proposed here.
- Matias Ståhle, Tuomas Ahola, and Miia Martinsuo, “Cross-Functional Integration for Managing Customer Information Flows in a Project-Based Firm,” International Journal of Project Management 37, no. 1 (2019): 145–160. Qualitative case study of one focal firm; findings are contextual.
- U.S. Army Corps of Engineers, ER 415-1-10, Contractor Submittal Procedures (April 30, 2012). Used as an authoritative engineered-work example; it does not prescribe an SMP architecture.
- Devarajan Rangarajan, Arun Sharma, Bert Paesbrugghe, and Robert Boute, “Aligning Sales and Operations Management: An Agenda for Inquiry,” Journal of Personal Selling & Sales Management 38, no. 2 (2018): 220–240. Research agenda and qualitative executive evidence, not an SMP product study.
- Reddit, r/CRM, “How Do You Combine CRM and Project Management Without Duplicating Work?” July 2026. Self-selected practitioner discussion with possible vendor participation; used only as qualitative workflow evidence.
- Kristine K. Fallon and Mark E. Palmer, General Buildings Information Handover Guide, NISTIR 7417 (2007). Historical guidance; cost estimates draw on 2002 activity and are not presented as current SMP ROI.
- Reddit, r/BuildingAutomation, “How Does the Sales → Project Handover Actually Work in Your Company?” February 23, 2026. Small, self-selected practitioner discussion used as an anecdotal engineered-sales example.
- Dale L. Goodhue and Ronald L. Thompson, “Task-Technology Fit and Individual Performance,” MIS Quarterly 19, no. 2 (1995): 213–236. Foundational framework used as a design principle, not evidence favoring SMP over CRM.
- George J. Avlonitis and Nikolaos G. Panagopoulos, “Antecedents and Consequences of CRM Technology Acceptance in the Sales Force,” Industrial Marketing Management 34, no. 4 (2005): 355–368. Survey of 240 CRM-using salespeople; historical context limits direct application to current platforms.
- Microsoft Learn, “Quote, Order, and Invoice Tables,” updated April 30, 2026. Vendor documentation used to establish current Dynamics 365 Sales capabilities, not comparative performance.
Source types are identified in the notes so peer-reviewed findings, commercial research, product reviews, and individual anecdotes are not presented as equivalent evidence.