Catalog planning brief ยท CMP-007

Service Marketplace vs Agency or Service-Business Portal

Should Service Marketplace or Agency or Service-Business Portal own independent provider supply, operate clarifying assignment, and provide evidence for payment flow?

Compare independent provider supply with one organization's own staff and delivery operation, clarifying assignment, pricing, customer ownership, quality control, and payment flow. Compare the models by deciding who owns independent provider supply, how clarifying assignment works, and how exceptions involving quality control are handled. Choose the model that makes evidence for payment flow a core responsibility rather than an optional feature.

Best for: Teams planning Service Marketplace vs Agency or Service-Business Portal that need to agree on independent provider supply, clarifying assignment, and payment flow before detailed scope.

Frame Service Marketplace versus Agency or Service-Business Portal around the actual operating boundary The decision moves from independent provider supply through the model choice, into clarifying assignment, and ends with evidence for payment flow. 1 AUDIENCE Independent provider supply 2 CORE RECORD Service Marketplace 3 DEFINING WORKFLOW Agency or Service-Business... 4 EVIDENCE Payment flow Frame Service Marketplace versus Agency or Service-Business Portal around the actual operating boundary The decision moves from independent provider supply through the model choice, into clarifying assignment, and ends with evidence for payment flow. 1 AUDIENCE Independent provider supply 2 CORE RECORD Service Marketplace 3 DEFINING WORKFLOW Agency or Service-Business... 4 EVIDENCE Payment flow
Test both models against one organization's own staff, exceptions around quality control, and evidence for payment flow; do not choose from labels alone.

Good fit / poor fit

Use independent provider supply and clarifying assignment to separate the models

The stronger label is the one that accurately assigns one organization's own staff, exceptions around quality control, and the resulting operating load. Optional screens should follow that boundary.

Choose Service Marketplace when

Service Marketplace is the clearest owner of independent provider supply and clarifying assignment.

  • Removing Agency or Service-Business Portal-specific features would not break how independent provider supply creates value.
  • one organization's own staff naturally belongs inside the Service Marketplace record and permission model.
  • The team can resolve exceptions around quality control and collect evidence for payment flow while operating Service Marketplace.

Choose Agency or Service-Business Portal when

Agency or Service-Business Portal better explains why one organization's own staff needs product support and how payment flow will be evidenced.

  • The product loses its purpose if Agency or Service-Business Portal no longer coordinates clarifying assignment.
  • independent provider supply needs the roles, state, or trust boundary implied by Agency or Service-Business Portal.
  • Ownership of exceptions around quality control is necessary operating scope, not speculative later work.

Decision matrix

Compare Service Marketplace and Agency or Service-Business Portal against this topic's real boundaries

Compare independent provider supply with one organization's own staff and delivery operation, clarifying assignment, pricing, customer ownership, quality control, and payment flow. The rows below turn that scope into five concrete decisions about independent provider supply, one organization's own staff, clarifying assignment, exceptions, and evidence.

Compare both models, or focus one column to trace its responsibilities.

Topic boundary Service Marketplace Agency or Service-Business Portal Why this changes the plan
Independent provider supply Make independent provider supply part of the Service Marketplace promise and name its owner. Make independent provider supply part of the Agency or Service-Business Portal promise and name its owner. A different owner for independent provider supply changes onboarding, permissions, and support.
One organization's own staff Model one organization's own staff only to the depth required by Service Marketplace. Model one organization's own staff only to the depth required by Agency or Service-Business Portal. The lifecycle of one organization's own staff determines records, integrations, and audit needs.
Clarifying assignment Trace one Service Marketplace path through clarifying assignment with visible state. Trace one Agency or Service-Business Portal path through clarifying assignment with visible state. Branches around pricing can materially widen the first release.
Exceptions around Quality control Assign the Service Marketplace operator's response to exceptions involving quality control. Assign the Agency or Service-Business Portal operator's response to exceptions involving quality control. Unowned exceptions around quality control become support and trust failures regardless of the label.
Payment flow Define the evidence Service Marketplace must produce for payment flow. Define the evidence Agency or Service-Business Portal must produce for payment flow. Evidence for payment flow separates the core model from optional feature activity.

First-release boundary

Scope the smallest release that makes payment flow observable

The first release of Service Marketplace vs Agency or Service-Business Portal should connect delivery operation to payment flow before expanding every variant of customer ownership, integration, automation, or reporting need.

Prove in the first release

  • Name one primary buyer and seller segment and the exact role of independent provider supply in its journey.
  • Model the minimum state and permissions needed for one organization's own staff and delivery operation.
  • Implement one complete path through clarifying assignment, including the essential branch around pricing.
  • Give the platform operator a practical way to detect, inspect, and recover exceptions involving quality control.
  • Capture evidence of payment flow so the team can continue, narrow, or revise the product boundary.

Hold until evidence justifies it

  • Additional audiences, variants, and advanced permissions around independent provider supply and one organization's own staff.
  • Automation, integrations, and optimization for customer ownership before the core workflow is reliable.
  • Sophisticated reporting or personalization beyond the evidence needed to verify payment flow.

Decisions that materially change effort

  • The number of roles and permission boundaries controlling independent provider supply and one organization's own staff.
  • Lifecycle branches, approvals, reversals, and recovery paths across clarifying assignment and pricing.
  • Operational exposure when exceptions involving quality control occur repeatedly or at scale.
  • External systems that create, change, or depend on delivery operation or customer ownership.
  • Audit, accessibility, availability, localization, and support expectations attached to payment flow.

Trust, exceptions, and operations

Assign ownership for clarifying assignment, exceptions around quality control, and payment flow

The interface for Service Marketplace vs Agency or Service-Business Portal is only the visible layer. The operating model must also govern independent provider supply, keep one organization's own staff trustworthy, and make recovery from exceptions involving quality control practical.

Ownership of Independent provider supply

The platform operator function needs explicit rules for creating, changing, and retiring independent provider supply while keeping one organization's own staff consistent.

  • Who creates or approves independent provider supply, and which roles may change it?
  • What happens when independent provider supply and one organization's own staff disagree?
  • Which changes need history, notification, approval, export, or deletion controls?

Control of Clarifying assignment

Every important transition through clarifying assignment needs a visible owner, especially where pricing changes the normal path.

  • Which states make progress through clarifying assignment visible to each role?
  • Where can pricing be automated safely, and where is review required?
  • How is duplicated, abandoned, or contradictory work returned to a valid state?

Recovery for Quality control exceptions

A credible release makes exceptions involving quality control visible, gives the platform operator a workable response, and preserves evidence for payment flow.

  • What can the buyer and seller do when an exception involving quality control occurs without contacting support?
  • Which evidence does the operator need to investigate and resolve exceptions around quality control?
  • Which signal demonstrates payment flow without relying on vanity metrics?

Useful next steps

Turn the planning boundary into an evidence-backed first release

For Service Marketplace vs Agency or Service-Business Portal, use the Marketplace guide to verify the wider product model, then choose whether a quick range or a detailed plan is the useful next step. These links are limited to routes that advance this decision.

Planning basis and review

A complete catalog brief with room for deeper research

This page is generated from the reviewed WebGrid opportunity catalogue and application-type decision model. The baseline was reviewed 17 August 2026; its next scheduled review is 17 February 2027.

This guide defines product responsibilities. Payment, tax, consumer, identity, privacy, and marketplace obligations depend on jurisdiction, provider configuration, contracts, and operating choices; verify them with the relevant specialists.