Case study · Marketing technology · India

AI audience platform

For an Indian marketing-technology company, Joistic rebuilt its audience platform from the ground up. Marketers describe the audience they want in plain English, AI turns that into a plan, the platform counts it live, and the audience is built for ad campaigns. It went from first commit to production in about five weeks.

Client

Ad-tech company, India (under NDA)

Start to production

About 5 weeks

Automated tests

223, 93.6% coverage

Hosting

Dedicated AWS account, Mumbai

The client

About the client

The client runs an audience platform for brands and agencies. We can't name them because the work is covered by an NDA. An earlier version had been built as a prototype by another agency and wasn't ready for real customers.

The problem

What needed fixing

Marketers know who they want to reach but not how to express it as filters and segments. The old prototype ran on demonstration data, with sample counts and demo logins instead of a working product.

The client needed a real product: separate workspaces for each brand, real audience counts, and infrastructure they could trust with customer data.

What we built

The system, piece by piece

Studio: describe an audience in plain English

A marketer types who they want to reach. AI turns the request into an audience plan, which is counted live against the audience store and can be refined into cohorts and saved.

Separate workspaces for each brand

Each brand has its own workspace and team, with roles for admins, members and data operators. Every query is limited to the signed-in brand's data.

Data uploads

Data operators upload large category files (up to 200 MB). A background worker validates them, protects personal identifiers by hashing them, and loads them into the audience store.

Builds and ad activation

Saved audiences are built into member lists for each brand's own connected Google Ads or Meta account, with brands taking turns in the processing queue.

Operations console

Platform admins see system health, uploads, jobs, AI usage and activations in one console.

Website lead capture

The marketing website's demo-request form feeds straight into the platform and emails the sales team.

AI

Where AI is used

  • Plain-English audience planning: the AI reads the marketer's request and produces a structured audience plan with criteria and signals.
  • The platform can run on Gemini or Claude, so the client isn't tied to one AI provider.
  • AI usage is tracked in the operations console so costs stay visible.
Controls

Built for customer data

  • Personal identifiers are hashed before they're stored, and each brand only ever sees its own data.
  • Production runs in its own AWS account with encrypted databases and secrets, audit logging, threat detection and alerts.
  • Every change goes through 223 automated tests and browser tests before release, and infrastructure changes are reviewed as code.
Results

What changed

  • The platform went live in production in October 2026, about five weeks after the rebuild started.
  • Real audience counts and separate brand workspaces replaced the demo prototype.
  • Google Ads and Meta activation is built and switches on once the platforms finish their app reviews.

A prototype proves an idea. Customer data needs a product: separate workspaces, tests and infrastructure you can defend. That's the gap this rebuild closed.

Timeline
  1. Sep 2026

    Rebuild started from the client's product spec

  2. Late Sep 2026

    Studio, uploads and brand workspaces on staging

  3. Oct 2026

    Production live on a dedicated AWS account

Built with
React 19 and ViteExpress 5 (TypeScript)PostgreSQL on AWS RDSAWS ECS with TerraformGemini and ClaudeResend email

Sharper operations. Smarter teams.
Let's build yours.

Start with one workflow and see the results before you expand.

Not ready for a call? Send us a short brief and a founder will reply within one working day.