중간 보고서 · 커밋된 receipt에서만 생성 · 운영 데이터 미포함

📡 BusinessRadar 중간 보고서

2026-08-15 · repo HEAD 943a43c feat(outreach): 슬롯 3개가 서로 다른 것을 죽이도록 재설계 · 재생성 node scripts/report.mjs
읽는 법. 아래 기회는 전부 candidate다 — 승인된 것은 하나도 없다. 점수는 에이전트 초안이고 확정은 사람이 한다. 각 카드의 얼마나 확실한가와 틀린다면 이 이유로 틀린다가 핵심이다. 요약에서 약점을 빼면 보고서가 아니라 홍보가 된다. 축 막대에 커서를 올리면 그 점수를 준 기준이 나온다.

기회 — 이게 무슨 사업인가

AI 생성 광고 카피의 규제 검수 게이트 (KR 공백 · JP 성립)

opp_yca_001 · yc-arbitrage · candidate · 근거등급 partial

병원·건기식·화장품 업체가 광고 문구를 올리기 전에, 그 문구가 법에 걸리는지 자동으로 검사하고 안전한 표현으로 바꿔주는 도구.

누가 돈을 내나
광고 문구를 승인하고 올리는 사람. 병원 마케팅 담당자, 건기식 온라인 판매사, 이들을 대행하는 대행사. 지금은 문구 하나 확인하려고 법무법인이나 심의 대행에 건당 비용을 낸다.
무엇을 파나
"이 문장은 위험합니다 + 이유(조항·유사 처분 사례) + 이렇게 바꾸세요." 판단을 대신 해주는 게 아니라 위험 표시와 대체 표현까지다. 여기서 더 나가면 SaaS가 아니라 대행업이 되고 우리가 책임을 진다.
왜 지금
규제 시행일이 4개월 뒤다. AI 생성 가짜 전문가 이미지를 쓴 광고 금지가 식품·의약품·화장품은 2026년 11월, 의료기기는 12월에 시행된다. 그전에 식약처는 이미 2025년에 '가짜 의사·약사' 광고 63건을 적발했고 2026년 7월에도 단속을 이어가고 있다. 컴플라이언스 도구는 규제 시행 직전 3~4개월에 가장 잘 팔린다 — 지금이 그 창의 초입이다.
왜 한국인가
일본에서는 이미 같은 문제를 푸는 도구가 9~18종 유료로 팔린다(무료 플랜, 월정액 있음). 즉 사람들이 돈을 낸다는 게 다른 나라에서 이미 증명됐다. 한국은 규제도 있고 단속도 세지는데 검색하면 심의 기관과 법무법인만 나온다. 새로 발명하는 게 아니라 이미 팔리는 걸 옮기는 것이라 리스크가 낮다.
도슨티와 무슨 상관인가
우리가 만드는 게 마케팅 카피 생성 파이프라인이다. 이 사업은 그 파이프라인 바로 뒤에 붙는 검사 단계다. 카피를 만드는 쪽이 검사도 팔면, 만든 사람이 책임까지 같이 지는 그림이 된다.
얼마나 확실한가
규제 시행일·단속·일본 가격대는 근거 URL로 확인됐다. 국내 공급자 역탐색도 3라운드 돌려서 "전용 SaaS 없음 / 대행사 내부 기능은 존재"까지 좁혔다. 구매자 언어도 브라우저 세션으로 403 소스까지 열어 원문 20건을 확보했다(아래). 아직 없는 건 구매 의사다. "이거 불편하다"는 확인됐지만 "이런 도구에 돈 내겠다"는 아직 못 들었다. 오히려 병원측에서는 "규제 자체가 부당하다"는 반대 방향 신호가 나왔다.
틀린다면 이 이유로 틀린다
① 의료광고는 법정 사전심의를 반드시 거쳐야 해서, 우리 검사가 심의를 대체하지 못하고 그냥 중복 비용이 될 수 있다. ② ~~일본 18종은 코모디티화 신호일 수 있다~~ → 약화됨: 실제 가격을 확인했다 (機械良文 15,000~60,000엔/월, AD SHIELD 월 10만엔). 공짜가 아니다. ③ 단속이 세지면 광고주가 AI 카피를 아예 줄여서, 도슨티 본체 수요까지 같이 줄 수 있다. ④ (역탐색 발견) 팔려는 대상인 대행사가 이미 자체 AI 검수를 갖고 있다 — 구매자가 곧 경쟁자다. 하룹이 그 사례고, "AI + 사람 이중 확인"을 파는 걸 보면 순수 AI 판정만으로는 이 시장이 책임을 못 진다는 뜻일 수 있다. ⑤ ~~규제기관이 같은 걸 만들어 시장이 공짜가 된다~~ → 약화됨: AI캅스는 감시→차단→수사 구조의 단속 인프라이고, 정책브리핑 원문에 사업자용 자가진단 공개 계획이 없다. 차세대 시스템도 2027년 단계적 구축이다. 다만 규제기관이 이 영역에 AI 역량을 쌓는다는 사실은 남는다. ⑦ (셀러 검증에서 발견 — 치명적) 공포와 오퍼가 어긋난다. 셀러 최대 공포인 메타 계정 정지는 반려 사유 7종 중 한국 법규와 겹치는 게 1개뿐이다. 한국 법을 지켜도 정지된다. ⑧ (셀러 검증에서 발견) 실수요가 검수가 아니다. 실무자 질문은 "이거 심의 대상인가요" (범위 판정)와 "문제 생겼을 때 핑계거리"(알리바이)에 몰려 있다. ⑥ (구매자 언어에서 발견 — 의료 세그먼트 한정) 규제 대상자가 규제를 수용하지 않는다. 병원측 커뮤니티의 지배 정서는 "도구가 필요하다"가 아니라 "이 규제가 부당하다"다 (국민청원, "보건소의 갑질", 닉네임 "억울합니다"). 분노 에너지가 구매가 아니라 규제 철폐 운동으로 흐르고, 최악의 경우 "이제 병원 블로그 마케팅은 끝"이라며 시장을 떠난다. 컴플라이언스 도구는 규제를 받아들인 사람에게만 팔린다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널3
채널 있으나 미검증
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성2
합계 18/25 · 자동 보류선 15 · 급성장 신호: 1. 가격·매출 · 3. 공급 · 4. 제도 · 6. 사회 현상
위임 → Dct-Geo (geo.docenty.ai)
국내 공급자 역탐색 — 광고 문구 법규 자동 검수 SaaS가 한국에 실재하는지 확인. 검색 미발견은 부재 증명이 아니므로 승인 게이트로 남아 있음
근거 1건

에이전틱 커머스 피드 대응 (ACP) — 에이전트가 읽는 상품 데이터 공급

opp_yca_002 · yc-arbitrage · candidate · 근거등급 partial

ChatGPT 같은 AI가 상품을 직접 찾아서 결제까지 할 수 있도록, 셀러의 상품·재고·가격 정보를 AI가 읽는 규격으로 바꿔서 연결해주는 일.

누가 돈을 내나
온라인 셀러. 규격 문서를 읽고 직접 붙일 여력이 없는 쪽.
무엇을 파나
상품 피드 연결과 유지(재고·가격이 실시간으로 맞게).
왜 지금
OpenAI·Stripe ACP, Google/Shopify UCP, AP2가 2026년에 한꺼번에 표준 경쟁으로 올라왔다. "어느 표준 하나를 붙일까"가 아니라 여러 표준 사이에서 안 보이지 않게 hedging하는 문제가 생겼다.
왜 한국·일본인가
검색해도 한국·일본 대응 사례가 안 나온다. 초기 구간이라는 뜻이다. 다만 "아직 아무도 안 했다"와 "여기선 안 일어난다"는 검색 결과가 똑같이 비어 보인다 — 이 둘을 못 가른 게 이 기회의 핵심 약점이다.
도슨티와 무슨 상관인가
하는 일이 GEO와 같다. GEO는 상품 정보를 AI가 이해하기 좋게 정리하는 일이고, 이건 그 정리된 정보를 AI가 가져갈 수 있는 규격으로 내보내는 일이다. shop-aeo에서 이미 상품 정보를 다루고 있으니 새로 배울 게 적다. 문제는 기술이 아니라 한국 플랫폼이 그 문을 열어주느냐이고, 그건 우리가 못 정한다.
얼마나 확실한가
기술 타이밍은 강해졌다. 공식 문서, GitHub issue activity, merchant readiness 가이드가 모두 살아 있다. 그러나 구매자 쪽 확실성은 여전히 낮다. 한국·일본에서 이걸 원한다는 발화는 한 건도 못 찾았고, 국내 플랫폼의 개방 정책도 확인 못 했다.
틀린다면 이 이유로 틀린다
① 네이버·쿠팡이 이 기능을 기본으로 내장하면 대행 수요가 0이 된다. ② 더 나쁜 경우: 네이버·쿠팡이 외부 AI에게 상품·결제를 열어줄 이유가 없어서 한국에서는 ACP가 아예 발생하지 않는다. 이건 경쟁에서 지는 게 아니라 시장이 없는 것이다. ③ 스코어 17점 중 5점이 "도슨티 파이프라인에 딱 맞는다"(offer)인데, 그건 우리 사정이지 시장 신호가 아니다. 시장 신호인 arbitrage(3)와 conversion(2)은 둘 다 낮다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널3
채널 있으나 미검증
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거2
이식 가능성4
합계 19/25 · 자동 보류선 15 · 급성장 신호: 2. 자본 · 3. 공급 · 4. 제도
근거 5건

GEO/LLMO 성과 증명 — 최적화가 아니라 "됐는지"를 판다

opp_yca_003 · yc-arbitrage · candidate · 근거등급 partial

GEO(=AI 검색에 잘 걸리게 만드는 작업)를 해준 다음, 진짜로 AI가 우리 가게·상품을 언급하게 됐는지 확인해서 숫자로 보여주는 서비스.

누가 돈을 내나
이미 GEO에 돈을 쓰고 있는데 효과를 윗선에 설명하지 못하는 사람. 마케팅 담당자, 대행사, 그리고 도슨티의 기존 GEO 고객.
무엇을 파나
"ChatGPT·Perplexity·네이버 AI에 이런 질문을 하면, 우리 브랜드가 몇 번 인용됐고 지난달 대비 어떻게 변했다"는 리포트. 최적화 작업이 아니라 작업이 됐는지에 대한 증명을 판다.
왜 지금
AI 답변에는 '검색 순위'가 없다. 인용되거나 안 되거나 둘 중 하나라서, 기존 SEO 순위 추적 도구로는 측정 자체가 안 된다. 측정 방법이 없는 채로 돈만 쓰는 구간이 지금이다.
왜 한국·일본인가
일본은 GEO를 해주는 회사는 이미 많다(절반 이상이 도입 단계를 넘겼다). 그런데 도입을 막는 1위 이유가 "ROI가 안 보인다"다. 실행은 넘치는데 증명이 없다. 한국은 실행조차 초기라 같은 빈칸이 더 일찍 열려 있다.
도슨티와 무슨 상관인가
셋 중 우리와 가장 가깝다. shop-aeo·place-aeo가 이미 라이브고, 새 고객을 찾을 필요 없이 기존 고객에게 추가로 파는 것이라 채널 비용이 0에 가깝다.
얼마나 확실한가
선행시장 제품과 가격대는 확인됐다. Peec AI·Profound 같은 공식 제품과 비교 글의 가격대가 살아 있다. 51.45%·23.34% 두 숫자는 여전히 2차 매체 인용이라 조심해야 하지만, 이제 그 숫자를 빼도 "AI visibility 계측 카테고리 성립"은 남는다.
틀린다면 이 이유로 틀린다
① "ROI가 안 보인다"가 사실은 "효과가 없다"의 완곡한 표현일 수 있다. 그렇다면 정직한 측정기는 자기 시장을 스스로 파괴한다 — 우리 계측기가 shop-aeo·place-aeo의 GEO 효과가 0이라는 걸 증명해버릴 수 있다는 뜻이다. 이건 오퍼 검증이 아니라 오퍼 사망 가능 실험이다. ② ~~원장에 고객 존재 근거 0건~~ → 해소됨: 운영자 확인으로 Dct-Geo 고객 약 10개사가 실재한다(2026-07-26). 다만 10개사는 첫 실험 표본으로는 작다 — 전원이 산다고 해도 유입 100세션 게이트를 못 넘기므로, 이걸로 스코어카드를 재튜닝할 수는 없다.
타이밍4
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성4
합계 20/25 · 자동 보류선 15 · 급성장 신호: 1. 가격·매출 · 3. 공급 · 5. 수요
근거 7건

AI 검색·ChatGPT 쇼핑 attribution ops — "AI 유입이 Direct로 사라지는 문제"를 판다

opp_yca_010 · yc-arbitrage · candidate · 근거등급 partial

ChatGPT·Claude·Perplexity·네이버 AI에서 생긴 유입과 전환이 GA4에서 Direct로 사라지지 않게, UTM/서버 이벤트/AI referral 리포트를 세팅해주는 서비스.

누가 돈을 내나
GEO나 AI 검색 최적화에 돈을 쓰기 시작했지만, "그래서 매출이 났나?"를 설명해야 하는 마케팅 담당자·대행사·커머스 셀러.
무엇을 파나
AI 검색 referrer 정리, UTM/landing 규칙, ChatGPT 쇼핑 feed 노출 체크, 전환 이벤트 검증, 월간 attribution 리포트.
왜 지금
OpenAI가 ChatGPT product discovery와 merchant feed 표면을 공식화했고, 쇼핑 research는 수억 명 사용자의 제품 비교 흐름에 들어갔다. 동시에 practitioner 자료는 GA4 누락과 query-level 부재를 반복해서 문제로 잡는다.
도슨티와 무슨 상관인가
shop-aeo·place-aeo가 이미 AI 검색에 걸리게 만드는 실행 자산이라면, 이 후보는 그 작업의 사후 증명과 예산 방어 레이어다.
얼마나 확실한가
플랫폼 변화는 공식 근거가 있다. OpenAI product discovery, ChatGPT merchant feed, shopping research는 모두 공개 페이지가 살아 있다. 공개 마케터·GA4 실무자 발화에서도 attribution gap, Direct 오분류, AI 유입 reporting 문제는 반복된다. 다만 기존 Dct-Geo 고객 직접 발화는 아직 0건이다.
틀린다면 이 이유로 틀린다
OpenAI·GA4·네이버가 native attribution을 빠르게 개선하면 우리가 팔 계측 ops가 얇아진다. 또는 기존 Dct-Geo 고객이 아직 광고/커머스 budget owner가 아니라면 channel 4가 과대평가다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거4
이식 가능성4
합계 22/25 · 자동 보류선 15 · 급성장 신호: 3. 공급 · 4. 제도 · 5. 수요
근거 5건

ChatGPT Ads launch-readiness & measurement ops

opp_yca_011 · yc-arbitrage · candidate · 근거등급 partial

ChatGPT Ads를 바로 집행하거나 파일럿에 들어갈 광고주에게 프롬프트 타겟 가설, 랜딩/UTM, 전환 이벤트, brand-safety 제외 기준, 월간 리포트를 세팅해주는 launch-readiness ops.

누가 돈을 내나
Google/Meta 광고를 이미 쓰고 있고, AI 검색·ChatGPT 광고를 새 채널로 테스트해야 하는 국내 광고주·대행사.
무엇을 파나
ChatGPT Ads 질문/맥락 후보, landing/UTM 규칙, OAI/GA4 전환 이벤트 검증, 금지·민감 문맥 제외 기준, 파일럿 성과 리포트.
왜 지금
OpenAI는 ChatGPT Ads 테스트, CPC bidding, 구매·관리 방식 확장, 결과 측정 개발을 공식화했다. 국내 마케터 공개 글도 "검색 다음 단계"와 "어떤 질문을 타겟할지"를 묻기 시작했다.
도슨티와 무슨 상관인가
shop-aeo·place-aeo·opp_yca_010이 organic AI discovery와 attribution을 맡는다면, 이 후보는 paid ChatGPT Ads 쪽 예산 집행 준비 레이어다.
얼마나 확실한가
공식 플랫폼 변화와 국내 마케터 발화는 강하다. 하지만 한국에서 실제 집행 가능한 광고주, 최소 예산, OpenAI Ads 접근 권한, 광고 budget owner 확인 전에는 승인 금지다.
틀린다면 이 이유로 틀린다
OpenAI가 self-serve와 measurement를 충분히 쉽게 만들면 ops 수요가 얇아진다. 또는 한국 롤아웃이 늦으면 지금 당장 파는 상품이 컨설팅 대기열에 머문다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거4
이식 가능성4
합계 22/25 · 자동 보류선 15 · 급성장 신호: 1. 가격·매출 · 3. 공급 · 4. 제도 · 5. 수요
근거 7건

AI-ready product catalog enrichment ops

opp_yca_012 · yc-arbitrage · candidate · 근거등급 partial

공급사 원본·기존 상세페이지·리뷰·FAQ를 AI-ready catalog로 바꿔 SKU별 검색/추천/AI 답변 노출에 유리한 상품 데이터로 정리하는 서비스.

누가 돈을 내나
SKU가 많고 상세페이지/상품 속성/검색 키워드 정리에 계속 시간을 쓰는 스마트스토어·쿠팡 셀러와 대행사.
무엇을 파나
상품명 규칙, 속성 누락 보강, 상세페이지 정보 구조화, FAQ/맥락 문장, marketplace별 feed/AI 검색 준비 체크리스트.
왜 지금
YC Anglera는 상품 데이터 enrichment agent가 SKU당 작업 시간을 크게 줄인다는 선행시장 신호를 준다. 국내 공개 글도 상세페이지 데이터화, 검색 행동 데이터, AI 추천 맥락 문장을 반복한다.
도슨티와 무슨 상관인가
shop-aeo가 이미 쇼핑 AI/GEO를 다루므로, 이 후보는 그 앞단의 상품 데이터 정리 업무다.
얼마나 확실한가
도슨티와의 인접성은 높다. 하지만 국내에도 상세페이지 제작·검색 데이터 운영·AI 마케팅 대행 공급이 많고, 직접 고객 발화가 없다.
틀린다면 이 이유로 틀린다
셀러는 상품 데이터 정리를 고통으로 느껴도 월 운영비가 아니라 일회성 상세페이지 제작비로만 본다. 또는 기존 대행사/마켓 솔루션이 충분해서 아비트라지 여지가 작다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성3
선행시장에 제품이 있으나 카테고리 성립 미확인 — 또는 제품은 많은데 전부 무료/번들이라 코모디티 의심
합계 20/25 · 자동 보류선 15 · 급성장 신호: 2. 자본 · 3. 공급 · 5. 수요
근거 6건

OpenAI Ads Pixel+CAPI implementation ops

opp_yca_013 · yc-arbitrage · candidate · 근거등급 partial

ChatGPT Ads 성과가 "클릭은 있었는데 매출·상품·전환 최적화가 제대로 잡혔나"에서 막히지 않도록, OpenAI Ads 측정 태그와 서버 이벤트를 실제 광고 운영 stack에 붙여주는 서비스.

누가 돈을 내나
ChatGPT Ads를 테스트하려는 국내 이커머스·교육·B2B SaaS 광고주와 광고 대행사.
무엇을 파나
OpenAI Ads Pixel 설치, Conversions API 서버 이벤트, GTM/서버사이드 태깅, GA4 이벤트 매핑, product-feed campaign insight 확인, conversion-optimized campaign 준비 체크.
왜 지금
OpenAI Ads 개발 문서에 Pixel, Conversions API, product feed, conversion-optimized campaign, conversion setup API가 구체적으로 열려 있다. 광고가 "언젠가"가 아니라 측정 구현이 필요한 단계로 내려왔다.
도슨티와 무슨 상관인가
opp_yca_011이 paid ChatGPT Ads launch-readiness라면, 이 후보는 그 안에서 가장 돈 받기 쉬운 구현 작업이다. opp_yca_010의 attribution ops와도 같은 server event/UTM/월간 리포트 파이프라인을 공유한다.
얼마나 확실한가
공식 문서와 GitHub GTM template 공급은 강하다. 하지만 한국 광고주 접근 권한, 초기 예산, 직접 buyer-language는 아직 없다.
틀린다면 이 이유로 틀린다
OpenAI Ads Manager가 self-serve로 충분히 쉬워지거나, Shopify/GTM 앱이 30초 설치로 시장을 흡수하면 운영 대행 마진이 얇아진다. 한국 롤아웃이 늦어도 단기 매출화가 막힌다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거4
이식 가능성4
합계 22/25 · 자동 보류선 15 · 급성장 신호: 1. 가격·매출 · 3. 공급 · 4. 제도
근거 8건

ChatGPT app submission readiness ops

opp_yca_014 · yc-arbitrage · candidate · 근거등급 partial

브랜드가 ChatGPT 대화 안에서 검색·예약·장바구니·체크아웃 같은 핵심 action을 제공하도록 Apps SDK 기반 app/plugin 출시 준비를 맡아주는 서비스.

누가 돈을 내나
ChatGPT를 새 유통 채널로 보고 앱 또는 체크아웃 경험을 만들고 싶은 커머스, 여행/예약, 교육, 콘텐츠 브랜드.
무엇을 파나
ChatGPT app use case 정리, MCP server 설계, UI component, auth/consent/privacy, domain/identity 준비, positive/negative submission test cases, 출시 후 prompt/metadata 최적화.
왜 지금
OpenAI는 ChatGPT 안의 apps, Apps SDK, plugin submission, Instant Checkout, Target/Instacart 같은 commerce app 사례를 공개했다. 대화형 앱과 체크아웃이 실제 제품 표면으로 내려오고 있다.
도슨티와 무슨 상관인가
shop-aeo와 product catalog enrichment가 "ChatGPT가 우리 상품을 이해하게 만들기"라면, 이 후보는 그 다음 단계인 "ChatGPT 안에서 우리 action을 실행하게 만들기"다.
얼마나 확실한가
공식 플랫폼 신호는 강하다. 하지만 국내 고객이 당장 app/plugin 구축비를 낼지, OpenAI review를 통과할 준비가 됐는지, 운영 난이도를 감당할지 확인되지 않았다.
틀린다면 이 이유로 틀린다
초기 파트너/대형 브랜드 중심으로만 열리고 중소 브랜드는 당분간 앱 출시 기회가 작을 수 있다. 또는 app 구축보다 product feed/Ads/attribution이 먼저라 예산 우선순위에서 밀린다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널3
채널 있으나 미검증
상품 연결4
수요 근거3
유사 사례 근거
이식 가능성4
합계 19/25 · 자동 보류선 15 · 급성장 신호: 2. 자본 · 3. 공급 · 4. 제도
근거 11건

Presence-lite agent QA/eval readiness ops

opp_yca_015 · yc-arbitrage · candidate · 근거등급 partial

OpenAI Presence 자체를 구현하는 게 아니라, Presence가 보여준 운영 기준을 작은 팀이 따라 할 수 있게 policies, guardrails, 승인 규칙, escalation, simulation set, eval scorecard, post-launch 개선 루프를 패키지로 만들어주는 서비스.

누가 돈을 내나
OpenAI API나 ChatGPT 기반 voice/chat agent를 고객지원·세일즈·IT 업무에 붙이려는 국내 중견 기업 운영팀.
무엇을 파나
업무별 agent policy map, tool/action permission matrix, human approval rule, escalation trigger, simulation cases, eval grader, launch checklist, 월간 failure review.
왜 지금
OpenAI가 Presence를 발표하며 production agent의 핵심 요소를 policies, guardrails, simulations, evaluation tools, approved actions, Codex-powered improvement process로 명명했다.
도슨티와 무슨 상관인가
직접 채널은 약하다. 기존 commerce/GEO 고객이 customer support agent나 sales agent를 같이 고민할 때만 adjacent하다.
얼마나 확실한가
공식 platform signal은 강하다. 하지만 Presence는 eligible enterprise 대상으로 limited general availability이고, FDE와 select global SI가 deployment를 주도한다. 그래서 P0가 아니라 watchlist다.
틀린다면 이 이유로 틀린다
OpenAI와 대형 SI가 상단 시장을 직접 가져가고, 중견 고객은 아직 agent 운영 예산이나 compliance owner가 없다. 또는 고객이 "그냥 ChatGPT Enterprise/Presence를 기다리겠다"고 하면 독립 서비스가 약하다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널2
상품 연결4
수요 근거3
유사 사례 근거
이식 가능성2
합계 16/25 · 자동 보류선 15 · 급성장 신호: 3. 공급 · 4. 제도
근거 2건

ChatGPT product discovery merchant-feed readiness ops

opp_yca_016 · yc-arbitrage · candidate · 근거등급 partial

상품이 ChatGPT에서 발견·비교될 때 누락되거나 잘못 설명되지 않도록 merchant feed와 상세페이지 구조를 AI shopping answer에 맞게 정리한다.

누가 돈을 내나
Shopify·카페24·스마트스토어 등에서 상품을 파는 셀러, 브랜드, commerce agency.
무엇을 파나
상품 속성 completeness audit, 비교 표에 필요한 spec field 정리, 가격/재고 freshness 점검, merchant-owned checkout handoff 점검, AI shopping query별 product answerability report.
왜 지금
OpenAI가 ChatGPT product discovery와 shopping research를 공개했고, 구매는 merchant-owned site/app에서 완료되는 방향을 명시했다.
도슨티와 무슨 상관인가
기존 GEO/AI 검색 최적화 고객과 매우 가깝다. opp_yca_010의 attribution ops와 묶으면 "AI가 보내는 발견→방문→구매" 전체를 볼 수 있다.
얼마나 확실한가
platform timing과 offer는 강하지만 국내 buyer receipt는 아직 없다.
틀린다면 이 이유로 틀린다
OpenAI/Shopify/카페24 앱이 feed readiness를 자동화하거나, merchant가 ChatGPT shopping 유입을 아직 거의 못 느끼면 별도 예산이 안 나온다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성4
합계 21/25 · 자동 보류선 15 · 급성장 신호: 3. 공급 · 4. 제도 · 5. 수요
근거 4건

ChatGPT Ads oCPC signal quality audit

opp_yca_017 · yc-arbitrage · candidate · 근거등급 partial

ChatGPT Ads가 클릭에서 전환 최적화로 넘어갈 때, "입찰에 먹이는 전환 이벤트가 믿을 만한가"를 감사하고 고쳐준다.

누가 돈을 내나
ChatGPT Ads를 테스트하거나 CPC/oCPC로 예산을 키우려는 광고주, performance agency.
무엇을 파나
Pixel/CAPI 이벤트 매핑, conversion setup review, oCPC goal sanity check, GA4/GTM/server event reconciliation, CRM downstream match check.
왜 지금
OpenAI Ads docs는 conversion-optimized campaigns와 Pixel/CAPI를 명확히 제시한다.
도슨티와 무슨 상관인가
opp_yca_013의 설치형 작업을 "예산 키우기 전 신호 감사"로 좁힌 버전이다.
얼마나 확실한가
공식 문서 근거는 강하다. 그러나 광고 접근권과 국내 budget owner receipt가 없다.
틀린다면 이 이유로 틀린다
OpenAI Ads Manager가 충분한 quality warning을 자동 제공하거나, agency/partner가 상단 시장을 가져가면 독립 audit 수요가 약하다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성4
합계 21/25 · 자동 보류선 15 · 급성장 신호: 1. 가격·매출 · 3. 공급 · 4. 제도
근거 6건

GA4 AI Assistant channel delta audit

opp_yca_018 · yc-arbitrage · candidate · 근거등급 partial

"GA4가 이제 AI Assistant를 보여준다"에서 끝나지 않고, 도입 전후 유입·전환·Direct 누락 추정이 얼마나 바뀌었는지 설명해준다.

누가 돈을 내나
AI referral이 늘었다고 의심하지만 GA4/CRM 해석이 흔들리는 마케팅팀.
무엇을 파나
GA4 AI Assistant channel before/after audit, custom source coverage check, Perplexity/기타 engine gap, Direct/unassigned leakage estimate, 예산 보고서.
왜 지금
공개 실무 자료가 GA4 AI Assistant channel과 남는 attribution gap을 함께 다룬다.
도슨티와 무슨 상관인가
opp_yca_010의 pain을 더 구체적인 "GA4 업데이트 이후에도 남는 문제"로 좁힌다.
얼마나 확실한가
timing은 좋지만 native GA4 기능이 오히려 pain을 줄이는 반증도 강하다.
틀린다면 이 이유로 틀린다
GA4 native channel이 충분히 정확해져 별도 audit 가치가 사라진다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결4
수요 근거3
유사 사례 근거
이식 가능성3
선행시장에 제품이 있으나 카테고리 성립 미확인 — 또는 제품은 많은데 전부 무료/번들이라 코모디티 의심
합계 19/25 · 자동 보류선 15 · 급성장 신호: 3. 공급 · 4. 제도 · 5. 수요
근거 3건

AI agent procurement risk certificate

opp_yca_021 · yc-arbitrage · candidate · 근거등급 partial

"agent가 실제로 이메일을 보내고 CRM을 고치고 데이터를 만질 수 있다면, 구매자가 뭘 믿고 승인하나"라는 procurement 병목을 문서와 eval evidence로 풀어준다.

누가 돈을 내나
enterprise에 AI agent를 팔려는 스타트업, SI, 내부 자동화팀.
무엇을 파나
권한 matrix, tool/action risk register, eval summary, red-team checklist, audit-log 샘플, residual-risk memo, insurance/procurement 대응 문서.
왜 지금
YC의 Klaimee와 TrustAI가 AI agent 보험·인증·continuous compliance를 명확한 카테고리로 만들고 있다.
도슨티와 무슨 상관인가
직접 채널은 약하다. 다만 Docenty가 agent/MCP/app을 고객에게 붙이기 시작하면 필수 부속품이 된다.
틀린다면 이 이유로 틀린다
대형 보험사·보안기업·OpenAI/FDE가 표준 증빙을 무료 템플릿화하면 소형 컨설팅 가치는 줄어든다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널3
채널 있으나 미검증
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성4
합계 20/25 · 자동 보류선 15 · 급성장 신호: 2. 자본 · 3. 공급 · 4. 제도
근거 4건

AI-ready product catalog normalization for agentic commerce

opp_yca_024 · yc-arbitrage · candidate · 근거등급 partial

AI commerce의 병목은 멋진 checkout보다 먼저, 상품 데이터가 AI가 읽고 비교할 만큼 깨끗하지 않다는 점이다.

누가 돈을 내나
SKU가 많고 공급사 자료가 messy한 브랜드, 쇼핑몰, 유통사, marketplace seller.
무엇을 파나
supplier PDF/image ingest, attribute schema, 비교 필드, variant normalization, AI search answerability, merchant feed export.
왜 지금
OpenAI product discovery/shopping research와 YC Anglera가 같은 하부 문제를 가리킨다.
도슨티와 무슨 상관인가
기존 GEO/commerce 고객과 매우 가깝다. opp_yca_016이 audit이면 이건 implementation이다.
틀린다면 이 이유로 틀린다
Shopify/카페24/marketplace 앱이 product enrichment를 자동화하거나, 고객이 AI shopping 유입을 아직 못 느끼면 예산이 늦다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널4
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성4
합계 21/25 · 자동 보류선 15 · 급성장 신호: 3. 공급 · 4. 제도 · 5. 수요
근거 3건

Regulated product claim linting for AI-generated commerce content

opp_yca_027 · yc-arbitrage · candidate · 근거등급 partial

AI copy 생성이 빨라질수록 규제 산업에서는 "많이 쓰는 것"보다 "잘못 쓰지 않는 것"이 더 비싼 문제가 된다.

누가 돈을 내나
화장품, 기능성 화장품, 건강기능식품, 의료 인접 제품을 온라인 판매하는 브랜드와 대행사.
무엇을 파나
금지/위험 표현 linting, 효능·효과 claim 근거 요구, AI-generated testimonial/전문가 표현 flag, 수정안, publish approval log.
왜 지금
MFDS 규제 축과 AI-generated content scale이 만난다. KISO/AI 기본법 흐름도 transparency/safety 압박을 키운다.
도슨티와 무슨 상관인가
상세페이지·광고·GEO 콘텐츠 생산 고객과 매우 가깝다.
틀린다면 이 이유로 틀린다
법률 자문 영역으로만 인식되어 software/ops 예산이 안 나오거나, 플랫폼 자체 검수가 충분해질 수 있다.
타이밍5
지금 이 분기에 창이 열림 — 날짜가 박힌 사건 + growth_signals 사다리 2단 이상 근거
유입 채널5
기존 도슨티 자산으로 즉시 도달 가능
상품 연결5
기존 상품에 직결 (같은 파이프라인에 붙는 인접 기능)
수요 근거3
유사 사례 근거
이식 가능성4
합계 22/25 · 자동 보류선 15 · 급성장 신호: 3. 공급 · 4. 제도 · 5. 수요
근거 4건

스윕 실행 기록

스윕 실행 기록
runmethod상태소스URL상한 도달비고
run_ng_001naver-geopartial317-웹 검색 3회 — 공개 뉴스·블로그 중심. 셀러 직접 발화(카페)는 수동 캡처 대기라 partial. 상한 미도달
run_yca_001yc-arbitragepartial89sourcesYC RFS(Fall/Summer 2026) 기준 도슨티 인접 카테고리 3건 스윕. 웹 검색 8회 = caps.sources 8 도달 → partial 종료. 그 외 partial 사유: (a) 한국 공급 공백은 '
run_yca_002yc-arbitragepartial36-opp_yca_002 재평가 스윕. OpenAI/Stripe ACP 공식 문서, GitHub spec activity, 2026 merchant guide를 확인해 agentic commerce timing을 재평가
run_yca_003yc-arbitragepartial68-opp_yca_003 GEO/LLMO 성과 증명 재평가. AI search visibility/LLMO monitoring 유료 도구 가격대와 카테고리 성립 여부를 확인. KR 직접 구매자 발화는 아직 미확인이라 p
run_yca_006yc-arbitragepartial33-opp_yca_010 국내 시장 적합성 보강 스윕. Brunch/Mobiinside 공개 GEO 성과 측정 글에서 AI 유입 트래픽, GA4 AI Search 세그먼트, AI Assisted Conversion, 국
run_yca_007yc-arbitragepartial44-opp_yca_010 선행시장 유료 가격대/경쟁 검증. Profound 공식 pricing, Peec pricing/비교, TeamAI GEO budget guide, Peec vs Ahrefs Brand Radar
run_yca_008yc-arbitragepartial55-opp_yca_010 국내 공급 공백 반증 스윕. GeoRank, Elifunt, Onthe AI, Growth, Tistory 공개 자료에서 국내 GEO 성과 측정/GA4 AI 유입/AI SOV/전환 질 측정 언어
run_yca_009yc-arbitragepartial46-ChatGPT Ads 공식 테스트·구매 방식 확장·측정 기능 개발 신호를 OpenAI 공식 자료, 국내 마케터 공개 발화, allowlist 내 attribution playbook으로 스윕. 새 별도 후보 opp_
run_yca_010yc-arbitragepartial35-YC Anglera류 AI product data enrichment/e-commerce catalog ops를 challenger 후보로 스윕. 도슨티 shop-aeo와 인접하지만 국내 상세페이지·검색 데이터 운영
run_yca_011yc-arbitragepartial59-OpenAI Ads developer docs에서 Pixel, Conversions API, product feed, conversion-optimized campaign이 확인되어 opp_yca_011을 더 좁은
run_yca_012yc-arbitragepartial210-ChatGPT Apps SDK와 Instant Checkout/agentic commerce app 신호를 스윕. 플랫폼 변화는 강하지만 도슨티 기존 고객 channel과 직접 구매 pain이 attribution/
run_yca_013yc-arbitragepartial44-ChatGPT Ads measurement 최신 공개 신호를 재확인. OpenAI 공식 입장은 ads test/원칙이고, ad-tech 보도와 server-side tracking 공급자는 self-serve/CAP
run_yca_004yc-arbitragepartial56-기존 GEO/LLMO 리드의 인접 고신호 변형 탐색. OpenAI 공식 product discovery/shopping research, ChatGPT merchants, ChatGPT Ads attribution
run_yca_005yc-arbitragepartial55-opp_yca_010의 공개 buyer-language 보강 스윕. Reddit DigitalMarketing/GoogleAnalytics 공개 스레드에서 GA4 attribution gap, Direct 오분류,
run_yca_014yc-arbitragepartial11-OpenAI Presence 공식 발표를 신규 seed로 평가. enterprise AI agent production workflow, policies, guardrails, simulations, evaluati
run_yca_015yc-arbitragepartial830-30 online-only probes across OpenAI product discovery, ChatGPT shopping research, ChatGPT Ads, OpenAI Ads developer docs
run_yca_016yc-arbitragepartial840urlsFirst 40 of 50 breakthrough online probes. Split because yc-arbitrage cap is 40 urls per run. Focus: YC RFS, AI agent in
run_yca_017yc-arbitragepartial510-Remaining 10 of 50 breakthrough online probes after run_yca_016 hit the 40-url cap. Focus: AI visibility pricing, Korea
run_yca_018yc-arbitragepartial612-2026-07-31 KST lead recheck. Used latest public signals from ChatGPT merchant product feeds, OpenAI Ads, OpenAI Ads deve
run_yca_019yc-arbitragepartial88urls_user_requested_50_opportunities_from_8_sourcesUser requested 50 more breakthrough opportunities. Kept within source cap by deriving multiple candidate opportunities f
run_yca_020yc-arbitragepartial818requested_batch_size_onlyOnline-only sweep for 50 additional breakthrough candidates. No customer outreach or approvals; candidates use allowlist
run_yca_021yc-arbitragepartial812requested_batch_size_onlyOnline-only sweep for 50 additional breakthrough candidates. No customer outreach or approvals; candidates use allowlist
run_yca_022yc-arbitragepartial810requested_batch_size_onlyOnline-only sweep for 50 additional breakthrough candidates. No customer outreach or approvals; candidates use public so
run_yca_023yc-arbitragepartial814requested_batch_size_onlyOnline-only sweep for 50 additional breakthrough candidates after run_yca_022. Focus: ChatGPT Ads/ACP execution, agentic
run_yca_024yc-arbitragecomplete830-
run_yca_025yc-arbitragecomplete46-
run_yca_026yc-arbitragecomplete88-
run_yca_027yc-arbitragecomplete88-Public-web sweep for 50 additional breakthrough opportunities around agentic operations, governance, payments, healthcar
run_yca_028yc-arbitragecomplete1616-Public-web sweep for 50 additional breakthrough opportunities around agent identity, AI governance, agentic commerce lia
run_yca_029yc-arbitragecomplete2424-Public-web sweep for 50 additional high-variance opportunities across AI-agent identity, agentic commerce/payment risk,
run_yca_030yc-arbitragecomplete88-Public-web sweep for 50 additional high-variance opportunities using YC RFS, OpenAI agentic commerce/payment/governance
run_yca_031yc-arbitragepartial88-Public web only: YC RFS, YC directory/company pages, OpenAI commerce docs. No customer contact; buyer receipts remain 0/
run_yca_032yc-arbitragepartial88-Public web only: OpenAI commerce docs, checkout/payment commentary, card-network agent-payment pages, retail-media clean
run_yca_033yc-arbitragepartial1010-Public web only: agentic commerce/payment, MCP security, AI-search attribution and retail-media clean-room signals. No c
run_yca_034yc-arbitragepartial45-
run_yca_035yc-arbitragepartial56-
run_yca_036yc-arbitragepartial44-

기회 원장 (최신 상태)

기회 원장 (최신 상태)
oppmethod합계근거상태사유
opp_ng_001naver-geo18completeapproveddeep-research 갱신: channel 3→4(구매자 검색어 '노출 안됨' 실증), conversion 3→4(US Rufus 대응 서비스 판매 실증 + KR 직접경쟁 존재). 근거 rese
opp_ng_002naver-geo16completeapproved사용자 승인 (2026-07-25)
opp_ng_003naver-geo9zeroheld스코어카드 합계 9 < 12 자동 보류 + 직접 발화 근거 zero — 셀러 수동 캡처 후 재평가
opp_ng_004naver-geo13partialcandidatebuyer-language receipt — 카피 근거용 (deep-research Pass 1)
opp_ng_005naver-geo18completeapproved사용자 지시로 랜딩 카피 반영 — AI탭은 '곧 출시'가 아니라 이미 정식 출시(2026-06)임을 확인, 프레임 수정
opp_yca_001yc-arbitrage18partialcandidate운영자 확인 2건(2026-07-26). (1) Dct-Geo 고객 10개사에 건기식·화장품 셀러는 없다 → 셀러 세그먼트에 대한 즉시 도달 경로가 없음이 확정. channel 3 유지(올릴 근거
opp_yca_002yc-arbitrage19partialcandidate2026-07-26 재평가. Timing 4→5: ACP는 OpenAI/Stripe가 유지하는 beta spec이고 GitHub issue가 2026-07에도 활발하다. Digital Applied
opp_yca_003yc-arbitrage20partialcandidate2026-07-26 재평가. 선행시장 카테고리 성립 확인: AI search visibility / LLMO monitoring 도구 비교·가격 글이 다수 존재하고, Peec AI·Profound
opp_yca_004yc-arbitrage7partialheld스코어카드 합계 7 < 15 자동 보류 유지. 공개 웹 3계층에서 구매자 어휘 7건을 URL과 함께 확보했으나 captured_by가 agent라 copy_rule의 manual ≥3 게이트는 여전
opp_yca_005yc-arbitrage-completecandidate브라우저 세션 캡처(robots-policy 4-b, 운영자 상시 지시). 비로그인 공개 페이지 1건. 게시 2025-05-08, 조회 1,166, 좋아요 4, 댓글 1. 작성자는 병원 마케팅 대행
opp_yca_006yc-arbitrage-completecandidate브라우저 세션 캡처(robots-policy 4-b). 비로그인 공개 페이지 1건. 작성자는 상세페이지 제작사. 가격 앵커 확보가 중요하다 — 심의비 2~5만원/건이 우리 제품 가격의 상한 기준선이
opp_yca_007yc-arbitrage-completecandidate브라우저 세션 캡처(robots-policy 4-b). 자유게시판 1건 + 관련글 제목. 게시 2025-05-27, 조회 937, 좋아요 5, 댓글 3. 이 receipt는 기회에 불리한 증거다
opp_yca_008yc-arbitrage-completecandidate브라우저 세션 캡처(4-b). 의료 대행사 3유형으로 분해했고 셋 다 도구를 살 유인이 약하다. (1) 대형·전문(하룹): 자체 AI 검수 보유 = 반증 ④ 그대로. (2) 숙련 전략형(리드유컴퍼니
opp_yca_009yc-arbitrage-completecandidate브라우저 세션 캡처(4-b) 2건 + 검색 2회. 판정: ④·⑥은 통과, 그러나 오퍼가 안 맞는다. (a) ④ 통과 — 셀러가 자체 AI 검수를 구축한다는 근거 없음. (b) ⑥ 통과 — 셀
opp_yca_010yc-arbitrage22partialcandidateConversion 4: 공개 커뮤니티에 'gaps in attribution and visibility', 'trying to report on AI through GA4', 'Direct has
opp_yca_011yc-arbitrage22partialcandidateTiming 5: OpenAI 공식 자료가 ChatGPT Ads 테스트, CPC bidding, 구매·관리 방식 확장, 결과 측정 개발을 명시한다. Growth ladder: 제도/플랫폼 공식화(4
opp_yca_012yc-arbitrage20partialcandidateTiming 5: YC Anglera는 e-commerce product data enrichment agent를 전면에 내세우고, 국내 아이보스 공개 글도 스마트스토어/쿠팡 상세페이지·검색 데이터
opp_yca_013yc-arbitrage22partialcandidateLatest check: OpenAI 공식 자료는 ads test/원칙을 제시하고, OpenAI Ads developer docs는 Pixel, CAPI, product feeds, conversi
opp_yca_014yc-arbitrage19partialcandidateTiming 5: OpenAI가 Apps SDK, plugin submission, Instant Checkout, Target/Instacart 같은 commerce app 파트너십을 공개했다.
opp_yca_015yc-arbitrage16partialcandidateTiming 5: OpenAI가 2026-07-22 Presence를 발표하며 production agent에 필요한 정책, 승인, escalation, simulation, evaluation,
opp_yca_016yc-arbitrage21partialcandidateOpenAI product discovery and shopping research make product attributes, comparisons, freshness, and merchant-o
opp_yca_017yc-arbitrage21partialcandidateThis is adjacent to opp_yca_013 but narrower: not installation, but pre-scale signal QA for conversion-optimiz
opp_yca_018yc-arbitrage19partialcandidateThis is a correction/extension to opp_yca_010. If native GA4 channel solves enough, standalone value drops; if
opp_yca_019yc-arbitrage16partialcandidateApps SDK is a real platform signal, but Docenty's current channel is closer to attribution and merchant feed r
opp_yca_020yc-arbitrage18partialcandidatePricing proves a diagnostic category exists, but arbitrage is weaker because tools are public and internationa
opp_yca_021yc-arbitrage20partialcandidateBreakthrough angle: not building another agent, but selling the trust/procurement evidence layer agents need.
opp_yca_022yc-arbitrage19partialcandidateStrong platform signal but not directly tied to Docenty commerce channel. Use as adjacent upsell only if exist
opp_yca_023yc-arbitrage18partialcandidateBreakthrough if private MCP apps become common in Enterprise/Edu. Needs buyer evidence from IT/security admins
opp_yca_024yc-arbitrage21partialcandidateLatest recheck: OpenAI merchant page says product feeds give merchants more control over how products appear a
opp_yca_025yc-arbitrage17partialcandidateLatest recheck: merchant-owned checkout direction keeps trust policy relevant but too early. This receipt inte
opp_yca_026yc-arbitrage20partialcandidateStrong Korean regulatory timing. Channel is not the current commerce/GEO wedge, but useful if Docenty sells AI
opp_yca_027yc-arbitrage22partialcandidate2026-07-31 KST recheck: public regulation signals around AI-generated virtual experts in cosmetics/food advert
opp_yca_028yc-arbitrage20partialcandidateBreakthrough candidate; feed schema is stable enough for implementation services, but no buyer receipt yet.
opp_yca_029yc-arbitrage20partialcandidateStrong technical pain hypothesis; buyer willingness unverified.
opp_yca_030yc-arbitrage18partialcandidateTrust-policy wedge is timely but may be too early for Korean merchants.
opp_yca_031yc-arbitrage19partialcandidateClear implementation gap, but value depends on merchant access to commerce feeds.
opp_yca_032yc-arbitrage19partialcandidatePotentially valuable but requires prompt monitoring and merchant margin data.
opp_yca_033yc-arbitrage22partialcandidateVery close to opp_yca_013; keep as sharper implementation variant, not a separate approval yet.
opp_yca_034yc-arbitrage18partialcandidateConcrete developer pain from CAPI batch semantics; buyer budget unverified.
opp_yca_035yc-arbitrage21partialcandidateGood packaging of existing 011/013 signals; no paid intent receipt yet.
opp_yca_036yc-arbitrage20partialcandidateAmbitious bundle; needs proof that buyers want combined content plus measurement.
opp_yca_037yc-arbitrage18partialcandidateServices/legal-adjacent wedge; buyer unknown.
opp_yca_038yc-arbitrage22partialcandidateStrong channel fit, but overlaps 024/028; keep as service packaging candidate.
opp_yca_039yc-arbitrage20partialcandidateClear recurring ops shape; willingness to pay unknown.
opp_yca_040yc-arbitrage17partialcandidateImportant future pain; may be premature until checkout volume exists.
opp_yca_041yc-arbitrage20partialcandidateBridge between commerce feed and regulated claim linting; no direct buyer receipt yet.
opp_yca_042yc-arbitrage22partialcandidateSubsegment of opp_yca_027 with sharper buyer and rule source; should be tested as 027 vertical.
opp_yca_043yc-arbitrage22partialcandidateStrong 027 vertical; needs buyer quote from cosmetics performance marketers.
opp_yca_044yc-arbitrage20partialcandidateRegulatory timing is strong; commercial owner may be platform, agency or brand.
opp_yca_045yc-arbitrage19partialcandidateConcrete compliance UX problem; needs legal interpretation and buyer confirmation.
opp_yca_046yc-arbitrage20partialcandidateHigh-risk vertical, but may require stronger domain/legal partnership.
opp_yca_047yc-arbitrage20partialcandidateUseful if marketplace policy data can be collected safely; no validation yet.
opp_yca_048yc-arbitrage21partialcandidateYC compliance infrastructure plus Korean AI/regulatory signal; direct buyer unverified.
opp_yca_049yc-arbitrage20partialcandidateStrong data-product wedge if regulations can be maintained; validation needed.
opp_yca_050yc-arbitrage18partialcandidateRelevant to deceptive AI content; data access and buyer owner unclear.
opp_yca_051yc-arbitrage19partialcandidateDeveloper/evaluator wedge; may be too tooling-centric without agency buyer proof.
opp_yca_052yc-arbitrage18partialcandidateRegulatory timing strong; less adjacent to current commerce assets than 010/027.
opp_yca_053yc-arbitrage17partialcandidateLarge compliance category, but not tightly connected to current channel.
opp_yca_054yc-arbitrage18partialcandidateClear timing, but buyer segmentation still broad.
opp_yca_055yc-arbitrage16partialcandidateBroad governance need; weak immediate channel.
opp_yca_056yc-arbitrage19partialcandidateUseful operational ambiguity resolver; direct willingness unknown.
opp_yca_057yc-arbitrage15partialcandidateInteresting but may be displaced by free support desk resources.
opp_yca_058yc-arbitrage17partialcandidateYC compliance infra signal plus Korean law timing; channel uncertain.
opp_yca_059yc-arbitrage17partialcandidateB2B procurement wedge; current team channel unclear.
opp_yca_060yc-arbitrage19partialcandidateRecurring monitoring shape, but needs agency buyer proof.
opp_yca_061yc-arbitrage19partialcandidateConcrete evidence-retention wedge; no buyer receipt.
opp_yca_062yc-arbitrage16partialcandidateYC RFS strong, but broad platform build outside current commerce focus.
opp_yca_063yc-arbitrage19partialcandidateStrong fit with this repo and ADR 0012; external buyer unverified.
opp_yca_064yc-arbitrage17partialcandidateRFS aligns, but requires product build beyond current wedge.
opp_yca_065yc-arbitrage16partialcandidateYC calls out self-maintaining APIs directly; channel to Korean SaaS teams unknown.
opp_yca_066yc-arbitrage19partialcandidateCombines multiplayer AI and compliance, but buyer pain unverified.
opp_yca_067yc-arbitrage12partialheldBreakthrough market but far from current assets and channel.
opp_yca_068yc-arbitrage12partialheldLarge RFS market but too far from current channel.
opp_yca_069yc-arbitrage14partialheldBig opportunity but outside current assets and requires child-safety expertise.
opp_yca_070yc-arbitrage12partialheldHuge demographic trend but no current distribution channel.
opp_yca_071yc-arbitrage16partialcandidateImportant trust layer; very hard and not near-term for current team.
opp_yca_072yc-arbitrage13partialheldSpeculative and far from current channel.
opp_yca_073yc-arbitrage20partialcandidateStrong bridge between disclosure compliance and campaign ops; no buyer receipt.
opp_yca_074yc-arbitrage22partialcandidatePossibly the strongest new package around 027; validate with agency buyer before promotion.
opp_yca_075yc-arbitrage22partialcandidateVery close to opp_yca_010 and likely the best agency packaging of the lead.
opp_yca_076yc-arbitrage20partialcandidateConcrete and adjacent; needs proof that catalog gaps block discovery enough to pay.
opp_yca_077yc-arbitrage21partialcandidateStrong bridge between GEO monitoring and regulated claim risk; no customer receipt yet.
opp_yca_078yc-arbitrage22partialcandidateStrong extension of the current lead; still no direct buyer receipt.
opp_yca_079yc-arbitrage22partialcandidateOfficial ChatGPT Ads measurement direction makes this concrete; buyer willingness unverified.
opp_yca_080yc-arbitrage21partialcandidateRevenue proof language is strong, but the estimator must be validated against real logs.
opp_yca_081yc-arbitrage21partialcandidateGood agency-retainer packaging; needs access to client analytics and CRM data.
opp_yca_082yc-arbitrage22partialcandidateProduct-feed ad rollout makes a narrowly scoped audit sellable; customer receipt still absent.
opp_yca_083yc-arbitrage20partialcandidateHigher-value analytics wedge, but requires ad spend and experiment discipline.
opp_yca_084yc-arbitrage20partialcandidateConcrete QA surface; buyer budget depends on ad volume.
opp_yca_085yc-arbitrage20partialcandidateImplementation wedge is clear; needs proof image QA is painful enough to pay.
opp_yca_086yc-arbitrage20partialcandidateGood operations product, but value must be tied to traffic or ad spend.
opp_yca_087yc-arbitrage20partialcandidateOpenAI merchant-owned checkout direction strengthens this; buyer urgency unknown.
opp_yca_088yc-arbitrage17partialcandidateInteresting post-purchase analytics angle; may be premature until traffic scales.
opp_yca_089yc-arbitrage22partialcandidateVery concrete implementation pain and close to existing analytics assets; no paid receipt yet.
opp_yca_090yc-arbitrage22partialcandidateRevenue-value setup is a stronger pain than basic pageview tracking; buyer validation missing.
opp_yca_091yc-arbitrage20partialcandidateCompliance-adjacent measurement pain; needs privacy/legal boundary review.
opp_yca_092yc-arbitrage21partialcandidateGood repositioning away from commodity visibility tools; must validate data availability.
opp_yca_093yc-arbitrage19partialcandidateClear brand-risk and margin-risk hypothesis; monitoring reliability uncertain.
opp_yca_094yc-arbitrage20partialcandidateStrong infrastructure layer for the regulated preflight challenger; buyer owner unknown.
opp_yca_095yc-arbitrage22partialcandidateSharp vertical around current Korean enforcement signals; still needs agency/brand price receipt.
opp_yca_096yc-arbitrage22partialcandidateVery concrete regulated-commerce implementation; buyer receipt absent.
opp_yca_097yc-arbitrage18partialcandidateUseful but data access may be hard; keep as challenger add-on.
opp_yca_098yc-arbitrage22partialcandidateCombines YC compliance ops with Korean regulated-ad timing; no buyer receipt.
opp_yca_099yc-arbitrage21partialcandidateStrong trust deliverable, but customer willingness must be tested.
opp_yca_100yc-arbitrage20partialcandidateHigh-value risk framing but may need insurer/legal partner.
opp_yca_101yc-arbitrage22partialcandidatePain is closer to urgent revenue blockage than generic compliance; no buyer receipt yet.
opp_yca_102yc-arbitrage20partialcandidatePreventive workflow is attractive, but buyers may prefer after-the-fact review.
opp_yca_103yc-arbitrage19partialcandidateCommercially interesting bridge between compliance and performance; validation needed.
opp_yca_104yc-arbitrage18partialcandidateRegulatory timing is real but channel is less clear than agencies/commerce.
opp_yca_105yc-arbitrage18partialcandidatePotentially large but broad; no near-term commerce channel.
opp_yca_106yc-arbitrage16partialcandidatePotentially high-ticket but channel and legal partnership are unclear.
opp_yca_107yc-arbitrage18partialcandidateB2B workflow is plausible; buyer urgency unproven.
opp_yca_108yc-arbitrage20partialcandidateRecurring ops shape; no proof agencies pay for policy monitoring yet.
opp_yca_109yc-arbitrage21partialcandidateStrong fit with this repo's dashboard policy and agent-workflow trend; external buyer receipt missing.
opp_yca_110yc-arbitrage18partialcandidateVery close to internal agent-ops assets, but broad market validation needed.
opp_yca_111yc-arbitrage19partialcandidateStrong productization of a real operational rule; no buyer receipts.
opp_yca_112yc-arbitrage18partialcandidateSecurity-governance pain is plausible; channel uncertain.
opp_yca_113yc-arbitrage22partialcandidateStrong agency workflow wedge; still no customer receipt.
opp_yca_114yc-arbitrage22partialcandidateHigh conversion usefulness if agencies fight clients on risky claims; buyer validation needed.
opp_yca_115yc-arbitrage19partialcandidateClear content-ops pain, but hard to prove before AI referral volume exists.
opp_yca_116yc-arbitrage20partialcandidateGood margin optimization hypothesis; no proof of immediate buyer pain.
opp_yca_117yc-arbitrage22partialcandidateStrong Korea-first implementation wedge; platform-specific integration proof needed.
opp_yca_118yc-arbitrage20partialcandidateGood bridge between ads, feeds and compliance; buyer validation absent.
opp_yca_119yc-arbitrage22partialcandidateVery actionable agency artifact; no real client negotiation receipt yet.
opp_yca_120yc-arbitrage19partialcandidateMore sophisticated analytics wedge; likely later than basic budget-defense report.
opp_yca_121yc-arbitrage22partialcandidateStrong revenue proof implementation for non-instant-purchase funnels; validation needed.
opp_yca_122yc-arbitrage21partialcandidatePotentially strong for local/service businesses, but current lead is still agency-first.
opp_yca_123yc-arbitrage22partialcandidateRecurring operational pain; direct API failure examples still needed.
opp_yca_124yc-arbitrage22partialcandidateCould be sold immediately as a workshop/checklist package; no customer receipt.
opp_yca_125yc-arbitrage21partialcandidateSimple and explainable; must avoid implying guaranteed ChatGPT ranking control.
opp_yca_126yc-arbitrage21partialcandidatePowerful bridge of commerce and compliance lanes; no buyer receipt yet.
opp_yca_127yc-arbitrage22partialcandidateThe boldest bundling of the best lanes; too broad for first sale, but useful as north-star package.
opp_yca_128yc-arbitrage22partialcandidateVery close to an urgent launch-room blocker; no buyer receipt yet.
opp_yca_129yc-arbitrage22partialcandidateConcrete implementation pain; needs proof agencies will pay separately rather than bundle into setup.
opp_yca_130yc-arbitrage22partialcandidateOperational retainer surface is strong; direct failure examples still needed.
opp_yca_131yc-arbitrage22partialcandidateSellable diagnostic for agencies; buyer willingness unverified.
opp_yca_132yc-arbitrage22partialcandidateClose to launch urgency, but may be too narrow unless packaged with Launch Room.
opp_yca_133yc-arbitrage20partialcandidateSecurity need is explicit but may require deeper trust and dev access.
opp_yca_134yc-arbitrage22partialcandidateJuly 2026 API change makes it timely; buyer pain not yet proven.
opp_yca_135yc-arbitrage22partialcandidateStrong reporting surface; needs real advertiser spend to validate.
opp_yca_136yc-arbitrage22partialcandidateA crisp catalog-ops wedge; needs access to ad insights and feed data.
opp_yca_137yc-arbitrage20partialcandidateUseful regional arbitrage report; immediate channel is narrower than agency Launch Room.
opp_yca_138yc-arbitrage20partialcandidateGood ops product for agencies at scale; may be too early for Korean SMB advertisers.
opp_yca_139yc-arbitrage22partialcandidateClear retainer-shaped reporting pain; needs real spend receipt.
opp_yca_140yc-arbitrage22partialcandidateGovernance need is plausible; no buyer receipt.
opp_yca_141yc-arbitrage22partialcandidateVery close to paid reporting value; customer receipt absent.
opp_yca_142yc-arbitrage22partialcandidateA useful preflight gate but may be perceived as analysis rather than implementation.
opp_yca_143yc-arbitrage22partialcandidateSharp launch-risk item; buyer validation missing.
opp_yca_144yc-arbitrage22partialcandidateHighly concrete; no direct buyer receipt.
opp_yca_145yc-arbitrage22partialcandidateOperationally strong but needs agency willingness to pay for governance.
opp_yca_146yc-arbitrage22partialcandidateVery practical implementation wedge; no real client receipt.
opp_yca_147yc-arbitrage22partialcandidateStrong for clinics, education and B2B; buyer channel still unvalidated.
opp_yca_148yc-arbitrage22partialcandidateClear vertical event mapping; regulated claims make execution sensitive.
opp_yca_149yc-arbitrage22partialcandidateRevenue-quality pain is plausible; implementation details need validation.
opp_yca_150yc-arbitrage22partialcandidateGood retention and upsell module; not the first sale.
opp_yca_151yc-arbitrage21partialcandidateUseful but probably bundled, not standalone.
opp_yca_152yc-arbitrage20partialcandidateStrategic commerce surface is real; near-term buyer urgency may lag ads setup.
opp_yca_153yc-arbitrage20partialcandidateStrong recurring catalog ops; traffic scale still uncertain.
opp_yca_154yc-arbitrage20partialcandidateUseful but copywriting can commoditize unless tied to feed quality and compliance.
opp_yca_155yc-arbitrage22partialcandidateExcellent strategic extension of revenue proof; still depends on access and merchant adoption.
opp_yca_156yc-arbitrage20partialcandidateGood catalog wedge; needs proof variants cause support or lost-sales pain.
opp_yca_157yc-arbitrage20partialcandidateCommercially tangible but narrower than full Launch Room.
opp_yca_158yc-arbitrage21partialcandidateStrong bridge between commerce and compliance; no buyer receipt.
opp_yca_159yc-arbitrage22partialcandidateVery practical end-to-end QA; still needs merchant access validation.
opp_yca_160yc-arbitrage20partialcandidateIncident workflow is useful but depends on observed traffic/issues.
opp_yca_161yc-arbitrage19partialcandidateInteresting margin-risk angle but likely later-stage.
opp_yca_162yc-arbitrage22partialcandidateEnforcement signal is strong; needs agency/brand price receipt.
opp_yca_163yc-arbitrage22partialcandidateConcrete enforcement example; buyer validation absent.
opp_yca_164yc-arbitrage22partialcandidateStrong operational pain if incidents happen; no direct receipt.
opp_yca_165yc-arbitrage20partialcandidateRecurring service shape; willingness to pay for monitoring alone unproven.
opp_yca_166yc-arbitrage20partialcandidateLarge problem but requires careful platform/legal workflow.
opp_yca_167yc-arbitrage18partialcandidateHigh pain but collection may hit platform access and legal boundaries.
opp_yca_168yc-arbitrage17partialcandidatePotentially high-ticket but legal channel unclear.
opp_yca_169yc-arbitrage18partialcandidateStrategically interesting but farther from current agency/ads wedge.
opp_yca_170yc-arbitrage17partialcandidateYC physical-world software signal is strong but far from current commerce assets.
opp_yca_171yc-arbitrage17partialcandidateGood agent-ops governance shape; channel unvalidated.
opp_yca_172yc-arbitrage13partialheldInteresting but too far from current channel and assets; keep as watchlist.
opp_yca_173yc-arbitrage17partialcandidatePotentially sellable but outside current buyer cluster.
opp_yca_174yc-arbitrage19partialcandidateStrong agent-governance idea; less direct than current commerce first-sale.
opp_yca_175yc-arbitrage19partialcandidateClose to internal workflow assets but external buyer unproven.
opp_yca_176yc-arbitrage21partialcandidateStrong bridge between marketing ops and agent governance; no buyer receipt.
opp_yca_177yc-arbitrage22partialcandidateVery aligned with current local-only dashboard discipline; buyer validation absent.
opp_yca_178yc-arbitrage22partialcandidateStrong schema-to-ops wedge; no buyer receipt yet.
opp_yca_179yc-arbitrage22partialcandidateA tiny but expensive launch blocker; must prove agencies pay separately.
opp_yca_180yc-arbitrage22partialcandidateRetainer-shaped operational pain; still missing customer language.
opp_yca_181yc-arbitrage21partialcandidateClose to catalog enrichment work; buyer urgency unverified.
opp_yca_182yc-arbitrage21partialcandidateLocalization wedge is plausible but public evidence is indirect.
opp_yca_183yc-arbitrage22partialcandidateActionable Ads API surface; customer willingness still unknown.
opp_yca_184yc-arbitrage22partialcandidateVery concrete launch blocker; needs proof it is not solved by platform UI.
opp_yca_185yc-arbitrage21partialcandidateImplementation service surface; may be replaced by feed apps for Shopify.
opp_yca_186yc-arbitrage22partialcandidateStrong retainer/reporting use case; direct buyer quote missing.
opp_yca_187yc-arbitrage22partialcandidatePain likely appears immediately after launch; still public-only.
opp_yca_188yc-arbitrage22partialcandidateDirectly supported by public endpoint shape; buyer validation absent.
opp_yca_189yc-arbitrage19partialcandidateApplication workflow is public, but willingness to pay is uncertain.
opp_yca_190yc-arbitrage22partialcandidateRevenue-facing feed cleanup; direct demand still unproven.
opp_yca_191yc-arbitrage22partialcandidateExplicit docs-supported failure-prevention step; no buyer receipt yet.
opp_yca_192yc-arbitrage22partialcandidateDocuments warn about volume, but threshold must be validated.
opp_yca_193yc-arbitrage22partialcandidateHigh-leverage attribution issue; public evidence is technical not buyer language.
opp_yca_194yc-arbitrage22partialcandidateCommon measurement pattern by analogy; OpenAI-specific buyer proof missing.
opp_yca_195yc-arbitrage20partialcandidateImportant governance item; procurement cycle may be slower.
opp_yca_196yc-arbitrage21partialcandidateExisting open-source tag shows implementation pattern; buyer validation required.
opp_yca_197yc-arbitrage18partialcandidateTechnically real but less adjacent to current Dct assets.
opp_yca_198yc-arbitrage22partialcandidateSmall but measurable source of reporting errors; buyer urgency unknown.
opp_yca_199yc-arbitrage22partialcandidateDirectly linked to irreversible campaign goal setup; unvalidated commercially.
opp_yca_200yc-arbitrage22partialcandidateExcellent agency governance artifact; buyer proof missing.
opp_yca_201yc-arbitrage22partialcandidateDocs prefer CAPI where possible; willingness to pay unproven.
opp_yca_202yc-arbitrage22partialcandidateBroadly reusable; must avoid becoming generic consulting.
opp_yca_203yc-arbitrage22partialcandidateVery adjacent to regulated lead-gen; no direct customer quote.
opp_yca_204yc-arbitrage22partialcandidateRetainer-shaped but must be validated by budget owners.
opp_yca_205yc-arbitrage20partialcandidateOperational security need; slower sale than revenue proof.
opp_yca_206yc-arbitrage22partialcandidateDirect docs workflow; commercial value depends on launch complexity.
opp_yca_207yc-arbitrage22partialcandidateStrong dashboard module; buyer validation absent.
opp_yca_208yc-arbitrage21partialcandidateNarrow but prevents costly errors; no buyer proof.
opp_yca_209yc-arbitrage21partialcandidateImplementation-specific; likely bundled.
opp_yca_210yc-arbitrage22partialcandidateGood operational tool if product catalogs are large enough.
opp_yca_211yc-arbitrage19partialcandidateVery narrow; useful only in broader QA bundle.
opp_yca_212yc-arbitrage22partialcandidateOps retainer wedge; direct demand unvalidated.
opp_yca_213yc-arbitrage22partialcandidateReporting budget exists by analogy; buyer proof missing.
opp_yca_214yc-arbitrage20partialcandidateReal 403/error surface; must test frequency with agencies.
opp_yca_215yc-arbitrage22partialcandidateVery close to opp_yca_010/124; buyer receipt missing.
opp_yca_216yc-arbitrage22partialcandidateHigh relevance to current thesis; no new buyer evidence.
opp_yca_217yc-arbitrage22partialcandidateOperationally useful, but public docs do not prove paid demand.
opp_yca_218yc-arbitrage22partialcandidateGood reporting product; customer proof absent.
opp_yca_219yc-arbitrage21partialcandidateBuyer is senior and budget-owning; sales cycle unknown.
opp_yca_220yc-arbitrage22partialcandidateHighly aligned with current package; direct demand still absent.
opp_yca_221yc-arbitrage21partialcandidateKorea-local wedge is plausible; source is global, not Korea-specific.
opp_yca_222yc-arbitrage21partialcandidateStrong adjacency to existing regulated-content thesis; needs current KR regulation receipts.
opp_yca_223yc-arbitrage21partialcandidateNeeds fresh KR regulatory proof before scoring higher.
opp_yca_224yc-arbitrage22partialcandidateVery sellable packaging; buyer validation still zero.
opp_yca_225yc-arbitrage22partialcandidateNatural buying artifact for pilots; no buyer receipt.
opp_yca_226yc-arbitrage22partialcandidateStrong sales-enablement shape; must validate RFP frequency.
opp_yca_227yc-arbitrage22partialcandidateUseful to protect pricing against tooling substitutes; buyer receipt missing.
opp_yca_228yc-arbitrage22partialcandidateOpenAI names beta self-serve, budgets and performance portal; buyer willingness still unverified.
opp_yca_229yc-arbitrage22partialcandidateCPC bidding is explicit; conversion economics must be validated with buyers.
opp_yca_230yc-arbitrage21partialcandidatePartner ecosystem and self-serve coexist; migration pain is plausible but indirect.
opp_yca_231yc-arbitrage21partialcandidateStrong positioning shift from keyword ads; may be bundled into creative service.
opp_yca_232yc-arbitrage21partialcandidatePublic policy/ads messaging supports need; paid demand not proven.
opp_yca_233yc-arbitrage21partialcandidateOperational need is clear from portal workflow; direct buyer receipt absent.
opp_yca_234yc-arbitrage20partialcandidateAPI and Ads Manager expose bulk/campaign resources; commercial pain is implementation-specific.
opp_yca_235yc-arbitrage22partialcandidateACP has product/promotions surfaces; buyer urgency unvalidated.
opp_yca_236yc-arbitrage22partialcandidateImplementation specificity high; buyer proof missing.
opp_yca_237yc-arbitrage22partialcandidateReporting terms are visible; paid value depends on client-facing pressure.
opp_yca_238yc-arbitrage20partialcandidatePolicy surface is current; regulated buyer demand needs receipts.
opp_yca_239yc-arbitrage20partialcandidateLaunch failure modes are plausible; direct paid pain unproven.
opp_yca_240yc-arbitrage21partialcandidateDelegated payment spec creates concrete compliance steps; approved-partner access limits near-term volume.
opp_yca_241yc-arbitrage21partialcandidateSpec explicitly assigns merchant responsibilities; buyer budget unknown.
opp_yca_242yc-arbitrage18partialcandidateTechnically sharp but narrower channel than current commerce/ads buyer.
opp_yca_243yc-arbitrage21partialcandidatePayment flow implies reconciliation work; direct merchant receipt missing.
opp_yca_244yc-arbitrage20partialcandidateApplication flow exists but access gate may reduce current demand.
opp_yca_245yc-arbitrage18partialcandidateLocale headers are visible; Korea-specific demand is inferred.
opp_yca_246yc-arbitrage21partialcandidateOpenAI positions merchant-owned fulfillment; support pain plausible.
opp_yca_247yc-arbitrage22partialcandidateCombines ACP and GA4 AI channel shift; still no buyer receipt.
opp_yca_248yc-arbitrage20partialcandidateCompliance/responsibility need is public but reactive demand uncertain.
opp_yca_249yc-arbitrage20partialcandidateStrong synthesis; direct Korean exporter demand missing.
opp_yca_250yc-arbitrage21partialcandidateMCP Apps UI standard and ChatGPT/Codex plugin path are official; buyer channel less immediate than ads.
opp_yca_251yc-arbitrage20partialcandidateImplementation surface is concrete; buyer frequency unknown.
opp_yca_252yc-arbitrage21partialcandidateAuth guidance is explicit; paid demand plausible for SaaS.
opp_yca_253yc-arbitrage21partialcandidateOpenAI docs explicitly warn about prompt injection risk in MCP; buyer validation missing.
opp_yca_254yc-arbitrage21partialcandidateDocs recommend caution around unofficial MCP servers; procurement value plausible.
opp_yca_255yc-arbitrage19partialcandidateOfficial docs mention secure tunnel; channel to buyers is narrower.
opp_yca_256yc-arbitrage21partialcandidateApproval-mode distinction is official; buyer pain needs validation.
opp_yca_257yc-arbitrage19partialcandidateSafety warning is explicit; may be free docs rather than paid service.
opp_yca_258yc-arbitrage19partialcandidateSpecific to app publication; direct paid demand unproven.
opp_yca_259yc-arbitrage19partialcandidateRisk is explicit; incident-response buying trigger is speculative.
opp_yca_260yc-arbitrage21completecandidateHard public deadline makes this unusually concrete; buyer base size unknown.
opp_yca_261yc-arbitrage21completecandidateHard sunset and migration guide exist; direct customer list missing.
opp_yca_262yc-arbitrage21completecandidateOfficial migration path and shutdown date are clear; buyer access must be validated.
opp_yca_263yc-arbitrage21partialcandidateMigration doc explicitly requires review/test; willingness to pay is likely but unverified.
opp_yca_264yc-arbitrage20partialcandidateDocs reference migration path; specific replacement choice may vary.
opp_yca_265yc-arbitrage21completecandidateMultiple deprecations on one timeline create inventory need; implementation may require account access.
opp_yca_266yc-arbitrage18completecandidateHard date exists; domain fit weaker than ads/agents.
opp_yca_267yc-arbitrage21completecandidateDeadline and multi-client operations fit agencies; buyer receipt absent.
opp_yca_268yc-arbitrage22partialcandidateSEJ reports GA4 channel change and recognized assistants; buyer demand still public-only.
opp_yca_269yc-arbitrage22partialcandidateGA4 reporting change creates a report-break event; direct buyer proof missing.
opp_yca_270yc-arbitrage22partialcandidateStrong synthesis of Ads, ACP and GA4 AI channel; still no buyer receipt.
opp_yca_271yc-arbitrage21partialcandidateKnown-list gap is explicit in reporting coverage; may be too small standalone.
opp_yca_272yc-arbitrage22partialcandidateReport discontinuity is real; paid memo demand unverified.
opp_yca_273yc-arbitrage21partialcandidateMFDS regulations and product-feed fields align; buyer proof missing.
opp_yca_274yc-arbitrage21partialcandidateRegulatory source is broad but current; needs cosmetics-specific Korean receipts.
opp_yca_275yc-arbitrage19partialcandidateRegulated device source exists; sales channel less direct.
opp_yca_276yc-arbitrage19partialcandidateImport food regulations are visible; buyer urgency uncertain.
opp_yca_277yc-arbitrage21partialcandidateStrong combined regulated/ads wedge; still buyer 0/3.
opp_yca_278yc-arbitrage20partialcandidateStable/Draft distinction is public; buyer urgency is inferred from implementation risk.
opp_yca_279yc-arbitrage21partialcandidateFile-upload production path is explicit; willingness to pay unverified.
opp_yca_280yc-arbitrage22partialcandidateOpenAI highlights richer visual product discovery; paid audit demand still proxy-only.
opp_yca_281yc-arbitrage21partialcandidateComparison fields are consumer-facing; evidence sourcing needs buyer validation.
opp_yca_282yc-arbitrage22partialcandidateStructured product feed need is official; pain concentrates in complex catalogs.
opp_yca_283yc-arbitrage22partialcandidateFeed docs emphasize accurate pricing and availability; buyer receipts missing.
opp_yca_284yc-arbitrage21partialcandidatePromotion/feed alignment is implied by feed and ads surfaces; paid pain unverified.
opp_yca_285yc-arbitrage22partialcandidateStructured catalog plus global product discovery make localization risk plausible; buyer validation absent.
opp_yca_286yc-arbitrage21partialcandidatePolicy and feed surfaces are public; regulated buyer payment proof missing.
opp_yca_287yc-arbitrage21partialcandidateProduction feed delivery creates operational failures; buyer pain must be tested.
opp_yca_288yc-arbitrage21partialcandidateProduction docs mention approved partners; access gate may slow sales.
opp_yca_289yc-arbitrage19partialcandidateDocs describe checkout session behavior and test mode; sales channel narrower.
opp_yca_290yc-arbitrage19partialcandidateDelegated payment flow is concrete; buyer path still unclear.
opp_yca_291yc-arbitrage21partialcandidateSpec assigns payment processing to merchant/PSP; buyer receipt absent.
opp_yca_292yc-arbitrage21partialcandidateCheckout keeps merchant systems responsible; direct finance demand unverified.
opp_yca_293yc-arbitrage21partialcandidateAPI exposes state transitions and irreversible archive semantics; paid demand unproven.
opp_yca_294yc-arbitrage20partialcandidateIrreversible archive detail is public; may be too small standalone.
opp_yca_295yc-arbitrage21partialcandidatePublic marketing coverage reports geo exclusions; official API surface supports campaign setup.
opp_yca_296yc-arbitrage22partialcandidateConversion-focused ads create measurement dependency; buyer proof absent.
opp_yca_297yc-arbitrage22partialcandidatePublic coverage mentions premium pricing and limited data; direct buyer receipts absent.
opp_yca_298yc-arbitrage21partialcandidateBulk tools are externally reported; implementation pain needs validation.
opp_yca_299yc-arbitrage22partialcandidateDocs distinguish Ads Manager feed eligibility; buyer validation missing.
opp_yca_300yc-arbitrage20partialcandidateAds rollout and labeling are public; paid compliance need unverified.
opp_yca_301yc-arbitrage23completecandidateOfficial OpenAI Ads, CAPI and oCPC docs make the measurement surface concrete; GA4 AI Assistant still has refe
opp_yca_302yc-arbitrage22partialcandidateIndustry coverage names SEO/PPC convergence; paid workflow demand still proxy-only.
opp_yca_303yc-arbitrage21partialcandidateChangelog recommends outputSchema; buyer demand must be validated.
opp_yca_304yc-arbitrage20partialcandidateFeature is explicit; paid value likely bundled with app readiness.
opp_yca_305yc-arbitrage20partialcandidateReference fields are specific; buyer frequency unknown.
opp_yca_306yc-arbitrage19partialcandidateBridge behavior is official; telemetry budget unproven.
opp_yca_307yc-arbitrage19partialcandidateTroubleshooting docs name widget-state persistence; paid demand likely niche.
opp_yca_308yc-arbitrage20partialcandidateReference warns about approval-gated arguments; buyer validation absent.
opp_yca_309yc-arbitrage21partialcandidateSecurity docs explicitly call out irreversible operations; buyer proof missing.
opp_yca_310yc-arbitrage21partialcandidateDocs say published plugins can run in ChatGPT and Codex; buyer channel untested.
opp_yca_311yc-arbitrage20partialcandidateGuidelines are explicit; paid review demand must be tested.
opp_yca_312yc-arbitrage19partialcandidateTroubleshooting path is public; one-off support demand unknown.
opp_yca_313yc-arbitrage20partialcandidateTool/UI metadata is concrete; paid demand unverified.
opp_yca_314yc-arbitrage21partialcandidatePublishing requirements are visible; customer access is the unknown.
opp_yca_315yc-arbitrage21partialcandidateSecurity docs recommend sharing prompts for testing injections; buyer validation absent.
opp_yca_316yc-arbitrage20partialcandidateIrreversible write action risk is public; service packaging needs receipts.
opp_yca_317yc-arbitrage21partialcandidateAuth docs separate anonymous/read-only from customer-specific/write tools; buyer proof missing.
opp_yca_318yc-arbitrage21partialcandidateConnector risk is explicit in docs; enterprise buyer access unvalidated.
opp_yca_319yc-arbitrage19partialcandidateIncident response is inferred from documented risks; buyer trigger is weaker.
opp_yca_320yc-arbitrage22partialcandidateFresh public report shows market fragmentation; buyer receipts absent.
opp_yca_321yc-arbitrage22partialcandidateFragmentation plus GA4 AI Assistant change create public evidence; payment proof missing.
opp_yca_322yc-arbitrage22partialcandidateAI search visibility coverage supports the need; buyer receipt absent.
opp_yca_323yc-arbitrage22partialcandidatePublic fanout analysis points to commercial prompts; buyer proof missing.
opp_yca_324yc-arbitrage22partialcandidateRecent MarTech coverage frames data ownership risk; paid audit validation missing.
opp_yca_325yc-arbitrage20partialcandidateTrust boundaries are publicly discussed; buyer path needs testing.
opp_yca_326yc-arbitrage22partialcandidateToday-dated public signal; needs buyer validation and official confirmation depth.
opp_yca_327yc-arbitrage22partialcandidatePublic growth numbers support urgency; buyer receipts still required.
opp_yca_328yc-arbitrage24partialcandidatePublic evidence shows official payment-network push plus merchant liability/fraud/dispute risk, but no direct
opp_yca_329yc-arbitrage21partialcandidateYC directory shows agent verification/control-plane startups; buyer urgency inferred until direct receipts exi
opp_yca_330yc-arbitrage20partialcandidateYC enterprise page signals MCP governance; willingness to pay for inventory needs buyer validation.
opp_yca_331yc-arbitrage21partialcandidateYC company page directly frames production agent access-control risk; direct buyer receipt missing.
opp_yca_332yc-arbitrage20partialcandidatePublic YC developer-tool descriptions mention shadow AI and agent control; local buyer pain unverified.
opp_yca_333yc-arbitrage19partialcandidateYC lists agent identity/communication infrastructure; demand for a service wrapper is proxy-only.
opp_yca_334yc-arbitrage20partialcandidateYC directory points to agent observability and conversation analytics; direct purchase proof absent.
opp_yca_335yc-arbitrage19partialcandidateYC machine-learning results mention coding-agent fleets with sandboxing and budget caps; buyer receipt missing
opp_yca_336yc-arbitrage19partialcandidateYC developer-tool descriptions mention durable execution and retries; paid consulting demand unverified.
opp_yca_337yc-arbitrage19partialcandidateYC source signals agent action verification and fix PRs; buyer demand inferred.
opp_yca_338yc-arbitrage20partialcandidateYC page frames enterprise AI agents over internal data with access control; direct buyer validation missing.
opp_yca_339yc-arbitrage21partialcandidateYC workflow page describes agents turning websites without APIs into reliable actions; service demand needs re
opp_yca_340yc-arbitrage21partialcandidateYC descriptions highlight computer-use agents in finance with human approval before submit; local buyer proof
opp_yca_341yc-arbitrage20partialcandidateYC workflow source names old software and legacy systems as automation targets; willingness to pay unverified.
opp_yca_342yc-arbitrage21partialcandidateYC workflow page shows GTM automations that produce Slack messages, PRs and tables; buyer receipt missing.
opp_yca_343yc-arbitrage19partialcandidateYC page describes systems surfacing suggested automations; consulting wedge is not yet validated.
opp_yca_344yc-arbitrage19partialcandidateYC workflow source includes agentic research with adaptive user feedback; buyer budget unclear.
opp_yca_345yc-arbitrage17partialcandidateYC lists AI bidding and purchasing for contractors; not adjacent enough to current assets yet.
opp_yca_346yc-arbitrage17partialcandidateYC AI assistant page describes carrier operations agents; channel fit is weaker for current business.
opp_yca_347yc-arbitrage20partialcandidateYC source says agents share customer context and run business processes; buyer pain needs validation.
opp_yca_348yc-arbitrage19partialcandidateYC AI assistant page describes agents trained by process documents; paid service demand unverified.
opp_yca_349yc-arbitrage17partialcandidateYC source includes proactive desktop copilots and privacy claims; buyer segment uncertain.
opp_yca_350yc-arbitrage19partialcandidateYC AI assistant source shows inbox/calendar agents; buyer proof missing.
opp_yca_351yc-arbitrage18partialcandidateYC AI assistant page includes end-to-end prior-authorization automation; current channel fit weak.
opp_yca_352yc-arbitrage19partialcandidateYC healthcare source reports contracted ARR, live revenue, 10x throughput and 100% pilot conversion for RCM vo
opp_yca_353yc-arbitrage18partialcandidateYC source gives workload and revenue examples for claim follow-up voice agents; direct buyer channel missing.
opp_yca_354yc-arbitrage17partialcandidateYC healthcare page mentions AI agents automating behavioral-health clinic tasks; purchase route uncertain.
opp_yca_355yc-arbitrage16partialcandidateYC healthcare source mentions voice biomarkers in care management; buyer/channel fit weak.
opp_yca_356yc-arbitrage18partialcandidateYC healthcare source names insurance denial appeals and RCM agent suites; direct receipts absent.
opp_yca_357yc-arbitrage16partialcandidateYC source says RCM agents serve billing companies and BPOs; no local buyer validation.
opp_yca_358yc-arbitrage20partialcandidateYC compliance page cites AI agents automating 80% of AML reviews and screening products; financial-services bu
opp_yca_359yc-arbitrage19partialcandidateYC Diligent page lists legal-entity due diligence and document review workflows; direct buyer proof missing.
opp_yca_360yc-arbitrage20partialcandidateYC compliance source names transaction-monitoring AI and a $24B US opportunity; local channel untested.
opp_yca_361yc-arbitrage19partialcandidateYC Bretton page emphasizes regulated banks, auditability and model validation; service demand unvalidated.
opp_yca_362yc-arbitrage19partialcandidateYC Diligent source explicitly includes false-positive remediation; direct buyer evidence missing.
opp_yca_363yc-arbitrage20partialcandidateYC MarkIt page names trade professionals, Excel, PDFs, broker portals and defensible classification; buyer rec
opp_yca_364yc-arbitrage19partialcandidateYC MarkIt source indicates agents work inside trade workflows; local buyer validation absent.
opp_yca_365yc-arbitrage15partialheldPublic signal is strong but channel and target-market access are too weak for current portfolio.
opp_yca_366yc-arbitrage15partialheldYC automation source shows backlog-clearing AI agents, but sales path is far outside current reach.
opp_yca_367yc-arbitrage15partialheldStrong public source, but pharma enterprise channel is too remote.
opp_yca_368yc-arbitrage15partialheldYC compliance result shows trial-submission agents, but current business has no biotech access.
opp_yca_369yc-arbitrage22partialcandidateYC search result cites CPG MCP data layer with rapid MRR and brand count; source needs deeper verification and
opp_yca_370yc-arbitrage21partialcandidatePublic YC operations signal is promising but needs page-level follow-up and buyer receipts.
opp_yca_371yc-arbitrage22partialcandidateYC payments source shows dispute/fraud analytics and AI rule recommendations; agentic-payment buyer receipt st
opp_yca_372yc-arbitrage22partialcandidateYC payments source describes rules for payment platforms; local paid demand not proven.
opp_yca_373yc-arbitrage18partialcandidateYC payments page includes AI-powered retries for involuntary churn; less tied to agentic commerce timing.
opp_yca_374yc-arbitrage16partialcandidateYC payments page cites HSA/FSA market size; fit to current portfolio is moderate.
opp_yca_375yc-arbitrage15partialheldInteresting payment infrastructure signal, but current buyer access and regulatory fit are weak.
opp_yca_376yc-arbitrage19partialcandidateYC payments page includes global payment infrastructure patterns; direct demand still proxy-only.
opp_yca_377yc-arbitrage21partialcandidateYC Cekura page reports 75+ customers and compliance-heavy sectors; direct service buyer receipt missing.
opp_yca_378yc-arbitrage21partialcandidateYC Cekura source validates QA across the agent lifecycle; local buyer channel still needs testing.
opp_yca_379yc-arbitrage22partialcandidateLarge acquisition and security guidance point to budget urgency; local buyer receipt missing.
opp_yca_380yc-arbitrage21partialcandidateAgent identity is an urgent security primitive; productization could be swallowed by IAM vendors.
opp_yca_381yc-arbitrage20partialcandidateGovernance gap is public; enterprise access remains hard without warm channel.
opp_yca_382yc-arbitrage20partialcandidateAudit-trail language is concrete, but buyer access is slower than ecommerce.
opp_yca_383yc-arbitrage19partialcandidateBoard-level governance pressure exists; service could be too generic without narrow template.
opp_yca_384yc-arbitrage21partialcandidateAudit-trail and incident-resolution need is explicit; must find buyer who already had incidents.
opp_yca_385yc-arbitrage20partialcandidateSecurity principle maps cleanly to agents; direct willingness unproven.
opp_yca_386yc-arbitrage19partialcandidateGovernance risk is real; drill packaging needs proof of pain frequency.
opp_yca_387yc-arbitrage18partialcandidateHigh-level demand but harder first sale; likely consulting-led.
opp_yca_388yc-arbitrage20partialcandidateDate-driven regulation helps timing; KR/US channel needs choosing.
opp_yca_389yc-arbitrage19partialcandidateGovernance need is broad; must avoid becoming undifferentiated consulting.
opp_yca_390yc-arbitrage20partialcandidatePrecise pain under governance; willingness likely rises after incidents or audits.
opp_yca_391yc-arbitrage19partialcandidateGovernance systems exist; service wedge is cleanup/import readiness.
opp_yca_392yc-arbitrage17partialcandidateStrong market narrative, weaker narrow buyer path.
opp_yca_393yc-arbitrage21partialcandidateMCP usage growth and security gap align; needs buyer with MCP in production.
opp_yca_394yc-arbitrage20partialcandidateCost-control pain is plausible; direct public budget signal is thinner than security/compliance.
opp_yca_395yc-arbitrage22partialcandidateVery close to 328; should fold into current lead unless buyer receipts show standalone budget.
opp_yca_396yc-arbitrage22partialcandidateStrong marketplace risk framing; still no real marketplace operator receipt.
opp_yca_397yc-arbitrage22partialcandidateChargeback pain has clear budget but transaction volume may still be early.
opp_yca_398yc-arbitrage20partialcandidateLegal uncertainty is public; conversion-sensitive copy may require legal partner.
opp_yca_399yc-arbitrage21partialcandidateClear technical/control gap; may require integration beyond service wrapper.
opp_yca_400yc-arbitrage20partialcandidateSupport fallout is plausible but weaker than fraud/liability budget.
opp_yca_401yc-arbitrage20partialcandidateTrust signal is real; badge markets can become commoditized.
opp_yca_402yc-arbitrage22partialcandidateDirectly extends current vendor sufficiency matrix; no buyer-paid receipt yet.
opp_yca_403yc-arbitrage20partialcandidateLarge market and cash pain; healthcare channel/procurement is difficult.
opp_yca_404yc-arbitrage19partialcandidateBuyer research demand exists, but vendor selection can be consulting-heavy.
opp_yca_405yc-arbitrage20partialcandidateVoice-agent operations need QA; local healthcare access uncertain.
opp_yca_406yc-arbitrage18partialcandidateDemand is plausible; must narrow to one workflow and buyer.
opp_yca_407yc-arbitrage19partialcandidateRegulatory pain is specific; channel remains hard.
opp_yca_408yc-arbitrage19partialcandidateCash impact is direct; procurement/channel are weak for solo startup.
opp_yca_409yc-arbitrage17partialcandidateSensitive but real; narrow buyer path still absent.
opp_yca_410yc-arbitrage17partialcandidateROI language is abundant; service needs access to internal metrics.
opp_yca_411yc-arbitrage19partialcandidateConcrete legal billing pain; channel and trust are the constraints.
opp_yca_412yc-arbitrage18partialcandidateLegal need is explicit; requires legal partner to sell safely.
opp_yca_413yc-arbitrage19partialcandidateWorkflow is valuable; existing vendors are already active.
opp_yca_414yc-arbitrage20partialcandidateProcurement adoption signal is strong; service needs buyer access.
opp_yca_415yc-arbitrage20partialcandidateFunding and BCG signal enterprise interest; direct service wedge still needs proof.
opp_yca_416yc-arbitrage19partialcandidateEnterprise redesign is real; channel is consulting-heavy.
opp_yca_417yc-arbitrage19partialcandidateLive logistics operations are attractive; buyer access and data integration matter.
opp_yca_418yc-arbitrage18partialcandidateAutomation adoption is broad; hardware/warehouse channel is hard.
opp_yca_419yc-arbitrage20partialcandidateYC company signal is concrete; local property-manager channel needs testing.
opp_yca_420yc-arbitrage19partialcandidateKnown AI real-estate use case; QA service needs differentiation.
opp_yca_421yc-arbitrage18partialcandidateSafety value is high; construction channel slow.
opp_yca_422yc-arbitrage20partialcandidateCost-reduction signal is clear; crowded vendor ecosystem.
opp_yca_423yc-arbitrage20partialcandidateResolution-rate promises require measurement; direct buyer receipt absent.
opp_yca_424yc-arbitrage17partialheldImportant but public-sector channel is slow and procurement-heavy.
opp_yca_425yc-arbitrage17partialheldLarge regulated pain but very hard channel.
opp_yca_426yc-arbitrage21partialcandidateAgent vendors and QA signal exist; could be crowded by observability tools.
opp_yca_427yc-arbitrage21partialcandidateDeveloper need is plausible and MCP-adjacent; direct budget signal missing.
opp_yca_428yc-arbitrage22partialcandidateConcrete QA evidence and agent adoption combine well; buyer channel still needs validation.
opp_yca_429yc-arbitrage22partialcandidate80% Fortune 500 active-agent signal makes timing strong; needs reachable security/IT operators.
opp_yca_430yc-arbitrage21partialcandidateNon-human identity ownership vacuum is explicit; product vendors may absorb it.
opp_yca_431yc-arbitrage21partialcandidateFirst-class identity and least privilege language is concrete; buyer access still unvalidated.
opp_yca_432yc-arbitrage20partialcandidateGovernance gap is timely; tabletop purchase may need incident/board pressure.
opp_yca_433yc-arbitrage21partialcandidateAudit trails are required for incidents; standardization service may be squeezed by platforms.
opp_yca_434yc-arbitrage20partialcandidateCyber AI specialization/cost signal is fresh; may be too technical for first service sale.
opp_yca_435yc-arbitrage21partialcandidateAgentic AI spend growth and local deployment cost claims make a CFO/FinOps wedge plausible.
opp_yca_436yc-arbitrage20partialcandidateCost/privacy signal is interesting; hardware vendors can own much of the budget.
opp_yca_437yc-arbitrage22partialcandidateDirectly reinforces 328 with regulatory/liability language; needs paid buyer receipt.
opp_yca_438yc-arbitrage22partialcandidateMRC/Shopify fraud signals are strong and ecommerce channel is close.
opp_yca_439yc-arbitrage22partialcandidateRTP fraud risk is concrete; may be owned by PSP/bank partners.
opp_yca_440yc-arbitrage22partialcandidateAgentic commerce signal gap is clear; vendor sufficiency must be tested.
opp_yca_441yc-arbitrage22partialcandidateMarketplace-specific seller/payout language is very close to target ICP.
opp_yca_442yc-arbitrage20partialcandidateEnterprise stablecoin rails are hot; buyer channel and regulatory complexity are heavier than ecommerce ops.
opp_yca_443yc-arbitrage20partialcandidateB2B payments growth is strong but sources are vendor/industry claims; needs controller/CFO receipt.
opp_yca_444yc-arbitrage20partialcandidateMany vendors create comparison pain; may become commodity content unless tied to buyer data.
opp_yca_445yc-arbitrage19partialheldHigh-value but fintech compliance channel is slow and trust-heavy.
opp_yca_446yc-arbitrage19partialheldRCM pain is huge, but channel/trust barrier is high for first sale.
opp_yca_447yc-arbitrage19partialheldPain is concrete but healthcare access is weak.
opp_yca_448yc-arbitrage19partialheldHigh-stakes but healthcare/contact center overlap requires careful validation.
opp_yca_449yc-arbitrage20partialcandidateAxiom describes evaluation burden clearly; legal buyer access is moderate.
opp_yca_450yc-arbitrage20partialcandidateCritical misses are concrete; crowded legal AI vendor landscape.
opp_yca_451yc-arbitrage19partialcandidateAdoption gap is credible; service may look like generic enablement.
opp_yca_452yc-arbitrage20partialcandidateProcurement budget/AI signals exist; buyer path slower than ecommerce/payment.
opp_yca_453yc-arbitrage20partialcandidateSpend-reduction math is compelling; existing procurement suites may cover it.
opp_yca_454yc-arbitrage19partialcandidateAgentic supply-chain adoption signals are strong; enterprise channel is heavy.
opp_yca_455yc-arbitrage19partialcandidateException/handoff need is precise; implementation/data access is hard.
opp_yca_456yc-arbitrage19partialcandidateOperational pain is clear; data integration burden is moderate.
opp_yca_457yc-arbitrage20partialcandidate100% interaction scoring trend is clear; vendor ecosystem crowded.
opp_yca_458yc-arbitrage20partialcandidateROI measurement pain is strong; buyer access and data exports needed.
opp_yca_459yc-arbitrage20partialcandidateCompliance monitoring is clear, but existing QA vendors have coverage.
opp_yca_460yc-arbitrage21partialcandidateAgent QA market exists; taxonomy can be a lightweight first product.
opp_yca_461yc-arbitrage22partialcandidateRetail agentic AI signal is strong and ecommerce channel is close.
opp_yca_462yc-arbitrage22partialcandidateMerchant fear is plausible; proof method needs hardening.
opp_yca_463yc-arbitrage22partialcandidateVery close to existing AI Ads/attribution wedge; buyer receipts still absent.
opp_yca_464yc-arbitrage22partialcandidateStrongly adjacent to first-sale Launch Room; direct buyer evidence missing.
opp_yca_465yc-arbitrage22partialcandidateDirectly maps to 328 liability evidence; standalone buyer still unproven.
opp_yca_466yc-arbitrage18partialheldReal compliance work, but sustainability procurement channel is outside current strengths.
opp_yca_467yc-arbitrage18partialheldHigh macro relevance but weak near-term buyer access.
opp_yca_468yc-arbitrage18partialheldNiche could pay, but channel is fragmented.
opp_yca_469yc-arbitrage20partialcandidateAgentic services spend and vendor evaluation burden align; risk of generic consulting.
opp_yca_470yc-arbitrage18partialcandidateBoard/governance pain is real but likely consulting-heavy.
opp_yca_471yc-arbitrage20partialcandidateRollback is concrete; needs buyer with production agent operations.
opp_yca_472yc-arbitrage21partialcandidateMCP/A2A trend is strong; production adoption evidence must be narrowed.
opp_yca_473yc-arbitrage21partialcandidateFuture-facing but concrete for liability; timing may be early for A2A in production.
opp_yca_474yc-arbitrage22partialcandidateReachable channel and simple package, but ARPU may be lower than 328.
opp_yca_475yc-arbitrage20partialcandidateHandoff boundaries matter across domains; needs a concrete first vertical.
opp_yca_476yc-arbitrage20partialcandidateLegal/security overlap is concrete; privacy constraints need careful design.
opp_yca_477yc-arbitrage22partialcandidateThis is the sharpest 328 kill question as a purchasable benchmark.
opp_yca_478yc-arbitrage22partialcandidateIt improves online-only iteration but cannot replace actual buyer receipts.
opp_yca_479yc-arbitrage22partialcandidateDelegated payment and verifiable intent make evidence replay urgent; buyer receipt still missing.
opp_yca_480yc-arbitrage22partialcandidateVerifiable intent creates a control surface; service buyer and urgency need proof.
opp_yca_481yc-arbitrage22partialcandidateACP makes catalog/order context machine-readable; drift control is a merchant-risk wedge.
opp_yca_482yc-arbitrage22partialcandidateVisa bot/agent threat framing supports timing; refund-specific pain needs buyer language.
opp_yca_483yc-arbitrage22partialcandidateStrong adjacency to 328 marketplace archetype; needs public target-account scoring before contact.
opp_yca_484yc-arbitrage22partialcandidateMachine-speed payment language is direct; exception workflow buyer is plausible.
opp_yca_485yc-arbitrage22partialcandidateConnects agent governance to regulated ecommerce copy; category needs sharper public buyer proof.
opp_yca_486yc-arbitrage22partialcandidateACP makes catalog legibility a new surface; conversion value is plausible but unvalidated.
opp_yca_487yc-arbitrage21partialcandidateSupport accountability appears naturally in delegated commerce; budget owner less sharp than fraud/payments.
opp_yca_488yc-arbitrage22partialcandidateTrust layer language is strong; risk is becoming a certification fantasy without platform demand.
opp_yca_489yc-arbitrage21partialcandidateOpenAI governance guidance names the deployment fear; channel is farther from ecommerce.
opp_yca_490yc-arbitrage21partialcandidateApproval and human oversight are explicit governance themes; needs budget owner evidence.
opp_yca_491yc-arbitrage21partialcandidatePermission drift is a clear control problem; vendor-native coverage may be sufficient.
opp_yca_492yc-arbitrage21partialcandidateRollback is concrete and sellable as a drill; demand unknown.
opp_yca_493yc-arbitrage21partialcandidateGovernance and verifiable intent both point to traceability; buyer segment broad.
opp_yca_494yc-arbitrage21partialcandidateSecurity/legal audit fear is strong; competition from security vendors likely high.
opp_yca_495yc-arbitrage21partialcandidateExecutives need framing, but willingness to pay for a catalog alone is unclear.
opp_yca_496yc-arbitrage21partialcandidateEvals are widespread but tooling may commoditize; service wrapper needs urgency.
opp_yca_497yc-arbitrage21partialcandidateProcurement/security friction is plausible; may be too template-like unless tied to an audit.
opp_yca_498yc-arbitrage21partialcandidateGovernance admin burden is real; service packaging must avoid becoming generic GRC.
opp_yca_499yc-arbitrage20partialcandidateFinance-agent category is rising, but channel is not as close as ecommerce/payment.
opp_yca_500yc-arbitrage21partialcandidateProcurement plus payments creates risk budget; needs public examples of agentic purchasing adoption.
opp_yca_501yc-arbitrage20partialcandidateClear finance-control pain but weaker existing channel.
opp_yca_502yc-arbitrage20partialcandidateAgent Pay for Machines and payment priorities suggest new rails; treasury buyer access is hard.
opp_yca_503yc-arbitrage20partialcandidateProgrammable digital dollars are named in the announcement; compliance path is unclear.
opp_yca_504yc-arbitrage21partialcandidateSupplier research is a natural agent task; buyer proof still missing.
opp_yca_505yc-arbitrage20partialcandidateAuditability is clear but sales route is slow.
opp_yca_506yc-arbitrage21partialcandidateB2B agent payments are explicit; onboarding service may be too early.
opp_yca_507yc-arbitrage18partialcandidateHealthcare RCM is a large pain, but channel and compliance burden are far from current assets.
opp_yca_508yc-arbitrage18partialcandidateSafety and handoff are concrete, but healthcare go-to-market is slow.
opp_yca_509yc-arbitrage18partialcandidateEvidence-chain need is strong; specialized healthcare context required.
opp_yca_510yc-arbitrage18partialcandidateConsent/intent concept transfers, but healthcare compliance is heavier.
opp_yca_511yc-arbitrage18partialcandidateUseful but specialized; not a first-sale path.
opp_yca_512yc-arbitrage18partialcandidateRecurring pain but needs data access and domain expertise.
opp_yca_513yc-arbitrage18partialcandidateAudit retention is likely real but healthcare channel is weak.
opp_yca_514yc-arbitrage19partialcandidateGovernance fit is strong; legal sales cycle likely slower than commerce/payment.
opp_yca_515yc-arbitrage19partialcandidateClear legal ops problem; channel less direct.
opp_yca_516yc-arbitrage19partialcandidateRisk is intuitive; proof of active agent negotiation adoption is still needed.
opp_yca_517yc-arbitrage19partialcandidateVendor diligence is familiar; may be too generic without buyer pull.
opp_yca_518yc-arbitrage20partialcandidateStrong regulated-copy adjacency; could reuse ad-compliance assets.
opp_yca_519yc-arbitrage19partialcandidateConcrete legal retention pain; sales route unclear.
opp_yca_520yc-arbitrage19partialcandidateGovernance question is timely, but procurement friction is high.
opp_yca_521yc-arbitrage18partialcandidateYC points to physical infrastructure; local channel is weak.
opp_yca_522yc-arbitrage18partialcandidatePhysical-world AI trend is real; operator access difficult.
opp_yca_523yc-arbitrage21partialcandidateBudget burn is concrete and closer to builders; needs current public buyer language.
opp_yca_524yc-arbitrage21partialcandidateCosts are immediate and testable; willingness to pay needs proof.
opp_yca_525yc-arbitrage21partialcandidateApproval UX is universal but may be owned by platforms.
opp_yca_526yc-arbitrage21partialcandidateRecurring tasks create latent risk; package could be small and sellable.
opp_yca_527yc-arbitrage21partialcandidateAgent-to-agent commerce/workflows are plausible; too early without adoption examples.
opp_yca_528yc-arbitrage21partialcandidateBroad packaging is clear, but needs a vertical with a reachable buyer.
opp_yca_529yc-arbitrage22partialcandidateMerchant-owned payment liability is explicit, but buyer receipts are still 0/3.
opp_yca_530yc-arbitrage21partialcandidateClear precedent from virtual-card agent controls; buyer channel is less direct than 328.
opp_yca_531yc-arbitrage22partialcandidateStrong ecommerce adjacency; risk is platform/agency commoditization.
opp_yca_532yc-arbitrage22partialcandidateHighly concrete marketplace operations pain; no live buyer receipt yet.
opp_yca_533yc-arbitrage22partialcandidateVery close to an already sellable 328 deliverable; actual dispute owners not contacted.
opp_yca_534yc-arbitrage22partialcandidateMerchant/marketplace gap is clear; budget proof absent.
opp_yca_535yc-arbitrage20partialcandidateSpecific use case is visible; target buyer may be consumer fintech rather than current channel.
opp_yca_536yc-arbitrage22partialcandidateStrong catalog/visibility pain, but overlaps with existing GEO vendors.
opp_yca_537yc-arbitrage19partialcandidateYC RFS calls out deepfake trust as decade-level infrastructure; channel is farther from Docenty assets.
opp_yca_538yc-arbitrage20partialcandidateCompelling trust-layer wedge; needs privacy architecture and buyer proof.
opp_yca_539yc-arbitrage19partialcandidateProblem is urgent but monetization depends on community budget.
opp_yca_540yc-arbitrage16partialheldBig market but far from current B2B commerce/payment channel.
opp_yca_541yc-arbitrage18partialcandidateCould fit regulated local services, but healthcare trust burden is high.
opp_yca_542yc-arbitrage21partialcandidateStrong governance service; buyer is broader enterprise security/ops.
opp_yca_543yc-arbitrage19partialcandidateMassive pain and budget, but channel/procurement distance is high.
opp_yca_544yc-arbitrage21partialcandidateService-shaped and sellable; needs a reachable regulated SMB segment.
opp_yca_545yc-arbitrage21partialcandidateDirectly agentic and auditable; can be packaged as a sample audit.
opp_yca_546yc-arbitrage20partialcandidateClear operational pain; source needs domain-specific regulatory proof per vertical.
opp_yca_547yc-arbitrage19partialcandidateHigh value but far from current reachable channel.
opp_yca_548yc-arbitrage21partialcandidateConcrete testable product; overlaps with agent QA challenger.
opp_yca_549yc-arbitrage17partialcandidateHuge labor/software gap; domain data and go-to-market are hard.
opp_yca_550yc-arbitrage15partialheldImportant category, but hardware/field ops channel is too far.
opp_yca_551yc-arbitrage18partialcandidateHigh-value physical-work wedge; local channel and data capture need proof.
opp_yca_552yc-arbitrage18partialcandidateYC company examples validate the workflow direction; channel not near current assets.
opp_yca_553yc-arbitrage17partialcandidateStrong evidence-data moat, but requires field adoption.
opp_yca_554yc-arbitrage19partialcandidateEcommerce logistics adjacency is good; implementation burden is high.
opp_yca_555yc-arbitrage15partialheldLarge industrial opportunity but too far from current channel and expertise.
opp_yca_556yc-arbitrage18partialcandidateYC explicitly flags aging as underserved; healthcare/caregiver channel is difficult.
opp_yca_557yc-arbitrage18partialcandidateYC company page gives concrete time-savings language; channel is not current.
opp_yca_558yc-arbitrage15partialheldConsumer/health trust and device distribution are hard.
opp_yca_559yc-arbitrage18partialcandidateClear pain, but buyer/payment path is ambiguous.
opp_yca_560yc-arbitrage20partialcandidateConcrete revenue leakage; regulated healthcare channel remains hard.
opp_yca_561yc-arbitrage20partialcandidateVery concrete QA need; selling into healthcare vendors may be reachable via agent QA angle.
opp_yca_562yc-arbitrage20partialcandidateYC RFS calls out secure sharing of arbitrary code; strong developer-tool fit.
opp_yca_563yc-arbitrage22partialcandidateDirectly matches current app/dashboard governance skill; buyer receipts absent.
opp_yca_564yc-arbitrage21partialcandidateStrong conceptual need; buyer language still early.
opp_yca_565yc-arbitrage22partialcandidateVery service-shaped and reachable; less differentiated than 328 unless verticalized.
opp_yca_566yc-arbitrage21partialcandidateBudget pain likely real; needs source proof beyond YC RFS for pricing.
opp_yca_567yc-arbitrage21partialcandidateHigh-trust governance need; requires security buyer channel.
opp_yca_568yc-arbitrage22partialcandidateHighly aligned with agent-ops and dashboarding; buyer proof missing.
opp_yca_569yc-arbitrage16partialheldPotentially huge consumer market, but not reachable as a first B2B sale.
opp_yca_570yc-arbitrage15partialheldConsumer education distribution is hard and far from current assets.
opp_yca_571yc-arbitrage16partialheldSchool procurement and safety burden are high.
opp_yca_572yc-arbitrage22partialcandidateDirectly sellable to agencies; differentiation requires vertical templates.
opp_yca_573yc-arbitrage22partialcandidateClear advisory product; must avoid becoming generic analyst content.
opp_yca_574yc-arbitrage19partialcandidateVertical stack evidence exists; local restaurant ops channel may be reachable but lower fit.
opp_yca_575yc-arbitrage21partialcandidateClear enterprise spend-control primitive; procurement channel proof needed.
opp_yca_576yc-arbitrage21partialcandidateBig control-layer need, but buyer may be enterprise finance rather than ecommerce.
opp_yca_577yc-arbitrage16partialheldStrategic category, but crypto compliance channel is far and volatile.
opp_yca_578yc-arbitrage22partialcandidateStrong ecommerce packaging; must be scoped to readiness, not guaranteed platform approval.
opp_yca_579yc-arbitrage22partialcandidateDirectly reinforces 328; buyer receipt is still 0/3.
opp_yca_580yc-arbitrage21partialcandidateStrong risk-ops artifact, but needs buyer language.
opp_yca_581yc-arbitrage21partialcandidateClear sample deliverable; no receipt yet.
opp_yca_582yc-arbitrage20partialcandidateGood compliance artifact; incident frequency unknown.
opp_yca_583yc-arbitrage21partialcandidateStrong readiness wedge, but could be bundled by agencies.
opp_yca_584yc-arbitrage21partialcandidateStrong fraud-ops fit; implementation depth risk.
opp_yca_585yc-arbitrage22partialcandidateVery close to 328 thesis; requires actual buyer review.
opp_yca_586yc-arbitrage22partialcandidateHighly packageable; risk of overclaiming platform access.
opp_yca_587yc-arbitrage20partialcandidateLarge fintech surface; buyer channel farther than merchant risk.
opp_yca_588yc-arbitrage17partialheldStrategic but bank sales cycle is too slow for first sale.
opp_yca_589yc-arbitrage19partialcandidateMarketplace trust signal is relevant; product boundary needs narrowing.
opp_yca_590yc-arbitrage21partialcandidateExcellent partner-channel packaging; no PSP receipt.
opp_yca_591yc-arbitrage21partialcandidateStrong legal/risk pain; implementation may need catalog data access.
opp_yca_592yc-arbitrage21partialcandidateEasy low-ticket product; less defensible than liability sprint.
opp_yca_593yc-arbitrage20partialcandidateGood catalog-data wedge; may fold into 531/578.
opp_yca_594yc-arbitrage20partialcandidateLegal ops is real but may be template-heavy.
opp_yca_595yc-arbitrage21partialcandidateBudget-defense artifact; timing score held below 5 because growth ladder is one-sided.
opp_yca_596yc-arbitrage20partialcandidateGood marketplace policy product; validate owner first.
opp_yca_597yc-arbitrage21partialcandidateStrong hands-on deliverable; buyer receipt missing.
opp_yca_598yc-arbitrage22partialcandidateCombines original attribution thesis with payment data; promising cross-sell.
opp_yca_599yc-arbitrage21partialcandidateGood 369 fallback reinforcement; not a new lead without receipts.
opp_yca_600yc-arbitrage21partialcandidateStrong CPG fallback artifact; no receipts.
opp_yca_601yc-arbitrage21partialcandidateClear budget-defense angle; CPG buyer still unvalidated.
opp_yca_602yc-arbitrage22partialcandidateStrong commerce-data wedge; overlaps with 531.
opp_yca_603yc-arbitrage21partialcandidateStrong sample story; needs actual brand data later.
opp_yca_604yc-arbitrage21partialcandidatePractical 369 fallback deliverable; no buyer receipt.
opp_yca_605yc-arbitrage21partialcandidateBudget-defense value is clear; sales path unproven.
opp_yca_606yc-arbitrage18partialcandidateUseful but may become consulting-heavy.
opp_yca_607yc-arbitrage22partialcandidateStrong regulated ecommerce wedge; may fold into existing compliance assets.
opp_yca_608yc-arbitrage20partialcandidateHigh-trust artifact; fintech channel must be validated.
opp_yca_609yc-arbitrage19partialcandidatePromising but wallet/issuer buyer path is slower.
opp_yca_610yc-arbitrage22partialcandidateVery sellable two-week readiness package; cannot promise certification.
opp_yca_611yc-arbitrage22partialcandidateConcrete paid workshop; no receipt yet.
opp_yca_612yc-arbitrage19partialcandidateUseful taxonomy; not enough by itself for a top lead.
opp_yca_613yc-arbitrage20partialcandidateGood neutral advisory wedge; might be free content.
opp_yca_614yc-arbitrage20partialcandidateOperationally useful but lower budget priority.
opp_yca_615yc-arbitrage21partialcandidateSellable enablement; less defensible than evidence tooling.
opp_yca_616yc-arbitrage21partialcandidateStrong marketplace pain; target accounts need narrowing.
opp_yca_617yc-arbitrage21partialcandidateConcrete data artifact; buyer receipt missing.
opp_yca_618yc-arbitrage21partialcandidateExecutive risk artifact; could justify higher price if buyer confirms.
opp_yca_619yc-arbitrage20partialcandidateTechnically promising, but buyer may be developer platform not merchant.
opp_yca_620yc-arbitrage20partialcandidateGood fraud-adjacent module; agent-specific evidence still early.
opp_yca_621yc-arbitrage21partialcandidateStrong content/data wedge; overlaps with product feed readiness.
opp_yca_622yc-arbitrage20partialcandidateStrong marketplace policy artifact; validate owner.
opp_yca_623yc-arbitrage19partialcandidateGood delegated-payment wedge; current repo channel weaker.
opp_yca_624yc-arbitrage21partialcandidateFinance evidence could pay; channel proof missing.
opp_yca_625yc-arbitrage22partialcandidateVery packageable; should fold into 328/578.
opp_yca_626yc-arbitrage22partialcandidateBridges discovery and checkout; no receipt.
opp_yca_627yc-arbitrage22partialcandidateExcellent sample deliverable; validate willingness to pay.
opp_yca_628yc-arbitrage21partialcandidateRecurring revenue path; first-sale proof missing.
opp_yca_629yc-arbitrage22partialcandidateBest fold-in to 328 because it turns liability into a concrete paid artifact; no buyer receipt yet.
opp_yca_630yc-arbitrage22partialcandidateStrong merchant risk artifact; validate owner and price.
opp_yca_631yc-arbitrage21partialcandidateExcellent consent/liability data primitive, but PSP integrations could slow sales.
opp_yca_632yc-arbitrage22partialcandidateConcrete sample deliverable; likely folds into 328 package.
opp_yca_633yc-arbitrage22partialcandidateBoard/risk language is strong; no receipt yet.
opp_yca_634yc-arbitrage21partialcandidateRecurring revenue extension, weaker first-sale urgency.
opp_yca_635yc-arbitrage22partialcandidateStrong fraud-ops pain; implementation scope must stay serviceable.
opp_yca_636yc-arbitrage22partialcandidateConcrete compliance/data artifact; overlaps with 328 readiness.
opp_yca_637yc-arbitrage22partialcandidateExecutive-friendly evidence output; likely folds into 328 memo.
opp_yca_638yc-arbitrage21partialcandidateCould open finance owner; channel is less direct than risk/ops.
opp_yca_639yc-arbitrage22partialcandidateVery concrete QA deliverable; buyer WTP unknown.
opp_yca_640yc-arbitrage21partialcandidateUseful but lower-ticket unless bundled with evidence vault.
opp_yca_641yc-arbitrage20partialcandidateGood advisory artifact, but may be free content unless paired with audit.
opp_yca_642yc-arbitrage20partialcandidateHigh-value fintech lane but sales cycle likely longer than merchant risk.
opp_yca_643yc-arbitrage20partialcandidatePotential vertical wedge; needs narrower buyer persona.
opp_yca_644yc-arbitrage20partialcandidateExcellent consent artifact but not the quickest first-sale channel.
opp_yca_645yc-arbitrage21partialcandidateGood marketplace extension; first buyer still unclear.
opp_yca_646yc-arbitrage22partialcandidateStrong sellable wrapper for 328; must avoid claiming official certification.
opp_yca_647yc-arbitrage22partialcandidateGood board-level deliverable, best as 328 add-on.
opp_yca_648yc-arbitrage21partialcandidateStrong budget-defense artifact; timing held because agent traffic volume is still early.
opp_yca_649yc-arbitrage21partialcandidateStrong enterprise security challenger; not closer than 328 to first sale.
opp_yca_650yc-arbitrage21partialcandidateMatches current local dashboard pattern; buyer channel still broad.
opp_yca_651yc-arbitrage21partialcandidateVery sellable security workshop; validate budget owner.
opp_yca_652yc-arbitrage21partialcandidateClear pain, but market may be pulled into platform security products.
opp_yca_653yc-arbitrage21partialcandidateStrong control artifact; buyer persona needs narrowing.
opp_yca_654yc-arbitrage21partialcandidateDogfoods current dashboard constraints; enterprise validation absent.
opp_yca_655yc-arbitrage20partialcandidateUseful advisory artifact; may commoditize into analyst content.
opp_yca_656yc-arbitrage20partialcandidateGood incident artifact, but reactive demand is uncertain.
opp_yca_657yc-arbitrage21partialcandidateStrong security service; not current lead without receipts.
opp_yca_658yc-arbitrage21partialcandidateHigh-value regulated workflow wedge; sales cycle longer than ecommerce risk.
opp_yca_659yc-arbitrage22partialcandidateRevives original attribution thesis with current AI-search pressure; still behind 328 on buyer memo.
opp_yca_660yc-arbitrage22partialcandidateBroad demand, but crowded SEO tooling risk.
opp_yca_661yc-arbitrage22partialcandidateBridges 328 commerce readiness and attribution; promising fold-in.
opp_yca_662yc-arbitrage21partialcandidateGood regulated content risk; needs data access and buyer validation.
opp_yca_663yc-arbitrage22partialcandidateHigh budget-story value; crowded analytics substitute risk.
opp_yca_664yc-arbitrage22partialcandidateUseful operator artifact but less novel than agentic payment liability.
opp_yca_665yc-arbitrage22partialcandidateStrong feed readiness wedge; can fold into 328 preflight dossier.
opp_yca_666yc-arbitrage22partialcandidateStrong pain but dashboard market is competitive.
opp_yca_667yc-arbitrage22partialcandidateHigh-quality bridge between 124 and 328; no receipt.
opp_yca_668yc-arbitrage19partialcandidateUseful but escalation paths are platform-dependent.
opp_yca_669yc-arbitrage21partialcandidateStrengthens 369 fallback; still no CPG buyer receipt.
opp_yca_670yc-arbitrage21partialcandidateGood one-week 369 deliverable; receipt missing.
opp_yca_671yc-arbitrage21partialcandidateStrong budget-defense fallback; no buyer receipt.
opp_yca_672yc-arbitrage18partialcandidateUseful but can become bespoke consulting.
opp_yca_673yc-arbitrage22partialcandidateGood bridge between 369 and AI shopping; worth watching.
opp_yca_674yc-arbitrage21partialcandidateSharp budget-saving artifact; no receipts.
opp_yca_675yc-arbitrage20partialcandidateGood anti-waste buyer story; could antagonize agency channel.
opp_yca_676yc-arbitrage21partialcandidateUseful planning artifact; no receipt.
opp_yca_677yc-arbitrage21partialcandidateStrong outcome framing for 369 fallback; validate WTP.
opp_yca_678yc-arbitrage22partialcandidateInteresting cross-budget challenger, but less first-sale focused than 328.
opp_yca_679yc-arbitrage21partialcandidateStrong owned-asset and price-gap challenger, but no outbound replies or paid deposits yet.
opp_yca_680yc-arbitrage23partialcandidateStrongest NvLand wedge because BrightLocal review behavior creates an owned-site follow-up gap, and local appo
opp_yca_681yc-arbitrage19partialcandidateDomain-registration growth and SMB website gap support timing, but public channel for new openings is less rea
opp_yca_682yc-arbitrage19partialcandidateReal pain, but scope and legacy migration risk make it weaker than no-owned-page appointment services.
opp_yca_683yc-arbitrage19partialcandidateUseful LTV add-on, but likely hard to sell before the first website outcome is visible.
opp_yca_684yc-arbitrage24partialcandidateHighest NvLand expansion segment because it preserves the review-to-booking pattern while broadening outbound
opp_yca_685yc-arbitrage21partialcandidateStrong repeatable segment with simple compliance and clear trial booking need, but public row collection is no
opp_yca_686yc-arbitrage20partialcandidateBroad outbound pool and concrete quote intent, but service-area claims and proof gathering add delivery variab
opp_yca_687yc-arbitrage19partialcandidateClear inquiry use case, but visual asset collection slows the cheap 72-hour delivery promise.
opp_yca_688yc-arbitrage20partialcandidatePotentially high ticket, but healthcare advertising rules break the low-cost repeatable first-wave motion.
opp_yca_689yc-arbitrage18partialcandidateGood when event/group keywords are visible, but ordinary restaurants may prefer platform or social presence ov

이 보고서에 넣지 않은 것 (ADR 0012)

보고서는 git에 커밋되므로, 운영 데이터는 설계상 제외한다. 이건 누락이 아니라 계약이다. 운영 수치가 필요하면 로컬 전용 대시보드를 쓴다: node scripts/dashboard.mjs --open (산출물은 ~/.harness/business-radar/, git 밖).