CoachingPortal's answer

CoachingPortal is the only coaching platform that combines three things in one place; auto-periodized training programs, a 1M+ food database with native meal planning, and white-label branding - all included on every plan, even free. Most competitors either do training or nutrition well, and almost none include white-labeling without charging extra for it. The auto-periodization engine alone is a genuine technical differentiator: no direct competitor ships this natively.

TranscriptFetch's answer:

Most short-form video has no caption track to download. TikTok’s auto-captions are opt-in per upload, Instagram never publishes a downloadable track, and many captions on both are burned into the video frames where no parser can read them. TranscriptFetch transcribes the audio when no caption track exists, on the same endpoint, with the same response shape. Your code never branches on which method produced the text. It also covers YouTube, TikTok, Instagram, X and Facebook plus any web page as clean Markdown, so a pipeline spanning several sources is one integration rather than five.

CoachingPortal's answer

Simpler economics - no confusing add-ons or tiers. What you see is what you pay. White-label branding from day one - your subdomain, logo, and colors, even on the free plan. Competitors like My PT Hub charge extra for this. Deeper nutrition, natively - 1M+ verified foods, 17,000+ recipes, barcode scanning, and AI smart food suggestions. TrueCoach relies on MyFitnessPal. Trainerize treats it as an add-on. Auto-periodization built in - no manual deload planning or progression tracking. The platform handles it automatically. PWA instead of a forced native app - clients get a polished, installable mobile experience without the coach dealing with app store submissions. Genuinely free to start - up to 5 clients, all features, no credit card. TrueCoach charges USD 26+ per month just to begin.

TranscriptFetch's answer:

Three reasons. Coverage: one API key and one response shape across five video platforms and the open web, instead of stitching together a library per platform. Reliability: requests run through rotating infrastructure, so code that works locally keeps working from a server, which is where most open-source approaches break. Billing that matches reality: one credit per successful response, with failed, blocked and empty results never charged. That last point matters on short-form video, where a meaningful share of any batch is music with no speech in it. There is also an MCP server, so AI agents can fetch transcripts as a tool without a custom integration.

CoachingPortal's answer

Online fitness coaches, nutrition coaches, and strength coaches who manage remote clients. Specifically:

Solo coaches and small coaching businesses who want to reduce admin and deliver a professional branded experience Coaches who currently use 3–5 separate tools and want everything in one place New coaches who want to start for free without risking money upfront Established coaches who are outgrowing basic platforms and need deeper nutrition + programming logic

TranscriptFetch's answer:

Developers and technical teams building on video and web content. The common cases are RAG and retrieval pipelines that need video as text, AI agents that need to read a link mid-conversation, content teams repurposing short-form video at scale, and media monitoring and research tools. It is an API first, so the buyer is usually the person writing the integration rather than an end user. The free browser tools exist for one-off transcripts and for evaluating output quality before writing any code.

CoachingPortal's answer

Based on the available product information, CoachingPortal's current customer base is made up of individual online coaches and small coaching businesses rather than large named enterprise accounts. The platform is purpose-built for:

Solo online fitness coaches Solo nutrition coaches Strength and performance coaches managing remote clients

CoachingPortal's answer

The fitness coaching world has a problem: talented coaches were spending more time on admin than actually coaching. They were duct-taping together multiple tools - a training app, a nutrition tracker, a client portal, a spreadsheet - none of which had their brand on it, and none of which talked to each other properly.

The insight behind CoachingPortal was twofold. First, a coach's brand is their business - their platform should reflect that from day one. Second, the repetitive coaching logic (progression, deloads, macro tracking, check-ins) should be automated so coaches can focus on the human side: relationships, accountability, and results. That's what led to building auto-periodization and white-label branding as non-negotiable foundations, not nice-to-haves.

TranscriptFetch's answer:

It started with discovering there is no good way to get the text of a video. YouTube’s official Data API will confirm a caption track exists and then refuse to hand it over, because captions.download requires the video owner’s OAuth token. The popular open-source libraries work until you deploy them, at which point platforms start refusing datacenter IPs. And YouTube is the easy case: TikTok and Instagram publish no caption file at all. Every workaround solved one platform, worked locally, and broke in production. TranscriptFetch is the version that handles the failure cases as first-class behaviour rather than edge cases.

CoachingPortal's answer

Next.js - frontend framework powering the marketing site and coach portal PWA (Progressive Web App) - gives clients an installable, offline-capable mobile experience on iOS and Android without app store submissions Custom subdomain architecture - powers the white-label portal (yourname.coachingportal.io) AI / CoachGPT - AI assistant that surfaces client insights and generates personalized coaching recommendations Barcode scanning - native food logging via camera for the nutrition module End-to-end encryption - data security in transit and at rest

TranscriptFetch's answer:

Next.js with TypeScript and Tailwind on the front end and API layer, Clerk for auth with SHA-256 hashed API keys, Neon Postgres with Drizzle ORM, Redis for caching, and Stripe for billing. The extraction layer is a Python and FastAPI service. Speech-to-text uses Whisper-class models. The MCP server is published in the official Model Context Protocol registry with a DNS-verified namespace.