WoodWing 2026: Mid-Year Product Update

Hello everyone, and welcome to another Product Update webinar. This time it's our mid-year update. Europe has been very hot in June, and I hope you're staying cool and in a nice, cozy environment while following the mid-year product updates from our Product Management team.

I am Magdalena, the Product Marketing Manager at WoodWing, and I will be moderating today's webinar. It is a great pleasure to introduce our speakers for today.

We start with Tom Pijsel, our VP of Product Management at WoodWing, who is going to wrap up the product roadmap summary and fill you in on the latest WoodWing Studio feature releases and updates.

Then we have our Product Manager for WoodWing Assets 6 and 10, Jouke Jongsma.

After Jouke, we're going to have Jeff Gapp on stage talking about WoodWing Connect and PDF Manager. Jeff joins us from our US office.

Last but not least, we have Paul Walker from the UK joining us. He is our Development Manager for WoodWing Connect and will showcase the latest updates for Workflow Assistant and the Content Delivery Hub.

At the end, we always have time to answer any questions you might have throughout the session. You can use the chat function on the right-hand side throughout the webinar. As I said, we always save a couple of minutes at the end to answer your questions.

A quick overview of today's agenda. We'll start with the product roadmap for the year, followed by WoodWing Studio and WoodWing Assets 6 and 10, covering the latest releases from the first half of the year. After that, we'll continue with WoodWing Connect and the WoodWing Apps.

Without further ado, I'd like to introduce Tom Pijsel to the stage. Thank you, Tom. Please walk us through the roadmap.

Tom Pijsel:

Thank you, Magdalena.

Let me walk you through the roadmap. This is a recap from the previous webinar.

For Assets, the main focus is on Assets 10. We're integrating Assets 10 with Studio so that you can drag and drop files into Studio and archive files from Studio back into Assets 10.

Besides that, we're working on additional features such as a native Trashcan in Assets 10 and several API improvements.

We're also redesigning and enhancing the Smart Styles Portals feature, giving you tighter control over sharing, accessibility, download options, metadata management and filtering.

Another very important topic is ensuring a smooth transition from Assets 6, with or without Studio, to Assets 10. We're therefore building migration tooling to support customers during that migration.

Finally, AI-powered Search. We're continuing to explore the possibilities of AI-powered Search. Several technology previews are already available, but this year our main focus is finding a cost-efficient way to make AI-powered Search available to all of you.

For Studio, the main focus is also the Assets 10 integration. The Studio and Assets teams are working closely together to bring this to market.

Besides that, we're working on two additional initiatives.

The first is AI Layout Automation. We'll cover this in more detail later in today's presentation. During the first half of the year, we focused primarily on newspapers, while in the second half we'll expand our focus to magazine production.

The second initiative is AI for content editors, both in the Digital Editor and the Print Editor. We'll also show more about that later.

Lastly, WoodWing Connect. We're focusing on the Connect Core, which includes the Studio and Assets connectors inside Workato.

We're consolidating these integrations onto one central platform, allowing us to upgrade them more easily, deliver updates faster, and expand the available feature set.

This also ties into our final roadmap item: expanding the capabilities of the WoodWing Apps, including PDF Manager, Workflow Assistant and the Content Delivery Hub.

With that, I'd like to hand over to Jouke for the update on Assets 6 and Assets 10.

Jouke Jongsma:

Thank you, Tom.

Good afternoon everyone. I'd like to walk you through the key updates we've made to our Assets products since the beginning of this year.

Let's start with Assets 6.

Our primary focus has been on overall platform stability and infrastructure performance optimization.

This isn't a one-off project but a continuous effort that will continue throughout the entire year.

If we look back at the first six months, we've already made significant progress. Our focus has mainly been on self-service improvements and UI modernization, making the user experience much more intuitive.

We've also successfully implemented several system optimizations that lay the foundation for what comes next.

In our August release, we'll focus on reducing backend and Elasticsearch load by introducing smarter pagination and more efficient query logic across several key areas.

For example, within the Linked Files panel we're replacing large single requests. Instead of requesting thousands of records at once, infinite scrolling will now load only fifty records at a time.

Within the History panel we've switched from retrieving the complete history in one request to scroll-based pagination of fifty records per page.

For Pin Collections we've introduced additional query optimizations to further improve responsiveness.

We've also improved the Management Console to simplify daily administration of users.

Filters now remain active even after creating a new user.

Group selections remain stable during renaming operations.

We now support plus symbols in email addresses.

Finally, an important improvement for our cloud customers is support for single file uploads up to 5 GB. This is now achieved using multipart Amazon S3 uploads.

Looking at Assets 10, the core team's primary focus is DAM consolidation and AI improvements.

During the past six months we've introduced Front-end Integration, enabling panel and action plug-ins. I'll show two examples of that shortly in a demo.

We've continued our migration work towards Elasticsearch, which is an important step in migrating from Assets 6 to Assets 10.

We've also introduced our first AI features, marking the first steps towards full natural language search and visual similarity search.

Looking ahead, as Tom already mentioned, we're focusing heavily on the Assets 10 Studio integration.

This will also introduce additional DAM consolidation features such as linked files and metadata facets directly inside the interface. Native Trashcan functionality and the improved Portals are also part of this work.

Let me zoom in on the AI improvements.

We already support AI auto-tagging, but we've now added contextual descriptions and AI-generated alt text. Assets can now generate rich, descriptive image captions together with accessibility-focused alt text.

We've also introduced audio and video transcription, including subtitle generation.

Assets now automatically generates complete transcripts together with subtitle files, storing these inside metadata fields.

Because the transcript becomes searchable, keywords inside audio and video files are now fully indexed, allowing these assets to appear directly in search results whenever a keyword matches.

To support all those AI features, we have now introduced a dedicated AI metadata category.

More AI features will follow. These features are currently available for demonstration, and we're investigating the appropriate commercial model.

Let's play a short video. In this video, I'll show two examples of Front-end Integration to demonstrate what's possible with the new Front-end Integration capabilities. I'll also show how the AI capabilities have been added to the product, including the rich text descriptions and how the audio and video transcription works.

Video... There we go.

[Video demonstration]

...organize, manage, and share their digital files efficiently.

This integration, in particular, allows sales representatives to browse and search.

[Music]

Today I'm thrilled to unveil our completely reimagined WoodWing Assets 10, a feature-rich and intuitive Digital Asset Management solution.

Those are some nice examples of what's possible with Front-end Integration, such as placing an image on a map or connecting with a Content Delivery Network.

You also saw a few examples of AI-powered Search and the first steps towards full natural language search.

More on that in future webinars.

I'll now hand it over to Jeff for WoodWing Connect.

Tom Pijsel: No, actually it's back to me.

Jeff Gapp: I was going to say... welcome back, Tom.

Tom Pijsel:

Thank you, Jeff.

Let me give you an update on WoodWing Studio.

Apart from the AI Assistant and Layout Automation, we've been working on adding support for Adobe InDesign and Adobe InCopy 2026. We've also upgraded to the latest PHP version, PHP 8.4.

For the AI Assistant, we've added the capability to create custom prompts.

As an administrator, you can now configure prompts, provide detailed explanations of suggested changes, and replace text. It's easier to show this in action, so we've created a short video.

Let me play the video to show you the latest updates.

Video:

Hello everyone.

We're going to take a look at how you can optimize your digital articles using the AI Assistant in the Digital Editor of WoodWing Studio.

This feature is designed to help reduce repetitive editorial work while keeping you firmly in control of the final story.

When writing articles, a lot of time can be spent refining tone, improving wording, or coming up with stronger headlines.

The AI Assistant helps streamline this process by offering built-in suggestions directly inside Studio. It's designed to improve efficiency without sacrificing editorial quality.

On the right side of the Digital Editor, I'll select the AI Assistant icon to open the AI Assistant panel.

The panel opens alongside my article so I can review suggestions without leaving the editor.

At the top of the panel I see the question:

"How can I help you today?"

From here I can choose from a set of predefined actions.

For example, I can ask the AI Assistant to shorten or lengthen the text, revise the tone of voice, or suggest new titles.

Let's start with title suggestions.

While the AI is processing, it's good to mention that your administrator can freely configure additional actions using the Studio Management Console.

The generated responses appear in the response bubble below your request.

This layout makes it easy to see exactly what was requested and what the AI returned.

You can also refine the generated answer or ask a different question using the input box at the bottom of the panel.

For example, let's ask for a new introduction.

I can now copy the generated introduction and use it directly in my article.

Let's have a look at a more advanced scenario.

I'll ask the AI to copy-edit my story.

This action evaluates the article and provides suggestions on how to improve it.

Finally, let's use the Translate option.

The Translate action works similarly to changing the tone of voice, shortening, lengthening, or performing any other rewrite.

With one click of a button, we can replace all the text in the article with the newly generated version.

Thank you for your attention.

Tom Pijsel:

So, the Digital Editor AI Assistant is now available for Ultimate customers in the WoodWing Cloud.

We're currently continuing development by adding support for the Print Editor. This will become available later this summer and will include a dedicated copyfit action.

We're also investigating whether we can make the same functionality available inside Adobe InCopy, but we'll share more about that during future webinars.

Let's move on to WoodWing Layout Automation.

Layout Automation combines your historical design expertise with AI intelligence to generate layout suggestions that save hours of repetitive work while ensuring pages remain fully editable in Adobe InDesign.

You can also mix and match automated layouts with traditional creative workflows within a single issue.

This ensures brand consistency while significantly speeding up the publishing process.

Before showing you what we've added over the last few months, let me first show a short refresher video demonstrating the capabilities of Layout Automation.

Video:

Hi.

In this video we'd like to show you AI Layout Automation in action.

As you can see, your page planning solution has already created the empty pages in WoodWing Studio and placed the sold advertisements.

The next step is placing the editorial stories on the page using the Layout Automation dialog.

[Video continues]

Note: this transcript has been auto-corrected using AI, it may contain mistakes.

At the bottom, we see a list of all the stories that have been written for this issue and category. At the top, we see how the algorithm is laying out the articles across the different pages.

As a user, I can now make some adjustments to the design. For example, by changing the story type from a lead story to a secondary story, or by changing the page number.

Let's change the page number for this story to page three.

When I click Update, we see that the story is now placed on page three.

Whether something is a lead story or a secondary story is ultimately a creative decision. It isn't determined solely by the number of characters. For example, you might have a relatively small story with a large image that should still be treated as the lead story.

When you're satisfied with the result, you can click the Compose Pages button.

The design is then sent to the InDesign Server and the stories are placed onto the page. This takes a moment.

Afterwards, you can continue using the existing production workflow. For example, you can preview the layout, open one of the stories in Adobe InCopy or the Print Editor, or continue refining the design directly in Adobe InDesign.

Thank you for watching.

Tom Pijsel:

Let me now walk you through the features we've recently added to Layout Automation.

The first addition is the ability to filter layouts and articles.

For example, if you want to limit the set of articles that can be placed based on a specific metadata field, you can now do this using a custom query.

As a user, you can create your own custom query and use it to filter the list of available articles.

We've also added options to take already placed articles into account.

This allows you to mix and match automated layouts with manually designed pages.

For example, you may already have a page containing a fixed column that has been manually placed because you know that part of the page will never change. Layout Automation can then automatically place the remaining content around that fixed article.

A new pin icon clearly indicates that an article has already been placed manually and that the remaining layout is generated around it.

Another thing we noticed while customers were using Layout Automation in production is that the decision to use a spread or two single pages is often made during production rather than during planning.

Therefore, users requested the ability to switch between spreads and single pages during production.

That capability has now been added.

Finally, we've introduced Placement Presets.

As an administrator, you can now create multiple placement presets that influence how the layout algorithm behaves.

For example, at the beginning of a production cycle you might want to maximize the number of articles that can be placed automatically.

Near the deadline, however, your priority may shift towards ensuring that every article fits neatly on the page.

Users can simply select the desired preset from the interface, after which the layout plan is regenerated according to that strategy.

Besides the text copyfit functionality we're currently developing, we're also working on Layout Fitting.

There are essentially three ways to make content fit:

One is by changing the length of the text.

Another is by selecting a different paragraph style.

With Layout Fitting, however, we don't change the editorial content at all.

Instead, AI intelligently adjusts the dimensions of layout frames to make the text fit naturally.

Because the text itself remains unchanged, no editorial review is required. It is purely smart layout optimization.

This functionality is now available as part of the AI Layout Automation package.

Here we see a page generated by Layout Automation.

You can right-click one of the article frames and select Fit Article with AI Creative.

The composition is then sent to the AI service, which optimizes the layout to ensure that the text fits perfectly.

Once processing is complete, the design is automatically updated.

While AI is optimizing one article, you can continue working on other articles or even work on another layout altogether.

You never have to wait for the AI process to complete.

With that, I'd now like to hand over to Jeff for the WoodWing Connect update.

Jeff Gapp:

Very good. Thank you, Tom.

As hopefully everybody knows by now, WoodWing Connect is the umbrella term we use for all of the integrations we build.

This includes our APIs, iPaaS solutions, webhooks, applications, and many other integration technologies.

We've been particularly active around what we call the Studio Core.

One area we've continued developing is PDF Manager, which we'll demonstrate in a moment.

PDF Manager has matured considerably thanks to customer feedback combined with our original vision. We continue expanding the capabilities and refining the tool.

If you're interested, we now have a publicly available PDF Manager introduction in our Help Center.

Another major enhancement is what we call the PDF Dialog.

Within Publication Overview, PDF Dialog allows users to generate PDFs in many different ways.

For example, you can create low-resolution PDFs, high-resolution PDFs, spreads, individual pages, page ranges, or complete sections.

It's a flexible interface that gives users extensive control over PDF generation.

We've also introduced the Connect API Proxy.

This provides a secure method for Studio to communicate with external endpoints.

Different authentication methods can be configured, including API keys and other validation mechanisms, ensuring secure communication between Studio and external systems.

Regarding Connect Webhooks and the Workato connectors, the Studio connector now supports the Studio Planning API.

This enables customers without a dedicated planning system to import planning information from sources such as Microsoft Excel or Google Sheets and automatically generate planned pages through the integration.

We're very proud of that capability.

Another feature currently in development allows metadata to be updated even while Studio objects are locked.

This functionality has generated considerable interest throughout the integration ecosystem.

It enables external workflows—for example, translation services—to report status updates back into Studio while someone else is still working on the layout.

That's a quick overview of our recent work around WoodWing Connect, Studio, and our iPaaS integrations.

As a reminder, we also continue expanding our pre-built integrations and technology partnerships.

The pre-built integrations are organized into categories, allowing customers to browse available integrations via the Integration Marketplace.

In addition, we invite technology partners to publish their own solutions.

Partners including ANF, Amendo, Tansa, Smartia, Brickswire and Contextual already have integrations listed in the marketplace for customers to explore.

Now I'll hand over to Paul Walker.

Magdalena:

Jeff, there's one more slide about PDF Manager that's actually yours.

Jeff Gapp:

You're right. I'll quickly cover that.

PDF Manager is a workflow-driven solution for generating PDF files.

The name is actually less descriptive than everything it can do.

It can generate files based on workflow or metadata, and there are several ways to trigger those processes.

Let's take a quick look at a short demonstration.

Video:

Hello everybody.

My name is Jeff Gapp and I am the Product Manager for WoodWing Connect.

Today I'd like to show you PDF Manager.

We'll look at generating PDFs, delivering PDFs, packaging files, and briefly introduce the Connect API Proxy, which provides a secure method for building integrations using Studio.

In this first example we're looking at the Studio Web Client.

On the right-hand side we see a workflow status and a metadata field labelled Create Multi-page PDF.

Many customers choose to use workflow statuses to trigger automated PDF generation.

If we change the status to Generate PDF, the PDF process immediately starts.

If the generation succeeds, the workflow status automatically changes to Done.

If the PDF fails—for example because a preflight check detects missing fonts or missing images—the status changes to PDF Generation Failed, together with detailed error information explaining what needs to be corrected.

Another method for triggering PDF generation is through metadata.

Any metadata field can be used to start a workflow or define specific PDF generation options.

In this example we're generating a multi-page PDF containing multiple pages from the layout.

Once generated, the PDF can be delivered to several destinations.

For example, it can be stored in WoodWing Assets, returned directly into Studio, uploaded to an Amazon S3 bucket, or delivered to another configured destination.

Here we're looking inside WoodWing Assets.

We can see the generated PDF together with automatic version management.

If preferred, versioning can be disabled or multiple visible versions can be maintained.

PDF Manager is not limited to creating PDFs.

It can also generate complete file packages, export JPEG images, PNG files, and several other output formats.

Back in the Studio Web Client we also have PDF Dialog available inside Publication Overview.

The interface has been refined extensively based on customer feedback.

Some organizations want generated PDFs to be emailed internally—for example to Marketing or Legal—while others want them delivered externally.

If email delivery isn't required, the interface can simply be configured to store the files back inside Studio.

Users can generate spreads, individual pages, complete sections or specific page ranges.

When sections are available they appear together with the corresponding number of pages.

For example, we can generate pages 1 through 5 instead of the complete publication.

After submitting the request, the Issue PDF is generated and stored according to the configured workflow.

PDF Manager also provides extensive troubleshooting capabilities.

Besides detailed error messages, administrators can inspect complete processing logs showing every step performed by InDesign Server during PDF generation.

Finally, I'd like to briefly introduce the Connect API Proxy.

The API Proxy allows Studio to communicate securely with external endpoints.

Authentication methods such as Bearer Tokens, custom headers and API keys can be configured, ensuring secure communication between Studio and external applications.

That's everything I'd like to show today regarding PDF Manager and the Connect API Proxy.

Thank you very much for your attention.

Jeff Gapp:

As always, if you have any questions or would like a live demonstration, please don't hesitate to contact us.

And this time I'll really hand things over to Paul.

Paul Walker:

Thank you, Jeff.

Hi everybody...

Note: this transcript has been auto-corrected using AI, it may contain mistakes.

Paul Walker:

I'm the Product Manager for the WoodWing Connect Apps, one of which is Workflow Assistant.

One of the key things we want to talk about today is the guardrails we've introduced.

To briefly remind everyone what Workflow Assistant is all about: the goal is to provide users with a workflow in a role-based, easy-to-understand format that reduces errors and minimizes the amount of training required.

It takes potentially complex business rules and simplifies them into an intuitive workflow, while still enforcing those business rules behind the scenes.

Users can therefore work with WoodWing Assets in a much more straightforward and guided way.

One of the recent additions is a complete set of Help files. You'll find a QR code on the slide, so please feel free to use it.

Now I'd like to show you the first demonstration. It consists of two parts.

First, I'll demonstrate the new guardrails we've added to Workflow Assistant for WoodWing Assets.

Secondly, I'll give you a sneak preview of a new chat capability that will help administrators configure the system later this year.

Let's start the video.

Video:

Hi.

This is a sneak preview of what's coming in Workflow Assistant 2.0.7.

We're preparing a complete demonstration environment that everyone will eventually be able to access.

It allows you to explore all available features, hover states, disabled states and other interface behaviour.

Today I'd specifically like to demonstrate the new guardrails.

For example, administrators can now configure required fields globally.

Within this demo environment, notifications guide users step by step.

They clearly indicate what action needs to be performed before users can continue.

In this example, a Lucene query determines whether an asset must first be selected before the workflow can proceed.

Once an asset has been selected, the notification disappears automatically and the next workflow steps become available.

Users can also deselect the asset again if necessary.

This demonstrates how Workflow Assistant guides users through every stage of a process while preventing mistakes.

It tells users exactly where they are, what needs to be completed and whether any problems still need to be resolved.

Several versions ago we introduced required fields.

As soon as a value is entered into a required field, the validation is satisfied and the field is no longer marked as required.

We've also introduced conditional required fields.

In this example, none of the fields are initially required.

However, using a simple metadata field and a Lucene query, administrators can dynamically determine when certain fields become mandatory.

This is especially useful for workflows involving image assets that require titles, descriptions or publication states before publishing.

Once the configured condition evaluates to true, all relevant fields immediately become required.

Another capability we've added is pattern matching using regular expressions.

For example, this field only accepts three to six alphabetical characters.

Numbers are automatically rejected.

Administrators can therefore validate not only whether information is entered, but also whether the entered data matches the expected format.

We've also significantly expanded reporting.

When running a report, users now receive much clearer feedback about exactly which metadata fields are included.

The Metadata Stamp also provides clear success and error notifications, giving users immediate feedback whenever something goes wrong.

Grouping assets has also been enhanced.

You can now configure any number of metadata fields within the grouping interface.

Rich Text is now optional rather than mandatory.

You can group multiple assets together and designate one or more lead assets.

In this demonstration, the lead asset is stored in the Container Key field, which aligns with Assets 6 functionality.

Finally, we're bringing AI into Workflow Assistant.

Within the configuration interface you can now enter prompts such as:

"I want to add notifications to this section."

The AI proposes the required configuration changes, after which you simply approve them.

The notifications immediately become available in the user interface.

The same applies to adding interface elements such as dropdown lists.

These AI-assisted configuration capabilities won't be part of version 2.0.7 but are planned for Workflow Assistant 2.0.8, scheduled for August.

Paul Walker:

That gives you an overview of what we're working on over the next few months for Workflow Assistant.

Now I'd like to move on to Content Delivery Hub.

For those unfamiliar with it, Content Delivery Hub is our multi-channel content transformation, enrichment and delivery platform.

It allows you to ingest articles from virtually any source, enrich them with assets from WoodWing Assets or external systems, transform them into different formats and finally deliver them to the CMS or publishing platform of your choice.

We've recently given Content Delivery Hub a major overhaul.

One of the biggest improvements is an entirely redesigned interface that makes configuration significantly easier.

Again, a major design principle has been adding guardrails to reduce configuration errors.

We've also introduced an interchange format.

This means that every transformation now passes through a central internal format.

As a result, whenever we add support for a new CMS or publishing platform, customers immediately gain access to all existing transformations without additional development.

Adding support for new destinations therefore becomes much faster.

Let's take a quick look at another sneak preview.

This functionality is planned for release later this autumn.

Video:

I'd like to give you a preview of some major improvements coming to Content Delivery Hub.

The first thing you'll notice is a completely redesigned WYSIWYG interface.

Instead of manually editing JSON configuration files, users now work through an intuitive visual wizard.

You simply connect Studio, define your publishing channels and configure transformations visually.

Here we're creating a simple flow from Digital Editor to an Amazon S3 destination.

As soon as we connect the output, the interface immediately identifies a configuration error.

We can now open the new AI Assistant—the same assistant you saw earlier in Workflow Assistant—and simply ask why the configuration isn't valid.

The AI immediately explains that a valid bucket name is missing.

After correcting the bucket configuration and saving the flow, the error indicator changes from red to green.

This dramatically simplifies the creation of multi-channel delivery workflows.

From the same interface you can also inspect execution history.

You can review every individual execution, determine why a particular item was skipped or investigate failed executions.

Again, the AI Assistant can analyse failures and explain configuration problems.

In this demonstration, the failure is once again caused by an invalid configuration.

These improvements make configuring and maintaining Content Delivery Hub considerably easier.

These capabilities will become available later this year.

Thank you.

Paul Walker:

That gives you a quick overview of what we're currently developing for both Workflow Assistant and Content Delivery Hub.

I'll now hand things back to Magdalena.

Magdalena:

Thank you so much.

Actually, before we wrap up, I'd like to thank Paul, Jeff, Jouke and Tom for presenting today's updates and ensuring that our customers, partners, prospects and everyone joining today's webinar remain up to date with everything happening across the WoodWing Assets, Studio and Connect portfolio.

Before we finish, I'd like to briefly mention another topic.

This concerns how search behaviour has changed.

Nearly 60% of searches now end without a click.

This is an important trend we'd like to highlight.

We've recently published a new report together with Media Voices that explores exactly what this means.

You can access the report by clicking the button displayed in the centre of your screen.

The report explains what the zero-click shift means for your content strategy and how to remain visible in an AI-first world.

If you don't download it now, you can also visit the webpage afterwards, enter your details and download the report there.

Looking at the time, we have just under five minutes remaining.

We've covered a considerable number of product updates and features currently under development.

I'm checking the chat but unfortunately I don't see any questions.

I'll give everyone another moment.

If you're interested in any of the WoodWing Apps—such as Content Delivery Hub, PDF Manager or Workflow Assistant for WoodWing Assets users—and would like a more detailed demonstration, please don't hesitate to contact us.

You can reach us via the contact form on woodwing.com.

Our Product Management team together with Professional Services will gladly schedule a session tailored specifically to your own use cases and demonstrate the applications in more detail.

It looks like we still don't have any questions.

I hope this mid-year product update has been useful and informative.

We're already looking forward to seeing you again at the beginning of 2027, when we'll kick off another year of product updates.

Our Product Management team will once again present the roadmap for the coming year and review everything launched during the second half of 2026.

Thank you again for spending your time with us today.

I hope you're managing to stay cool during the heatwave.

Tom, do you have any final words?

Tom Pijsel:

No, I'd simply like to thank everyone for joining us today.

And as Magdalena mentioned, if you have any follow-up questions, please don't hesitate to reach out to us.

Magdalena:

Exactly.

You can always submit the contact form on woodwing.com and one of our team members will get back to you.

Thank you all once again.

I wish everyone a wonderful evening—or, if you're joining us from the United States, a wonderful rest of your day.

We hope to see you again very soon.

Opmerking: dit transcript is automatisch gecorrigeerd met behulp van AI en kan fouten bevatten.