CRM

CRM - Pedro tracks who the team works with, what happened in each contact, what was proposed and what should happen next. Shared identities stay in Core; offers come from Products & Services; external accounts come from Tooling and Access.

Arrows show data use, not automatic actions.

Start here

Your task	Guide
Work a lead through to a decision	Complete the sales cycle
Log a call or meeting and plan the next action	Log contact
Propose an offer and close a deal	Manage deals
Enroll and attribute campaign work	Manage campaigns
Route Cal.com bookings to a seller	Onboard a seller
Check the pipeline and totals	Review the pipeline

Choose the right surface

Open Data in CRM - Pedro. Work in table views: grid intakes collect and validate inputs, operational queues show the next action, and reference views let you find records after they leave an intake. Airtable Interfaces are outside this operating model.

Intakes and checks explains how records advance. Data views links every available view.

What is verified

The reference covers the 20 current tables and 375 fields as of 2026-11-04, the 70 Data views inventoried on 2026-10-28 that still exist, three native automations and the Cal.com Booking Intake workflow in n8n. Mirrors explain local use and link to the owning domain. Screenshots show existing fictitious records and real empty queues.

Since 2026-10-21 the base changed in three ways. The Universal Tags rollout of 2026-10-22 gave every table an optional Tags link to the shared catalog, adding 26 columns. Interaction gained the calendar view Verena - Cal.com, and Seo Companies was renamed SEO Companies. No formula, link target, intake view or automation changed until 2026-11-03, when the Tasks table was added. On 2026-11-04 Relationship lost Due date*, Task°, the Follow-up formula and Intake Step step 3, and the Cal.com flow stopped writing to Relationship. The same day a lead became a Deal at stage Lead: Deal gained Company°, People°, Source° and Legacy Relationship ID and the stage Meeting Scheduled, Interaction gained People° and Company°, the Relationship rows were migrated to Deals, and the Cal.com flow began to create or advance a Deal. Later that day the Relationship table was deleted, with its two automations and the 17 fields in other tables that pointed to it.

Campaign enrollment is currently manual. The native next-contact copy automation no longer exists; next actions are Tasks. See known gaps before relying on automatic follow-up, deduplication or campaign routing.

The v1 scope was closed on 2026-10-21 with manual enrollment and attribution: the seller links each campaign Deal to its campaign in Campaign° (its Interactions follow through Deal°), records the next action and reviews the portfolio. Existing Cal.com capture remains; automatic Campaign routing, sequences, targets, dashboards and Interfaces are deferred. The Offer linked to the Deal and manual outcome reconciliation meet the initial scope.

The first controlled pilot ran on October 21, 2026: 12 of 17 cases passed in the technical sample and 5 remain blocked for full acceptance. New/existing capture, manual attribution, replay, rescheduling and cancellation were verified; proposals and won/lost outcomes were simulated. Real campaign readiness, a controlled meeting and independent review, and unmapped-source capture still need validation. Test bookings were cancelled and test records closed. Facts without dedicated fields need explicit, reviewable manual records; essential failures require correction and retesting before acceptance. Scope closure is not operational certification. On 2026-10-28 the homologation was still pending: the Work Item “Sign off CRM v1 manual operation (homologation)” waits on cases P01, P05, P15, P16 and P17 and on the reviewer check. Known gaps lists the open Work Items.