# SaaS integration page brief

Blank brief and fictional integration example

Use the blank brief to document one supported product pair, then inspect the fictional connection and its before-and-after rewrite. Replace the example details with verified facts before sharing. This manual file does not connect products, install a connector or approve publication.

Pack version 1.0 · 16 September 2026. Brief version 1.0.

Guide: https://rankecho.io/resources/fix/integration-page

## Part 1 — Brief and fictional filled example

Copy this for one supported product pair. Replace every bracketed field from product, engineering, security, pricing, partner, and support owners before publication.

# SaaS integration-page brief

Version 1.0 — manual planning brief

## Page control
- Product pair [required]:
- Canonical URL and publisher [required]:
- Support status and governing source [required]:
- Fact owner, checked date, and refresh triggers [required]:
- Primary buyer, use case, and qualification boundary [required]:

## Connection contract
- Method [native / partner or iPaaS / custom API / manual file]:
- Builder, operator, and support owner:
- Required accounts, plans, add-ons, and separately charged services:
- Installation surface and setup CTA:
- Authentication and required roles or permissions:
- Source objects and eligible states:
- Trigger or schedule:
- Direction [A to B / B to A / two-way by object]:
- Destination objects or actions:
- Create, update, delete, duplicate, and retry behavior:
- Real-time, scheduled, or manual cadence:
- Field mapping, filters, volume, region, or version limits:
- Historical backfill and attachment behavior:
- Data visibility or security boundary:
- Failure notice, recovery step, and escalation route:
- Explicit unsupported workflows:

## Page plan
1. Opening answer: pair, method, direction, best fit, and main limit.
2. What connects: exact object, field, trigger, direction, and cadence table.
3. Requirements: accounts, plans, cost or quote path, roles, and permissions.
4. Limits: excluded data, updates, deletions, backfill, volume, region, and failure handling.
5. Setup and support: prerequisites, ordered steps, validation, owner by issue, and one accurate CTA.

## Owner QA before publishing
- Confirm the connection in current governing documentation or a recorded scoped test.
- Have the responsible product, security, pricing, partner, and support owners verify facts.
- Replace broad claims such as “seamless two-way sync” with object-level direction and limits.
- Check visible title, H1, canonical, indexability, descriptive internal links, structured-data agreement, setup links, and mobile rendering.
- Record completed checks, unresolved facts, approver, and next review date.

## Measurement plan
- Discovery: eligible query impressions and clicks; separately identified AI-referral sessions.
- Actions: brief copy, setup open, install start, contact, trial, and completed setup where observable.
- Proposed event names only: integration_brief_copy, integration_setup_open, integration_install_start, integration_contact, trial_start.
- Keep query, session, event, account, and customer denominators separate. Preserve unattributed traffic; avoid causal claims.

## Filled fictional example: ClearDesk + LedgerLane
- Fictional status: supported, partner-built connection listed by ClearDesk; no account test was performed.
- Buyer job: export newly approved ClearDesk invoices into LedgerLane for bookkeeping.
- Method and direction: partner-operated, one-way ClearDesk → LedgerLane.
- Trigger and cadence: approved invoices queue for a daily 02:00 UTC export; this is not real-time.
- Objects: invoice and customer IDs, dates, currency, lines, subtotal, tax, and total create one LedgerLane invoice.
- Required fictional access: ClearDesk Growth or Enterprise, LedgerLane Business, a ClearDesk admin, and a LedgerLane billing admin. Partner service pricing is quote-based.
- Limits: no attachments, deletion propagation, later field updates, historical backfill, or LedgerLane-to-ClearDesk writeback.
- Permissions: the listed fields reach the partner and LedgerLane under their fictional access terms; the buyer must review them.
- Support: partner handles installation and authentication; ClearDesk owns source-field eligibility; LedgerLane owns destination validation errors.
- CTA: Open setup guide. Validate one non-production invoice before enabling the daily schedule.
- Opening answer: “ClearDesk connects to LedgerLane through a partner-built, one-way daily export of newly approved invoices. It requires the stated plans and admin roles; it does not sync attachments, deletions, later changes, historical invoices, or LedgerLane data back to ClearDesk.”

Manual brief with a fictional example. Verify the live pair, commercial terms, permissions, limits, and support route before publication.

## Part 2 — Before and after rewrite

### What does a precise integration answer look like?

Fictional before: “Connect ClearDesk and LedgerLane for seamless two-way sync. Keep all invoice data current automatically in real time.” That copy overstates the fictional product because the supported workflow is a partner-operated daily export in one direction.

Fictional after: “ClearDesk connects to LedgerLane through a partner-built, one-way daily export of newly approved invoices. ClearDesk Growth or Enterprise and LedgerLane Business are required. The export does not include attachments, deletions, later updates, historical backfill, or LedgerLane-to-ClearDesk changes. Review permissions, then validate one non-production invoice in the setup guide.”

The revision exposes the mechanism, direction, cadence, plan gates, limits, and next step. ClearDesk and LedgerLane are invented; this is not a real integration, customer result, ranking observation, or account test.

## Use this pack

1. Save a copy for one supported product pair and complete the blank fields from their governing sources.
2. Use the fictional pair and rewrite to check direction, cadence, plans, permissions, limits and support ownership. Replace all invented details before applying them to a real offer.
3. Keep unresolved facts visible and complete owner QA before publication. The proposed measurement events require separate instrumentation.

Next workflow: [Evaluate the Fix Engine](https://rankecho.io/product/fix-engine). Inspect a [sample fix](https://rankecho.io/sample-fix) first. Full-page writing or refreshing is a separate [content add-on](https://rankecho.io/pricing/content), not included with the visibility subscription.