# 大河内 雄斗《コードが書けなくても分かるAI活用💡》 (@yuto_okochi) on x

- id: koinon:creator:x_yuto_okochi
- url: https://koinonlink.com/kol/x/yuto_okochi
- schema_version: 1.4

## Identity
- platform: x
- handle: yuto_okochi
- platform_url: https://twitter.com/yuto_okochi
- website: https://linktr.ee/okochiy
- country: Japan
- entity_type: creator
- person_id: Cross-platform identity not resolved for this creator.

## Reach
- followers: 542
- following: 229
- posts_total: 7975
- posts_observed: 1
- posts_per_day: 1.48
- account_age_days: 5390
- verified: true
- size_tier: nano

## Engagement
- status: peak_post_only
- peak_post_engagement_rate: 0.00185
- best_post_interactions: 1
- measurement_source: x_post_interactions
- measurement_formula: interactions on one post — likes, or likes + reposts + replies depending on the discovery path (the two are not distinguishable in the stored data)
- comparable_pool: peak_interactions
- status_note: We have only the single best observed post, so no mean exists. peak_post_engagement_rate is an UPPER BOUND, systematically higher than an average — never compare it against an average rate.
- unit_note: engagement_rate and peak_post_engagement_rate are ratios (0-1); avg_interactions_per_post and best_post_interactions are absolute counts. Read status before reading any number: a null rate has several different causes and status says which one applies here.

## Content
- category: software
- subcategory: ai_tools
- category_confidence: 0.94
- category_source: derived_from_recent_content
- topics: Non-coding AI implementation, AI workflow design, Business automation with AI, AI ROI measurement, Free AI diagnostic services, AI adoption sustainability
- bio: コードが書けなくても分かるAI活用を発信
法人・個人事業主向け｜AI研修・業務自動化
▶︎5年間で1200人規模イベントを10回以上企画・運営
▶︎ライブ配信事業の現場をAIで自動化(月25時間→30分の事例)
▶︎何を自動化できるか分からなくてOK
　あなたの業務、無料で診断します(DMへ)

## Audience (inferred)
- status: present
- description: Small to mid-sized business owners and operational managers in Japan who are exploring AI adoption but lack technical skills, seeking practical, non-coding ways to implement AI in their workflows
- roles: ecom_ops
- seniority: decision_maker
- pain_points: Struggling to sustain AI initiatives due to constantly rewriting prompts from scratch, Unable to justify AI investment because budgets are limited to tool costs only, Not knowing what parts of their business can actually be automated, Lacking internal expertise to design reusable AI workflows
- posts_analysed: 2
- confidence: 0.4

## Commercial (inferred)
- audience_buyer_fit: 0.9
- promotion_intent: 0.9
- open_to_collaboration: false
- contact: Koinon does not publish creator contact details.

## Quality signals
- authenticity_score: 52
- authenticity_basis: engagement_observed
- credibility_score: 52
- flagged_for_review: false
- koinon_bd_grade: B — measures Koinon partner-outreach fit, not creator quality
- interpretation: Signals for triage, not verdicts. A flag means the profile is worth a manual check.

## Evidence
- [x_yuto_okochi#ac280c76] 勘がいい人は気づいてるけど、 AI活用が続かない会社には共通点があります。 毎回、ゼロからプロンプトを書き直している。 続いている会社は、指示を「スキル」として 置き場所ごと設計しています。 英系メディアエージェンシーのBrainlabsは、 4週間で約1,000人にClaude Coworkを展開し、 社員自身が約400個のスキルを作りました。 保存版｜社内AIを使い捨てで終わらせない5設計 ❶ 置き場所を業務ツールの中に置く 同社は社内ナレッジと同じNotionに集約 ❷ 1スキルに必ず1オーナー 更新とレビューの責任者を決める ❸「こんなスキルが欲 (https://twitter.com/yuto_okochi/status/2073004397370728454)
- [x_yuto_okochi#1239d72b] AI導入で失敗する会社は、 契約した時点で半分決まっています。 理由は、予算が「ツール代」で終わっているからです。 米Cox Communicationsの公開事例が分かりやすい。 同社はClaude Codeを大規模に展開し、初年度のAI投資で7倍のリターンを得たと説明しています。 対象は15,000人規模。しかも開発部門だけで止めていません。 注目すべきは倍率ではなく、この2点です。 ① どの業務に使うかを、先に選んでいる ② 使い始めるハードルを下げる作業に、人と時間を割いている 多くの会社が①だけで満足して、②に予算をつけません。 結果、アカウン

## Provenance
Every inferred field below carries how it was produced. Facts stay facts; inferences stay inferences.

- audience.description: source_type=ai_inferred, confidence=0.4, freshness_days=20, method=llm_persona_from_recent_content
- audience.roles: source_type=ai_inferred, confidence=0.4, freshness_days=20, method=llm_persona_from_recent_content
- audience.seniority: source_type=ai_inferred, confidence=0.4, freshness_days=20, method=llm_persona_from_recent_content
- commercial.audience_buyer_fit: source_type=ai_inferred, confidence=0.6, freshness_days=80, method=llm_scorer — Relative signal within Koinon indexing, not a market-wide score.
- commercial.promotion_intent: source_type=ai_inferred, confidence=0.6, freshness_days=80, method=llm_scorer
- quality.anomaly_flags: source_type=heuristic, confidence=0.5, freshness_days=112, method=profile_snapshot_and_engagement_ratio_heuristic — Means "worth a manual check", NOT confirmed fraud. Flags can be wrong and are not a verdict about the person.
- quality.authenticity_score: source_type=heuristic, confidence=0.5, freshness_days=80, method=Profile-shape heuristic from a single snapshot (follower count, following ratio, account age, posting volume, verification), reduced for engagement red flags where post engagement was collected. Where only a follower count is available the score saturates at 58. — The input set differs by platform; do not compare this score across platforms.
- quality.koinon_bd_grade: source_type=ai_inferred, confidence=0.5, freshness_days=112, method=llm_partner_fit_classifier + fit_score >= 0.6 AND authenticity >= 60 => A; fit_score >= 0.4 AND authenticity >= 45 => B; else C. authenticity < 30 or a promotional-pattern flag => quarantine. — Koinon partner-outreach fit, not creator quality.
- reach.followers: source_type=observed, confidence=0.95, freshness_days=112, method=platform_profile

## Freshness
- profile_checked_days_ago: 112
- content_analysed_days_ago: 80
- audience_updated_days_ago: 20

## AI retrieval
- indexing_requests: 11
- user_triggered_requests: 0
- note: Being indexed in bulk is not the same as being retrieved to answer a question.

## This profile
- Claim or correct: https://koinonlink.com/claim?k=x_yuto_okochi
- Request removal: https://koinonlink.com/claim?k=x_yuto_okochi
- Terms: https://koinonlink.com/for-ai