Competitor activity turned into a weekly content plan

Competitor research that produces a weekly content plan

Services: AI Agents ; AI Workflow Automation
Delivery: Competitor-intelligence SaaS, AI strategy, subscriptions, and background processing.

The processing count is a historical reported figure. Plan capacity and timeouts describe the product, not customer growth.

The product needed to turn competitor activity into a strategy and content calendar for the user's business. That required more than a model call: competitor data had to arrive, remain usable, and refresh on a schedule.

Delivery exposed practical problems. Adding a competitor could create duplicate scrape jobs and spend collection credits repeatedly. Analysis could start before every competitor finished loading. Social-platform image URLs expired, leaving missing thumbnails. Stuck jobs left the interface loading indefinitely.

Those failures affected both the quality of the plan and the cost of producing it.

Business onboarding establishes the brand context. Users add competitors, collection jobs gather platform activity, and the backend prepares that material for AI strategy generation.

The application presents the playbook, competitor benchmarks, weekly insights, and a content calendar. Subscription billing and plan limits control access and usage. Scheduled updates repeat the collection and analysis workflow.

The March 27 delivery record documents parallel collection, duplicate-job prevention, and a generation gate: strategy, weekly update, and calendar run once after competitor loading finishes.

It also records persistent thumbnail storage to avoid expired CDN links and a fifteen-minute timeout for stuck jobs.

Make collection completion explicit. Generating a strategy before the inputs are ready risks producing an incomplete comparison and repeating paid model work.

Store media rather than depending on temporary URLs. The user needs to inspect the source post when reviewing the analysis.

Treat competitor slots as a billable resource. Deleting an accidental addition within two minutes refunds the slot. Later deletion does not reset consumption; slots renew with the billing period.

Make failure visible. A timed-out job needs an end state and an actionable message, not an endless spinner.

The product connects ingestion, strategy, weekly updates, calendar generation, billing, and administration. Existing portfolio records report 14,200+ posts processed.

The dated delivery log records fixes for duplicate jobs, repeated generation, expiring images, and indefinite loading. These are concrete operational improvements; the records do not establish a percentage reduction in marketing labor or growth in audience engagement.

Next.js and React; TypeScript, Node.js, Express, PostgreSQL; Apify; Anthropic Claude streaming API with structured parsing and retries; S3 media storage, FFmpeg tooling; Stripe; Resend; background ingestion and weekly workers.