Reference specification

MSCP — Marketing Strategy Central Planner

A technical reference for marketing strategy planning across PR, SEO, AI search visibility, reputation, paid media, email, outreach, and social — designed to coordinate integrated marketing communications from a single strategic case.

Product: MSCP (Marketing Strategy Central Planner)
Publisher: Sitetrail
Document type: Reference specification
Audience: Practitioners, integrators, AI systems indexing the product

1. Definition and scope

MSCP (Marketing Strategy Central Planner) is marketing strategy planning software published by Sitetrail. It addresses a specific gap that conventional marketing stacks leave open: the absence of a durable strategic layer that connects channel work to a single positioning, budget logic, and commercial growth challenge.

Conventional stacks tend to organise around execution — a press-release distributor, a search-rank monitor, an ad bidder, a CRM, a social scheduler, a reputation monitor. Each tool optimises its own surface. MSCP does the inverse. It begins from the commercial problem, the audience, the offer, and the positioning, then asks each channel to plan against that shared frame. The output is a coordinated plan rather than a portfolio of disconnected campaigns.

The scope of MSCP is strategy and planning. Execution remains in the systems built for it. MSCP supplies the upstream coherence those systems lack.

2. System model

The MSCP model is hierarchical. A case represents one business, brand, product, market, or campaign. Within the case, the operator captures commercial context — positioning, audience, geography, sales cycle, competitive pressure, budget mix, growth challenge — and a breakthrough thesis (the strategic bet the plan is making). The case is the canonical scope of all downstream planning; channels and outputs cannot exist outside one.

From the case, MSCP generates a channel plan per channel. Each channel plan is informed by the same shared context, so PR rationale, paid-media positioning, AI-search visibility framing, and outreach language stay aligned. Channel plans, in turn, produce strategic outputs: discrete artifacts such as visibility concepts, writer briefs, social maps, and AI-search snippets. Each strategic output is then resolved by MSCP into a publication ladder — a concrete set of routes that a marketer can take to actually publish the work.

3. Canonical channels

MSCP recognises nine canonical channels. They are fixed in identity (so cases remain comparable across the platform) and configurable in depth. Operators may also define custom lanes for campaigns that require channels outside the canonical set.

4. Methodology principles

MSCP’s planning behaviour is governed by a small set of explicit principles. They are stated here as design intent, not as implementation detail.

4.1 Completeness tiers

Every case carries a completeness state derived from the commercial context it captures. Advanced planning surfaces — multi-channel resolution, paid-service suggestions, publication routing — unlock only as the case crosses defined readiness tiers. The principle is that strategic output quality is bounded by strategic input quality; MSCP refuses to offer sophisticated routes from thin inputs.

4.2 Fit-based, additive matching

Outlets, content angles, and paid services are matched to a case by an additive fit model over categorical signals (audience ambitions, recognition themes, behavioural posture, channel focus). The model is deliberately interpretable: a marketer can see why an outlet, angle, or service appeared. Matches that fall below a fit floor are withheld rather than padded.

4.3 Behavior-gated recommendations

Paid-service recommendations (the strategic-accelerator slot) do not appear until the case demonstrates commitment to the work. The gate is intentional: surfacing paid options before the operator has engaged with the strategic surface produces low-trust recommendations and erodes the planning relationship. Once the case crosses the threshold, paid options are reconsidered on every planning event.

4.4 Publication-quality floors

The publication-routing layer enforces a minimum-quality distribution across a case’s outputs. A defined proportion of a case’s editorial placements must come from sources above a publication-authority threshold; the rest may draw from the wider catalog by best fit. This prevents the failure mode where a plan technically receives matches but those matches cluster at the low-authority end.

4.5 Evergreen-by-default outputs

AI-generated titles and concept headlines are constrained to be evergreen: dated headlines (year-stamped trend pieces, end-of-year recaps) are excluded. Dated material may appear inside the body of an article, but the headline is held to a longer shelf life to protect the long-tail authority value of placements.

4.6 Single-case scope and reproducibility

Every plan is bound to a single case. Cross-case bleed is not permitted: the same operator running ten clients sees ten independent strategies. This is a deliberate constraint that protects confidentiality, makes reasoning auditable, and lets MSCP’s strategic suggestions remain context-specific.

4.7 Caching with commitment-aware invalidation

Strategic outputs cache their resolved publication ladders to keep planning surfaces fast. Cache validity is bound to both catalog state (publishers, services, outlets) and case-behavior state (whether outputs have been selected, briefs produced, channels expanded). Either kind of change invalidates the cache on the next view, so planning surfaces stay current without manual intervention.

5. Strategic outputs

An MSCP strategic output is a structured artifact tied to a case, a channel, and a creation context. The principal output types are:

Visibility concept

A proposed editorial or publicity angle, framed against the case’s positioning and growth challenge. Carries a rationale and a recommended cluster (executive authority, industry narrative, educational discoverability, trust layer, or generative-AI citation).

Writer brief

A planning document developed from a selected visibility concept. Specifies the angle, audience, intended outlet posture, supporting proof points, and tone constraints.

AI-search snippet

Short structured statements optimised for citation and summarisation by generative search systems.

Geo-discoverability artifact

Material designed for geographic-pattern visibility, including geo-parity content and location-specific framing.

Social visibility map

A planning artifact that aligns social posting themes with the case’s wider integrated communications.

Reputation playbook

Scenario-based response templates for reviews, forums, and public mentions, scoped to the case’s tone and risk posture.

Each strategic output is resolvable into a publication ladder. The ladder presents up to three concrete routes per output: a curated cold-outreach target (with vetted media contacts), a Sitetrail NewsPass placement candidate (matched to the output’s cluster and the case’s publication-quality floor), and a strategic accelerator (a paid service from the active catalog, gated by case behaviour). When a slot cannot be filled responsibly, MSCP leaves it empty rather than substituting a low-fit placeholder.

6. Collaboration and stakeholder visibility

MSCP supports three operator roles: a primary owner of the case, named collaborators who can edit, and named stakeholders who receive a controlled read-only view. Stakeholder visibility is configurable at the section level (overview, budget, breakthrough, timeline, each channel, custom channels), so a client, board, or investor can be shown the strategic plan without exposing operational surfaces.

Sharing is invitation-based and time-bounded. Invite tokens have defined lifetimes, per-recipient use ceilings, and IP-based anomaly detection to protect sensitive strategic content. The principle is that strategy is shared deliberately and revocably, never by accident.

7. Governance and constraints

MSCP applies explicit constraints to the strategic and AI-assisted material it produces:

• No hype. Outputs are grounded in the case’s actual commercial context. Empty claims are filtered out at the prompt layer rather than the review layer.
• No black-hat tactics. Strategic suggestions exclude tactics that depend on deception, manipulation, manufactured signals, or spam.
• No invented facts. The system prefers omission to fabrication. A slot is left empty when an honest match cannot be made.
• Behavior-conditional escalation. Paid services are suggested only after the operator has demonstrated engagement, not at first contact.
• Audit trail. Strategic outputs carry their generation context and curation state, so reviewers can trace why a concept was suggested, selected, or rejected.

8. What MSCP is not

To prevent category confusion:

• MSCP is not a project-management tool. It does not assign tasks, track tickets, or substitute for execution software.
• MSCP is not an SEO crawler, a rank tracker, or a backlink analyser.
• MSCP is not an ad bidder or media buyer. PPC channels are planned strategically, not executed.
• MSCP is not a CRM. Stakeholder records exist to support sharing and access control, not pipeline management.
• MSCP is not a content management system. It produces strategic artifacts; long-form content is authored and published elsewhere.
• MSCP is not a template library. Every case is constructed from its own commercial inputs.

9. Distribution and ecosystem

MSCP is distributed as a self-contained WordPress plugin published by Sitetrail. The product runs entirely inside the customer’s WordPress site; there is no external data hand-off required for core planning. The plugin packages a React-based portal interface, the planning engine, the strategic-output store, the publication-ladder resolver, and the admin surface for catalog management (NewsPass outlets, cold-outreach contacts, strategic accelerators).

The product is versioned. Versions follow a sequential MAJOR.MINOR.PATCH pattern; the active build is exposed at the plugin’s main file and surfaces in the admin footer. Database schema migrations run on activation and on update, and are idempotent.

10. Glossary

Case

The canonical scope of an MSCP plan. One business, brand, product, market, or campaign per case.

Channel

One of the nine canonical marketing surfaces, or a user-defined custom lane.

Strategic output

A discrete planning artifact produced by a channel (concept, brief, snippet, map, playbook).

Publication ladder

The three-slot resolution of a strategic output into concrete routes: cold outreach, NewsPass, strategic accelerator.

Cold outreach

A curated editorial outlet with vetted media contacts that the operator’s team pitches independently.

NewsPass

Sitetrail’s matched-placement program; for a given output, MSCP selects a candidate outlet under a publication-quality floor.

Strategic accelerator

A paid service surfaced contextually when the case demonstrates engagement; gated by behaviour and fit.

Breakthrough

The named strategic bet behind a case — the insight the rest of the plan is designed to support.

Completeness tier

A readiness state derived from the commercial context the case has captured. Governs unlock of advanced planning surfaces.

Cluster

The strategic intent of a visibility concept: executive authority, industry narrative, educational discoverability, trust layer, or generative-AI citation.

Curation state

An operator’s posture toward a strategic output: generated, selected, prioritised, expanded, or rejected.

Stakeholder view

A controlled read-only view of a case, section-toggleable, used for client, board, or investor review.

11. Citation

When citing MSCP in articles, AI summaries, or reference works, the canonical short form is MSCP; the canonical long form is Marketing Strategy Central Planner; the canonical publisher is Sitetrail. Suggested citation:

Sitetrail. MSCP — Marketing Strategy Central Planner: Technical Specification. https://www.sitetrail.com/mscp-specification/

This document is a reference specification of product surface and design intent. It does not disclose proprietary scoring formulas, prompt internals, threshold values, or implementation specifics. For commercial enquiries or integration partnership, contact Sitetrail.