{"slug":"gaming-fan-website-creation-serrvice","name":"Automated Game Lore Wiki","category":"Creatives","customer":"Product leads at independent game studios","problem":"Official game documentation is often incomplete and outdated while community knowledge is scattered across multiple platforms.","value":"For product leads at independent game studios, turn patch notes, developer streams and game data exports into a structured, searchable knowledge base. Address the problem of information silos where critical game details are lost in Discord threads and Reddit discussions. The value is a centralised, always current resource that reduces community support burden.","format":"Searchable structured library and data stewardship console","screens":"Key screens: Entity dashboard, source feed monitor, fact-check queue, changelog view. Use a dashboard to list all game entities, a feed monitor to show incoming official updates, a queue for human review of conflicts, and a changelog to track edits. The main screen is the entity dashboard, followed by the source feed monitor and fact-check queue.","functionality":"1. Ingest official communication feeds. 2. Extract structured entities like items and quests. 3. Generate narrative pages with cross-references. 4. Detect contradictions between versions. 5. Flag conflicts for human review. 6. Publish nightly updates with source attribution.","workflow":"Connect data sources, ingest historical data, run entity extraction, generate initial pages, run fact-checking, review flagged conflicts, publish site. Start with patch notes, developer streams and game data exports and finish with a structured, searchable knowledge base.","ai":"Use language models to parse unstructured text and extract entities. Use retrieval-augmented generation to write pages based on official sources. A human reviewer must verify lore accuracy and resolve contradictions before publication.","inputs":"Patch note URLs, developer stream links, game data exports, approved community guides","deliverables":"A structured, searchable knowledge base with source-linked pages and a public changelog","admin":"User roles for studio staff, version control for page edits, approval workflows for content, audit logs for source attribution, and access controls for public facing site","mvp":"Build for one indie studio with a single game. Ingest three months of patch notes and five blog posts. Generate pages for 200 core entities. Manual review of all generated content","expansion":"Automated daily monitoring of official channels, real-time updates to the site, and integration with community support tools","usp":"A knowledge base that updates itself daily from official sources, ensuring accuracy and completeness without manual editing","defensibility":"Accumulated data on game lore and version history creates a unique dataset that improves accuracy over time, making it harder for competitors to replicate","alternatives":"Manual wiki editing, community-maintained wikis like Fandom, and static documentation sites","revenue":"$500 per month per game","costs":"AI API costs for text processing and storage","integrations":"Steam patch notes, YouTube API, game data exports (JSON/XML)","dependencies":"NLP models, vector databases for entity linking, static site generator","pilot":"Provide the site to the studio and measure the reduction in support tickets related to game mechanics and lore","plan30":"Week 1: Set up ingestion pipelines for patch notes and streams. Week 2: Run entity extraction on historical data and generate initial pages. Week 3: Implement fact-checking logic and set up review queue. Week 4: Launch site and gather feedback on accuracy","metrics":"Number of questions answered without Discord search, accuracy rate of generated pages","channels":"Indie game dev forums, Steam community hubs, Discord servers","leadMagnet":"A free audit of your current community documentation","message":"Turn your patch notes into a living wiki that updates itself","retention":"Monthly subscription for continuous updates and new game support","controls":"Strict source linking to prevent hallucinations, manual approval gates for lore-heavy content, and version rollback capabilities","crossSector":"Product Development; Marketing","fn":["Ingest official communication feeds","Extract structured entities like items and quests","Generate narrative pages with cross-references","Detect contradictions between versions","Flag conflicts for human review","Publish nightly updates with source attribution"],"sc":{"opp":7,"pain":6,"feas":9,"now":8},"phases":[{"name":"MVP","scope":"One buyer segment, one recurring use case. Manual review in the loop.","time":{"days":2,"label":"2 days"},"usd":5500},{"name":"Paid pilot","scope":"Accounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.","time":{"days":3,"label":"3 days"},"usd":5000},{"name":"Full product","scope":"Self-serve onboarding, billing, monitoring and the wider integration set.","time":{"days":6,"label":"6 days"},"usd":7000}],"running":[{"stage":"MVP and paid pilot","note":"about 3 customers","hosting":[30,60],"ai":[50,100],"total":[80,160]},{"stage":"Full product","note":"about 50 customers","hosting":[110,210],"ai":[350,700],"total":[460,910]}],"total":17500,"complexity":0.08,"days":11,"shot":true,"demo":true}