{
  "id": 12815110,
  "title": "From Prompt-and-Response to Agentic Workflows: Engineering an AI Content Platform for Telehealth",
  "url": "https://urgent.news/2026/10/08/from-prompt-and-response-to-agentic-workflows-engineering-an-ai",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-08T07:20:31.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/omjariwala/from-prompt-and-response-to-agentic-workflows-engineering-an-ai-content-platform-for-telehealth-4gjk"
  },
  "original_language": "en",
  "account": "A healthcare organization approached us with an AI-powered platform designed for SEO. While the prototype functioned effectively, it struggled to scale due to its architecture. The system relied heavily on a single AI provider and lacked the capability to handle multiple brands.\n\nThe challenge was to transform the prototype into a production-ready software without compromising the workflow that had been validated. We identified several key issues: the original architecture's limitations, the dependency on a single AI model, the absence of persistent context, the lack of human evaluation, and the need for compatibility with various publishing environments.\n\nTo address these issues, we restructured the workflow into a more complex, multi-stage process. Each stage had a specific responsibility, moving away from treating the LLM as a general-purpose assistant. We shifted the AI layer to OpenRouter, enabling the system to work with multiple models through a common integration. An additional layer for image generation was also incorporated.\n\nPersistent context was introduced to the workflow, allowing the system to remember previous stages and maintain continuity. This enabled different agents to work on various stages while retaining the necessary information. Despite the AI-generated content, human evaluation remained crucial, particularly in a domain like healthcare where quality is paramount. Human reviewers provided natural-language feedback, which became part of the system's context for future generations.\n\nRecognizing the need for compatibility with multiple publishing environments, we added CMS capabilities to the platform. This allowed the system to support both WordPress and Astro-based websites while maintaining compatibility with WordPress. Custom WordPress components were also created for specific generated content, such as HTML-based infographics.\n\nThe final result was a multi-tenant platform supporting around 14 brands. The system connected various stages, including discovery, research, AI agents, SEO/AEO/GEO evaluation, human feedback, CMS, and publishing. The key takeaway was not to use AI agents, but to understand when a prototype has progressed beyond the experimental stage. Once an AI workflow becomes part of a real healthcare business, reliability, context, model abstraction, human review, and scalable architecture must be considered as fundamental product requirements.",
  "summary": "A healthcare company came to us with an internal AI-powered SEO platform. The prototype already worked. It could research topics, generate content, perform SEO checks and publish to WordPress. The problem was scalability. As the system grew, it became increasingly difficult to maintain. The architecture relied too heavily on a single AI provider, browser-side state and workflows that were not…",
  "key_points": [
    "Transformed prototype into production-ready multi-tenant platform supporting 14 brands",
    "Restructured workflow into multi-stage process with persistent context and human evaluation",
    "Switched AI layer to OpenRouter for compatibility with multiple models"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}