Platform Overview & Architecture

Overview

Intempt is agentic software for GTM teams: one customer context, four products (Marketing, Sales, Analytics, and Design), and the AI agents that do the work inside each one. An organization is the top-level account, and a project is the working unit inside it, the boundary for a team's data and settings. Everything else on this page, the products, the agents, and the data underneath, lives inside a project's scope.

📘 Good to know

This page describes the platform's structure: how organizations, projects, the four products, and the agents inside them fit together. For what each product actually does, see What is Intempt?

How it works

Organizations and projects

An organization can hold one or more projects. You switch between organizations and projects from the selector at the top of the sidebar. See Organizations & Projects for how access and roles work across both levels.

One customer context

Every product reads from the same data foundation instead of its own copy of the customer. Data lands as discrete events, each with a name, a timestamp, a unique identifier, a Master ID linking it to whoever performed it, and a JSON of properties, and Intempt makes those events available for analysis within seconds of ingestion. Unified user and account profiles, computed attributes, and segments are all built on top of that same event stream.

A segment built for a campaign in Marketing and a filter a rep uses in Sales both draw from this one context, not two different copies of the customer. See How Intempt Works for the ingestion and real-time infrastructure behind this layer, and the Glossary for exact definitions of Attributes, Segments, and the other terms used here.

Four products, one sidebar

The sidebar has two halves, and neither of them switches. Six destinations sit at the top and belong to no product: Home, Brand, Asset library, Attributes, Users and Integrations. Below them are four collapsible groups, one per product. All four render at once — you are not switching between modes, you are collapsing the groups you are not using today.

The six pinned destinations sit outside the groups because all four products need them. Users is not inside Sales, Asset library is not inside Design, and Attributes is not inside Analytics — putting a copy of each in every group is how one product becomes four.

Collapsing a group hides its modules; it doesn't change the organization, project, or data underneath. That stays the one customer context described above.

Agents run inside each product

Blu is Intempt's AI layer: your GTM workforce, made up of eight agents distributed across the four products above, not one generic assistant floating over all of them.

• Analytics - Data Analyst. The Data Analyst explains every driver and ranks fixes by dollar impact.
• Design - Creative Designer and Content Marketer. The Creative Designer generates for the person, not the audience.
• Marketing - Lifecycle Marketer, A/B Tester, and Performance Marketer. The A/B Tester experiments, the Lifecycle Marketer runs journeys.
• Sales - Outbound Prospector, Pipeline Closer, and RevOps Automator. The Outbound Prospector and Pipeline Closer handle the work between meetings.

You set the strategy in each product's modules. The agents scoped to that product run the plays.

Where to go next

• What is Intempt? for what each of the four products actually does, one level down from this page.

• Organizations & Projects for how access and roles work across organizations and projects.

• How Intempt Works for the event ingestion and real-time infrastructure the one customer context runs on.

• The Glossary for definitions of Attributes, Segments, and the other terms used throughout this page.