{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aproject-management-specialists-lessons-learned-facilitation%3At-ais-low-tech%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aproject-management-specialists-lessons-learned-facilitation%3At-ais-low-tech%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Aproject-management-specialists-lessons-learned-facilitation%3At-ais-low-tech%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:project-management-specialists-lessons-learned-facilitation:t-ais-low-tech:v1","lens":"AIService","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":1,"C7_magicLensFit":1,"C4_competitorHonesty":1,"C6_crossSlotCoherence":1,"C1_customerSpecificity":1,"C2_problemFrictionRealism":1,"C9_killCriteriaAttestability":1,"C3_approachEngineCoverability":1,"C5_differentiationLoservilleEscape":1},"upperRightLoserville":true},"cellRef":{"id":"work-contexts.org.ai/project-management-specialists-lessons-learned-facilitation","stableHash":"wcc:project-management-specialists:lessons-learned-facilitation:document:v1"},"problem":{"slotStatement":"Each project close-out retro costs the agency ~$420 (3 hrs of a $140/hr delivery lead facilitating + writing up notes into Notion), and 7 of every 10 retros produce a doc nobody reads on the next kickoff — so the same incomplete-handoff pattern (ambiguous acceptance criteria, missing creds, half-documented infra) causes an average of 11 rework hours on the very next engagement, billed at cost against a fixed fee."},"approach":{"oneSentence":"Pay-per-retro API + a 40-line CLI: POST your Jira/Linear project ID and Slack channel export, get back a structured lessons-learned JSON (root-cause tagged, linked to the exact ticket/message that evidenced it) plus a kickoff-checklist diff against your next project — $0.35 per retro processed, free for your first 25, no seat fees, no sales call, paste an API key and run."},"customer":{"icpShape":"Founder or technical partner at a bootstrap digital/dev agency (company-type-bootstrap-agency, 8–40 FTEs) running 6–20 concurrent client projects in Jira/Linear/Asana, where the buyer is the Agency Managing Partner (signs the Stripe card, owns margin) and the daily user is the senior delivery lead / tech lead who runs retros and closes out projects.","beachheadShape":"EarlyAdopterJTBD: bootstrap agencies closing out fixed-fee engagements where the same scoping miss keeps recurring across projects because nobody has time to mine prior retros."},"archetype":"startup-archetypes.org.ai/AIService-Subscription","beachhead":"EarlyAdopterJTBD: bootstrap agencies closing out fixed-fee engagements where the same scoping miss keeps recurring across projects because nobody has time to mine prior retros.","competitors":{"substitutes":[{"name":"The Python script + OpenAI call the tech lead would otherwise write over a weekend","category":"manual-bridge","uncopyabilityReason":"Not a product — but this is the real alternative; the wedge is that maintaining the Jira/Slack/Linear export plumbing and the root-cause taxonomy stops being fun by month two."},{"name":"The agency's inherited 'Lessons Learned.xlsx' on Google Drive, maintained by whichever PM has been there longest","category":"informal"},{"name":"Retrium","category":"incumbent","uncopyabilityReason":"Retrium is a seat-priced facilitated-retro SaaS ($39/user/month) sold to in-house agile coaches; shifting to a $0.35/event self-serve API would cannibalize its seat-license revenue model and collapse its sales-led motion — a distribution-channel barrier, not a technical one."},{"name":"Atlassian Intelligence / Jira AI summaries","category":"AI-native horizontal","uncopyabilityReason":"Atlassian's summaries run inside a single Jira instance and cannot cross-reference Slack threads, Linear issues, or Git commits that actually carry the handoff-loss evidence at a multi-tool agency — the integration-depth barrier is that Atlassian will not index competitor issue trackers, which every bootstrap agency's client portfolio forces them to use."},{"name":"Parabol","category":"incumbent","uncopyabilityReason":"Parabol's product surface is a human-facilitated retro meeting tool with a freemium seat model; converting to an unattended per-event API would require rebuilding around project-data ingestion rather than meeting facilitation — a deployment-mode mismatch between synchronous meeting UX and async batch API."}]},"studioThesis":"T-AIS-LOW-TECH","killThreshold":{"K":8,"M":50,"N":7,"rubricItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C7_magicLensFit","C8_lensFit","C9_killCriteriaAttestability"],"verdictPolicy":"all-load-bearing-pass-and-overall-ge-X","loadBearingItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C9_killCriteriaAttestability"],"verdictPolicyVerbatim":"KILL unless every load-bearing rubric item passes per workbook AND overall pass-rate ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Setup friction (schedule a demo + seat rollout ↔ paste API key, curl one endpoint, billed per retro)","yAxis":"Cross-tool handoff evidence (single-tool summary only ↔ joins Jira + Linear + Slack + Git to pinpoint the exact missed handoff)","winningQuadrant":"Self-serve per-event API that cross-joins the agency's actual toolchain (Jira ticket #, Slack message ts, commit SHA) to name the specific handoff that caused rework on the next project","loservilleEscape":true,"loservilleQuadrant":"Seat-licensed single-tool retro apps like Retrium/Parabol that require the delivery lead to manually paste context from Slack and Git into a facilitated meeting board, then produce a Notion doc disconnected from the next kickoff"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Aproject-management-specialists-lessons-learned-facilitation%3At-ais-low-tech%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Aproject-management-specialists-lessons-learned-facilitation%3At-ais-low-tech%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Aproject-management-specialists-lessons-learned-facilitation%3At-ais-low-tech%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/project-management-specialists-lessons-learned-facilitation","thesis":"https://api.sb/v1/theses/T-AIS-LOW-TECH"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575aecbd7c90ce","edgeLocation":"a0575aecbd7c90ce","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aproject-management-specialists-lessons-learned-facilitation%3At-ais-low-tech%3Av1/references"},"items":[]}}