You are running a deep buyer intelligence extraction pipeline for Next Chapter M&A Advisory. Your mission: build a "know them better than they know themselves" dossier for SAP SuccessFactors as a potential acquirer of HR.com. This is a TEST RUN on one company. If it works, we run all 63.
A dossier so detailed that when Ewing Gillaspy cold-calls SAP's VP of Product Growth Strategy, he can say: "Josh, in your Q3 2025 earnings call, Christian Klein said [exact quote]. HR.com's 1.92M member community solves that exact problem. Here's how." Not summaries. Not vibes. Exact quotes, exact dates, exact sources.
How does SAP sell SuccessFactors? Direct enterprise sales? Channel/partner? What's the primary revenue model (subscription, licensing, services)? What's the ACV range? Who is the ICP (company size, industry, buyer persona)? What is their market position — leader, challenger, niche — in what specific HCM segment?
What are SAP's publicly stated challenges? Search earnings calls for language like "headwinds," "competitive pressure," "churn," "engagement," "retention." These are the pain points HR.com's assets can address. Extract:
- Publicly stated challenges (array)
- Exact earnings call phrases that signal pain (array)
- Competitive pressures — who is threatening them and how
- Growth constraints — what limits their growth (audience reach, content, data, community)
What has Christian Klein said on record about where SAP is going in 2-3 years? Search:
- Earnings call transcripts
- SAP Sapphire keynotes
- Podcast interviews
- Investor day presentations
- Blog posts and authored content
Extract: CEO's stated 2-3 year direction, 3-5 named strategic priorities, investment themes, and the overarching transformation narrative.
For EVERY acquisition SAP has made since 2021:
- Target company name
- Deal value (or "undisclosed")
- Date (YYYY-MM-DD)
- Stated rationale (exact quote from press release)
- Outcome — did they integrate it? Did they write it down? Did the CEO reference it in subsequent earnings calls? Did analysts love it or pan it?
- Source URL
Then characterize the M&A pattern: bolt-on content? Platform rollups? Audience aggregation? Tech tuck-ins? What's the appetite: active/selective/dormant?
SAP files 20-F (annual) and 6-K (interim) with SEC. CIK: 0001000184.
Retrieve from EDGAR (https://efts.sec.gov/LATEST/):
- Every 20-F annual report for fiscal years 2021-2025
- Every 6-K filing for the last 3 years
- Any filings related to acquisitions (F-4, etc.)
From each filing, extract:
- Revenue figures and growth rates (total SAP and SuccessFactors/HCM segment separately)
- HCM segment performance: customer count, cloud ARR, growth rate
- Strategic priorities from MD&A — exact language about "community," "ecosystem," "platform," "audience," "engagement," "HR," "workforce," "talent"
- Risk factors mentioning competitive threats in HR/HCM
- M&A language — capital allocation, acquisition pipeline mentions, stated intent
- Cash position and available credit facilities
- Any mention of content, media, professional development, or community platforms
Find at least 10 direct, VERBATIM quotes from SAP leadership. Never paraphrase. Sources to search:
Earnings call transcripts (all 12 quarterly calls from 2023-2025):
- "SAP earnings call transcript Q1 2025"
- "SAP earnings call transcript Q2 2025"
- "SAP earnings call transcript Q3 2025"
- "SAP earnings call transcript Q4 2025"
- (repeat for all 4 quarters of 2024 and 2023)
Leadership interviews and presentations:
- "Christian Klein interview podcast"
- "Christian Klein keynote speech SAP Sapphire"
- "Christian Klein blog post"
- "SAP SuccessFactors leader interview"
- "Josh Gosliner SAP" (VP Product Growth Strategy — the cold call target)
- "Dominik Asam SAP capital allocation M&A"
- "SAP SuccessFactors analyst day presentation"
- "Christian Klein SAP investor day transcript"
For each quote, record this exact JSON structure:
{
"speaker": "Full name",
"title": "Title at SAP",
"quote": "EXACT verbatim quote — do NOT paraphrase",
"source_url": "URL where this was published or transcript located",
"date": "YYYY-MM-DD",
"context": "Earnings call Q3 2025 / Sapphire keynote / Forbes interview / etc.",
"relevance_to_hrcom": "Which specific HR.com asset this quote connects to and why"
}
For each acquisition found in #4, find:
- The original press release (URL)
- Subsequent analyst/media coverage — did they overpay? Did analysts love it? Did competitors react?
- Analyst ratings: firm name, analyst name, rating (Buy/Hold/Sell), price target, any commentary about M&A strategy
- Relevant press releases about partnerships, strategic moves, or competitive positioning
Using ALL evidence from steps 1-7, write:
THE STRATEGIC LOGIC (2-3 sentences): Why SAP needs what HR.com has, using SAP's OWN WORDS from the quotes you found.
THE ASSET MAP (1 paragraph): Which specific HR.com assets solve which specific SAP challenges. Every claim must reference evidence from steps 1-7.
BUSINESS MODEL INTEGRATION (2-3 paragraphs): Exactly how SAP would deploy each HR.com asset inside their existing products. Name SAP's actual products: SuccessFactors Employee Central, SuccessFactors Learning, SuccessFactors Recruiting, SAP BTP, SAP Store, SAP Community Network, SuccessFactors Workforce Analytics. Explain the revenue mechanism for each asset deployment. Example level of specificity:
"SAP sells HCM to large enterprise customers. HR.com is the ultimate community to embed within SAP SuccessFactors. If the community alone is worth staying within, you get unlimited shots on goal to provide value ahead of selling them your solution. SAP could white-label MyPeople.ai across all SuccessFactors customers, creating a locked-in professional development layer that competitors cannot replicate. The 4,000+ Accredited Webcasts feed into SuccessFactors Learning as a proprietary CPE-eligible content library, replacing dependency on Skillsoft and LinkedIn Learning with owned IP."
COMPETITIVE BLOCK (1-2 sentences): What happens if Workday or Oracle acquires HR.com instead of SAP. What strategic option does SAP lose?
COLD CALL OPENER: One sentence for Josh Gosliner's ear in the first 10 seconds. Must reference a specific quote or challenge from the evidence.
EMAIL HOOK: One sentence opening a cold email to Christian Klein. Specific enough he thinks "this person understands our business."
FIT SCORE: 1-100 with evidence-based rationale using this rubric:
- 80-100: Multiple HR.com assets directly solve stated challenges. Acquisition pattern consistent. Leadership quotes practically describe needing HR.com.
- 60-79: At least 2 assets address needs. Strategic direction aligns. Some M&A appetite evidence.
- 40-59: General alignment but limited direct evidence.
- 20-39: Tangential connection only.
- 1-19: No meaningful alignment.
Do NOT use a single LLM for any analysis step. Use this exact architecture:
Exa.ai (web search) → raw research materials
↓
EDGAR API (SEC filings) → raw filing text
↓
┌─────────────────────────────────────────┐
│ DUAL RESEARCH (run in parallel) │
│ DeepSeek (researcher_1) analyzes data │
│ Mistral (researcher_2) analyzes data │
│ Both extract the same 8 categories │
└──────────────┬──────────────────────────┘
↓
┌─────────────────────────────────────────┐
│ INSPECTION (Groq — inspector_1) │
│ Merges researcher_1 + researcher_2 │
│ Identifies contradictions │
│ Flags disagreements with both sources │
└──────────────┬──────────────────────────┘
↓
┌─────────────────────────────────────────┐
│ CERTIFICATION (inspector_2) │
│ Try: Claude Code CLI (claude -p) │
│ If fails: DUAL FALLBACK │
│ → Run BOTH OpenAI AND DeepSeek │
│ → Cross-check their outputs │
│ → Use best result, flag differences │
│ Certifies all data fields │
│ Extracts final structured fields │
└──────────────┬──────────────────────────┘
↓
┌─────────────────────────────────────────┐
│ SYNTHESIS (synthesizer) │
│ Try: Claude Code CLI (claude -p) │
│ If fails: DUAL FALLBACK (same as above)│
│ Writes final narrative + scoring │
└─────────────────────────────────────────┘
If any two agents disagree on a FACT (revenue figure, quote attribution, deal value, date), include BOTH versions with their sources and FLAG the discrepancy. Do not silently pick one.
[KEY MANAGED VIA DOPPLER][KEY MANAGED VIA DOPPLER] (base: https://api.deepseek.com/v1, model: deepseek-chat)[KEY MANAGED VIA DOPPLER] (base: https://api.mistral.ai/v1, model: mistral-small-latest)[KEY MANAGED VIA DOPPLER] (base: https://api.groq.com/openai/v1, model: llama-3.3-70b-versatile)[KEY MANAGED VIA DOPPLER] (base: https://api.openai.com/v1, model: gpt-4o-mini)All providers use OpenAI-compatible API format except Claude CLI (subprocess).
rdnnhxhohwjucvjwbwch (and-call-command) — DECOMMISSIONED 2026-04-22. Data archived to dwrnfpjcvydhmhnvyzov in *_archive_2026_04_22 tables.https://rdnnhxhohwjucvjwbwch.supabase.co (dead — do not connect)$SUPABASE_SERVICE_ROLE_KEY env var for NEW instance.dwrnfpjcvydhmhnvyzov (Next Chapter OS DB) — use $SUPABASE_URL from ~/.zshrc⚠️ BOTH OLD URLS (asavljgcnresdnadblse and rdnnhxhohwjucvjwbwch) ARE NOW DEAD. Use dwrnfpjcvydhmhnvyzov only.
Update these fields via PATCH to /rest/v1/buyer_dossiers?slug=eq.sap-successfactors:
| Field | Type | What goes here |
|---|---|---|
| exa_research_raw | JSONB | All Exa search results (full text + URLs + query log) |
| sec_filing_raw | JSONB | All SEC filing extractions (20-F, 6-K) |
| analysis_dual_raw | JSONB | researcher_1 and researcher_2 full outputs |
| validation_report | JSONB | Inspector merge report with contradictions |
| certification | JSONB | Final certified data with confidence levels |
| certified_challenges | TEXT | SAP's stated challenges from evidence |
| certified_ceo_vision | TEXT | Christian Klein's stated direction with quotes |
| certified_key_quotes | TEXT | All 10+ quotes formatted with attribution |
| certified_acquisition_history | TEXT | Full M&A history with outcomes |
| certified_acquisition_appetite | TEXT | active/selective/dormant with evidence |
| certified_hr_tech_presence | TEXT | SuccessFactors market position detail |
| certified_community_strategy | TEXT | SAP's community/ecosystem approach |
| certified_fit_signals | TEXT | Specific signals HR.com addresses |
| certified_market_position | TEXT | SAP's position in HCM market |
| certified_revenue | TEXT | Latest revenue figure with source |
| certified_employees | TEXT | Employee count with source |
| quotes | JSONB | Array of all quote objects (see format above) |
| quote_count | INTEGER | Number of verified quotes found |
| fit_narrative | TEXT | Full multi-section narrative |
| fit_score | INTEGER | 1-100 score |
| fit_rationale | TEXT | Evidence-based score explanation |
| fit_synthesis_raw | JSONB | Full output: cold_call_opener, email_hook, business_model_integration, competitive_block, primary_assets array |
| gtm_revenue_model | TEXT | Revenue model description |
| gtm_sales_motion | TEXT | Sales motion (enterprise/PLG/channel) |
| pipeline_status | TEXT | Set to "COMPLETE" when done |
| research_cost_usd | FLOAT | Total API cost for this dossier |
| completed_at | TIMESTAMP | ISO timestamp when finished |
Update via PATCH to /rest/v1/deal_research?company_name=eq.SAP SuccessFactors&asset_type=eq.Buyer Target:
| Field | Type | What goes here |
|---|---|---|
| story_narrative | TEXT | Full narrative with ALL sections: FIT NARRATIVE, BUSINESS MODEL INTEGRATION, COMPETITIVE MOAT, COLD CALL SCRIPT, EMAIL SUBJECT LINE, EMAIL BODY, RECENT STRATEGIC MOVES, UPGRADE NOTES (with quotes, challenges, fit signals) |
| confidence | TEXT | HIGH if fit_score >= 70, MEDIUM if >= 40, LOW if < 40 |
| call_opener | TEXT | Cold call opener sentence |
| revenue | TEXT | SAP's latest annual revenue |
| employees | TEXT | Employee count |
| business_strength | TEXT | "Community" or "Platform" |
⚠️ This deal_research table feeds the Lovable app LIVE at https://next-chapter-reports.lovable.app/deals — whatever you write here shows up on that page immediately.
ewing-operating-system/dossier-pipeline~/Projects/dossier-pipeline/~/Projects/dossier-pipeline/data/buyer_dossiers/sap-successfactors.jsonLog every API call to dossier_cost_log table:
- api_name, operation, cost_usd, tokens_in, tokens_out, model, provider
SAP SuccessFactors already has a dossier with good narrative content. Do NOT overwrite the following sections — ENRICH them with evidence:
Your job is to ADD the missing evidence layer: the 10+ quotes, the SEC filing data, the acquisition history with outcomes, and the earnings call language. The narrative skeleton is good. The evidence is what's missing.
Start now.