Pulse

Pulse was designed as a controllable publishing system rather than another AI wrapper. The goal was to own generation, approval, scheduling, platform publishing, and feedback loops inside one workflow.

Built to generate, schedule, publish, and track multi-channel content with approval flow, publisher logic, analytics, and a tighter operational loop.

Most content teams still run on fragmented prompts, copy-paste publishing, and zero operational visibility. The system needed to create useful content, manage draft state, respect channel differences, and keep publishing from becoming a manual burden again.

1. [01]

   Built generators for batch, on-demand, repurpose, evergreen, and autopilot-driven flows.

2. [02]

   Integrated publishing pathways for X, LinkedIn, Facebook, blog, and newsletter delivery.

3. [03]

   Added scheduling logic, metrics collection, and settings-backed operational controls.

1. [01]

   Created a reusable internal content machine instead of one-off prompt sessions.

2. [02]

   Reduced the distance between idea generation and publish-ready output.

3. [03]

   Kept the system auditable with tests and explicit workflow state.

• [01]

  Stack

  Next.js, TypeScript, Supabase, Resend, Vitest
• [02]

  Status

  Self-hosted content automation engine
• [03]

  Stack

  • Next.js 16
  • TypeScript
  • Supabase
  • Resend
  • Vitest