Introduction

Tekst.com helps large enterprises eliminate boring work. Their AI-driven Agentic Process Automation connects inbox, CRM, and ERP to automate end-to-end workflows without heavy IT projects or disruptive change management. They already had a Webflow website and had recently gone through a redesign, but the result wasn’t where it needed to be: visually limited, hard to scale, and not fully aligned with their positioning. In a fast-moving SaaS landscape, Tekst.com needed a website that could evolve at the same pace as their product and pipeline. That’s when they teamed up with SKROL, not for another complete reinvention, but for a focused, high-quality rebuild that would give them a clean system to grow on.

‍

Situation

Tekst.com operates in a rapidly evolving space: AI, automation, enterprise processes, complex integrations. Their audience is sharp, operations leaders, digital transformation teams, CRM and IT owners who care about reliability as much as innovation. The website needed to speak to them clearly. The previous setup made that difficult. Although built in Webflow, it wasn’t structured for reuse or scale. Imagery and layouts were hard to extend, making every new page feel like a one-off. The site didn’t fully support Tekst.com’s story, proof points, and use cases at the level of clarity and consistency they needed. On top of that, the team wanted better alignment with their CRM and go-to-market operations, without sacrificing speed. The goal was clear: create a stable, scalable Webflow foundation that fits Tekst's brand and product story, can be iterated on quickly, and is technically sound from day one.

Our role

Stepped in as Tekst ’s design and Webflow partner: refining their interface, translating the brand into a more robust layout system, rebuilding key pages, and setting up a scalable CMS and clean technical base, all while working in tight deadlines with rapid feedback loops through Slack.

‍

Approach

Tekst is a young, driven team working in a domain that doesn’t wait. Instead of slowing them down with long cycles, we focused on building a strong, flexible system as quickly as possible. We started by mapping which parts of the existing site worked, what needed restructuring, and which components they would need repeatedly: use cases, customers, careers, resources, and product-focused storytelling. From there, we designed and developed directly in a shared, iterative flow: short feedback cycles, clear ownership, and constant alignment on “does this help you move faster after we’re gone?”. Scalability, reuse and clarity were the guiding principles behind every decision.

‍