iVAFlow

A framework doesn't have to mean constraints. iVAFlow is intentionally minimal about visual opinions — it provides structure without imposing style.

Every slide is a blank canvas. There's no enforced grid, no mandatory colour palette, no layout template you have to work within. If a slide needs to look completely unlike every other slide in the deck, that's not a workaround — it's just how it works.

Full layout control per slide

Navigation bars, padding, header and footer regions — all of it can be shown, hidden or customised on a slide-by-slide basis. A slide can inject custom imagery into the nav area, remove chrome entirely for a full-bleed visual, or add arbitrary CSS. No two slides need to look the same.

Rich interactive components, ready to go

iVAFlow ships a library of pre-built, composable components: animated ISI drawers, scrollable content regions with drag inertia, tabbed panels, full-screen modals, slide navigation controls. All of them accept arbitrary content — drop in whatever the design calls for. The TabBar component integrates with slide navigation so that stepping through tabs feels native, with no extra code required from the slide author.

A shared design vocabulary

iVAFlow uses a consistent styling system throughout, meaning developers and designers share a common language for layout and styling. Brand tokens — colours, typography, spacing — are defined once and applied consistently across the entire build.

The biggest cost in iVA production isn't the build — it's the iterations. The back-and-forth over things that broke in QA, the Vault upload that needed three attempts, the fix that introduced a new problem. iVAFlow is designed to eliminate as much of that as possible before it happens.

Problems caught before they reach you

The components and patterns that most commonly cause issues in a custom build are the ones iVAFlow has already solved and tested. On top of that, the framework is structured so that common wiring mistakes — a broken link between slides, a missing reference — are caught automatically during the build, before anything reaches review. You spend less time in QA cycles and fewer rounds going back to fix things.

Faster turnarounds

iVAFlow is built for speed at every stage. Only the slides that have actually changed are repackaged on each build iteration — so the time between a content update and a file that's ready to review is significantly shorter than a conventional build. Faster reviews, faster sign-off, faster to Vault.

Review without waiting on Vault

Every build produces a fully functional browser-accessible preview — identical in structure to the Veeva build, reviewable on any device without iRep or Vault access. Stakeholders can review, comment and sign off without waiting for an upload cycle.

Automated approval PDFs

The approval PDF is generated automatically as part of every build — always in sync with the latest content, never a separate manual step. Screenshots are captured automatically, including modal states and expanded panels.

One build, multiple outputs

The same underlying content can be deployed to Veeva CLM, a web-based preview environment, or a congress kiosk — without starting again from scratch. No parallel builds to maintain, no risk of versions drifting apart.

If your team is building components that need to live inside an iVA — a cost calculator, a custom data visualisation, a personalised content module — iVAFlow's iframe SDK gives you a clean integration surface without needing to know anything about the underlying Veeva architecture.

The iframe SDK

Your component runs inside a standard iframe on any slide. Load the SDK as an npm package, via CDN script tag, or as a standalone JS file — whichever fits your stack. Full TypeScript type definitions are included for teams using TypeScript. Full documentation at ivaflow.app.

Navigation control

Your component can trigger any navigation the framework itself supports — jump to any slide by ID, step forward or back, navigate to a named chapter or section, or step directionally. Current slide, chapter and section IDs are all available as JavaScript Promises, so your component can branch logic based on where in the presentation the user is.

Analytics integration

Fire events directly into iVAFlow's tracking layer — your component doesn't need to know or care whether the destination is Veeva Call Clickstream or PostHog. Events are validated against the same schema as the rest of the iVA, and duration tracking is supported with automatic per-second updates in Veeva mode.

Analytics destinations

Veeva Call Clickstream and PostHog are supported out of the box. The analytics architecture is designed to be extended — additional providers can be added without changes to slide or component code.

No Veeva knowledge required

From your component's perspective, the integration surface is a clean JavaScript API. The complexity of Veeva's navigation model, Clickstream record structure and iRep environment is handled entirely by iVAFlow. Your team builds to the SDK; we handle the platform.