{
  "url": "https://ideanavigatorai.com/ideas/game-publishing-tech-due-diligence/",
  "vertical": {
    "name": "Software, AI & Developer Tooling",
    "slug": "software-ai"
  },
  "exports": {
    "jsonUrl": "https://ideanavigatorai.com/ideas/game-publishing-tech-due-diligence.json",
    "markdownUrl": "https://ideanavigatorai.com/ideas/game-publishing-tech-due-diligence.md",
    "calendarUrl": "https://ideanavigatorai.com/ideas/game-publishing-tech-due-diligence.ics",
    "backlogUrl": "https://ideanavigatorai.com/ideas/game-publishing-tech-due-diligence/backlog.json",
    "genesisUrl": "https://ideanavigatorai.com/ideas/game-publishing-tech-due-diligence/genesis.json",
    "dossierPdfUrl": "https://ideanavigatorai.com/dossiers/game-publishing-tech-due-diligence.pdf"
  },
  "report": {
    "title": "Tech due diligence for game publishing deals",
    "date": "2026-11-08T00:00:00.000Z",
    "slug": "game-publishing-tech-due-diligence",
    "market": "Game publishing and investment",
    "buyer": "Head of production or business development at an independent game publisher that funds external studios against milestones",
    "problem": "Publishers commit milestone funding on the strength of a vertical slice and a pitch, then learn months later that the build sits on an outdated or unpatched engine version, depends on middleware nobody licensed for the target platforms, has no reproducible build pipeline, or will struggle with console certification. Technical surprises become slipped milestones, re-scoping and write-offs, and generic software due-diligence firms don't cover engines, platform certification or game middleware.",
    "whyNow": "Engine and middleware terms keep shifting under live projects: Unity raised Pro and Enterprise prices 5% from January 12, 2026 and no longer includes Havok Physics with paid plans from Unity 6.3, and Unreal's 3.5% 'Launch Everywhere with Epic' royalty (instead of 5%) since January 1, 2025 depends on ongoing release conditions. In October 2025 Unity patched CVE-2025-59489 in builds from 2017.1 onward, with no patch for 2017 and 2018 editors, which made engine version a security question.",
    "evidence": [
      "Unity's advisory for CVE-2025-59489 (CVSS 8.4, patch available October 2, 2025) tells developers to upgrade the Editor and rebuild, or apply a binary patch, and lists no patch for 2017.x and 2018.x editors.",
      "Unity's pricing page states a 5% Pro and Enterprise increase from January 12, 2026 and that Havok Physics is no longer included from Unity 6.3, a direct middleware-license change for projects that use it.",
      "Under 'Launch Everywhere with Epic', Unreal royalties fall from 5% to 3.5% only if a game ships on the Epic Games Store no later than on other PC and Android stores, which changes deal economics.",
      "A 2026 publisher guide lists certification history, build-pipeline compliance and milestone-gate track record among what publishers vet in external studios, but these checks are mostly interviews, not build audits."
    ],
    "mvp": "A fixed-scope audit kit: a scanner run under NDA on the studio's repository and build machine that inventories engine version and patch level, plugins and middleware with their license terms, open-source licenses, build reproducibility and CI, and performance captures on target hardware, plus a platform-cert readiness checklist the studio completes from its own developer access. A short expert review turns it into a red, amber and green report mapped to the deal's milestones, and repeat scans at each milestone flag drift.",
    "difficulty": "high",
    "confidence": 38,
    "monetization": "Fixed fee per pre-signing audit, plus a per-milestone monitoring subscription for publishers and game-focused investors.",
    "risks": [
      "Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.",
      "Console certification requirements sit behind platform NDAs, so the checklist must be run with the studio's own developer access rather than published by the vendor.",
      "Deal volume per publisher is small, so revenue depends on the audit becoming a standard step that publishers and investors require."
    ],
    "validationTest": "Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.",
    "validation": {
      "rubricVersion": "INAV-VALIDATION-2026-06-04",
      "overallScore": 46,
      "verdict": "Rethink",
      "summary": "Rethink is the current validation verdict: competitive saturation is the strongest signal, while feasibility is the main evidence gap to close before scaling the build.",
      "criteria": [
        {
          "id": "demand-signal",
          "label": "Demand signal",
          "weight": 0.24,
          "score": 4.4,
          "reasoning": "Demand looks weak because the report has 4 source-backed signal(s), an editorial confidence of 38/100, and a defined buyer in Game publishing and investment.",
          "evidence": [
            "Unity's advisory for CVE-2025-59489 (CVSS 8.4, patch available October 2, 2025) tells developers to upgrade the Editor and rebuild, or apply a binary patch, and lists no patch for 2017.x and 2018.x editors.",
            "Target buyer: Head of production or business development at an independent game publisher that funds external studios against milestones"
          ]
        },
        {
          "id": "problem-severity",
          "label": "Problem severity",
          "weight": 0.22,
          "score": 4.5,
          "reasoning": "Problem severity is weak when the buyer pain, customer value, and dream-outcome scores are combined.",
          "evidence": [
            "Publishers commit milestone funding on the strength of a vertical slice and a pitch, then learn months later that the build sits on an outdated or unpatched engine version, depends on middleware nobody licensed for the target platforms, has no reproducible build pipeline, or will struggle with console certification. Technical surprises become slipped milestones, re-scoping and write-offs, and generic software due-diligence firms don't cover engines, platform certification or game middleware.",
            "Unity's advisory for CVE-2025-59489 (CVSS 8.4, patch available October 2, 2025) tells developers to upgrade the Editor and rebuild, or apply a binary patch, and lists no patch for 2017.x and 2018.x editors."
          ]
        },
        {
          "id": "willingness-to-pay",
          "label": "Willingness to pay",
          "weight": 0.2,
          "score": 4.5,
          "reasoning": "Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.",
          "evidence": [
            "Fixed fee per pre-signing audit, plus a per-milestone monitoring subscription for publishers and game-focused investors.",
            "Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price."
          ]
        },
        {
          "id": "competitive-saturation",
          "label": "Competitive saturation",
          "weight": 0.18,
          "score": 5.4,
          "reasoning": "Competitive room is reduced by 1 recorded alternative(s); the wedge must stay narrow and differentiated.",
          "evidence": [
            "Recorded alternative: madewithlove Technical Due Diligence",
            "Competitive score rewards a narrow wedge, not absence of research."
          ]
        },
        {
          "id": "feasibility",
          "label": "Feasibility",
          "weight": 0.16,
          "score": 4,
          "reasoning": "Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.",
          "evidence": [
            "Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.",
            "Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews."
          ]
        }
      ],
      "nextValidationStep": "Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.",
      "generatedAt": "Sun Nov 08 2026 09:00:00 GMT+0100 (Central European Standard Time)"
    },
    "tags": [
      "game-development",
      "due-diligence",
      "licensing"
    ],
    "sources": [
      "https://unity.com/security/sept-2025-01",
      "https://unity.com/products/pricing-updates",
      "https://gamefromscratch.com/unreal-engine-launch-everywhere-with-epic/",
      "https://www.gamedevoutsourcing.com/answers/what-publishers-look-for-in-external-studios"
    ],
    "affiliate": false,
    "affiliateProducts": [],
    "reportGeneratedAt": "Sun Nov 08 2026 09:00:00 GMT+0100 (Central European Standard Time)",
    "oneLine": "Tech due diligence for game publishing deals should be tested as a narrow first-win workflow for one buyer: Head of production or business development at an independent game publisher that funds external studios against milestones.",
    "complaintSeeds": [],
    "scorecard": [
      {
        "label": "Opportunity",
        "score": 4,
        "rating": "Needs proof",
        "detail": "Tech due diligence for game publishing deals has an editorial confidence score of 38/100 before live buyer validation."
      },
      {
        "label": "Problem",
        "score": 3,
        "rating": "Needs proof",
        "detail": "Publishers commit milestone funding on the strength of a vertical slice and a pitch, then learn months later that the build sits on an outdated or unpatched engine version, depends on middleware nobody licensed for the target platforms, has no reproducible build pipeline, or will struggle with console certification. Technical surprises become slipped milestones, re-scoping and write-offs, and generic software due-diligence firms don't cover engines, platform certification or game middleware."
      },
      {
        "label": "Feasibility",
        "score": 4,
        "rating": "Needs proof",
        "detail": "A high build can work if the MVP stays limited to the first repeated workflow."
      },
      {
        "label": "Why now",
        "score": 8,
        "rating": "Strong",
        "detail": "Engine and middleware terms keep shifting under live projects: Unity raised Pro and Enterprise prices 5% from January 12, 2026 and no longer includes Havok Physics with paid plans from Unity 6.3, and Unreal's 3.5% 'Launch Everywhere with Epic' royalty (instead of 5%) since January 1, 2025 depends on ongoing release conditions. In October 2025 Unity patched CVE-2025-59489 in builds from 2017.1 onward, with no patch for 2017 and 2018 editors, which made engine version a security question."
      }
    ],
    "businessFit": {
      "revenuePotential": "$250K-$2M ARR potential if the wedge proves budget urgency and becomes a recurring workflow.",
      "executionDifficulty": "Execution is high; the main constraint is staying narrow enough for a first proof loop.",
      "goToMarket": "Start with manual concierge output, direct outreach, and community proof before paid acquisition.",
      "founderFit": "Best for an AI-assisted solo founder who can interview the buyer and ship a focused first version quickly."
    },
    "offerLadder": [
      {
        "stage": "lead-magnet",
        "label": "Lead magnet",
        "offer": "Tech Due Diligence For Game Publishing Deals checklist",
        "price": "Free",
        "valueProvided": "Helps Head of production or business development at an independent game publisher that funds external studios against milestones audit the painful workflow before buying software.",
        "goal": "Capture qualified leads and learn the buyer's exact language."
      },
      {
        "stage": "frontend",
        "label": "Frontend offer",
        "offer": "Concierge review or paid template",
        "price": "$19-$99",
        "valueProvided": "Delivers the first useful output manually before automation is trusted.",
        "goal": "Validate urgency, workflow fit, and willingness to pay."
      },
      {
        "stage": "core",
        "label": "Core offer",
        "offer": "Tech due diligence for game publishing deals focused SaaS",
        "price": "$49-$499/month",
        "valueProvided": "Turns the recurring manual workflow into a repeatable product loop.",
        "goal": "Create the recurring revenue product after the narrow wedge survives tests."
      },
      {
        "stage": "continuity",
        "label": "Continuity",
        "offer": "Monitoring, benchmarks, and monthly reporting",
        "price": "$99-$1,000/year add-on",
        "valueProvided": "Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.",
        "goal": "Increase retention and make the product part of a routine."
      },
      {
        "stage": "backend",
        "label": "Backend offer",
        "offer": "Done-with-you setup, agency, or team rollout",
        "price": "Custom",
        "valueProvided": "Adds implementation help, integrations, and workflow migration.",
        "goal": "Capture higher-value accounts once the productized wedge is proven."
      }
    ],
    "economics": {
      "pricingAnchor": {
        "offer": "Tech due diligence for game publishing deals focused SaaS",
        "priceLow": 49,
        "priceHigh": 499,
        "cadence": "/month",
        "basis": "Derived from this report's \"Core offer\" offer-ladder stage ($49-$499/month). These are price-anchored scenarios, not market-size claims."
      },
      "scenarios": [
        {
          "label": "Proof",
          "customers": 10,
          "mrrLow": 490,
          "mrrHigh": 4990,
          "note": "Ten paying customers proves willingness to pay and funds continued validation."
        },
        {
          "label": "Wedge",
          "customers": 50,
          "mrrLow": 2450,
          "mrrHigh": 24950,
          "note": "Fifty customers in one niche makes the workflow the default in that circle and feeds referrals."
        },
        {
          "label": "Vertical leader",
          "customers": 250,
          "mrrLow": 12250,
          "mrrHigh": 124750,
          "note": "A few hundred accounts in one vertical is a real business before any horizontal expansion."
        }
      ],
      "breakEven": "At $49-$499/month, 1 customers cover the stated Local-first MVP budget: $0-$10K before paid acquisition. budget within a month; fewer if they land at the top of the range.",
      "sizingHypothesis": "Size the buyer universe in one day: count head of production or business development at an independent game publisher that funds external studios against milestones reachable through the report's channels (directories, associations, communities) until the list stops growing — the test only needs the first 100 names, not a TAM estimate.",
      "benchmark": "1 adjacent product recorded (0 strong). Position the price against what head of production or business development at an independent game publisher that funds external studios against milestones already pays in time or tooling, and verify each named alternative's public pricing during the sprint."
    },
    "whyNowFactors": [
      {
        "label": "Demand visibility",
        "score": 3,
        "signal": "Unity's advisory for CVE-2025-59489 (CVSS 8.4, patch available October 2, 2025) tells developers to upgrade the Editor and rebuild, or apply a binary patch, and lists no patch for 2017.x and 2018.x editors.",
        "detail": "Build only if the complaint repeats across interviews, posts, or existing workflow artifacts.",
        "evidenceUrl": "https://unity.com/security/sept-2025-01"
      },
      {
        "label": "Tooling readiness",
        "score": 4,
        "signal": "AI-assisted product work and managed infrastructure reduce the first-version cost.",
        "detail": "The first release should automate one high-friction step rather than become a broad platform.",
        "evidenceUrl": "https://unity.com/products/pricing-updates"
      },
      {
        "label": "Budget clarity",
        "score": 3,
        "signal": "Fixed fee per pre-signing audit, plus a per-milestone monitoring subscription for publishers and game-focused investors.",
        "detail": "Ask for money during validation before building the full workflow.",
        "evidenceUrl": "https://unity.com/security/sept-2025-01"
      },
      {
        "label": "Competitive window",
        "score": 7,
        "signal": "The wedge is specific enough to test without claiming the whole market.",
        "detail": "Position around one buyer and one measurable first-win outcome.",
        "evidenceUrl": "https://unity.com/security/sept-2025-01"
      }
    ],
    "proofSignals": [
      {
        "category": "Pain",
        "score": 3,
        "title": "Repeated workflow friction",
        "detail": "Unity's advisory for CVE-2025-59489 (CVSS 8.4, patch available October 2, 2025) tells developers to upgrade the Editor and rebuild, or apply a binary patch, and lists no patch for 2017.x and 2018.x editors.",
        "evidenceUrl": "https://unity.com/security/sept-2025-01"
      },
      {
        "category": "Money",
        "score": 3,
        "title": "Budget hypothesis",
        "detail": "Head of production or business development at an independent game publisher that funds external studios against milestones is the first group to test because the monetization path is: Fixed fee per pre-signing audit, plus a per-milestone monitoring subscription for publishers and game-focused investors.",
        "evidenceUrl": "https://unity.com/security/sept-2025-01"
      },
      {
        "category": "Urgency",
        "score": 4,
        "title": "Switching pressure",
        "detail": "Urgency becomes real only if the current workaround costs time, risk, money, or reputation every week.",
        "evidenceUrl": "https://unity.com/products/pricing-updates"
      },
      {
        "category": "Distribution",
        "score": 10,
        "title": "Reachable buyer language",
        "detail": "The first channel should be whichever source lane already contains the buyer's vocabulary.",
        "evidenceUrl": "https://unity.com/security/sept-2025-01"
      }
    ],
    "existingProducts": [
      {
        "title": "madewithlove Technical Due Diligence",
        "url": "https://madewithlove.com/technical-due-diligence/",
        "sourceName": "madewithlove",
        "sourceType": "vendor-site",
        "strength": "possible",
        "rationale": "Established investor-side technical due diligence (60+ items, about two weeks) for SaaS companies and startups; it does not cover game engines, console certification or middleware licensing."
      }
    ],
    "marketGap": {
      "underservedSegments": [
        "Head of production or business development at an independent game publisher that funds external studios against milestones who still run the workflow in spreadsheets, generic docs, email, or chat threads.",
        "Small teams in Game publishing and investment that feel the pain weekly but are too narrow for broad incumbents.",
        "New adopters who need guided proof before committing to a larger platform."
      ],
      "featureGaps": [
        "A narrow workflow that reaches value without configuration-heavy onboarding.",
        "A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.",
        "A handoff path from manual concierge service to repeatable software."
      ],
      "differentiationLevers": [
        "Use specificity as the wedge: one buyer, one workflow, one measurable result.",
        "Show proof earlier than broad competitors with before-and-after examples and small pilot data.",
        "Keep implementation lighter than incumbent suites or generic AI assistants."
      ]
    },
    "executionPlan": {
      "businessType": "Data and intelligence product",
      "timeline": "8-12 weeks",
      "budget": "Local-first MVP budget: $0-$10K before paid acquisition.",
      "buyerPersonas": [
        "Head of production or business development at an independent game publisher that funds external studios against milestones",
        "Budget owner who feels the operational cost of the broken workflow.",
        "Hands-on operator willing to pilot a narrow tool before a full rollout."
      ],
      "painPoints": [
        "Publishers commit milestone funding on the strength of a vertical slice and a pitch, then learn months later that the build sits on an outdated or unpatched engine version, depends on middleware nobody licensed for the target platforms, has no reproducible build pipeline, or will struggle with console certification. Technical surprises become slipped milestones, re-scoping and write-offs, and generic software due-diligence firms don't cover engines, platform certification or game middleware.",
        "Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.",
        "Console certification requirements sit behind platform NDAs, so the checklist must be run with the studio's own developer access rather than published by the vendor."
      ],
      "mvpApproach": "Build only the first-win workflow for \"Tech due diligence for game publishing deals\" and keep research, setup, and exceptions manual until the wedge is proven.",
      "initialOffer": "Concierge review or paid template",
      "acquisitionChannels": [
        {
          "channel": "Community pain posts",
          "cadence": "Weekly",
          "why": "Use communities and forums where Head of production or business development at an independent game publisher that funds external studios against milestones already describe the painful workflow.",
          "format": "Problem teardown, interview ask, and short demo clip",
          "targetMetric": "5 qualified calls or 10 detailed replies in 7 days"
        },
        {
          "channel": "Direct outreach",
          "cadence": "Daily during validation",
          "why": "Direct conversations are the fastest way to verify budget ownership and switching cost.",
          "format": "Concierge pilot offer with a manually prepared sample",
          "targetMetric": "3 paid pilots, LOIs, or budget-owner follow-ups"
        },
        {
          "channel": "Searchable comparison content",
          "cadence": "Bi-weekly",
          "why": "Alternative and comparison pages reveal objections, pricing language, and buying intent.",
          "format": "Before-and-after page or alternatives memo for the exact workflow",
          "targetMetric": "Organic clicks, booked demos, or waitlist joins from comparison intent"
        },
        {
          "channel": "Launch directory",
          "cadence": "Once MVP is clickable",
          "why": "Launches test whether the promise is legible to people outside the first interview set.",
          "format": "Single-purpose demo and first-win story",
          "targetMetric": "25% demo completion or 10 waitlist joins"
        }
      ],
      "milestones": [
        "Interview 10 people who match the buyer persona.",
        "Ship a clickable demo or concierge workflow that produces the first useful artifact.",
        "Run one paid pilot or collect explicit pricing objections before automating the rest.",
        "Promote to a deeper build plan only after the wedge survives validation."
      ],
      "successMetrics": [
        "Problem resonance: 5+ calls or 10+ detailed replies.",
        "Activation: 25% of demo visitors complete the first-win path.",
        "Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps."
      ],
      "risks": [
        "Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.",
        "Console certification requirements sit behind platform NDAs, so the checklist must be run with the studio's own developer access rather than published by the vendor.",
        "Deal volume per publisher is small, so revenue depends on the audit becoming a standard step that publishers and investors require.",
        "Trying to build a broad platform before the narrow workflow has proof."
      ],
      "nextActions": [
        "Write the one-sentence promise and test it in the strongest channel.",
        "Create the lead magnet and use it to recruit interviews.",
        "Build the smallest demo that proves the first win."
      ]
    },
    "frameworks": {
      "valueEquation": {
        "dreamOutcome": {
          "label": "Dream outcome",
          "score": 7,
          "rating": "Strong",
          "detail": "The buyer gets a visible first win around Tech due diligence for game publishing deals."
        },
        "perceivedLikelihood": {
          "label": "Perceived likelihood",
          "score": 6,
          "rating": "Promising",
          "detail": "Trust depends on proof, demos, and credible source links."
        },
        "timeDelay": {
          "label": "Time delay",
          "score": 4,
          "rating": "Needs proof",
          "detail": "Short setup and concierge onboarding make the promise easier to believe."
        },
        "effortAndSacrifice": {
          "label": "Effort and sacrifice",
          "score": 4,
          "rating": "Needs proof",
          "detail": "Reduce switching cost with imports, templates, and a manual migration path."
        },
        "improvements": [
          "Increase proof with a specific before-and-after demo.",
          "Reduce time to value with concierge onboarding.",
          "Remove effort by deferring integrations until one workflow is proven."
        ]
      },
      "marketMatrix": {
        "uniqueness": 7,
        "customerValue": 5,
        "quadrant": "Novel but unproven",
        "detail": "High value plus high uniqueness deserves deeper research; lower uniqueness requires a clear distribution advantage."
      },
      "acp": {
        "audience": {
          "label": "Audience",
          "score": 3,
          "rating": "Needs proof",
          "detail": "Head of production or business development at an independent game publisher that funds external studios against milestones"
        },
        "community": {
          "label": "Community",
          "score": 9,
          "rating": "Exceptional",
          "detail": "Use the strongest source lane as the first reachable community."
        },
        "product": {
          "label": "Product",
          "score": 4,
          "rating": "Needs proof",
          "detail": "Keep the first product narrower than the market category."
        }
      },
      "categorization": {
        "type": "Data and intelligence product",
        "market": "Game publishing and investment",
        "target": "Head of production or business development at an independent game publisher that funds external studios against milestones",
        "mainCompetitor": "madewithlove Technical Due Diligence",
        "trendAnalysis": "Trend and keyword signals are directional until verified with live customers and source citations."
      }
    },
    "communitySignals": [
      {
        "channel": "Reddit / forums",
        "count": "Research lane",
        "signal": "Look for complaints, workarounds, and repeated questions.",
        "firstMove": "Post a problem teardown for Game publishing and investment and ask how people solve it today."
      },
      {
        "channel": "Launch communities",
        "count": "Validation lane",
        "signal": "Launch traction shows whether the promise is legible.",
        "firstMove": "Ship a narrow demo and watch which promise gets clicks."
      },
      {
        "channel": "Review and alternative pages",
        "count": "Objection lane",
        "signal": "Pricing and alternatives expose buyer objections.",
        "firstMove": "Write an alternatives page that owns one narrow use case."
      }
    ],
    "keywordAnalysis": {
      "summary": "Keyword signals should be treated as directional. The strongest terms combine Game publishing and investment, the buyer workflow, and the first output the product creates.",
      "fastestGrowing": [
        {
          "keyword": "tech ai",
          "volume": "directional medium",
          "growth": "rising with AI adoption",
          "competition": "medium"
        },
        {
          "keyword": "diligence automation",
          "volume": "directional low",
          "growth": "steady niche demand",
          "competition": "medium"
        }
      ],
      "highestVolume": [
        {
          "keyword": "game software",
          "volume": "directional medium",
          "growth": "rising with AI adoption",
          "competition": "high"
        },
        {
          "keyword": "publishing template",
          "volume": "directional low",
          "growth": "steady niche demand",
          "competition": "medium"
        }
      ],
      "mostRelevant": [
        {
          "keyword": "tech workflow",
          "volume": "directional medium",
          "growth": "rising with AI adoption",
          "competition": "medium"
        },
        {
          "keyword": "diligence validation",
          "volume": "directional low",
          "growth": "steady niche demand",
          "competition": "low"
        }
      ],
      "source": "IdeaNavigator AI editorial keyword heuristic",
      "freshness": "generated with the daily report"
    },
    "founderFit": {
      "score": 6,
      "idealFor": "A solo or AI-assisted founder with direct access to Head of production or business development at an independent game publisher that funds external studios against milestones.",
      "advantages": [
        "Can talk to the buyer before writing much code.",
        "Can ship a narrow first-win demo quickly.",
        "Can use local-first research artifacts to keep validation moving without a large team."
      ],
      "gaps": [
        "Needs real buyer access, not only desk research.",
        "Needs proof of budget or repeated urgency.",
        "Needs a crisp wedge before broad product work starts."
      ],
      "avoidIf": [
        "You cannot reach the buyer directly.",
        "The idea only sounds interesting but does not save time, money, risk, or reputation.",
        "You want to build the full platform before validating the first workflow."
      ],
      "nextMove": "Run the lead magnet and first-win demo tests before promoting the broad version."
    },
    "roast": {
      "verdict": "Interesting hypothesis, but it needs sharper demand evidence before build time.",
      "blindSpots": [
        "Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.",
        "A broad AI assistant can flatten differentiation unless the wedge is painfully specific.",
        "The first release can become a generic dashboard if the job is not named tightly."
      ],
      "hardQuestions": [
        "Who wakes up already trying to solve this?",
        "What do they stop paying for or stop doing when this works?",
        "What proof would make a skeptical buyer trust it in one screen?",
        "What is the smallest paid version of this idea?"
      ],
      "deRiskingMoves": [
        "Sell a manual pilot before building automation.",
        "Record five exact phrases buyers use to describe the pain.",
        "Cut any feature that does not support the first measurable win."
      ]
    },
    "buildActions": [
      "Delete any report section that feels generic before building.",
      "Run the lead magnet and first-win demo tests.",
      "Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach."
    ],
    "handoffPrompts": {
      "buildPrompt": "Build a narrow MVP for \"Tech due diligence for game publishing deals\" for Head of production or business development at an independent game publisher that funds external studios against milestones. Preserve the evidence, build only the first-win workflow, include source links, and treat Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price. as the first acceptance gate.",
      "reviewPrompt": "Review the \"Tech due diligence for game publishing deals\" MVP for over-breadth, unsupported claims, weak buyer proof, privacy risk, and missing validation instrumentation. Do not approve expansion until the kill criteria and success metrics are measurable."
    },
    "killCriteria": [
      "Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.",
      "No buyer can name a current cost in time, money, risk, or reputation.",
      "The first demo does not produce a clear next step, paid pilot, or specific objection."
    ],
    "sourceDetails": [
      {
        "title": "Unity Security Advisory sept-2025-01 (CVE-2025-59489)",
        "url": "https://unity.com/security/sept-2025-01",
        "sourceType": "vendor-docs",
        "summary": "Unity's advisory for the runtime flaw affecting builds from 2017.1 onward, with fixed Editor versions, a binary patch tool and no patch for 2017-2018."
      },
      {
        "title": "Unity Pricing Changes",
        "url": "https://unity.com/products/pricing-updates",
        "sourceType": "vendor-docs",
        "summary": "Unity's official timeline: Runtime Fee cancelled 2024, 5% Pro and Enterprise increase from January 12, 2026, Havok dropped from Unity 6.3."
      },
      {
        "title": "Unreal Engine Launch Everywhere with Epic (GameFromScratch)",
        "url": "https://gamefromscratch.com/unreal-engine-launch-everywhere-with-epic/",
        "sourceType": "trade media",
        "summary": "Explains the 3.5% Unreal royalty available from January 1, 2025 for games that ship on the Epic Games Store at the same time as elsewhere."
      },
      {
        "title": "What Publishers Look For in External Studios (Game Dev Outsourcing)",
        "url": "https://www.gamedevoutsourcing.com/answers/what-publishers-look-for-in-external-studios",
        "sourceType": "industry",
        "summary": "Directory guide listing certification history, pipeline compliance and milestone-gate record as publisher vetting criteria."
      }
    ]
  },
  "derived": {
    "economics": {
      "pricingAnchor": {
        "offer": "Tech due diligence for game publishing deals focused SaaS",
        "priceLow": 49,
        "priceHigh": 499,
        "cadence": "/month",
        "basis": "Derived from this report's \"Core offer\" offer-ladder stage ($49-$499/month). These are price-anchored scenarios, not market-size claims."
      },
      "scenarios": [
        {
          "label": "Proof",
          "customers": 10,
          "mrrLow": 490,
          "mrrHigh": 4990,
          "note": "Ten paying customers proves willingness to pay and funds continued validation."
        },
        {
          "label": "Wedge",
          "customers": 50,
          "mrrLow": 2450,
          "mrrHigh": 24950,
          "note": "Fifty customers in one niche makes the workflow the default in that circle and feeds referrals."
        },
        {
          "label": "Vertical leader",
          "customers": 250,
          "mrrLow": 12250,
          "mrrHigh": 124750,
          "note": "A few hundred accounts in one vertical is a real business before any horizontal expansion."
        }
      ],
      "breakEven": "At $49-$499/month, 1 customers cover the stated Local-first MVP budget: $0-$10K before paid acquisition. budget within a month; fewer if they land at the top of the range.",
      "sizingHypothesis": "Size the buyer universe in one day: count head of production or business development at an independent game publisher that funds external studios against milestones reachable through the report's channels (directories, associations, communities) until the list stops growing — the test only needs the first 100 names, not a TAM estimate.",
      "benchmark": "1 adjacent product recorded (0 strong). Position the price against what head of production or business development at an independent game publisher that funds external studios against milestones already pays in time or tooling, and verify each named alternative's public pricing during the sprint.",
      "isDerived": false
    },
    "reflexivity": {
      "type": "mixed",
      "score": 1,
      "confidence": "low",
      "signals": [
        {
          "label": "Platform play",
          "side": "fulfilling",
          "weight": 1,
          "basis": "matched \"platform\""
        }
      ],
      "headline": "Mixed reflexivity — execution over secrecy",
      "publishGuidance": "No dominant reflexivity signal. Publish the analysis, but note that execution speed and distribution matter more than secrecy here; revisit if the space shows saturation."
    },
    "planspiel": null,
    "demand": {
      "slug": "game-publishing-tech-due-diligence",
      "verticalSlug": "software-ai",
      "buildYes": 0,
      "buildNo": 0,
      "payYes": 0,
      "payNo": 0,
      "claimCount": 0,
      "visitors": 0,
      "revealedDemand": 0,
      "signalStrength": "none",
      "drivers": []
    },
    "validationSprint": {
      "days": [
        {
          "day": 1,
          "title": "Build the buyer list",
          "action": "List 50-100 named head of production or business development at an independent game publisher that funds external studios against milestones prospects from Community pain posts and Direct outreach — names, not categories.",
          "threshold": "50+ named, reachable buyers on the list."
        },
        {
          "day": 2,
          "title": "Join the watering holes",
          "action": "Join and observe Reddit / forums, Launch communities, Review and alternative pages. Collect the exact words buyers use for this pain.",
          "threshold": "10+ verbatim pain quotes captured."
        },
        {
          "day": 3,
          "title": "Send first outreach",
          "action": "Send the cold outreach template (below) to 15 buyers from the day-1 list, personalized with one detail each.",
          "threshold": "15 sent; 3+ replies of any kind."
        },
        {
          "day": 4,
          "title": "Run buyer interviews",
          "action": "Hold 15-minute calls using the interview script (below). Listen for current workarounds and what they cost.",
          "threshold": "3+ completed interviews."
        },
        {
          "day": 5,
          "title": "Run the report's validation test",
          "action": "Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether...",
          "threshold": "Problem resonance: 5+ calls or 10+ detailed replies."
        },
        {
          "day": 6,
          "title": "Make the smoke offer",
          "action": "Offer \"Concierge review or paid template\" at $19-$99 to every interviewed buyer. Manual delivery is fine — payment is the signal.",
          "threshold": "1+ pre-commitment (payment, signed LOI, or scheduled paid pilot)."
        },
        {
          "day": 7,
          "title": "Decide against the kill criteria",
          "action": "Score the week against this report's kill criteria, then take the stated next validation step: Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether...",
          "threshold": "A written build / keep-testing / kill decision."
        }
      ],
      "passSignal": "Pass: thresholds on days 3, 4, and 6 are met — proceed to the next validation step with real buyer language in hand.",
      "failSignal": "Kill or rethink if the week confirms: Fewer than five qualified buyers agree to discuss the workflow after targeted outreach."
    },
    "executionReadiness": {
      "score": 35,
      "tier": "Research first",
      "summary": "Tech due diligence for game publishing deals scores 35/100 for execution readiness. The recommended next step is Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.",
      "bottlenecks": [
        "Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.",
        "Console certification requirements sit behind platform NDAs, so the checklist must be run with the studio's own developer access rather than published by the vendor.",
        "Deal volume per publisher is small, so revenue depends on the audit becoming a standard step that publishers and investors require.",
        "A broad AI assistant can flatten differentiation unless the wedge is painfully specific.",
        "The first release can become a generic dashboard if the job is not named tightly.",
        "Needs real buyer access, not only desk research.",
        "Needs proof of budget or repeated urgency."
      ],
      "accelerators": [
        "Can talk to the buyer before writing much code.",
        "Can ship a narrow first-win demo quickly.",
        "Can use local-first research artifacts to keep validation moving without a large team.",
        "Use specificity as the wedge: one buyer, one workflow, one measurable result.",
        "Show proof earlier than broad competitors with before-and-after examples and small pilot data.",
        "Keep implementation lighter than incumbent suites or generic AI assistants.",
        "Concierge review or paid template"
      ],
      "firstActions": [
        "Write the one-sentence promise and test it in the strongest channel.",
        "Create the lead magnet and use it to recruit interviews.",
        "Build the smallest demo that proves the first win.",
        "Delete any report section that feels generic before building.",
        "Run the lead magnet and first-win demo tests.",
        "Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach."
      ],
      "launchPlan": [
        {
          "date": "2026-11-08",
          "title": "Frame the wedge",
          "action": "Write the one-sentence promise and test it in the strongest channel.",
          "proof": "Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price."
        },
        {
          "date": "2026-11-11",
          "title": "Interview 10 people who match the buyer persona.",
          "action": "Create the lead magnet and use it to recruit interviews.",
          "proof": "Problem resonance: 5+ calls or 10+ detailed replies."
        },
        {
          "date": "2026-11-15",
          "title": "Ship a clickable demo or concierge workflow that produces the first useful artifact.",
          "action": "Build the smallest demo that proves the first win.",
          "proof": "Activation: 25% of demo visitors complete the first-win path."
        },
        {
          "date": "2026-11-22",
          "title": "Run one paid pilot or collect explicit pricing objections before automating the rest.",
          "action": "Delete any report section that feels generic before building.",
          "proof": "Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps."
        },
        {
          "date": "2026-11-29",
          "title": "Promote to a deeper build plan only after the wedge survives validation.",
          "action": "Run the lead magnet and first-win demo tests.",
          "proof": "Fewer than five qualified buyers agree to discuss the workflow after targeted outreach."
        },
        {
          "date": "2026-12-08",
          "title": "Execution checkpoint 6",
          "action": "Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.",
          "proof": "Promote to a deeper build plan only after the wedge survives validation."
        }
      ],
      "builderPrompt": "Create a dated execution plan for \"Tech due diligence for game publishing deals\". Keep the first milestone tied to Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.. Use these bottlenecks: Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.; Console certification requirements sit behind platform NDAs, so the checklist must be run with the studio's own developer access rather than published by the vendor.; Deal volume per publisher is small, so revenue depends on the audit becoming a standard step that publishers and investors require.; A broad AI assistant can flatten differentiation unless the wedge is painfully specific.; The first release can become a generic dashboard if the job is not named tightly.; Needs real buyer access, not only desk research.; Needs proof of budget or repeated urgency.. Use these accelerators: Can talk to the buyer before writing much code.; Can ship a narrow first-win demo quickly.; Can use local-first research artifacts to keep validation moving without a large team.; Use specificity as the wedge: one buyer, one workflow, one measurable result.; Show proof earlier than broad competitors with before-and-after examples and small pilot data.; Keep implementation lighter than incumbent suites or generic AI assistants.; Concierge review or paid template. Link the output to the Idea Builder prompt and do not expand beyond the first validated workflow.",
      "markdown": "# Execution Scorecard: Tech due diligence for game publishing deals\n\nScore: 35/100\n\nTier: Research first\n\nTech due diligence for game publishing deals scores 35/100 for execution readiness. The recommended next step is Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.\n\n## Bottlenecks\n- Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.\n- Console certification requirements sit behind platform NDAs, so the checklist must be run with the studio's own developer access rather than published by the vendor.\n- Deal volume per publisher is small, so revenue depends on the audit becoming a standard step that publishers and investors require.\n- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.\n- The first release can become a generic dashboard if the job is not named tightly.\n- Needs real buyer access, not only desk research.\n- Needs proof of budget or repeated urgency.\n\n## Accelerators\n- Can talk to the buyer before writing much code.\n- Can ship a narrow first-win demo quickly.\n- Can use local-first research artifacts to keep validation moving without a large team.\n- Use specificity as the wedge: one buyer, one workflow, one measurable result.\n- Show proof earlier than broad competitors with before-and-after examples and small pilot data.\n- Keep implementation lighter than incumbent suites or generic AI assistants.\n- Concierge review or paid template\n\n## Dated Launch Plan\n- **2026-11-08 / Frame the wedge**: Write the one-sentence promise and test it in the strongest channel. Proof: Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.\n- **2026-11-11 / Interview 10 people who match the buyer persona.**: Create the lead magnet and use it to recruit interviews. Proof: Problem resonance: 5+ calls or 10+ detailed replies.\n- **2026-11-15 / Ship a clickable demo or concierge workflow that produces the first useful artifact.**: Build the smallest demo that proves the first win. Proof: Activation: 25% of demo visitors complete the first-win path.\n- **2026-11-22 / Run one paid pilot or collect explicit pricing objections before automating the rest.**: Delete any report section that feels generic before building. Proof: Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n- **2026-11-29 / Promote to a deeper build plan only after the wedge survives validation.**: Run the lead magnet and first-win demo tests. Proof: Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n- **2026-12-08 / Execution checkpoint 6**: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach. Proof: Promote to a deeper build plan only after the wedge survives validation.\n\n## Builder Prompt\nCreate a dated execution plan for \"Tech due diligence for game publishing deals\". Keep the first milestone tied to Offer three publishers a discounted audit on a current or recently signed deal, compare the findings with what later went wrong in production, and ask whether each would make the audit a standard pre-signing step at the quoted price.. Use these bottlenecks: Studios may refuse source access before a deal is signed, limiting the audit to builds, documents and interviews.; Console certification requirements sit behind platform NDAs, so the checklist must be run with the studio's own developer access rather than published by the vendor.; Deal volume per publisher is small, so revenue depends on the audit becoming a standard step that publishers and investors require.; A broad AI assistant can flatten differentiation unless the wedge is painfully specific.; The first release can become a generic dashboard if the job is not named tightly.; Needs real buyer access, not only desk research.; Needs proof of budget or repeated urgency.. Use these accelerators: Can talk to the buyer before writing much code.; Can ship a narrow first-win demo quickly.; Can use local-first research artifacts to keep validation moving without a large team.; Use specificity as the wedge: one buyer, one workflow, one measurable result.; Show proof earlier than broad competitors with before-and-after examples and small pilot data.; Keep implementation lighter than incumbent suites or generic AI assistants.; Concierge review or paid template. Link the output to the Idea Builder prompt and do not expand beyond the first validated workflow.\n"
    },
    "firstContactKit": {
      "subjectLines": [
        "Question about tech workflow",
        "How are you handling publishers commit milestone funding on the strength of a ve...",
        "15 minutes on a game publishing and investment workflow?"
      ],
      "coldMessage": "Hi {{firstName}},\n\nI'm researching how head of production or business development at an independent game publisher that funds external studios against milestones handle this today: Publishers commit milestone funding on the strength of a vertical slice and a pitch, then learn months later that the build sits on an outd...\n\nI'm not selling anything yet — I'm testing whether \"Tech due diligence for game publishing deals\" is worth building, and I'd rather learn from people living the workflow than guess.\n\nWould you trade 15 minutes for first access (and a say in what gets built) if it goes ahead?\n\n{{yourName}}",
      "interviewQuestions": [
        "Walk me through the last time this happened: Publishers commit milestone funding on the strength of a vertical slice and a pitch, then learn months later that the b... What did you actually do?",
        "What does that workaround cost you — in hours, money, or risk — in a normal month?",
        "What have you already tried or bought to fix it, and why didn't it stick?",
        "If \"A fixed-scope audit kit: a scanner run under NDA on the studio's repository and build machine that...\" existed, what would have to be true for you to switch in the first week?",
        "Who else feels this worse than you do — and would you introduce me?"
      ],
      "whereToSend": [
        "Community pain posts — Problem teardown, interview ask, and short demo clip",
        "Direct outreach — Concierge pilot offer with a manually prepared sample",
        "Searchable comparison content — Before-and-after page or alternatives memo for the exact workflow",
        "Reddit / forums — Post a problem teardown for Game publishing and investment and ask how people solve it today.",
        "Launch communities — Ship a narrow demo and watch which promise gets clicks."
      ]
    },
    "lifecycle": {
      "schemaVersion": "INAV-LIFECYCLE-1",
      "slug": "game-publishing-tech-due-diligence",
      "stage": "Crowding",
      "stageRank": 3,
      "timingScore": 28,
      "timingBand": "closing",
      "timingLabel": "Window closing",
      "summary": "Crowding (28/100): demand exists, but funded or visible competitors are compressing the window.",
      "drivers": [
        "Adoption substrate is up 20.8% across matched packages."
      ],
      "cautions": [
        "2 matched company signals raise saturation.",
        "2 funded competitor signals reduce timing."
      ],
      "components": {
        "recheckStatus": "not-yet-eligible",
        "demandScore": 55,
        "trendScore": 0,
        "adoptionVelocity": 20.8,
        "saturationScore": 68,
        "competitorCount": 3,
        "fundedCompetitorCount": 2,
        "complaintEchoScore": 22,
        "ageDays": 1
      },
      "matchedCompanies": [
        {
          "name": "AppFolio",
          "category": "Property management software",
          "funded": true,
          "funding": {
            "round": "Public",
            "amount": "IPO 2015",
            "date": "2015-06-26"
          }
        },
        {
          "name": "ServiceTitan",
          "category": "Field service management",
          "funded": true,
          "funding": {
            "round": "IPO",
            "amount": "$625M",
            "date": "2024-12-12"
          }
        }
      ]
    },
    "verticalContext": {
      "vertical": {
        "slug": "software-ai",
        "name": "Software, AI & Developer Tooling",
        "shortName": "Software & AI",
        "description": "Developer teams, SaaS operators, AI builders, and infrastructure owners who need reliability, observability, and AI-output quality control.",
        "keywords": [
          "software",
          "developer",
          "saas",
          "ai operations",
          "ai tooling",
          "devops",
          "open-source",
          "open source",
          "api",
          "data center",
          "web operations",
          "infrastructure",
          "ai-ops",
          "llm",
          "ai quality",
          "cybersecurity",
          "cyber",
          "identity and access",
          "ai agents",
          "applied research",
          "applied science",
          "machine learning"
        ]
      },
      "hubUrl": "/verticals/software-ai/",
      "rank": 62,
      "total": 62,
      "standing": "Ranked 62 of 62 by validation score among published Software, AI & Developer Tooling reports.",
      "related": [
        {
          "title": "AI workflow reliability monitor for small teams",
          "slug": "ai-workflow-reliability-monitor-for-small-teams",
          "url": "/ideas/ai-workflow-reliability-monitor-for-small-teams/",
          "market": "AI operations",
          "verdict": "Validate",
          "validationScore": 79
        },
        {
          "title": "AI operations signal monitor: Amazon CEO's talks with U.S. officials triggered crackdown on Anthropic models",
          "slug": "ai-operations-signal-monitor-amazon-ceo-s-talks-with-u-s-officials-triggered-crackdown-on-anthropic-models",
          "url": "/ideas/ai-operations-signal-monitor-amazon-ceo-s-talks-with-u-s-officials-triggered-crackdown-on-anthropic-models/",
          "market": "AI operations",
          "verdict": "Validate",
          "validationScore": 78
        },
        {
          "title": "AI operations signal monitor: AMD acquires Taalas to boost inference performance by etching models in silicon",
          "slug": "ai-operations-signal-monitor-amd-acquires-taalas-to-boost-inference-performance-by-etching-models-in-silicon",
          "url": "/ideas/ai-operations-signal-monitor-amd-acquires-taalas-to-boost-inference-performance-by-etching-models-in-silicon/",
          "market": "AI operations",
          "verdict": "Validate",
          "validationScore": 78
        }
      ],
      "tagRelated": [
        {
          "title": "Licensing and approvals hub for voice actors' AI clones",
          "slug": "licensing-app-for-voice-actors-monetizing-their-ai-clones",
          "url": "/ideas/licensing-app-for-voice-actors-monetizing-their-ai-clones/",
          "market": "Voice-talent licensing and rights management",
          "verdict": "Research",
          "validationScore": 50
        }
      ]
    }
  }
}