Agency Scroll 2025 Retrospective: 60 clients, nearly 100 projects, a method and stacks that hold up

In 2025, Scroll supported nearly 60 clients across close to a hundred projects. Apps, business apps, websites, and everything connecting these worlds: automation, data, content, conversion.

This article isn’t a showcase. You’ll understand what we delivered, with which building blocks, why we use them, and what it changes when you’re an SME, a small business, or an entrepreneur who needs to move fast without patching things together.

Key takeaways from Agency Scroll’s 2025 retrospective

In 2025, Scroll delivered nearly 100 projects with a simple logic: reduce timelines, secure data, and maintain a clean user experience.

The most frequent stacks combine Plasmic, Supabase, n8n, Directus and Webflow, because they cover most needs: acquisition, content, authentication, back-office, and automation.

The most recurring projects are conversion-focused websites, client portals, internal business apps, back-offices, and tool integrations.

The biggest time-saver isn’t “moving fast”—it’s making quick decisions on a clear scope, then delivering in short cycles.

The main risk when launching a web or app project isn’t the technology. It’s the accumulation of vague small decisions that turn into a big problem six months later. In 2025, we focused on avoiding this.

What “nearly 100 projects” really means in 2025

When we say “nearly 100 projects,” we’re not talking about 100 identical large-scale builds. In reality, a solid year of delivery looks like a portfolio of different formats.

There are full creations: a new website, a new app, a new client space.

There are extensions: adding modules, multi-role access, a back-office, a CMS, payment, a request or validation workflow.

There are useful overhauls: not a cosmetic redesign, but one that simplifies content, clarifies the offer, fixes performance, or improves conversion rates.

There’s also smart maintenance: optimising what’s already running, securing automations, improving event tracking, consolidating data, and reducing manual operations.

This mix explains an important point: an agency that maintains a high pace doesn’t “go faster” by magic. It industrialises what can be, without making projects rigid.

The project types that mattered most at Scroll in 2025

Conversion-focused websites

We delivered many websites because they’re often the first visible building block. But a good website isn’t just a clean page. It serves a clear purpose: generating leads, qualifying them, and feeding a pipeline.

In 2025, an effective website looks like this: an explicit value proposition above the fold, early proof points, a simple reading path, a content system that allows publishing without breaking the design, and clean tracking to measure performance.

For this type of project, Webflow remains a strong choice because the marketing team can iterate, the output is polished, and the time-to-live is short. When the “app” part comes in, the site can stay on Webflow while the product evolves elsewhere.

Apps and client portals

The other major category is apps, often client-facing: tracking spaces, documents, requests, tickets, onboarding, or subscription management.

The challenge here isn’t the interface. The real challenge is identity and data. Who logs in, what they’re entitled to, and how the information is structured.

This is where the Plasmic + Supabase duo becomes highly effective. Plasmic enables the assembly of modern interfaces with a component-based logic, while Supabase provides a solid foundation for authentication, databases, storage, and consistent access rules.

Internal business apps

Business apps are often the best profitability lever for an SME. They reduce internal friction: duplicate entries, email validations, poorly maintained shared files, makeshift reporting, repetitive operations.

In 2025, we saw a return of very similar needs: request management, validation workflows, resource management, production tracking, commercial operations, or support management.

A business app project succeeds when it aligns with the team’s actual workflow—not a theoretical org chart. That’s why scoping is so critical. We need to understand the “path” of a request, a file, or a client, then build around it.

Back-office and content management

As soon as content becomes a priority, governance is essential. Not necessarily heavy, but clear: who can publish, who validates, what structures are used, and how to avoid breaking the site or app.

Directus addresses this need perfectly when you want a clean back-office, roles, content models, and a database that doesn’t descend into chaos.

We often used it as a management layer, connected to a Plasmic front-end or a website, to properly separate “editing” from “display.” This avoids workarounds. It also prevents every modification from requiring technical intervention.

Automations and integrations

A significant portion of the value delivered in 2025 is invisible. It lies in automations.

n8n is often the piece that connects everything. CRM, email, support, billing, databases, enrichment, notifications, and syncs. If you don’t do this work, your team pays the operational debt daily.

The key point is that automation isn’t a bonus. It’s a way to reduce a project’s operational cost from the very first versions. But it must be done properly, with logs, alerts, recovery mechanisms for failures, and clear rules.

Why these stacks keep coming up: Webflow, Plasmic, Supabase, Directus, n8n

The Agence Scroll 2025 retrospective is also a story of tool choices. Not because we love tools. Because they address real constraints.

Webflow: speed and clarity for marketing

Webflow is excellent when the site needs to change often. Sales pages, landing pages, offer overhauls, publishing, light A/B tests, iterations on hierarchy.

It’s also a tool that helps maintain consistent rendering quality. So fewer details breaking on mobile, fewer surprises, and fewer endless tweaks.

Plasmic: an app interface that remains maintainable

Plasmic is compelling when you need a rich app interface with reusable components and the ability to evolve quickly.

For client portal or business app projects, it allows you to maintain a high level of polish while staying flexible. This matters because an app evolves. And if every change is a major project, you lose the “fast and well” advantage.

Supabase: a pragmatic backend for authentication and data

Supabase provides a solid foundation for most SME apps: authentication, PostgreSQL database, storage, and security logic.

The big issue is rights consistency. Who can read, write, edit, delete. This often makes or breaks a project. When it’s well-defined, everything else becomes simpler.

Directus: content governance and clear back-office

Directus is useful as soon as multiple people manage content, or when you need a clean back-office.

It’s also very practical when you want to prevent content changes from turning into code changes. Marketing gains autonomy, and the product remains stable.

n8n: industrializing operations

n8n is the layer that eliminates copy-pasting and hidden workflows buried in email inboxes.

Synchronization, enrichment, document generation, notifications, alerts, routing, CRM updates, event tracking. When well-designed, it saves a lot of time. And it reduces human errors.

The most common combinations and what they enable

Instead of talking about separate tools, it’s more useful to talk about combinations. In 2025, certain pairings keep coming up because they cover full needs.

Webflow site + n8n automations

This is a classic when the goal is to convert and qualify. The site collects. n8n routes, enriches, notifies, and updates internal tools. Result: shorter delays between “lead” and “action.”

Plasmic client portal + Supabase

When there’s a login, data, documents, and roles, this duo is highly effective. It allows delivering a useful V1, then evolving the experience without starting from scratch.

Directus content + Plasmic or site front-end

As soon as content multiplies, you need a clear back-office. Directus manages models, roles, and validations. The front-end displays. The system holds up better over time.

Connecting everything with n8n

Most companies use multiple tools. The real challenge is making them work together without the team becoming the “human integration layer.”

n8n then becomes a backbone: visible, versionable workflows with safeguards.

What we learned in 2025 about pace and quality

Delivering nearly 100 projects in a year requires discipline. Not in the “heavy process” sense. In the “clear and repeatable decisions” sense.

Speed comes from framing, not sprinting

When a project goes off track, execution is often blamed. In reality, the cause is usually upstream: vague objectives, shifting scope, poorly defined data, or misunderstood roles.

In 2025, the framing that works boils down to a few things: a clear target, an expected outcome, a realistic V1, a simple data model, and access rules defined early.

When these elements align, you can deliver fast and iterate without stress.

Permissions and roles are the most underestimated pain point.

With apps and portals, the “roles and permissions” issue always comes up. The question isn’t whether it will come up. The question is when you’ll address it.

When it’s tackled too late, it’s costly. You have to rework screens, queries, and user flows. And sometimes, you even need to restructure the data.

When it’s addressed early, it’s an accelerator. Everything becomes more stable.

Unsupervised automation is technical debt.

Automation is good. But automation that fails silently is a hidden problem.

In 2025, we reinforced a simple principle: every automation must have a trace, a recovery method, and a failure alert. Otherwise, you’ll discover the bug at the worst possible moment—often through a client.

Content must be designed as a system.

As a website or app grows, so does its content. Pages, use cases, FAQs, resources, documents, templates, policies, private content.

Without a clear structure, content becomes a permanent construction site. Directus is often the answer, but beyond the tool, it’s about discipline: models, validation, and clear ownership.

What 2025 confirms for Scroll—and what it opens up for the future

This Scroll Agency 2025 retrospective confirms one simple truth: value doesn’t come from a miracle tool. It comes from a clear foundation, short-cycle execution, and a coherent stack that stands the test of time.

When an SME or entrepreneur wants to move fast, the challenge isn’t just delivering a V1. The challenge is delivering a system that can evolve, connect with existing tools, and remain maintainable through iterations.

In 2026, Scroll continues in this direction: sharp scoping, rapid delivery, clean interfaces, and robust automation. If you want to turn an idea into a high-performing product or website without losing months to back-and-forth, our services cover these exact needs—from scoping to run and industrialisation.