Evgeny Krukov

Context: streaming production of SEO articles for agency clients. 20+ unrelated verticals, from screw piles and solid-fuel boilers to dentistry and accounting. One editor covers the whole path, from brief to published HTML page.

Problem: expensive competitor research was being repeated for every article. Meanwhile the text has to beat what already ranks, clear anti-spam filters, ship as finished HTML with Schema.org against the client's CMS contract, and be structured to be quoted by AI search.

Solution: separated the expensive one-off research from the cheap repeatable production. Market, niche and competitive field are analysed once and frozen into a permanent content plan that works as both an editorial calendar and a knowledge base. After that, a seven-step loop on a single command: brief from the plan, targeted analysis of 3–5 competitors, headline, draft, five quality-control skills in fixed order, quantitative verification through the official Turgenev API, delivery.

Result: production cycle cut from 2 days to 1 hour. 300+ published articles. Client site traffic from article SEO up to ×2, per the agency's data.

Role: pipeline architecture, build, operation, editorial ownership.

Full case study with architecture, pipeline and metrics — Full case study.

Context: large mobile live-service project, high volume of game, system, and UX text; pipeline ran on Google Sheets with custom scripts.

Problem: interlinked spreadsheets and scripts, separate export scripts per dev branch, high cost of edits, risk of desync.

Solution: full ownership of the migration to Gridly, including project structure, scheduled auto-export to Git, localization views, direct task assignment to localizers.

Result: task cycle cut from 25 working days to 45 working hours, major reduction in manual work, transparent scalable pipeline.

Role: Senior Game Writer / Text Production Owner.

Context: casual city-builder with match-3 mechanics, 6-week release cycle, one writer covering all text across several teams.

Task: stable, scalable production of every text type without quality loss or dev delays.

Solution: full ownership of the text block, pipeline simplification, automation, content prepared 2 versions ahead (proactive, not reactive).

Result: 1000+ lines of game text per release, task cycle cut from 25 working days to 45 working hours, no quality loss.

Role: Senior Game Writer, responsible for quality, volume, timelines, and production-readiness of all project text.

"Gardener's Calendar", Android + Web + Node app for Russian gardeners, live, monetized without ads. dacha.studio1008.com · app on RuStore · Google Play.

Room: a private social platform, profiles, live interaction, in development. room.studio1008.com.

Landing-page builder: my own platform for small-business websites. sites.studio1008.com.

Tender: an AI tender-analytics platform for a client, live on a VPS (NDA, private client work).

Web since 2008: 30+ sites on WordPress, Tilda, Taplink, LPGenerator, MODX and custom CMS — launch, setup, maintenance, content management. TemplateMonster certified. Own unified-RSS plugin for Dzen published in the WordPress.org catalogue.

SEO: 300+ texts across different niches, lead author of the Kontur agency blog. Details in the AI pipeline case above.

Brought AI into production at three companies, each time from scratch:

Belka Games, 2023: integrated ChatGPT and Gemini into the content pipeline, wrote internal prompting guidelines, trained the team.

Playrix: AI localization tooling alongside Gridly.

Kontur: a full production pipeline with automated quality control.

Same principle in all three: AI speeds up the draft, a human always owns the final quality call.