Understand What Your Xtrusio Service Plan Includes

Your Xtrusio subscription combines platform access, client-specific configuration and a team that delivers the agreed work. Your signed agreement defines the questions monitored, content produced, publishing scope and custom requirements. This page explains how to read that scope; it does not replace your agreement.

The three parts of the service

The shared platform supports company research, buyer questions, AI monitoring, reporting, content planning and publication tracking.

Your client-specific layer contains your company context, approved product facts, competitors, brand voice and agreed workflows. Additional modules and integrations depend on the requirements included in your subscription. A feature available in another client's workspace is not automatically part of yours.

The delivery team operates the agreed service. Each account has an allocated developer and a journalist/content writer, with additional resources according to the subscription. Allocation means responsibility for your account, not exclusive full-time staffing.

Agree the monitoring workload

Confirm three things before monitoring begins:

1. Which buyer questions are approved for monitoring.
2. Which AI engines are included.
3. How many completed scans are due and when the team will run them.

The team owns the schedule. The allowance is generally two or three scans according to the agreement. Failed attempts do not replace the obligation to complete the contracted scans; the team handles retries and unresolved problems.

The research process can produce a focused set of 150–200 questions. That research target is not an entitlement to monitor every question on every engine at any frequency. The approved monitoring scope governs the delivered workload.

For example, 150 questions across six engines and two scans means 1,800 planned question-engine observations. This is a workload illustration, not a pricing formula, credit allowance or standard package.

Agree the content and publishing scope

Your agreement should distinguish the number of written pieces from where they will be published. A completed draft, an approved article and a live publication are different stages.

Standard placements on the website list supplied for your client are included as specified in the subscription. The client approves publisher-selection criteria, and the team continues finding suitable publishers within those criteria and the agreed scope. Inclusion does not mean unlimited placements or guaranteed publisher acceptance.

Larger or exceptional publishing projects require separate scope and cost confirmation. PR drafting, publication and tracking use a separate PR subscription arrangement. Social and video work follow the channels and responsibilities agreed for your account.

Client-blog publishing can use a configured CMS connection or a manual handoff. Do not assume that every CMS is already connected. Third-party publication is coordinated by the journalist team with the publisher.

Your approval responsibilities

Before execution, the team reviews the company Foundation with you. You approve the buyer questions, product and service descriptions, facts and figures. When sources conflict, your approved factual decision guides the work.

You also review the main content before publication. There is no revision-count limit before you approve that content. This does not include unlimited unrelated new articles or indefinite revisions after approval.

Useful feedback identifies the article, the specific problem and the correct fact or supporting source. If your product information changes, tell the team which facts changed so it can update the relevant work. Do not assume every existing draft is automatically rewritten.

Custom development within your subscription

Client-specific features, agent workflows and integrations are included within the agreed subscription scope. Describe the business problem and the desired result; the team logs the requirement manually and agrees what needs to be delivered.

The team typically develops and integrates an agreed change within 7–15 days. This is typical delivery, not a guaranteed deadline for every request. Agree the requirement, access needs and acceptance criteria before work starts. Inclusion does not mean unlimited development.

Custom development is provided while the subscription or contract is active. It stops when the contract ends; ongoing development or maintenance after termination is not implied.

Know what completion does and does not mean

Publication is a deliverable. Google indexing, appearance in an AI answer and citation of a particular URL are separate outcomes controlled by external systems. A subscription does not guarantee rankings, citations, leads or revenue.

Ask the team to report delivered work separately from observed results. A publication awaiting a later scan is not yet evidence that AI has cited it. An unsuccessful scan attempt is not a completed monitoring obligation.

Your scope checklist

Before work begins, confirm:

• The approved question set, included engines and completed-scan schedule.
• The number of content pieces and the intended channel for each.
• The standard publisher scope and any separately priced projects.
• Who supplies evidence, approves facts and approves publication.
• Your allocated contacts and the route for reporting problems.
• The requirements and acceptance criteria for custom work.
• What continues, stops or needs a separate agreement when the contract ends.

Keep these decisions in one maintained service agreement. If a request falls outside it, ask the team to confirm scope and cost before the work proceeds.