Analyzing 8K+ Pages for $180: A Practical LLM Data Workflow
gaganghotra_ · x · 2026-07-21
A developer shared a hands-on case of using LLMs (Claude 3.5 Sonnet and Opus) to analyze data for a large client e-commerce site. - **Context**: The site is massive, featuring nearly 8,000 product pages, 183 collection pages, and over 4,000 blog posts. - **Workflow**: The developer fed 3 years of Google Search Console, GA4 (via BigQuery), and Shopify data into the models to analyze and identify pages that should be purged or merged. - **Cost & ROI**: Total token spend over a couple of weeks was around $180. It saved massive time compared to manual analysis, and the expense can be claimed as R&D and direct client deliverables for tax returns, making the net cost effectively zero.
More from coding & agent
- A one-page guide maps AI agents from core concepts to real-world use cases — goyalshaliniuk · 2026-07-21
- OxDeAI opensource protocol moves AI-agent policy checks before execution — docybo · 2026-07-21
- Kimi staff member builds a VR companion with Kimi Code K3 demo — dejavucoder · 2026-07-21
- Kimi K3 took 75 minutes and still failed a simple diagram task, user says — MinusKarma01 · 2026-07-21
- Coding agents need better rules for when to read search summaries or full pages — RhubarbLarge2747 · 2026-07-21
- Chart compares open tickets across Gemini, Codex, Claude, Grok and Opus 3 — nptacek · 2026-07-21