Not a Library. A Content Layer.
You expected a folder of PDFs. What you're looking at is dynamic content infrastructure — composed modules that the platform deploys autonomously across Segmentation Intelligence and Clinch, simultaneously, without you duplicating a thing.
The Tools Exist. The Category Doesn't.
Each tool solves a fragment of the problem — storing, embedding, or sending content. None of them treat content modules as architectural primitives that multiple surfaces consume.
Content Management
CMS platforms and tools like Notion let you build reusable content blocks. They're storage and presentation layers — excellent at organising, poor at deploying. Nothing in them decides when a specific contact should receive a specific module.
Proposal Tools
Proposal platforms let you embed rich media inside deals. But the content is locked inside the proposal — it cannot be deployed elsewhere as standalone engagement. One deal, one audience, one surface.
Marketing Automation
Automation platforms send content on triggers, but the content is typically a templated email or a link to a static page — not a rich, multi-element experience built for a specific context.
Curated Resources fills the gap: content modules as primitives that multiple surfaces consume.
The module your Segmentation Intelligence sends to a dormant client is the same module Clinch embeds inside the next proposal. The investment in building one module pays off across every surface — not locked in a page, a deal, or a template.
One build. Multiple deployments. Each module carries explanatory text, embedded video, sample assets, and scheduling widgets. Every surface that needs it — draws from the same source.
- SI Deployment
- Clinch Proposals
- Nurture Sequences
- Artefacts
- Webby Pages
A coach builds a single module about their scaling-bottleneck diagnostic — explanatory text, embedded video walkthrough, sample worksheet, calendar widget. In a CMS, it sits on a page waiting for visitors. In a proposal tool, it's locked inside a deal. With Curated Resources, SI deploys it to past clients showing scaling signals, Clinch embeds it in live proposals, nurture sequences reference it when a contact engages with the topic.
A composed experience.
Not a document.
Every Curated Resource module is a multi-element, brand-governed experience — constructed once with strategic intent, scoped to a specific audience, and deployed for as long as it stays relevant.
Rich Text Blocks
Narrative and explanation in your voice. The connective tissue between every other element in the module.
Embedded Video
Walkthroughs, explanations, personal messages. Recorded once, deployed to every contact who needs it.
iFrames
Live interactive content — charts, dashboards, calculators — embedded directly inside the module experience.
Forms
Capture responses, commitments, or questions. Every submission flows into the contact's intelligence profile.
Calendar Widgets
Book time directly inside the module. No redirect, no friction — the next conversation starts here.
Graphics & Images
Visual assets governed by your brand's identity system. Consistent, on-brand, automatically.
Code Blocks
Technical content formatted cleanly. API examples, configuration snippets, implementation guides.
Downloadable Files
PDFs, spreadsheets, documents — attached to the module and tracked when accessed.
External Links
Curated references to third-party resources. Context-appropriate, never generic link dumps.
What this looks like: a fiduciary advisor builds "Understanding Q3 Market Volatility"
The module opens with a narrative block in the advisor's voice — acknowledging the quarter's turbulence, framing the context without panic. Below it, an embedded video: the advisor walking through the dynamics personally, two minutes, eye-to-eye with the client.
Next, an interactive chart iFrame showing historical volatility patterns — the client can explore the data themselves. Then a form where the client can submit a specific question for their next portfolio review. Finally, a calendar widget for booking a one-to-one conversation directly.
Scoped to the existing client segment at creation — not retroactively tagged. Segmentation Intelligence will never deploy this module to a B2B principal's key account contact. The brand's voice, visual identity, and communication guardrails govern every element by construction, not by review.
SI decides when to share — and what, and how
Segmentation Intelligence continuously evaluates every contact — relationship stage, recent interactions, engagement patterns, segment membership, behavioural signals. For most contacts at most moments, the right move is silence or direct outreach. But there are moments when the right move is to share something — a module that addresses a concern, reinforces a value proposition, or advances a narrative the contact needs to absorb.
SI identifies those moments and deploys the matching module without manual selection. Deployment is structural, not scheduled. SI is not sending a weekly resource. It is detecting a moment in a specific contact's relationship lifecycle where sharing is the strategically correct action — and executing.
See your world in motion
Every segment has its own anxiety — the client who went quiet, the renewal window approaching, the five-year gap. SI acts before you have to ask.
Proposals lose deals because they're documents. Clinch deals with embedded modules are experiences.
Most proposals are static. A prospect opens it, scans it, makes a binary decision based on incomplete absorption of your value. The attention unit is wrong — you're asking someone to read when they should be engaging.
When you assemble a Clinch deal, you drop Curated Resources directly into the proposal structure. The module renders inline, fully interactive. A video plays inside the proposal. A calendar widget books a follow-up without leaving the deal. A form captures objections in real time.
A Clinch deal with embedded modules does two jobs. It closes the specific deal, and it demonstrates the brand's depth and intentionality. Prospects don't receive a proposal — they receive an experience that feels considered.
A consultant sends a six-month engagement proposal. Standard scope, pricing, terms. But embedded between sections is a Curated Resource walkthrough of the diagnostic framework — the same module SI uses to re-engage dormant prospects.
The prospect watches the embedded video, engages with the interactive diagnostic, books a clarification call through the embedded calendar. By the time they reach the signature block, they've moved from prospect to engaged participant.
One Library. Every Surface. Compounding.
A single module library consumed by SI, Clinch, nurture sequences, and artefacts — where every module built creates compounding leverage across every surface.
Four surfaces. One content layer.
Segmentation Intelligence
SI selects and deploys modules autonomously — matching the right content to the right relationship stage, without manual assignment.
Learn moreClinch Deals
Modules embed inside interactive proposals as contextual proof points — case studies, guides, and insights that strengthen every deal.
Learn moreNurture Sequences
Email and SMS sequences reference modules dynamically — every touchpoint carries substance, not filler. The library fuels the cadence.
Learn moreArtefacts
Personalised deliverables incorporate module elements — reports, summaries, and briefs that show each contact their own situation.
Learn moreThe architectural choice to centralise content modules into a deployment layer — rather than building separate content for each surface — is what makes the system pay off in year two and beyond. A module built for one purpose ends up serving three. A library of fifty modules powers hundreds of deployments and dozens of deals over its lifespan.
This is not a content folder. It is a content layer the platform consumes.
Build once. Deploy where it matters. Compound continuously.
Common assumptions,
addressed directly
Consistency without context is noise. Having content and having a deployment layer that knows which contact needs which module at which stage are fundamentally different capabilities. The system doesn't just send more — it scopes what gets sent to the situation each contact is actually in, so every touchpoint compounds relevance instead of diluting it.
You build a module once. The Content Engine and Curated Resources layer then deploys it across every relevant surface — email, SMS, resource pages, nurture sequences — compounding its value over time. Compare that to manually selecting, formatting, and sending content forever. The architecture does the repetitive work; you do the thinking once.
A segment-scoped module that arrives because the system detected a life event, a renewal window, or a shift in engagement behaviour feels more personal than a mass newsletter you sent to everyone on Tuesday. The intelligence layer matches content to context — that's not automation pretending to be human; it's architecture that earns attention because it's genuinely relevant.
Newsletters treat every contact the same — same content, same cadence, same channel. Content modules are scoped to specific situations: a first-home buyer gets different resources than a refinancing client; a dormant referral partner gets a different re-engagement sequence than an active one. The Segmentation Intelligence layer ensures the right module reaches the right person through the right channel. That's not a newsletter's job.
A system with documented deployment rules, brand-encoded compliance guardrails, and auditable content logs is inherently more compliant than ad-hoc outreach typed at 11pm. Every module is pre-approved, every deployment is tracked, and every channel respects the boundaries you set. The architecture doesn't bypass compliance — it makes compliance the default instead of the exception.
Direct outreach is powerful — and the system knows when it's the right move. But there are moments when a contact needs to absorb, not respond: when they're researching options, weighing a decision, or simply not ready for a conversation. Content modules exist for those moments — they maintain presence and build credibility in the space between conversations, so when you do call, you're not reintroducing yourself. The two approaches are complementary, not competing.
See the architecture run
One module. Your industry. Deployed through your channels and embedded in a live deal — in under thirty minutes.
No commitment to build a library — just see what the architecture does with a single module.