Retrospective Agence Scroll 2025:60 customers, nearly 100 projects, a method and stacks that stick

In 2025, Scroll supported nearly 60 customers on a few hundred projects. Apps, business apps, websites, and everything that connects these worlds: automation, data, content, conversion.

This item is not a window. You will understand what we delivered, with what bricks, why we use them, and what changes when you are an SME, a VSE or an entrepreneur who must move quickly without tinkering.

The key points of the Agence Scroll 2025 retrospective

Scroll delivered nearly 100 projects in 2025 with a simple logic: reduce deadlines, make data reliable, and keep a clean user experience.

The most frequent stacks combine Plasmic, Supabase, n8n, n8n, Directus and Webflow, because it covers the majority of needs: acquisition, content, authentication, authentication, back-office, and automations.

The projects that come back the most are sites that convert, customer portals, internal business apps, back offices, and integrations between tools.

The factor that saves the most time is not “going fast”, it's deciding quickly on a clear perimeter, then delivering in short cycles.

The main risk when you launch a web or app project is not technology. It's the pile-up of small, fuzzy decisions that become a big problem six months later. In 2025, we mainly worked to avoid this.

What “nearly 100 projects” really cover in 2025

When we say “nearly 100 projects”, we are not talking about 100 identical major projects. In reality, a solid delivery year is like a portfolio of different formats.

There are complete creations: a new site, a new app, a new customer area.

There are extensions: addition of modules, multi-role transition, addition of a back office, addition of a CMS, addition of a payment, addition of a request or validation process.

There are useful redesigns: not an aesthetic redesign, but a redesign that simplifies the content, clarifies the offer, fixes the performance, or improves the conversion rate.

There is also smart running: optimizing what is already running, making automations more reliable, improving event tracking, consolidating data, and reducing manual operations.

This mix explains an important point: an agency that keeps up a high pace does not magically “go faster”. It industrializes what can be industrialized, without making projects rigid.

The types that mattered the most at Scroll in 2025

Conversion-oriented websites

We delivered a lot of sites, because it is often the first visible brick. But there's more to a good site than just one clean page. It is used for a clear action: generate requests, qualify, and feed a pipeline.

In 2025, an effective site looks like this: an explicit value proposition at the top of the page, early evidence, a simple reading path, a content system that allows publishing without breaking the design, and a clean follow-up to measure.

It is for this type of project that Webflow remains very strong, because the marketing team can iterate, the rendering is clean, and the time-to-live is short. When the “app” part arrives, the site can stay on Webflow, while the product evolves elsewhere.

Apps and customer portals

The other big family is apps, often on the client side: tracking space, documents, requests, tickets, onboarding, or subscription management.

The difficulty here is not the interface. The real difficulty is identity and data. Who connects, what they are entitled to, and how do we organize information.

This is where the Plasmic + Supabase duo becomes very effective. Plasmic makes it possible to assemble modern interfaces with component logic, and Supabase provides a solid foundation for authentication, database, storage, and consistent access rules.

Internal business apps

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

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

A business app project succeeds when it relies on the real flow of the team. Not on a theoretical flowchart. That's why framing is so important. You need to understand the “path” of a request, a file, or a customer, and then build around it.

Back office and content management

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

Directus meets this need very well when you want a clean back office, roles, content models, and a base that doesn't turn into chaos.

It has often been used as a management layer, connected to a Plasmic front or to a site, to properly separate “editing” and “displaying”. It avoids tinkering. And it also prevents each modification from costing a technical intervention.

Automations and integrations

Much of the value delivered in 2025 is invisible. It is found in automations.

N8n is often the piece that connects everything. CRM, email, support, billing, billing, databases, databases, enrichment, notifications, and synchronizations. If you don't do this work, your team pays the debt on a daily basis.

The key point is that automation is not a bonus. It is a way to reduce the operational cost of a project, from the very first versions. But it must be done properly, with logs, alerts, resutures in case of failure, and clear rules.

Why do these stacks come up so much: Webflow, Plasmic, Supabase, Directus, n8n

The Agence Scroll 2025 retrospective is also a story about the choice of tools. Not because we like the tools. Because they correspond to real constraints.

Webflow: speed and clarity for marketing

Webflow is great when the site needs to move often. Sales pages, landing pages, offer redesigns, publishing, A/B light tests, iterations on the hierarchy.

It is also a tool that helps maintain stable rendering quality. So fewer details that break on mobile, fewer surprises, and fewer endless retouching.

Plasmic : an app interface that remains maintainable

Plasmic is great when you want a rich app interface, with reusable components, and the ability to evolve quickly.

On customer portal or business app projects, it allows you to maintain a high level of finish, while remaining flexible. It's important because an app evolves. And if each evolution is a work in progress, you lose the advantage of “quickly and well”.

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 the coherence of rights. Who can read, write, modify, delete. This is often what makes or breaks a project. When you put it right, everything else becomes easier.

Directus : clear content governance and back office

Directus is useful when there are several people who manage content, or when you want a clean back office.

It's also very handy when you want to avoid content changes becoming code changes. Marketing gains autonomy, and the product remains stable.

n8n: the industrialization of operations

n8n is the layer that avoids copy and paste and workflows hidden in mailboxes.

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

The combinations that come up the most, and what they allow

Instead of talking about separate tools, it's more useful to talk about combinations. In 2025, some associations come back often because they cover complete needs.

Webflow website + n8n automations

It's a classic when the objective is to convert and qualify. The site collects. n8n routes, enriches, notifies, and updates internal tools. The result: less time between “lead” and “action”.

Plasmic + Supabase customer portal

When there is a connection, data, documents, and roles, this duo is very effective. It makes it possible to deliver a useful V1, then to evolve the experience without starting from scratch.

Directus content + Plasmic front or site

As soon as the content multiplies, we want a clear back office. Directus manages models, roles, validations. The front shows. The system lasts better over time.

Connect everything with n8n

Most businesses have multiple tools. The real challenge is to make them work together without the team becoming “human integration”.

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

What we learned in 2025 about speed and quality

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

Speed comes from framing, not from sprinting

When a project gets out of hand, we often blame the execution. In reality, the cause is often upstream: unclear objectives, changing scope, poorly defined data, or poorly understood roles.

In 2025, the framework that works consists of a few things: a clear target, an expected result, a realistic V1, a simple data model, and access rules set early.

When these points are aligned, you can deliver quickly and iterate without stress.

Rights and roles are the most underrated pain point

On apps and portals, the topic “roles and permissions” always comes up. The question is not whether that happens. The question is when do we take care of it.

When it's treated too late, it's expensive. It is necessary to resume screens, requests, routes. And sometimes you need to change the data structure.

When treated early, it's an accelerator. Everything is becoming more stable.

Automation without supervision is a debt

Automating is good. But automation that fails without warning is a silent problem.

In 2025, we reinforced a simple logic: automation must have a trace, a means of recovery, and a signal in case of failure. Otherwise, you discover the bug at the worst moment, often via a customer.

Content should be thought of as a system

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

If the content has no structure, it becomes a permanent project. Directus is often an answer, but beyond the tool, it is above all a discipline: models, validation, and clear ownership.

What 2025 confirms for Scroll, and what does it mean for the future

This Agence Scroll 2025 retrospective confirms one simple thing: value does not come from a miracle tool. It comes from a clear base, from an execution in short cycles, and from a coherent stack that lasts over time.

When an SME or an entrepreneur wants to move quickly, the challenge is not only to deliver a V1. The challenge is to deliver a system that can evolve, connect to existing tools, and remain maintainable over iterations.

In 2026, Scroll continued in this direction: clean framework, fast delivery, clean interfaces, and robust automations. If you want to turn an intention into a successful product or site without wasting months back and forth, our services cover precisely these topics, from the framing phase to the run and industrialization.