iVAFlow
iVAFlow is the framework Ramp uses to build interactive visual aids. It's not a product, not something we sell. It's how we work, refined over years of building this kind of thing for clients.
Why it matters
One build, many channels
A single codebase outputs to web, kiosk, and CLM formats, with no rebuilding from scratch for each delivery context.
Faster builds, faster updates
Shared components and templated structures mean less time on boilerplate up front, and when a campaign needs updating, changes are quicker and lower-risk too.
Analytics built in
Tracking comes ready to go: PostHog, Veeva, and other destinations are supported out of the box, not bolted on after the fact.
Fewer errors
Tested, reusable patterns reduce the surface area for things to go wrong, especially around Veeva-specific quirks that are easy to get wrong from scratch.
Built to evolve
iVAFlow is developed between projects, not just within them, so every build benefits from what we've learned on the last one. We've built and sold platforms like this before, and we're applying that experience here.
Built for how everyone works
Project managers & client services
Predictable timelines, and when a campaign needs updating post-launch, that work is faster and lower-risk too.
Designers
iVAFlow sits in the background. It doesn't impose a visual style, a tool, or a workflow. iVAFlow just makes what you design easier to build and maintain.
Marketers
Fewer surprises late in the process, and the ability to make updates after launch without a full rebuild.
Developers
Less boilerplate, sensible conventions, and a foundation that's actively maintained rather than reinvented per project.
Under the hood
iVAFlow is built around a shared component library and a templated build process. Pages are assembled from reusable interactive elements, including navigation, overlays, data persistence, and kiosk adaptation, rather than coded individually each time. The same source can target multiple output formats (CLM, kiosk, standalone web) through configuration rather than rebuilding. Analytics tracking, to PostHog, Veeva's own reporting, or other destinations, is configured once and applies consistently across every output.
For developers
Full technical documentation, component reference, and build conventions live at docs.ivaflow.app.