Implementation Approach

A new way to think about content automation.

For too long, investment firms have been pushed into content automation projects that look great on paper but fall apart in practice. Long timelines, over-engineered templates, “phase two” work that never gets delivered.

It’s all part of a legacy implementation model that wasn’t built for the realities of investment content or the teams producing it.

The legacy approach tends to:

Extend time to value
Create rigid components
Require constant developer support
Fall apart when Sales and Client Service need different things
Look good in a diagram, but fail in actual investment content workflows

Firms don’t struggle because their teams are incapable — they struggle because the old model asks them to solve problems in the wrong order.

Why Traditional Implementations Fail

Most legacy content automation requires firms to:

Analyze everything upfront
Teams try to standardize all components for all content types before building anything. The result? Months of meetings. Slow progress. No visible output.

Wait for perfect data
Projects stall until data warehouses or pipelines are complete, pushing timelines out by months —sometimes years.

Design “universal” components
In theory, this creates consistency. In reality, Sales wants X, Client Service wants Y, and the universal template breaks immediately.

Use large cross-functional teams
More voices introduce more requirements, more exceptions, and more redesigns.

This is the Big Bang approach. It’s the reason so many content automation initiatives never get traction.

The Assette Approach: Build What Matters First, Let Reuse Emerge

This is the reason Assette implementations feel different:

You no longer have to fix everything upfront.
You only have to start.

Assette was built specifically for investment firms, and our architecture changes what’s possible in an implementation.

The difference starts with how we handle data.

Data Objects: The Architectural Shift

Data Objects define what data to show and how it should be organized: separating data logic from both transformation and display.

Most platforms blend business logic directly into templates.

Assette separates it, with a distinct Data Object layer that centralizes what and how to show your data across all your outputs.

The result: faster updates, stronger governance, and consistent data everywhere.

This separation unlocks everything the legacy model
couldn’t solve:

Data can be imperfect or decentralized – Assette transforms it on the fly
Components can be built for real use cases first, not hypothetical universal use cases
Reuse emerges naturally once the first outputs are live Marketing and business teams gain control without needing developers
Each component is consistent, auditable, and ready to use across reports, decks, dashboards, and AI workflows

Implementation Principles

When the model is working for you rather than against you, implementation becomes straightforward.

Start with one content type
Focus on your highest-impact deliverable, such as client reports. Build only the components that matter most and deliver value to users immediately.

Let reuse emerge naturally
When you move to the next output, such as a sales deck, most components already exist. Differences are usually stylistic, not structural.

Keep teams small and skilled
A focused two or three-person pod moves faster than a large committee. You get decisions, momentum, and real output instead of analysis paralysis.

Don’t wait for perfect data
Use what you have. Handle transformations, calculations, and validations in Assette. Clients care about consistent, accurate content, not internal data structures.

Avoid over-engineering
Investment content changes frequently. Overly complex components slow progress. Build cleanly, iterate quickly, and evolve only when needs become real.

Document as you go
Clear naming, helpful descriptions, and strong component metadata make the system easy to use for your team and AI-assisted workflows.

A Simple Example

Let’s say you start with Client Reports.

You build:

Performance charts
Attribution summaries
Holdings detail table
Standard disclosures
Section-level commentary shells

When it’s time to build your Sales Deck:

The performance chart is already built
The attribution tables are already built
The disclosures are already tied to the data
You build a new holdings summary

Because components were historically created manually by different people, firms often end up with only stylistic differences across content types.

With Assette, you simply reuse existing components, eliminating rework and bringing consistency to your sales and client materials.

Reuse isn’t forced. It emerges naturally.