Offer Catalog (Notion): 3‑Tier Portfolio + 2 Add‑Ons + Red Scope Gate

Keep this high‑level index at the top of your Notion page so you and clients can scan caps, SLAs, and add‑ons at a glance.

• Starter — [STARTER_NAME] — caps: 1 workflow • single channel • up to 500 interactions/mo • 2 KB sources • 2‑week support • Email 48h
• Pro — [PRO_NAME] — caps: up to 3 workflows • multi‑channel • up to 2,000 interactions/mo • up to 10 KB sources • 4‑week support • Priority 4h
• Enterprise/Custom — [ENTERPRISE_NAME] — scope by quote • custom SLAs • 60‑day hypercare • Optional 24/7 1h + 99.9% uptime (hosting only)
• Add‑Ons — Additional Workflow (+1) • Priority Response SLA (upgrade)

Name: [STARTER_NAME] (example: "Assistant Quickstart")

Who it’s for:

• New clients validating one use case or one team, predictable scope, limited integrations.

Outcome:

• Ship [ONE_PRIMARY_OUTCOME] in [DAYS_TO_DELIVER] days and hand over with a 2‑week warranty/support window.

Scope caps (hard limits):

• Workflows/Processes: 1
• Channels: 1 (choose one: chat | email | web form)
• Interactions: up to 500/mo (if hosted agents)
• Knowledge base sources: up to 2
• Integrations: native connectors only; no custom API code
• Concurrency: 1 active task at a time (queue‑based)

Deliverables:

• Configured workflow/agent + [BASIC_DASHBOARD_OR_LOGS]
• Acceptance criteria: [STARTER_ACCEPTANCE_CRITERIA]

Support & SLA (toggle one):

• Standard 48‑hour email support within [BUSINESS_HOURS] [TIMEZONE]

Post‑launch support window:

• 2 weeks for break/fix on shipped scope (no net‑new features)

Pricing (example defaults — edit):

• Setup: $[STARTER_SETUP_FEE] one‑time
• Monthly (if hosting/run): $[STARTER_MONTHLY_FEE]

Assumptions:

• Client provides access to [SYSTEMS] and [DATA_SOURCES] before kickoff.
• No uptime guarantees (we do not host runtime at Starter).

Exclusions:

• Custom API builds • multi‑system orchestration • real‑time on‑call • regulated data handling

Name: [PRO_NAME] (example: "Assistant + Automations Pro")

Who it’s for:

• Teams with 2–3 connected workflows and multi‑channel delivery, needing iteration and light hosting.

Outcome:

• Launch [UP_TO_3_OUTCOMES] with weekly iteration and measurement.

Scope caps (hard limits):

• Workflows/Processes: up to 3
• Channels: multi‑channel (pick any 2: chat, email, SMS, voice, web form)
• Interactions: up to 2,000/mo (if hosted agents)
• Knowledge base sources: up to 10
• Integrations: native or light custom (no net‑new APIs; auth + mapping only)
• Concurrency: 2 active tasks at a time

Deliverables:

• Hosted workflow/agent(s) + dashboards (latency, cost/run, conversions)
• Weekly iteration slot and rollback plan
• Acceptance criteria: [PRO_ACCEPTANCE_CRITERIA]

Support & SLA (toggle one):

• Priority 4‑hour response during [BUSINESS_HOURS] [TIMEZONE] via [PRIORITY_CHANNEL]

Post‑launch support window:

• 4 weeks for break/fix on shipped scope

Pricing (example defaults — edit):

• Setup: $[PRO_SETUP_FEE] one‑time
• Monthly (hosting/iteration): $[PRO_MONTHLY_FEE]

Assumptions:

• We host runtime for the covered workflows in our stack; no uptime guarantees beyond response/restore SLOs.

Exclusions:

• Cross‑org SSO, HA/DR architecture, on‑prem/VPC, broad data labeling projects

Name: [ENTERPRISE_NAME] (example: "Critical Ops — Custom/Enterprise")

When to use:

• Red‑flag scope (see Scope Gate) or mission‑critical workloads that require custom SLAs, HA/DR, or regulated data.

Outcome:

• Define a custom scope with firm SLO/SLA targets and a 60‑day hypercare plan.

Scope (defined per project):

• Workflows/Processes: [NUMBER_OR_RANGE]
• Channels: [CHANNELS]
• Interactions: [INTERACTION_CAP]
• Sources: [KB_SOURCES]
• Integrations: custom APIs, multi‑system orchestration, data pipelines

Support & SLA (toggle one):

• 1‑hour response, 24/7 via [EMERGENCY_CHANNEL]
• Optional uptime: 99.9% (only if we host the runtime end‑to‑end with observability)
• Restore targets: [RTO]/[RPO]

Post‑launch support window:

• 60‑day hypercare for break/fix on shipped scope

Pricing (example framing — edit):

• Discovery & architecture: $[DISCOVERY_FEE]
• Build: $[BUILD_FEE_RANGE]
• Run (monthly): $[RUN_MONTHLY_FEE] + on‑call $[ONCALL_FEE] (if selected)

Assumptions:

• Logging, monitoring, and paging are instrumented before SLAs commence.

Exclusions:

• "Unlimited requests" • undefined success criteria • vendor uptime guarantees we do not control

Use these two add‑ons to absorb legitimate expansion without reopening base scope.

A. Additional Workflow (+1)

• What it adds: one additional workflow/process to any tier
• Dependencies: must fit existing stack and channels
• Price: $[ADDITIONAL_WORKFLOW_PRICE] one‑time setup (+$[ADDITIONAL_WORKFLOW_MONTHLY] monthly if hosted)
• Delivery time impact: +[DAYS_TO_DELIVER_ADDON] business days
• Acceptance criteria: [ADDON_WORKFLOW_ACCEPTANCE]

B. Priority Response SLA (upgrade)

• What it adds: upgrades support to the next SLA block
• Options (pick one):
  • 4‑hour business‑hours response via [CHANNEL] — $[PRIORITY_SLA_4H_PRICE]/mo
  • 1‑hour 24/7 response via [CHANNEL] — $[PRIORITY_SLA_1H_PRICE]/mo (requires on‑call rotation)
• Start date: begins after monitoring + paging test
• Not included: uptime guarantees unless Enterprise hosting is selected

Paste these blocks into Notion toggles and switch ON exactly one per tier.

Block 1 — Standard Support (48h)

• Channel: Email [SUPPORT_EMAIL]
• Hours: [BUSINESS_HOURS] [TIMEZONE]
• First response time: within 48 business hours
• Scope: break/fix on shipped features; no new feature requests

Block 2 — Priority Support (4h)

• Channel: [SLACK_OR_TEAMS] + Email
• Hours: [BUSINESS_HOURS] [TIMEZONE]
• First response time: within 4 business hours
• Escalation: next‑business‑day incident review

Block 3 — Emergency (1h, 24/7)

• Channel: [PAGER_CHANNEL] (primary), [SLACK_OR_TEAMS] (secondary)
• First response time: within 1 hour, 24/7
• Restore SLO: service restored or workaround within [RESTORE_TARGET]
• Uptime: only commit if we host runtime; otherwise state response/restore SLOs only

Yellow = negotiable with add‑ons or Pro. Red = requires Enterprise/Custom. Use this to qualify in minutes.

Yellow Flags (often solved by add‑ons):

• +1 workflow beyond tier cap
• +1 channel (e.g., add SMS to chat)
• • KB sources beyond cap (e.g., 10 → 15)
• Light custom mapping to an existing API connector
• Real‑time alerts/monitoring for shipped scope

Red Scope Gate (triggers Enterprise/Custom):

• Multi‑system orchestration across ≥ 3 core systems
• Net‑new custom API development or vendor without SDK/docs
• 24/7 on‑call without observability or paging in place
• Uptime guarantees when we don’t host the runtime
• Regulated data (HIPAA/PCI/FERPA) or on‑prem/VPC requirement
• "Unlimited tasks/requests" or undefined success criteria
• Concurrent work > [WIP_LIMIT] active tasks

Always excluded from all tiers unless explicitly added to a Custom SOW:

• Copywriting beyond workflow prompts and system messages
• Manual data entry or call center staffing
• Security audits, pen tests, or compliance certifications
• Broad data labeling/annotation projects
• Native mobile app development
• Migration of legacy systems outside the agreed scope
• Vendor uptime guarantees we do not control

Clarify ownership and handover to avoid surprises.

• Source code & configs: [OWNERSHIP_POLICY] (example: "Client owns deliverables; studio retains internal libraries and templates.")
• Access & accounts: production accounts are in Client tenancy by [CUTOVER_DATE]
• Documentation: admin runbook + rollback plan delivered by [DOCS_DATE]
• Warranty: break/fix only within the support window (2w/4w/60d per tier)
• Change requests: anything beyond acceptance criteria is a new add‑on or SOW

Quick math you can do on a call. Edit the example anchors.

Example price anchors (edit):

• Starter: Setup $[STARTER_SETUP_FEE] + $[STARTER_MONTHLY_FEE]/mo (if hosted)
• Pro: Setup $[PRO_SETUP_FEE] + $[PRO_MONTHLY_FEE]/mo (hosting + weekly iteration)
• Enterprise: Discovery $[DISCOVERY_FEE] → Build $[BUILD_FEE_RANGE] → Run $[RUN_MONTHLY_FEE]/mo (+ on‑call if selected)
• Add‑Ons: +$[ADDITIONAL_WORKFLOW_PRICE] per workflow, +$[PRIORITY_SLA_4H_PRICE]/mo (4h) or +$[PRIORITY_SLA_1H_PRICE]/mo (1h 24/7)

Estimator (fill the placeholders and compute):

• First‑month total = Setup + Monthly + Recurring Add‑Ons + One‑time Add‑Ons
• Ongoing monthly = Monthly + Recurring Add‑Ons

Guardrails:

• Do not waive caps. Sell add‑ons instead.
• Tie volatile spend to usage caps (interactions, channels, KB sources).

Copy this block into a new Notion page, fill the brackets, and paste to your website or PDF proposal.

Heading: [SERVICE_NAME] — [TIER_NAME]

Proof chips:

• Caps: [CAPS_CHIP] (e.g., "1 workflow • 1 channel • 500 interactions/mo")
• SLA: [SLA_CHIP] (e.g., "48h email" or "4h priority" or "1h 24/7")
• Support Window: [SUPPORT_WINDOW_CHIP] (e.g., "2‑week warranty")

Outcome (1 sentence):

• We deliver [PRIMARY_OUTCOME] in [DAYS_TO_DELIVER] days with [RESULT_METRIC].

What’s included:

• [INCLUDED_1]
• [INCLUDED_2]
• [INCLUDED_3]

What’s not included:

• [TOP_EXCLUSION_1] • [TOP_EXCLUSION_2] (see full catalog for scope)

Price:

• Setup $[SETUP_FEE] + $[MONTHLY_FEE]/mo (if hosted)

Stack:

• [STACK_TOOLS]

CTA:

• Button: [CTA_LABEL] → [CTA_LINK]

Use this 5‑step sequence on every lead.

1. Qualify with Scope Gate:

• If any Red flag → move to Enterprise/Custom track.
• If only Yellow flags → keep tier, attach add‑ons.

2. Pick the tier:

• Map to Starter/Pro caps. Write [TIER_NAME] at the top of notes.

3. Select one SLA block:

• 48h (Starter), 4h (Pro), or 1h 24/7 (Enterprise or SLA add‑on).

4. Price on the call:

• Base Setup + Monthly + selected add‑ons. Say the number, then recap caps.

5. Send the Service Card:

• Paste the generated card, add [START_DATE], and include the acceptance criteria.

Track changes so you can roll back decisions and show versioned promises to clients.

• v[VERSION] — [DATE]: [WHAT_CHANGED] (e.g., raised Pro interaction cap from 1,500 → 2,000)
• v[PREV_VERSION] — [DATE]: [WHAT_CHANGED]

Notes:

• Update the Service Card chips whenever caps or SLAs change.

Use these defaults unless you have full hosting and monitoring.

• If you do not host runtime: promise response/restore SLOs, not uptime.
• Business hours: [BUSINESS_HOURS] [TIMEZONE] (e.g., 9–5 CT, Mon–Fri)
• Communication channels per tier:
  • Starter: Email [SUPPORT_EMAIL]
  • Pro: Email + [SLACK_OR_TEAMS]
  • Enterprise: Email + [SLACK_OR_TEAMS] + [PAGER_CHANNEL]
• Concurrency (WIP limits): Starter 1 • Pro 2 • Enterprise [WIP_LIMIT]
• Post‑launch support windows: 2w (Starter) • 4w (Pro) • 60d (Enterprise)
• Observability (for SLAs): error rates, latency, cost/run, interactions/mo