saas-agent-investor-narrative-on-sla

Use when producing or reviewing the saas agent investor narrative on sla component of a business plan; applies its specialist evidence, decisions, and acceptance tests instead of neighbouring pipeline skills.

Aller à l'installation

Dépôt: peterbamuhigire/business-plan-skills
Dernière activité de la source: 13 juillet 2026 à 14:11
Langue détectée de SKILL.md: anglais
Étoiles: 1
Forks: 1

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Retour à la recherche Retour à l’installation

name	saas-agent-investor-narrative-on-sla
description	Use when producing or reviewing the saas agent investor narrative on sla component of a business plan; applies its specialist evidence, decisions, and acceptance tests instead of neighbouring pipeline skills.
metadata	{"portable":true,"compatible_with":["claude-code","codex"]}

SaaS Agent Investor Narrative on SLA Skill

Overview

In 2025-2026 agent-investor diligence, SLA discipline has migrated from "operational footnote" to "investability gate." Agent-specialist funds (Madrona, Conviction, Greylock-AI, agent-focused early-stage at a16z / Bessemer / Sequoia AI), vertical AI funds, sovereign-AI envelopes and DFIs all now read SLA performance during DD. Bad SLA narrative loses rounds; good SLA narrative compresses diligence and supports premium multiple.

The narrative has two faces:

Confidence-builder — when SLA is measurable, published, audited, disclosed; credit ratio low; reserve methodology disciplined; dispute discipline strong. This narrative reads as "operational maturity at scale" and supports a +5 to +25% multiple overlay.
Liability question — when SLA performance is hidden, ad hoc reserves, undisclosed disputes, credit ratio drift, no third-party validation. This narrative gets read as "unpriced revenue volatility" and drives -10 to -40% discount or "pass with feedback."

Most early-stage agent founders default to the liability question because they have not built the discipline. The fix is structural: build the SLA discipline, then build the narrative.

This skill is the narrative discipline — how to talk about SLA in pitch deck, data room, investor updates, board calls, and Q&A. It does not replace the underlying SLA discipline (controls, reserves, telemetry) — it codifies how that discipline is communicated externally.

Diagnose the current narrative position — confidence-builder, neutral, or liability question. Use the dimension scorecard from references/saas-agent-sla-investor-narrative.md. Honest scoring; sceptical-investor lens.
Identify the gap — for each dimension where the score is below "investor-ready", note: is this a discipline gap (SLA discipline not built) or a communication gap (built but not communicated)? Treat these differently.
Build the headline narrative. Four standard openers, calibrated to score:
- Strong (3.5+): "Our published SLA performance over the last four quarters has held at {x}% uptime, {y}% DoD compliance, with SLA-credit accrual at {z}% of agent revenue against a disciplined reserve methodology audited by {firm}. SLA is part of our moat — we publish and we deliver."
- Improving (2.5-3.4): "Our SLA discipline is maturing. Last four quarters we moved from {prior} to {current} on uptime and from {prior} to {current} on credit ratio; reserve methodology now {auditor-reviewed / quarterly true-up} and we expect to publish by {date}."
- Building (1.5-2.4): "We have committed SLAs in {n} of {m} customer contracts; our internal SLA telemetry shows {x}% uptime; we have built the reserve methodology and will engage an auditor in {quarter}; we expect to publish externally in {quarter}."
- Weak (<1.5): Do not lead with SLA in the deck. Either rebuild discipline first, or position the round explicitly as use-of-proceeds for SLA discipline build.
Build the moat-thesis paragraph — if SLA is part of the moat (it usually is for vertical / regulated agents):
- SLA is moat-relevant because: customer switching cost includes re-establishing SLA history with a new vendor; auditor and regulator engagement raises the floor for new entrants; published performance creates an anchor that competitors must beat
- Cite specific examples: "{Enterprise customer X} renewed at {n}% expansion partly citing our SLA history" or "{Regulator Y} pre-cleared us partly on the basis of our SLA disclosure regime"
- Reconcile with saas-agent-moat-and-wrapper-risk so the moat narrative is consistent
Prepare the peer-benchmark slide / paragraph — investors compare. Use public agent-vendor SLA disclosures (where available), DFI / multilateral published expectations, and sector-regulator-published expectations. Where direct peer data is unavailable, benchmark against:
- Hyperscaler SLAs (AWS / Azure / GCP) for uptime
- Enterprise SaaS SLAs (Salesforce / ServiceNow / Workday) for incident-credit ratios
- BPO SLAs (Genpact / Concentrix / Teleperformance) for resolution time and quality
- Vertical regulator SLA expectations (FCA, OCC, SEC, FDA, CBK, CBN, SARB, FSCA, etc.)
Prepare the pitch-deck slide — one slide. Headline: SLA performance + reserve discipline. Body: 4-quarter trend chart (uptime / accuracy / credit ratio); reserve methodology one-liner; disclosure posture one-liner; one customer testimonial reference quote.
Prepare the data-room SLA section — populate per meta-due-diligence/references/saas-agent-sla-data-room-contents.md. Contents: SLA policy memo; published performance; reserve methodology + true-up history; refund-reserve methodology; dispute log + aging; audit-firm engagement letter; customer SLA contracts (redacted); regulator correspondence (where applicable); insurance certificates (where applicable).
Prepare the investor-update SLA block — quarterly. Per references/saas-agent-sla-investor-narrative.md template. Three sentences: performance vs commitment; credit accrual + reserve adequacy; forward signal (next quarter expected performance + any policy change).
Prepare FAQ rebuttals — for the standard sceptical-investor questions:
- "What if you have a catastrophic SLA breach?" — point to reserve adequacy + stress-tested scenarios + insurance (if any)
- "Are customers gaming the SLA?" — point to gaming-detection controls + dispute escalation
- "Is your reserve methodology audited?" — point to auditor engagement
- "What if foundation-model pricing makes your SLA-tier unviable?" — point to vendor-cost pass-through clauses and FX corridor
- "What if a regulator mandates a new SLA standard?" — point to regulator engagement + monitoring + repricing flexibility
- "Why are you publishing SLA?" — answer: because investors and enterprise customers reward operational maturity; non-disclosure now signals weakness
Wire to valuation overlay — the SLA narrative connects to meta-agent-valuation-overlay-for-sla which quantifies the multiple effect. Pitch-deck pre-money should be reasoned through the overlay.
Wire to bankability — the SLA bankability checklist (meta-bankability-scoring/references/saas-agent-sla-bankability-checklist.md) is the structured evidence backing the narrative. Investor DD will test the bankability dimensions; narrative should match.
Wire to the living plan — assign cadence per below.

Element	Cadence	Owner	Variance threshold
SLA-narrative score refresh	quarterly	CEO + CFO	-0.5 point quarterly
SLA pitch slide refresh	per round + quarterly	CEO + Head of GTM	performance-trend break
Investor-update SLA block	quarterly	CFO + CEO	missed quarter
Data-room SLA section refresh	quarterly + pre-round	CFO + Legal	DD opens
Peer-benchmark scan	quarterly	Head of Strategy	new public peer disclosure
FAQ rebuttal refresh	semi-annually + trigger	CFO + CEO + Legal	new sceptical question seen
Reserve-methodology disclosure refresh	quarterly	CFO + Auditor	true-up cadence
Audit-firm engagement status	quarterly	CFO + Board	status shift
Regulator-SLA-engagement comms	quarterly	Compliance + CEO	new consultation

DFI / multilateral lens — IFC, AfDB, FMO, BII, Proparco, FCDO, USAID, GIZ now read SLA performance in agent-product DD. SLA narrative for DFI rounds should explicitly cite the development outcome that the SLA defends (e.g. "SLA on agri-advisory accuracy underpins farmer-income claim").
Sovereign-AI procurement lens — KE Huduma, NG NIMC, RW Irembo, UG NITA-U, ZA Home Affairs and sector regulators (CBK, CMA, CBN, SEC, SARB, FSCA, BoU, CMA-UG, NDPC) increasingly include SLA schedules in tenders; investor narrative should cite the sovereign anchor as SLA-discipline evidence.
African insurer scrutiny — African insurers (Britam, Sanlam, Old Mutual, Jubilee, ICEA Lion, Liberty, NIC, Heritage, Madison) vetting agent vendors look for SLA evidence; cite where an insurer has placed cover or named the vendor.
Peer benchmarking is thin — published African agent SLA peer data is scarce; benchmark against global agent vendors plus African hyperscale (AWS af-south-1, Azure ZA, GCP africa-south1) plus African BPO majors (CCI Global, iSON Xperiences, Genesys SA, Africa's Talking voice infra).
FX-corridor in SLA narrative — when local-currency revenue meets USD costs, the SLA narrative must reconcile FX-corridor clauses and reserve-currency choice; investors test this.
Reserve currency disclosure — local-currency reserves vs USD-cost exposure; disclose the choice and the FX hedge (if any).
Mobile-money settlement reliability — for per-resolution agents settling through MoMo / M-Pesa / Airtel Money / Wave / Orange Money / OPay, settlement-failure rate is part of SLA performance; disclose.
Local audit firm coverage — where Big-4 unavailable, mid-tier (BDO, Grant Thornton, Mazars, RSM, PKF, Crowe, Baker Tilly) plus auditor-acceptable reserve methodology can still earn a confidence-builder narrative.
Public-sector reference value — strong SLA performance on public-sector contracts (Huduma, NIMC, Irembo, NITA-U, Home Affairs analogues) is reference-grade for institutional investors; cite explicitly with consent.
Cross-border listing pathways — JSE / NSE / NGX / EGX listings increasingly require SLA disclosure for tech issuers; narrative should anticipate listing-doc requirements where exit-via-listing is on the table.

Input artefact	Source/provider	Required	Behaviour when absent
Reconciled funding need, use-of-funds schedule, financing capacity, traction evidence, milestones, and investor or lender criteria for saas agent investor narrative on sla	Financial model, implementation plan, client records, and target-financier materials	Yes	If absent, the funding gap, uses, repayment capacity, dilution effect, or stage evidence is unavailable, return a financing-readiness gap note and withhold the amount or instrument recommendation.
Finalised business brief, target reader, country, and stage	Client intake and engagement owner	Yes	Stop section decisions and route the missing context to client intake.
Reconciled upstream assumptions that this section consumes	Named pipeline owners	Conditional	Record the dependency, affected claim, owner, and recovery step; do not substitute an invented value.

Artefact	Consumer	Observable acceptance condition
Investor SLA narrative linking service evidence, credits, reserves, trust controls, downside, and valuation implications	Plan author and target decision-maker	The artefact answers the section decision and traces each material conclusion to the supplied evidence.
saas agent investor narrative on sla exception and handoff note	Downstream section owners	Every blocked or conditional item names its consequence, owner, evidence request, and restart condition.
saas agent investor narrative on sla release record	Reviewer or plan assembler	Records the checks completed, failures, unassessed items, professional review required, and release state.

Evidence	Format	Acceptance condition
Ask-to-use reconciliation, financing-option decision record, milestone release logic, and caveat register	Source-linked table, calculation, or annotated prose	The evidence is reproducible from named inputs and distinguishes verified fact, management assumption, and inference.
saas agent investor narrative on sla decision record	Decision note	States the selected action, rejected credible alternative, countercase, rationale, and risk accepted or avoided.
saas agent investor narrative on sla review trace	Gate entry	Identifies the date, input versions, reviewer role, failed checks, recovery owner, and any check that remains not assessed.

Choice or condition	Action	Failure or risk avoided
For saas agent investor narrative on sla, the preferred instrument does not match cash-flow capacity, stage, security, or investor-return evidence	reject it, compare the viable alternatives, and state the milestone needed to reopen the option	A mismatched ask can create unaffordable debt, avoidable dilution, or failed diligence
For saas agent investor narrative on sla, A current legal, regulatory, tax, accounting, market, or platform claim controls the saas agent investor narrative on sla decision	Verify the controlling source, effective date, jurisdiction, and reviewer status before release	Stale external facts become permanent plan assumptions
For saas agent investor narrative on sla, The evidence reconciles with neighbouring sections and the countercase does not overturn the choice	Complete investor sla narrative linking service evidence, credits, reserves, trust controls, downside, and valuation implications, attach the evidence and release record, and hand off named dependencies	Premature release and repeated downstream rework