Product 12
The Asset-Production Platform
Three production engines exposed as one platform: PDF render, image library and alt-text, and the talking-head video producer with word-synced captions.
The team that delivers it
What it is
Three production engines exposed as one platform. A document render engine behind every PDF, an image library and alt-text pipeline, and the producer that turns a written brief into a team-page video. Plus the HeyGen-driven talking-head pipeline that gives any portrait a spoken introduction, and the word-synced caption layer that ships with every video.
Built for
The whole company's asset production, originally per-product, now consolidated. Anything that needs a PDF, an image, or a video comes through here.
Who else could use it
Content businesses producing assets at scale. Agencies that want a reusable production stack rather than per-client pipelines. SaaS companies whose generated artefacts (reports, certificates, lessons, slide decks) need consistent branding and accessibility. Education businesses that want talking-head explainers without a studio.
What they get
The three engines as APIs they can call from their own product, or the admin surface for direct production by a human team.
Maturity
Customer 3 shipped (EFO, MBA, personal brand). Productisation for external buyers is mostly API documentation work; the architecture is already multi-tenant in spirit.
Pricing posture
Per-asset SaaS metered. Or annual licence with bring-your-own-LLM-and-storage credentials.
Lives at
build-log.ts: 20 May 'The talking-head video pipeline', 26 May 'The asset-production platform', 27 May 'Word-synced agent-video captions', Apr 'The production tooling'.
What we'll be writing about it
- origin
When every product needed its own production pipeline
The duplicate work that pushed us to consolidate, and what the shared platform replaced.
For: Multi-product founders running duplicate pipelines
- mechanism
Three engines, one platform: how PDF, image and video share a brand
What the asset platform exposes, how brand consistency is enforced, and what an in-product call to it looks like.
For: Product engineers building generative artefacts
- transformation
What a SaaS looks like when every artefact it generates is on-brand and accessible
Why the asset layer is the difference between a product that ships JPEGs and a product that ships finished work.
For: B2B SaaS founders whose product generates client-facing artefacts