PPactDocs
Getting started

What is Pact?

Pact is a consent-native CRM that helps you build genuine customer relationships while respecting privacy.

Pact is a modern, consent-native CRM designed for teams that need to manage customer relationships at scale without sacrificing trust. It combines the power of traditional CRM and marketing automation with a privacy-first architecture — every contact interaction is anchored to explicit consent.

New to Pact?

Start with the Quickstart — you’ll import contacts and send your first sequence in under 15 minutes.

Core concepts

Unlike legacy CRM tools that treat consent as a checkbox, Pact models consent as a first-class entity. Every time you send an email, trigger a sequence, or run a campaign, Pact checks the underlying consent record. When consent is revoked, Pact automatically suppresses all outbound activity — no manual list scrubbing required.

Multi-tenant architecture

Pact is built for agencies, franchises, and enterprise customers that need strict data isolation between clients or business units. Each tenant gets its own encrypted namespace, RBAC roles, and audit trail. A user in Tenant A cannot see or modify anything belonging to Tenant B.

Sequences and playbooks

Outbound sales and marketing are coordinated through sequences (automated email/task workflows) and playbooks (rules that trigger sequences based on CRM events). This means your team spends time on conversations, not managing follow-up schedules.

AI-augmented workflows

Pact ships with built-in AI capabilities for email drafting, contact enrichment, and lead scoring. You can configure which AI provider to use (Anthropic, OpenAI, or Azure OpenAI) and override system prompts per tenant to match your brand voice.

What Pact is not

Pact is not a mass email blast tool. It is designed for 1:1 and 1:few relationship management, not bulk newsletter sends to millions of addresses. If you need a high-volume broadcast platform, you will want to integrate Pact with a dedicated ESP.

Architecture overview

code
Browser (Next.js 14)
  → FastAPI backend (multi-tenant, RBAC)
    → Postgres (tenant-scoped data)
    → Cache + queue layer
    → Workers (enrichment, ETL, delivery)

The web frontend lives under web/ and talks to the FastAPI backend. Both are containerized and deploy to a managed cloud runtime, with a managed Postgres database and in-memory cache handling persistence.

Next steps

Ready to dive in? Pick a starting point: