Webflow Stack Functional Flow Validation
Budget: $3,000 – $5,000 USD
I have a Webflow-based product already styled and live, wired into TryInteract, Outsetta, Jetboost, and Zapier. Before launch I need a developer to tighten the functional pieces that sit on top of that stack.
Three new functional states must be added and fully wired on the Home page, the Nav bar, and the Dashboard. Each state changes what the visitor can see, so the core interaction is filtering what’s seen rather than eye-candy animations or hover gimmicks.
Beyond those states, I also need:
• Secure endpoints that let the site pull dynamic data from five CMS collections without exposing private keys.
• Jetboost filtering logic ported over to the Dashboard so a “bot press” event automatically shows the correct filtered view.
• A simple progression page written in clean, reusable code that advances a user through defined steps and updates the Outsetta member record accordingly.
Everything must remain no-code-friendly for future editors, meaning custom scripts should be modular, documented, and loaded through Webflow embeds or Outsetta snippets—not deep in the Webflow theme files.
If you know the quirks of Webflow + Outsetta auth, Jetboost filter attributes, and Zapier webhooks, and can prove previous stack integrations, let’s talk timelines and milestone testing so we can ship this confidently.
Three new functional states must be added and fully wired on the Home page, the Nav bar, and the Dashboard. Each state changes what the visitor can see, so the core interaction is filtering what’s seen rather than eye-candy animations or hover gimmicks.
Beyond those states, I also need:
• Secure endpoints that let the site pull dynamic data from five CMS collections without exposing private keys.
• Jetboost filtering logic ported over to the Dashboard so a “bot press” event automatically shows the correct filtered view.
• A simple progression page written in clean, reusable code that advances a user through defined steps and updates the Outsetta member record accordingly.
Everything must remain no-code-friendly for future editors, meaning custom scripts should be modular, documented, and loaded through Webflow embeds or Outsetta snippets—not deep in the Webflow theme files.
If you know the quirks of Webflow + Outsetta auth, Jetboost filter attributes, and Zapier webhooks, and can prove previous stack integrations, let’s talk timelines and milestone testing so we can ship this confidently.
Related categories:
JavaScript
CSS
CMS
HTML5
jQuery / Prototype
Web Development
API
Webflow
Zapier
Web Application