diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md
index 00ded5e36b0..bb69037e490 100644
--- a/content/en/docs/quickstarts/responsive-web-app.md
+++ b/content/en/docs/quickstarts/responsive-web-app.md
@@ -254,6 +254,33 @@ To deploy your app to a cloud environment, you can hit **publish** to deploy you
 To deploy your app to the Mendix Cloud (Paid), there are multiple options for hosting. Please refer to this guide on [our hosting options](/developerportal/deploy/mendix-cloud-deploy/) for more information on which plan is best for your project.
 {{% /alert %}}
 
+## Build Faster with Maia
+
+Throughout this guide, you built your Employee app by hand — dragging entities onto the canvas, wiring up buttons, and writing microflow logic step by step. That's a great way to learn how Studio Pro works under the hood. But once you're comfortable with the basics, you don't have to do everything manually. **Maia**, Mendix's built-in AI assistant, can take over much of this repetitive modeling work for you.
+
+Unlike a typical chatbot that only answers questions, Maia is *agentic*: she can read your app's current domain model, pages, and logic, understand the context you're working in, and then directly create or modify app elements on your behalf. Ask her to add an entity, generate a page, or build out a microflow, and she'll produce real, editable Studio Pro artifacts — not just a suggestion or a code snippet for you to copy in.
+
+Maia isn't one single feature but a collection of capabilities woven into Studio Pro. The one you'll use most often is **[Maia Make](https://docs.mendix.com/refguide/mendix-ai-assistance/)**, a conversational interface where you describe what you want in plain language and Maia generates the domain model changes, pages, or microflows to match. Alongside Maia Make, you'll also find focused generators (for domain models, pages, workflows, and OQL queries), recommenders that suggest the next best widget or microflow activity as you build, and guidance tools like **[Maia Chat](https://docs.mendix.com/refguide/maia-chat/)** and **[Maia Explain](https://docs.mendix.com/refguide/mendix-ai-assistance/)** for when you want an explanation rather than a change to your app. As you grow more advanced, **[Maia Agent Skills](https://docs.mendix.com/refguide/maia-agent-skills/)** and Agent Instructions let you teach Maia your team's own conventions so her suggestions stay consistent with how your organization builds apps.
+
+### Try It Yourself: Extending the Employee App
+
+Let's put Maia to work on the app you just built. Right now, your Employee entity captures a job role as free text — let's use Maia to turn that into a proper Department entity, linked to Employee, along with an overview page.
+
+1. In Studio Pro, open **Maia Make** from the top bar.
+1. In the chat box, describe what you want:
+
+    > "Add a Department entity with a Name attribute. Create a one-to-many association from Department to Employee, so each employee belongs to one department. Then generate an overview page listing all departments with their employees, and add that page to the app's navigation."
+
+1. Maia will process the request and propose a set of changes — typically a new entity in your domain model, the association to Employee, a new page with a data grid, and a navigation entry linking to it. **Review** the proposed changes in the preview panel.
+1. Click **Accept** to apply the changes to your app. You'll see the new **Department** entity appear in your App Explorer, already connected to Employee, along with a new item in your app's navigation menu.
+1. **Open** the generated page and run your app locally (**F5**) to see the new Department overview — now reachable directly from the navigation menu — alongside your existing Employee Overview page.
+
+{{% alert type="info" %}}
+You can keep iterating conversationally from here — for example, asking Maia to "add validation so a department name can't be empty" or "add a dropdown on the Employee page to select a department." Each request builds on the app state Maia already understands, so you don't need to re-explain your app every time.
+{{% /alert %}}
+
+As you get more comfortable, try using **[Maia Explain](https://docs.mendix.com/refguide/maia-explain/)** on the microflow you built earlier (`Act_Employee_NewEdit`) to see how Maia summarizes logic you already created — a useful way to sanity-check your own work or onboard a teammate to the app quickly.
+
 ## Finished!
 
 Congratulations on completing and deploying your very first Mendix App! Next, head over to the [Academy](https://academy.mendix.com/link/home) and get started with our **Crash Course** learning plan, or continue learning here in our docs pages by continuing onto part two. For videos on the latest news and updates, head to our [YouTube page](https://www.youtube.com/c/MendixCommunity). Or see what our awesome community is up to on our [Medium publication](https://medium.com/mendix).