# Demonstrations

### How to use this page

Use these demos to see the full flow. You go from prompt to deploy, with real examples.

{% hint style="info" %}
If you just want to “see it working”, start with **Start here**.
{% endhint %}

### Start here (recommended)

These three demos cover 80% of what you need.

1. **Sales CRM (from scratch)**\
   Prompt → specification → app → preview.\
   Video: *coming soon*. Template: *coming soon*.
2. **Inventory + alerts + dashboard**\
   Minimum stock, automatic alerts, management view.\
   Video: *coming soon*. Template: *coming soon*.
3. **Approvals (discount > 10%) end-to-end**\
   Multi-level workflow, audit trail, permissions.\
   Video: *coming soon*. Template: *coming soon*.

### Demos by industry

Choose a sector and adapt the template.

* **Healthcare**\
  Electronic medical record, scheduling, profile-based permissions.\
  Video: *coming soon*. Template: *coming soon*.
* **Construction and engineering**\
  Project management, budgets, measurements and approvals.\
  Video: *coming soon*. Template: *coming soon*.
* **Finance**\
  Financial control, cost centers, approvals.\
  Video: *coming soon*. Template: *coming soon*.
* **Retail**\
  POS, inventory, promotions, discount rules.\
  Video: *coming soon*. Template: *coming soon*.
* **Logistics**\
  Tracking, routing, status and SLAs.\
  Video: *coming soon*. Template: *coming soon*.
* **Education**\
  Course platform, assessments, certificates.\
  Video: *coming soon*. Template: *coming soon*.

### Demos by use case

Grouped by “product” vs “capability”.

#### Products (complete apps)

* **CRM**\
  Customer management, pipeline and activities.\
  Video: *coming soon*. Template: *coming soon*.
* **Helpdesk**\
  Tickets, queues, SLAs and support macros.\
  Video: *coming soon*. Template: *coming soon*.
* **Portal**\
  Internal vs external access, self-service.\
  Video: *coming soon*. Template: *coming soon*.

#### Capabilities (reusable pieces)

* **Approvals (workflow)**\
  Multi-level approval by value, area, risk.\
  Video: *coming soon*. Template: *coming soon*.
* **RBAC (roles and permissions)**\
  Profiles, rules by entity, screen and action.\
  Video: *coming soon*. Template: *coming soon*.
* **API + Webhook (integrations)**\
  Events, external calls and synchronization with ERP/CRM.\
  Video: *coming soon*. Template: *coming soon*.

### How to run a demo (standard flow)

{% stepper %}
{% step %}

### Watch the video and copy the prompt

Find the demo video. Copy the original prompt and the acceptance criteria.
{% endstep %}

{% step %}

### Generate the app and approve the specification

Paste the prompt into Madrix. Approve the specification before proceeding.
{% endstep %}

{% step %}

### Run the app and validate the basics

Create test records. Validate permissions, rules and flows.
{% endstep %}

{% step %}

### Adapt to your scenario

Replace names, fields and rules. Add integrations and notifications afterward.
{% endstep %}

{% step %}

### Deploy to Cloud environment

Deploy to Dev/Staging/Prod. Collect evidence and audit trails if needed.
{% endstep %}
{% endstepper %}

### Assets per demo (checklist)

Use this list to standardize each demo.

* [ ] **Clonable template** (“use this demo as template”)
* [ ] **Original prompt** used in the video
* [ ] **Versions** (v1, v2, v3) with short changelog
* [ ] **Diff of what changed** between versions (when it makes sense)
* [ ] **Evidence package** (if it is a “production readiness” demo)

### Next steps

* Want to learn by doing: [Practical Tutorials](/hands-on-tutorials.md)
* Want to get started in 15 min: [Start here](/get-started-here.md)
* Stuck on something: [Troubleshooting](/troubleshooting.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.madrix.dev/demonstrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.