- Project
- Our own product
- Our role
- Product · Architecture · Full stack · Automation
- Duration
- In development
01 / Behind the product
A real need. A considered solution.
Challenge
Finding clients, quoting, producing and delivering usually spread across five separate tools in an ad studio; work gets lost in the gaps. Producing cinematic AI ad videos also demands decisions that repeat per brand: tone, colour, approved concepts, revision history.
Approach
Two apps in one repository: the public site and client delivery portal, plus an internal CRM, lead pipeline and project tracker. Shared packages hold brief, lead-scoring and outreach schemas in zod; the Supabase schema and RLS come from the same package.
Production is a "director" layer: production, scoring and outreach playbooks, and per-brand memory (brief, approved concepts, colour and tone notes, a production cost log). Sourcing runs as scraping with Apify, scoring with a model and outreach with Instantly; the daily mailbox limit is 25 and the main domain is never used for cold outreach. Text is never rendered into video by the model; overlays are added in post.
Result
The whole flow from sourcing to delivery lives in one place; Turborepo-shared types keep both apps on the same contract. Production runs through Higgsfield with approval gates never skipped; development continues.
02 / Inside the product
The experience, on screen.
Open a screen to explore the details.02 images
03 / Scope & details
The details make the experience.
- 01
Public site and client delivery portal
- 02
Internal CRM, lead pipeline and project tracker
- 03
Automated sourcing, scoring and outreach
- 04
Shared type packages through Turborepo
Technology
Next.js / Turborepo / Supabase / Tailwind CSS
INSIDE THE PRODUCT
The engineering behind the interface.
Systems we built and concrete problems we addressed in this project.
The director layer
director/playbooks defines the production, scoring and outreach flows; director/briefs/<brand> keeps the brief, approved concepts, revision history and colour / tone notes as brand memory. Model and credit cost are logged on every project.
Shared contracts
packages/core defines brief, lead-scoring and outreach schemas in zod; packages/db carries the Supabase schema, migrations, types and client factory. pnpm typecheck checks the whole workspace in strict mode.
Outreach rules live in the system
The main domain is never used for cold outreach and the daily mailbox limit is 25; Apify scraping, model scoring and Instantly sending live under director/scripts. When the client supplies imagery it is used as the reference instead of generating.
Your idea could be next.
What could we build for you?
From a first release to a growing platform. Let’s plan the design, development and launch together.
From Türkiye to the US, UK, Australia and everywhere in between.