Marketing SaaS · Feature development · [X] months · [price range or monthly]

The product needed features. The team had no room to build them. I did.

CS Platform is an AI-powered marketing hub that replaces five to seven separate tools for marketing teams. As it grew, it needed a set of complex features shipped fast without breaking what already worked. I built three of the biggest ones.

6 → 1

messaging channels, one inbox

social networks scheduled from one screen

[X]

features shipped in [Y] months

This is your situation if…

You run a software product and your roadmap is longer than your team's capacity.
The features you need mean wiring up several third-party services — messaging platforms, social networks, AI — and making them behave as one.
You'd rather bring in one person who takes a feature from spec to production than onboard an agency.

The problem

The platform's users — B2B and B2C marketing teams — were asking for three things at once: every inbound message from Facebook, Instagram, TikTok, LinkedIn, WhatsApp and website chat in one place; an AI agent that could answer client questions from each company's own knowledge base; and scheduling plus analytics across seven social networks.

Each of those meant integrating several outside services, building the plumbing between them, and fitting it all into an existing product that customers were already using every day. The in-house team was fully booked.

What I built

Three features, in the order they shipped. [confirm order]

1
One inbox for six channels.
Facebook, Instagram, TikTok, LinkedIn, WhatsApp and website chat, all landing in a single screen. Along the way I found and fixed a data bug that was silently corrupting some Facebook subscriber IDs at scale.
2
An AI agent that answers from each client's own material.
It learns from the company's knowledge base, replies to inbound questions, and hands qualified leads to a human sales agent.
3
Scheduling and analytics across seven networks.
Publish from one dashboard, then see how each post performed on each platform, with results collected automatically every day.

The scheduler and per-platform analytics.

For technical readers: how it's built

Unified inbox via ManyChat and Unipile integrations with custom webhooks and Supabase Edge Functions; a JavaScript integer-overflow bug on Facebook subscriber IDs resolved; RAG-based AI agent over per-client knowledge bases; scheduling through the Upload-Post API; daily analytics snapshots with pg_cron and Edge Functions. Built with Claude Code.

Claude Code

ManyChat

Unipile