> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prets.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> How Prets fits into your systems and customer journey

This section explains how Prets fits into your systems and customer journey, in the same practical terms you use to run your business.

It is written for teams who need to understand not just what Prets does, but how it behaves once embedded:

* **CTOs and engineers** responsible for integration
* **Operations and compliance teams** responsible for execution
* **Product owners** accountable for conversion and customer experience

This is not API documentation. It is the operating model.

## Where Prets fits in practice

Energy upgrades are sold by you — but decided over time by the customer.

Prets sits after the offer, before the final commitment. That is the moment where customers slow down:

* they want to understand the total investment;
* they compare ways to pay;
* they hesitate on forms, documents, and next steps.

Prets supports this phase without taking ownership away from anyone.

You remain the merchant. Funding providers remain the decision-makers. Customers remain in control.

Prets simply makes the process understandable and finishable.

## How Prets integrates

Prets is designed to fit into existing setups — not to replace them. Most merchants start small, then deepen integration as volume grows.

<Tabs>
  <Tab title="Embedded flow">
    **The fastest way to get live.**

    Prets runs directly inside your website, offer environment, or checkout using an embedded component.

    From the customer's perspective, nothing feels external. From your perspective, there is no new frontend to maintain.

    Used when you want to:

    * add payback and affordability insight after the offer;
    * let customers compare payment options calmly;
    * allow applications to start and finish without redirects.
  </Tab>

  <Tab title="API-driven integration">
    **For teams that want full control over the experience.**

    You design the journey. Prets provides the logic behind it: calculations, comparisons, application steps, and status handling.

    Typically used by:

    * utilities or large installers;
    * platforms with their own CRM or sales tooling;
    * teams operating across products, regions, or providers.
  </Tab>

  <Tab title="Hybrid setup">
    **Most long-term customers end up here.**

    Customer-facing steps run in embedded flows. Data, status, and reporting are handled through APIs.

    This keeps the customer journey simple while giving your teams operational control.
  </Tab>
</Tabs>