Ribeirão Preto, São Paulo — September 28, 2026. Mountain View, California, in my heart. Throughout the development of Weplex, we sometimes encounter situations where an internal tool could make an important part of our day-to-day work significantly easier. In the current AI and agentic days, following an AI-native approach also means reconsidering what deserves to become software. Instead of adapting every workflow to an existing product, founders and technical teams can increasingly build small, purpose-specific tools around the problems they actually encounter.
Weplex Studio came from one of those situations. Presentations are important at Weplex. We use them to educate customers, explain our work, support existing clients, and create marketing material. The complication is that many of these presentations need to point to real things: a client's actual website, an interface, real content, examples, or data.
This becomes particularly interesting for Weplex because much of what we create already lives on the web. At the same time, vertical video has become a practical format both for communicating directly with clients and for publishing marketing material designed primarily for mobile devices.
So the question became: could we create a presentation environment around the web itself, while making the same material useful for recording vertical videos?
We built Weplex Studio as an internal tool to explore that answer: a frame-based, slide-based authoring environment where web content, text, visual elements, and animations can be composed in layers and sequenced into presentations designed to be recorded.
A Sequencer for Web-Based Presentations
At its core, Weplex Studio works as a sequencer.
A presentation is organized into frames or slides that can be advanced while recording. Instead of requiring everything to become a static screenshot, a frame can incorporate web material through iframes and combine it with additional presentation layers.
This is particularly useful when the subject of the presentation is itself a website or web application.
The author can bring the actual page into the presentation and then add elements around it: text can be detached from the underlying material, sections can be highlighted, visual layers can be stacked, and animation can direct attention to a particular part of the experience.
The result is somewhere between a slide-authoring system and a lightweight presentation environment for the web.
Because the presentation itself is structured as a sequence, the person recording can concentrate more on communication and less on manipulating windows, finding pages, repositioning content, or reproducing the same setup for every take.
The portrait-oriented format also fits naturally with the way much of this material is eventually consumed: on mobile devices, through direct communication with customers, or as vertical video.
From Customer Support to Marketing
Weplex Studio was intentionally developed as a flexible internal tool rather than around one specific type of video.
For customer communication, we can use it to explain a website, demonstrate functionality, highlight a client's content, or create training and support material.
For marketing, the same system can be used to structure short presentations, product demonstrations, customer cases, and vertical videos. The underlying mechanism remains essentially the same; what changes is the communication objective.
The following examples show the range of presentations we create, from explaining a user experience idea to presenting customer websites and a support workflow. Each video is embedded here so you can see the examples in context.
Weplex CEO — marketing: the “3-second test”
Weplex CEO — marketing: presenting the MrClínica customer case
Weplex CEO — marketing: presenting customer examples in English
Weplex CEO — marketing: presenting a clinic customer example in English
Weplex CEO — training: presentation about the robot
The interesting part for me is not simply that AI helped us build another piece of software. It is what an AI-native approach can change about the threshold for building internal software in the first place.
A founder or technical team encounters small operational problems constantly. In the past, many of them would remain manual because building a dedicated tool would not justify the development cost. In the AI-native environment, that calculation begins to change.
Weplex Studio is one example of that shift: a tool born from a very specific communication problem, built around our actual workflow, and then progressively expanded as we discovered other situations where the same underlying system could help.
