Terms & Conditions

Last updated: July 23, 2026

These Terms and Conditions (“Terms”) govern the use of REVsign OS, the revenue intelligence platform developed and implemented by REVsign (“REVsign”, “we”) for its clients (“Client”, “you”). By engaging or using REVsign OS, the Client accepts these Terms.

1. Definitions

  • Platform / REVsign OS: REVsign’s proprietary system that centralizes sales operations, detects business and technology signals across the Client’s accounts, and drafts outreach and expansion messaging — always subject to human approval before anything is sent.
  • Base Plan: an asynchronous deployment of REVsign OS — the Client receives the system’s impact (alerts, drafts, reports) without needing to learn a new interface.
  • Custom Plan: an additional layer of frontend, authentication, and real-time monitoring built on top of the Base Plan, without rebuilding what is already deployed.
  • Client Instance: the code, database, configuration, and integrations deployed specifically for the Client.
  • Sub-processor: any third-party provider REVsign uses to operate the Platform on the Client’s behalf (e.g., infrastructure, artificial intelligence, or email delivery providers). The current list is available in the Privacy Policy.

2. Scope of service

REVsign develops and implements REVsign OS as a proprietary platform, built with the Client’s own code, that integrates into the tools the Client already uses (CRM, ERP, data providers, email) without requiring their replacement. Implementation can be deployed in full or by module, depending on the Client’s needs.

REVsign offers two service tiers:

  • Base Plan — Asynchronous Operation: a dedicated data engine (a database isolated per client), specialized AI agents operating within parameters fixed in code, orchestration of recurring workflows (market radar, account scans, cost reports), email notifications, and version control of all code in a private repository.
  • Custom Plan — Integrated Dashboard: adds a purpose-built web application, secure authentication, real-time monitoring, and, when required, bridge servers (MCP) to connect legacy internal systems or ERPs. Moving from the Base Plan to the Custom Plan does not require rebuilding the existing deployment.

3. Intellectual property

  • Client-owned: the code, data, and configuration specific to the Client Instance belong to the Client. They are version-controlled in a private repository the Client has access to, ensuring full traceability and no black boxes.
  • REVsign-owned: the framework, methodology, agent architecture, and reusable components of REVsign (including the “Reveal Signals” doctrine) are owned by REVsign and licensed to the Client for use during the term of the contracted service. This license does not transfer ownership of those components.
  • Development prompts and recipes: the specific prompts, instructions, and “recipes” REVsign uses internally to design, train, or tune the AI agents during the development and implementation of the Client Instance are not part of the Client’s intellectual property, even though the result of applying them — the final code and configuration deployed to the Client Instance — is. These prompts and recipes are REVsign know-how and fall under the point above.
  • Third-party software integrated into the Platform retains its own licenses and terms.

4. Integrations with the Client’s tools

The Client authorizes REVsign to connect REVsign OS to the systems it designates (CRM, ERP, data providers, email, etc.). The Client represents that it holds the rights and credentials necessary to authorize such connections and is responsible for keeping them valid.

5. Operational guarantees and limits

  • Human approval, always: no outreach email, expansion proposal, or report leaves the Platform without explicit human approval from the Client’s designated owner. REVsign does not contact the Client’s end customers on its own.
  • Exclusion filters: an exclusion list and a 60-day per-account cooldown apply automatically before a draft is even generated.
  • Resilience: if a third-party provider fails, the Platform uses a backup provider when one exists, or defers and retries the operation until it completes, without losing or duplicating work.
  • These guarantees stem from the system’s architecture and do not, on their own, constitute a guarantee of business outcomes.

6. Service provided “as is”

The Platform and related materials are provided “as is,” without express or implied warranties of fitness for a particular purpose, except as expressly stated in these Terms. To the extent permitted by applicable law, REVsign will not be liable for indirect, incidental, or consequential damages arising from use of the Platform.

7. Data processing

REVsign acts as a data processor with respect to data it processes within REVsign OS on the Client’s behalf. Details on what data is processed, for what purpose, and through which sub-processors are set out in the Privacy Policy.

8. Term, billing, and termination

The service is contracted by plan through a subscription, with specific commercial terms (price, billing cycle, scope) agreed separately with each Client. REVsign or the Client may terminate the service as commercially agreed. Upon termination, the Client retains access to the private repository containing the code and data of its Instance, as these belong to the Client.

9. Changes to these Terms

REVsign may update these Terms to reflect changes to the service or applicable regulations. The current version is published on this page along with its last-updated date.

10. Governing law and jurisdiction

These Terms are governed by the laws of Argentina. For any dispute arising from these Terms, including disputes involving Clients located outside Argentina, the parties submit to the ordinary competent courts of the City of Buenos Aires, Argentina, expressly waiving any other venue or jurisdiction. These Terms do not include an arbitration clause.

11. Contact

For any questions about these Terms, write to hola@revsignlab.com.