Why We Built GetIntent as a Script, Not a CMS
Most personalization tools want you to migrate your entire site. We refused. Here is why we built a zero-config script that works with your existing stack.
When we started building GetIntent, we looked at the landscape of personalization tools. They all demanded the same thing: "Migrate to us."
They wanted us to rebuild our site in their proprietary builder, host it on their servers, and lock our data into their ecosystem. We said no.
Your Stack is Sacred
We believe your tech stack is your choice. Whether you love Next.js, swear by Webflow, or are stuck on WordPress, that's your business. Our job shouldn't be to replace your stack; our job is to make it smarter.
That's why we engineered GetIntent as a lightweight, drop-in script. It works like a layer on top of your existing site. It doesn't care what CMS you use. It doesn't care if you're server-side rendered or a static site.
How It Works Under the Hood
When a user lands on your site, our script wakes up. It scans the URL for intent signals (like utm_term=running_shoes). It then parses your DOM, identifies the key text elements we've targeted, and swaps them out for the AI-generated variants we've pre-cached on the edge.
The whole process takes milliseconds. No migration, no "integration hell," no breaking changes. Just copy, paste, and personalize. We built it this way because it's the tool we wanted to use.