Content Alfa is a content workflow product. Its core design problem is keeping brand decisions, drafts, client review, and delivery connected as work moves between people and tools.
Rahman Fakhru · Product case study
Content ideas often live in chats, notes, spreadsheets, screenshots, and client messages. A draft alone cannot explain which brand context it followed, who approved it, or what happened after approval.
Rahman Fakhru designed and built the product workflow and interface represented in this published case study. The product is active and still evolving; the page describes the documented system rather than a completed client engagement.
Brand identity, audience, tone, pillars, and platform rules feed planning and production. Content then moves through review, approval, scheduling, and a record of what was delivered. These states make handoff visible instead of burying it in a chat thread.
AI supports drafting and variation. It does not silently approve brand decisions or publish on a client's behalf. Review and publishing status stay explicit, with an audit trail for operational decisions.
Manual inputs, CSV, screenshots, and embeds keep the workflow usable when a paid API is unavailable. Bring-your-own-key (BYOK) makes the model provider and usage cost a choice the user can see.
The public case study documents a brand-context workspace, roadmap and calendar, content states, share-link client review, AI-assisted drafting, BYOK configuration, and export or fallback paths. Screenshots below are captured from the project; they are not mock dashboards made for this page.
Content production — a carousel is treated as a structured deliverable.
Third-party publishing and analytics access vary by platform and permission. The product does not claim that every integration is available for every user, nor that AI output replaces client approval.
The useful unit of an AI product is a complete, inspectable task. A draft generator adds less value when the context, approval, and delivery decisions remain scattered elsewhere.
Inspect the original case study and public project before discussing a similar product. Scope and responsibilities depend on your context.