Tools for the creative team

01

The work around the work

A creative team spends time looking for assets, checking versions, making new crops, and rebuilding familiar page structures. These are connected tasks, and they can pull attention away from the decisions that actually need it.

I worked on tools that support that production process: hearcut for asset discovery and preparation, and an LP Builder for editing a page in context. The aim is practical: keep the materials findable and make common changes easier to complete.

02

Make an image useful beyond its filename

The hearcut implementation syncs assets from SharePoint and brings together metadata, tags, search, and related variants. It includes AI services for image tagging and visual embeddings, alongside conventional text and tag filters.

Those approaches cover different needs. Sometimes someone knows the exact name. Sometimes they know what they want to see in the picture. A useful library should support both without requiring everyone to remember the folder structure.

Duplicate grouping and variant counts give crops and resizes a relationship to the original asset. That helps keep a gallery from becoming a wall of almost-identical pictures.

01FindSearch, tags, and related variants
02PrepareInspect the image and select a crop
03UseCreate and export for the placement

Reconstructed process summary based on the project materials.

Hearing-aid charging case with devices against blue — Product-focused asset from the supplied image collection.

Synthetic couple talking at an evening event — Lifestyle direction from the supplied AI-generated collection. These are examples of asset variety, not verified hearcut outputs.

03

Carry the asset into production

The crop interface includes common social and display sizes, a custom crop, and format selection. The banner creator extends that work into a canvas-based editor with text, imagery, and export.

The implementation also includes Microsoft sign-in and storage integrations. These dependencies matter: a local demo can show the interface, but it cannot prove that a company’s live permissions, sync process, and image services are configured correctly.

AI belongs inside that workflow where it removes repetitive description or helps retrieve an image. It does not remove the need to inspect the final crop or creative.

Small hearing aids displayed on a hand against blue — Scale and handling: a wide composition with room around the product.

Charging case held in one hand against orange — A second treatment uses warm color and a charging-case interaction.

04

Edit the page where you can see the consequence

The LP Builder lets someone select a template, switch between mobile and desktop, edit text directly in the page, and download the resulting HTML. The supplied templates cover Natural Hearing, Brain Health, and Lightbulb directions.

That is a deliberately constrained editing surface. It exposes the decisions people make repeatedly without asking them to rebuild the page. The preview makes it possible to see when a small copy change becomes a layout problem.

I inspected the working mobile preview and its template and editing controls. The template contains image placeholders, so it is shown as a production tool rather than a finished landing page.

The supplied builder combines template selection, viewport controls, inline editing, and HTML export.

05

Measure the handoffs

The deliverables establish a connected approach to finding, preparing, and using creative assets. The source material does not establish team adoption or measured production-time savings, so I do not attach a speed claim.

I would evaluate the system with a few real production tasks: find an appropriate image, locate its alternatives, make the needed crop, and update a page. Completion time, failed searches, rework, and export quality would tell us which part of the process still needs attention.