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

# Engagements

> How working with REM runs: one workflow, fixed scope, explicit production criteria.

REM starts with one network or application and one workflow, and gets it into production before adding breadth. Delivery is hands-on at first; the connectors, mappings, workflows, and controls built along the way are what become reusable product.

## How an engagement runs

<Steps>
  <Step title="Discovery">
    A short working session to pin down the workflow, the data, the destination system, and what "correct" means. See the questions below.
  </Step>

  <Step title="Fixed-scope pilot">
    One live workflow, delivered in roughly four to six weeks against written production criteria. For example: authorised ledger view → REM connector → canonical events → your ledger or stream → reconciliation and audit trail.
  </Step>

  <Step title="Production">
    The pilot moves to production once the agreed criteria are met, in the deployment mode your security boundary allows.
  </Step>

  <Step title="Managed deployment and support">
    Ongoing deployment, support, and SLAs for the running workflow, then expansion to the next workflow or network.
  </Step>
</Steps>

## Example first engagements

* Private Zk chain application → customer Kafka, Snowflake, or accounting system
* Tempo Zone → ledger, reporting, and reconciliation backend
* Private-EVM tokenised bond → lifecycle events and books-and-records synchronisation
* Custody or provider feed plus ledger view → settlement reconciliation
* Stablecoin product → production data, delivery, and operational controls
* Multi-entity stablecoin flows → intercompany settlement evidence and reconciliation

## Discovery questions

Come ready to talk through:

1. Which event or state must appear in which system?
2. What is rebuilt or handled manually today?
3. Which failures are expensive, common, or audit-sensitive?
4. Who owns the problem, the budget, and the production decision?
5. What data is authorised, and where may it be processed?
6. What finality, latency, completeness, retention, and residency rules apply?
7. Which actions remain under your or your custodian's control?
8. What result would convert a pilot into production?

## A good fit

Engagements work best when there is:

* a live product or a dated production launch;
* an urgent, recurring integration or operational problem;
* authorised access to the required data;
* a named owner in product, engineering, implementation, treasury, finance operations, or controllership;
* a real destination system and a correctness requirement;
* an agreed dataset and security boundary; and
* potential reuse across customers, entities, or deployments.

REM does not take on speculative token issuance, free generic demos, or custom development unrelated to the workflow.

## Ways to work together

| Model                  | What it looks like                                                                                                                                                                      |
| :--------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Direct**             | REM delivers the workflow for your application, infrastructure, stablecoin, RWA, network, or treasury team.                                                                             |
| **Embedded / OEM**     | REM becomes the embedded or white-label integration backend inside your product, deployed for each of your customers.                                                                   |
| **Subcontracting**     | REM provides specialist, white-label delivery capacity inside a prime contractor's client engagement, with clear scope, documentation, security boundaries, and non-solicitation terms. |
| **Managed deployment** | REM runs, supports, and maintains the workflow after it goes live.                                                                                                                      |

## Get in touch

<CardGroup cols={2}>
  <Card title="Book a call" icon="calendar" href="https://calendar.app.google/1oJJb3QyFQ61Pras7">
    Bring the network, the destination system, and the records that have to agree.
  </Card>

  <Card title="Email" icon="envelope" href="mailto:hi@rem.money">
    [hi@rem.money](mailto:hi@rem.money)
  </Card>
</CardGroup>