Failure PatternDecision layer

The Scoopkit Archive Window Trap: Why Agencies Fail With Scoopkit on Retainer Clients

Symptom: Client asks for a six-month trend retrospective and the Free tier's 45-day archive returns nothing before that cutoff, forcing a scramble to rebuild history from screenshots. Root cause: Archive depth is a plan boundary, not a setting: Free holds 45 days and Pro extends to 12 months, so any client deliverable with a lookback longer than the subscribed tier silently returns empty result sets rather than an error.

By InnovaAI ResearchPublished

Trend Signal Monitoring
How do you recognize it?
  • •Client asks for a six-month trend retrospective and the Free tier's 45-day archive returns nothing before that cutoff, forcing a scramble to rebuild history from screenshots
  • •Monthly API spend stays flat at $0 while the agency bills a monitoring retainer, because nobody upgraded past 100 requests/day and the dashboard silently shows stale events
  • •Two client dashboards display different article_count values for the same event_id because one integration polls REST while the other consumes the webhook payload at a different pipeline tick
  • •An agency pitches Scoopkit as a general news monitor, then discovers every event carries primary_category values from a fixed AI-industry taxonomy of 10 categories and 57 subcategories, so a client's fintech or climate brief has no home
  • •Delivery team burns hours hand-merging events that Scoopkit already clustered, because they never inspected the structured fields (event_id, headline, primary_category, article_count, reported_at) before building the UI
Why does it happen?
  • •Archive depth is a plan boundary, not a setting: Free holds 45 days and Pro extends to 12 months, so any client deliverable with a lookback longer than the subscribed tier silently returns empty result sets rather than an error
  • •The 100 requests/day Free ceiling is generous enough to demo convincingly, which lets an agency ship a client-facing product without ever hitting the wall until traffic scales past the pilot
  • •Scoopkit covers AI-industry news from dozens of sources on a 10-minute polling cycle; agencies that sell it as broad market intelligence inherit a coverage gap the vendor never claimed to fill
  • •Enterprise limits and archive are quote-only via contact sales, so agencies that outgrow Pro mid-contract have no self-serve upgrade path and stall delivery while procurement runs
How do you fix it?
  • •Audit every live client integration against its subscribed tier: confirm the archive window (45 days on Free, 12 months on Pro) exceeds the longest lookback any deliverable promises, and move clients to Pro at $49/month before the gap surfaces
  • •Pull the OpenAPI spec at api.scoopkit.dev/openapi.json and reconcile the 10-category/57-subcategory taxonomy against each client's brief; drop or re-scope any account whose subject matter falls outside AI-industry coverage
  • •Instrument request consumption per client key so the 100 req/day Free limit and the 10k req/day Pro limit are visible before throttling, not after a digest fails to send
  • •Standardize on one delivery mode per client (REST polling, webhooks, the npx scoopkit CLI, or the MCP server) and document which one owns the source of truth for event records, so article_count discrepancies stop reaching the client
Open the Scoopkit courseScoopkit decision recordBrowse the Academy

More on Scoopkit

More for Trend Signal Monitoring