April 2026
NIRAVU
Architecture Assessment

Data Pulse Solutions (DEMO)

Zoho CRM System Architecture Review

Client-facing architecture assessment prepared from the current Atlas evidence package.

Assessment date April 2026
Assessment reference ATLAS-48F0AA5F
Assessment score
51
STRUCTURAL REVIEW RECOMMENDED

Structured review advised before scaling.

Composite score across Architecture, Automation, Governance, and Reliability.

Prepared by Niravu
Zoho CRM
Table of Contents

Table of Contents

Overall Score & What It Means
Architecture Snapshot
Structural Architecture Map
Automation Concentration (Top Modules)
Access & Oversight
System Reliability
System Health, Themes & Action Plan
Appendix: Module-by-Module Details
Appendix: Field Density Detail
Overall Score & What It Means
Niravu Atlas Overall Score
51
STRUCTURAL REVIEW RECOMMENDED

Structured review advised before scaling.

Composite score explanation

Composite score across Architecture, Automation, Governance, and Reliability.

How To Interpret This Score

This is not a pass/fail score. It is a management tool for understanding where your CRM is strongest and where focused improvement is needed.

The value is in comparing strengths and weaknesses across Architecture, Automation, Governance, and Reliability.

The rest of this report explains what is driving each area, then translates those signals into priority themes and an action agenda.

Assessment Methodology

Atlas uses an intentional metadata-first methodology so leaders can evaluate system design, controls, and risk posture without exposing customer content.

This assessment is based on system metadata and configuration. We did NOT access, read, or analyze customer data, emails, notes, or transactions.

No AI Inference

Your data never passes through an AI model. The Atlas scan reads your CRM configuration and structural metadata through authenticated, read-only API connections. Every score, insight, and recommendation in this report is produced by deterministic rules-based logic — no customer data, records, emails, or notes are processed by any large language model or AI inference service, at any stage. AI-assisted analysis is available as a future opt-in capability.

  • Read-only API access
  • OAuth 2.0 authentication
  • Metadata-only analysis
  • TLS 1.2+ encryption in transit
Integration Scope

Atlas scans Zoho CRM configuration only. When integrations such as Zoho CRM or Zoho Sign surface data within CRM, Atlas assesses the CRM-visible portion of that integration. The connected applications themselves are not accessed.

Niravu Platform Context
Atlas Assessment and mapping
Pathfinder Prioritization
Navigator Execution and ongoing management
Architecture
53
What this evaluates
How the CRM is structurally designed: modules, relationships, field design, and structural alignment.
What we observed
Current structure includes 62 modules, 932 fields, 250 related lists, and 1,918 relationship edges.
How to improve
Confirm which modules are core operating systems and protect their design standards first.
Automation
20
What this evaluates
How work is executed in the system: workflows, blueprints, and automation coverage.
What we observed
Automation inventory shows 51 configured assets across 7 hotspot modules.
How to improve
Set one operating standard for automation design in high-impact modules.
Governance
85
What this evaluates
How control and ownership are managed: roles, profiles, ownership, and access clarity.
What we observed
Governance configuration includes 3 roles, 3 profiles, 7 configured users, and 3 active users.
How to improve
Assign clear executive ownership for governance standards and decision rights.
Reliability
54
What this evaluates
How dependable and recoverable the system is: backups, safeguards, and system trust.
What we observed
Backup controls currently show 0 source surfaces, 0 backup jobs, and 0 destinations.
How to improve
Confirm minimum reliability standards for backup, verification, and retention control ownership.
Architecture Snapshot

Architecture Snapshot

Architecture subscore anchor
53
Architecture
Medium

This snapshot summarizes current tenant scale and the strongest confirmed operating signals in the Atlas package.

Modules
62
Current module inventory
Fields
932
Current field footprint
Related Lists
250
Confirmed relationship-list surfaces
Graph Edges
1918
Confirmed graph relationship edges

Operational Data Scale

Operational record counts were not included for this assessment run.

Operational record counts were not included for this assessment run.

Priority Modules for Review

These modules currently show the strongest concentration of Architecture, Automation, Governance, or Reliability signals and are the highest-priority areas for review in this assessment.

Leads
Composite priority score: 65.5
Deals
Composite priority score: 62.2
Contacts
Composite priority score: 54.2
Accounts
Composite priority score: 49.0
Module inventory by type 62 total
CRM native active2235%
Integration-managed1321%
Custom-built23%
CRM native hidden610%
System framework1931%
Integration Ecosystem
Zoho Bookings1 module
Appointments

Atlas assesses the CRM-visible configuration only; Zoho Bookings itself is outside CRM scan scope by design.

Zoho Bookings1 module
Appointments Rescheduled History

Atlas assesses the CRM-visible configuration only; Zoho Bookings itself is outside CRM scan scope by design.

Calendarbookings1 module
Calendar Bookings

Atlas assesses the CRM-visible configuration only; Calendarbookings itself is outside CRM scan scope by design.

Services1 module
Services

Atlas assesses the CRM-visible configuration only; Services itself is outside CRM scan scope by design.

Zoho Finance4 modules
Invoices
Estimates
Sales Orders
Purchase Orders

Atlas assesses the CRM-visible configuration only; Zoho Finance itself is outside CRM scan scope by design.

Zoho Sign3 modules
Zoho Sign Documents
Zoho Sign Recipients
Zoho Sign Document Events

Atlas assesses the CRM-visible configuration only; Zoho Sign itself is outside CRM scan scope by design.

Intentional Architecture — Hidden Native Modules

The following native CRM modules are present but have been intentionally hidden by an administrator: Quotes, Sales Orders, Purchase Orders, Invoices, Cases, Solutions.

This is consistent with deliberate administrative decisions, not gaps or errors.This is consistent with a Zoho CRM integration — Books manages billing natively. No corrective action is required.

Structural Architecture Map

Structural Architecture Map

ENGAGEMENT / ORIGINATION Campaign ACTIVITY / COORDINATION Calls AFD 56.2% Tasks AFD 70.6% Meetings AFD 24.3% CORE CRM OPERATING MODEL Lead AFD 37.4% Contact AFD 36.7% Account AFD 29.5% Deal AFD 52.7% COMMERCIAL / DELIVERY SUPPORT Product AFD n/a Invoice AFD n/a Sales Order AFD n/a Estimate AFD n/a SPECIALIZED / ADJACENT Zoho Sign Document AFD n/a Calendar Booking Competitor Vendor Zoho Sign Recipient
Legend

Use this legend to read structural lanes, contextual module treatments, and AFD population signals in the diagram.

  • AFD (Average Field Density): shows how consistently reportable fields are populated by module.
  • AFD scope: system-required/generated fields and unsupported-count surfaces are excluded.
  • Structural lanes: operating core, adjacent domains, and broader extension layers show concentration bands.
  • Primary categories: each lane represents where operational load and dependency concentration are most visible.
  • Light-gray contextual modules show visible connected structure not promoted into the primary structural set.
  • Pale dotted modules represent hidden or disabled modules shown for structural context only.
  • Connectors represent confirmed relationship evidence included in this bounded structural view.
Structural concentration

Concentration Pattern

Structural concentration remains narrow compared with the overall module footprint.

Operating core
4
Small set of modules carries the heaviest structural load.
Lead, Contact, Deal, Account
Adjacent domain layer
12
Second tier supports commercial execution and nearby specialist workflows.
Product, Invoice, Price Book, Vendor
Broader extension layer
25
Wider tenant breadth exists at materially lower structural density.
Service, Function, Price Book, Email Analytics
Primary structural layer

Operating Core

4 modules carry the clearest operating core in the current relationship evidence.

Lead
Front-end intake hub supporting qualification and early pipeline coordination.
238 graph-edge signals
23 related lists
17 linked modules
Relationship context
Contact, Account
Revenue flow
Product
Supporting domains
Campaign
Contact
Relationship anchor connecting customer context, pipeline movement, and downstream activity.
207 graph-edge signals
22 related lists
17 linked modules
Relationship context
Lead, Account
Revenue flow
Deal, Product
Deal
Revenue workflow hub linking commercial progression, products, and supporting artifacts.
178 graph-edge signals
19 related lists
15 linked modules
Relationship context
Contact, Lead, Account
Revenue flow
Product
Account
Account context hub tying people, revenue activity, and follow-up into a shared record.
168 graph-edge signals
21 related lists
13 linked modules
Relationship context
Lead, Contact
Revenue flow
Product, Deal
Adjacent domain layer

Adjacent Business Domains

Revenue flow
Commercial lifecycle modules that sit immediately around the operating core.
3 modules represented
Product, Invoice, Price Book
Commercial support
Supporting surfaces that help pricing, vendors, and controlled documents move revenue work forward.
1 modules represented
Vendor
Supporting domains
Additional modules that reinforce the core without carrying equal structural weight.
8 modules represented
Zoho Sign Document, Campaign, Zoho Sign Recipient, Service, Function
Shared infrastructure

Shared Connective Infrastructure

Collaboration and documents
Shared notes, attachments, and communication surfaces preserve context across customer and commercial workflows.
Note
Attachment
Most visible across Lead, Contact, Account pathways.
Activity coordination
Meetings, tasks, calls, and related activity layers extend follow-up across the operating core.
Meeting
Task
Call
Most visible across Lead, Contact, Account pathways.
Execution support
Checklist-style surfaces add lightweight execution support around adjacent workflows.
Checklists
Most visible across Lead, Contact, Account pathways.
Structural implication

Takeaway

This tenant is structurally centered on relationship and revenue workflows, with adjacent commercial support domains and shared activity and document infrastructure extending those processes across the broader CRM.

Integration Ecosystem

The following third-party and cross-platform integrations expose modules into the CRM. Each integration adds configuration surface that Atlas cannot fully inspect — only the CRM-visible footprint is shown.

Zoho BookingsActive integration1 CRM-visible module
Appointments
No record count

Atlas assesses the CRM-visible configuration only. Zoho Bookings itself is outside CRM scan scope — these modules represent the CRM integration surface only.

Zoho BookingsActive integration1 CRM-visible module
Appointments Rescheduled History
No record count

Atlas assesses the CRM-visible configuration only. Zoho Bookings itself is outside CRM scan scope — these modules represent the CRM integration surface only.

CalendarbookingsActive integration1 CRM-visible module
Calendar Bookings
No record count

Atlas assesses the CRM-visible configuration only. Calendarbookings itself is outside CRM scan scope — these modules represent the CRM integration surface only.

ServicesActive integration1 CRM-visible module
Services
No record count

Atlas assesses the CRM-visible configuration only. Services itself is outside CRM scan scope — these modules represent the CRM integration surface only.

Zoho FinanceActive integration4 CRM-visible modules
Invoices
No record count
Estimates
No record count
Sales Orders
No record count
Purchase Orders
No record count

Atlas assesses the CRM-visible configuration only. Zoho Finance itself is outside CRM scan scope — these modules represent the CRM integration surface only.

Zoho SignActive integration3 CRM-visible modules
Zoho Sign Documents
No record count
Zoho Sign Recipients
No record count
Zoho Sign Document Events
No record count

Atlas assesses the CRM-visible configuration only. Zoho Sign itself is outside CRM scan scope — these modules represent the CRM integration surface only.

Automation Concentration (Top Modules)

Automation Concentration (Top Modules)

Automation subscore anchor
20
Automation
Low

Top modules by automation volume based on 51 extracted automation assets.

Automation Distribution by Module

Leads
15
Deals
12
Contacts
8
Accounts
3
Zoho Sign Documents
3
Calls
1
Tasks
1
Leads
Total automation assets: 15
Automation mix
Workflows3
Assignment Rules1
Notification Rules3
Email Templates5
Blueprints1
Custom Buttons2
Deals
Total automation assets: 12
Automation mix
Workflows5
Notification Rules2
Email Templates3
Custom Buttons2
Contacts
Total automation assets: 8
Automation mix
Workflows1
Notification Rules1
Email Templates4
Custom Buttons2
Accounts
Total automation assets: 3
Automation mix
Email Templates1
Custom Buttons2
Zoho Sign Documents
Total automation assets: 3
Automation mix
Workflows2
Custom Buttons1
Calls
Total automation assets: 1
Automation mix
Validation Rules1
Tasks
Total automation assets: 1
Automation mix
Blueprints1
Workflow Execution Health

2 active workflows are dormant (null or >90-day execution gap)

Workflow NameStatusLast Executed
Big Deal RuleActive2025-11-21 ⚠ Dormant
Email - Assigned to SalesActive2026-03-06
Send Welcome Email when a Contact is createdActive2026-02-26
Update Quote BA Sent Date FieldActive2026-01-09
Email - Assigned to CTOActive2026-03-03
Populate_Account_Product_Name_in_DealNameActive2026-01-08 ⚠ Dormant
Update Quote BA Signed field in QuotesActive2026-01-09
SEND NDAActive2026-03-05
Lead Assignment - No Interest ListedActive2026-03-03
Update Deal NameActive2026-02-26
When a Deal is closed send a notificationActive2026-03-05
Custom Function Audit
⚠ 8 custom functions are active but source code is not accessible to Atlas — no documented audit trail available.
Update Deal NameNot availableSource not accessible
Update Deal in Sign DocumentNot availableSource not accessible
Update Quote TotalNot availableSource not accessible
Update Quote Signed Field in QuotesNot availableSource not accessible
Update Quote BA Sent FieldNot availableSource not accessible
Populate Deal Name in Subject Quote CreationNot availableSource not accessible
SEND NDANot availableSource not accessible
Populate_Account_Product_Name_In_DealNameNot availableSource not accessible
Access & Oversight

Access & Oversight

Governance subscore anchor
85
Governance
High
Users
7
Configured user records
Roles
3
Role configuration inventory
Profiles
3
Profile configuration inventory
Active users
3
Active status in current system configuration

Access Configuration Distribution

Active users
3
Inactive users
4
Administrative access
5

Role Distribution

Sales
1 users
CEO
6 users

Profile Distribution

Sales Team
1 users
Administrator
5 users
SupportProfileInternal
1 users
User Access Register
⚠ 4 of 4 inactive users retain elevated role or profile assignments — privilege persistence risk.
⚠ 1 active admin account uses non-company email domain — identity verification risk.
NameRoleProfileStatusEmail DomainRisk Flags
Pam AdamsSalesSales TeamActivedatapulsesol.com
Samantha LeeCEOAdministratorActivedatapulsesol.comConfirmed admin
Maya ChenCEOAdministratorDisableddatapulsesol.comPrivilege persistence
Jordan BlakeCEOAdministratorDisableddatapulsesol.comPrivilege persistence
Carlos RamirezCEOAdministratorDisableddatapulsesol.comPrivilege persistence
Shehryar YousaffCEOAdministratorActivegmail.comConfirmed admin Non-company email
Zoho Support UserCEOSupportProfileInternalDisabledzohocrmusersupport.comPrivilege persistence
System Reliability

System Reliability

Reliability subscore anchor
54
Reliability
Medium

Reliability signals are anchored in backup control metadata and supplemented by recoverability, verification, retention, and operational-confidence signals.

Backup controls were identified, but no schedule/run/catalog records were present for this tenant.

Source surfaces
0
Systems with backup control evidence
Backup jobs
0
Configured scheduled jobs
Destinations
0
Configured or runtime-observed destinations
Execution records
0
Observed run or catalog execution records
Verification records
0
Catalog validation records
Retention policies
0
Explicit retention policy records
No authoritative backup topology mappings were observed for this tenant.

Backup Coverage and Verification Status

Unknown-state mapping counts are not applicable because no authoritative mappings were evaluable.
No backup schedule, run, or catalog records were found for this tenant in the control DB.
System Health, Themes & Action Plan

System Health, Themes & Action Plan

Leadership briefing: this section consolidates the current operating posture, key decisions, strategic themes, and sequenced actions in one view.
Data Quality Spotlight
18%
Lead Attribution Health
Contacts · Lead_Source
Attribution breaks at lead-to-contact conversion if low
0%
Pipeline Visibility
Deals · Reason_For_Loss__s
Win/loss analysis not possible if 0%
5%
Call Outcome Capture
Calls · Call_Result
Calls logged but outcomes not captured if low
Critical Field Population Gaps

The following business-critical fields are below the 20% population threshold on core modules. These gaps affect attribution, forecasting, and reporting accuracy.

Contacts · Lead_Source18% populated
Lead Source
Attribution breaks at lead-to-contact conversion — marketing ROI cannot be calculated.
Deals · Reason_For_Loss__s0% populated
Reason for Loss
Win/loss analysis is not possible — pipeline improvement decisions lack evidence.
Calls · Call_Result5% populated
Call Outcome
Calls are logged but outcomes are not captured — activity quality cannot be measured.
Accounts · Account_Type2% populated
Account Type
Segmentation and targeting are not possible without account type classification.

What we are seeing

Architecture concentration
Core dependencies currently center on Lead, Contact, Deal, Account.
Automation concentration
Leads carries 15 automation assets in the current package.
Governance clarity
Control structures currently include 3 roles and 3 profiles.
Top Structural + Operational Risks
  • Ownership boundaries and decision accountability require clearer alignment across teams.
  • Core module dependencies remain concentrated, so changes in priority modules can ripple broadly.
  • Execution dependencies are overlapping across architecture, automation, governance, and reliability surfaces.

Top decisions

Decision 1

Clarify which modules should remain core operating systems versus supporting records.

Decision 2

Confirm who owns governance and reliability controls across business and system leadership.

Decision 3

Decide where automation should be standardized versus reduced to protect execution quality.

Key themes

Key relationship mappings must be confirmed before structural changes proceed
Risk Thememedium confidencemedium severity

Complete validation for the 247 unresolved relationship mappings and approve canonical link definitions before structural changes proceed.

Leadership focusApprove the dependency model for core modules before schema changes.
Automation is concentrated in a small set of modules
Risk Themehigh confidencemedium severity

Standardize automation design in Contacts, Deals, Accounts, and Leads and retire overlapping buttons and templates.

Leadership focusAdopt one trigger and exception standard for priority workflows.
Architecture operating alignment
Risk Themehigh confidencemedium severity

Schema boundaries are not explicit enough, which raises conflict risk during coordinated releases.

Leadership focusSet hard change gates for high-impact relationships.
Ownership boundaries across systems require clarification
Risk Themehigh confidencehigh severity

Define ownership and synchronization boundaries for crm invoices vs books invoices across systems before additional integration changes.

Leadership focusSet mandatory restore-testing cadence and recovery pass criteria.
Key structural dependencies must be confirmed before structural changes proceed
Risk Themehigh confidencemedium severity

Execution and verification records must be confirmed to support dependable backup commitments.

Leadership focusApprove minimum verification and retention controls for all backup sources.

Action plan

Actions are sequenced for near-term execution first, followed by targeted validation steps.

High-Confidence Actions

Prioritized actions are ordered for immediate execution based on business impact and confidence.

Action 1
Access configuration is concentrated in one role profile

Rebalance role assignments to reduce concentration in the 'CEO' cohort and distribute control coverage across roles.

Suggested owner: Executive Sponsor | Suggested timing: Next | Theme area: Governance | Evidence confidence: high
Action 2
Automation is concentrated in a small set of modules

Standardize automation design in Contacts, Deals, Accounts, and Leads and retire overlapping buttons and templates.

Suggested owner: Revenue Operations | Suggested timing: Next | Theme area: Automation | Evidence confidence: high
Action 3
Automation.custom buttons has repeated extraction limits

Resolve repeated extraction failures for automation; custom buttons under CUSTOM BUTTONS FETCH FAILED and rerun coverage validation.

Suggested owner: Operations Lead | Suggested timing: Next | Theme area: Reliability | Evidence confidence: high
Action 4
Cross module relationship structure is dense

Sequence structural changes through an impact review of 212 inter-module links and 250 related-list surfaces before rollout.

Suggested owner: System Owner | Suggested timing: Next | Theme area: Architecture | Evidence confidence: high
Action 5
Key structural dependencies must be confirmed before structural changes proceed

Resolve the 19 missing relationship targets to stabilize structural integrity and downstream automation behavior.

Suggested owner: Operations Lead | Suggested timing: Next | Theme area: Reliability | Evidence confidence: high

Further Investigation

Confirm investigation items before broader rollout commitments.

Action 6
Administrative access indicators appear broadly distributed

Rationalize administrative access distribution across users and enforce explicit approval criteria for elevated privileges.

Suggested owner: Executive Sponsor | Suggested timing: Next | Theme area: Governance | Evidence confidence: medium
Action 7
Key relationship mappings must be confirmed before structural changes proceed

Validate related-list link definitions and resolve unmatched mappings.

Suggested owner: System Owner | Suggested timing: Next | Theme area: Architecture | Evidence confidence: medium
Appendix

Module-by-Module Details

Module-by-module details summarize observable metadata for each major module: structural links, automation assets, communication assets, and role-level ownership patterns.

Leads

Structure
Related lists
  • Notes
  • Calls
  • Events
  • Tasks
  • ChronologicalView
  • ChronologicalView History
  • Calls History
  • Tasks History
  • Events History
  • Emails
Automation
Workflow rules
  • Email - Assigned to Sales
  • Email - Assigned to CTO
  • Lead Assignment - No Interest Listed
Blueprints
  • Lead nurturing process
Assignment rules
  • New Lead Assignment
Communication Assets
Email templates
  • Form Submission Outreach
  • Chat Submission Outreach
  • Cold Call Outreach Email
  • Lead Assignment
  • Leads Zoho Sign Template
Ownership Signals
Role-level baseline ownership pattern (system-wide)
  • CEO: 85.7%
  • Sales: 14.3%

Deals

Structure
Related lists
  • Notes
  • Attachments
  • ChronologicalView
  • Calls
  • Events
  • Tasks
  • ChronologicalView History
  • Calls History
  • Events History
  • Tasks History
Automation
Workflow rules
  • Big Deal Rule
  • Populate_Account_Product_Name_in_DealName
  • SEND NDA
  • Update Deal Name
  • When a Deal is closed send a notification
Blueprints
No blueprints present.
Assignment rules
No assignment rules captured.
Communication Assets
Email templates
  • Deal Closed - Assign Mgr
  • Deals Zoho Sign Template
  • Big Deal Alert
Ownership Signals
Role-level baseline ownership pattern (system-wide)
  • CEO: 85.7%
  • Sales: 14.3%

Contacts

Structure
Related lists
  • Notes
  • Attachments
  • Open Appointments
  • ChronologicalView
  • Calls
  • Events
  • Tasks
  • Appointments History
  • ChronologicalView History
  • Tasks History
Automation
Workflow rules
  • Send Welcome Email when a Contact is created
Blueprints
No blueprints present.
Assignment rules
No assignment rules captured.
Communication Assets
Email templates
  • Reconnecting with Contact
  • Welcome Email
  • Test Template
  • Contacts Zoho Sign Template
Ownership Signals
Role-level baseline ownership pattern (system-wide)
  • CEO: 85.7%
  • Sales: 14.3%

Accounts

Structure
Related lists
  • Notes
  • Attachments
  • ChronologicalView
  • Calls
  • Events
  • Tasks
  • ChronologicalView History
  • Calls History
  • Events History
  • Tasks History
Automation
Workflow rules
No workflow rules captured.
Blueprints
No blueprints present.
Assignment rules
No assignment rules captured.
Communication Assets
Email templates
  • Account Zoho Sign Template
Ownership Signals
Role-level baseline ownership pattern (system-wide)
  • CEO: 85.7%
  • Sales: 14.3%

Zoho Sign Documents

Structure
Related lists
  • Notes
  • Attachments
  • Emails
  • Tasks
  • Events
  • Calls
  • Tasks History
  • Events History
  • Calls History
  • CheckLists
Automation
Workflow rules
  • Update Quote BA Sent Date Field
  • Update Quote BA Signed field in Quotes
Blueprints
No blueprints present.
Assignment rules
No assignment rules captured.
Communication Assets
Email templates
No email templates linked.
Ownership Signals
Role-level baseline ownership pattern (system-wide)
  • CEO: 85.7%
  • Sales: 14.3%
Appendix

Field Density Detail

Module-level field density detail derived from the canonical artifact normalized/analysis/field_density_by_module.json. Observed fields only.

Account

51 records
AFD 29.5%
Field LabelDensity (%)
Ownership0.0%
Parent Account0.0%
Shipping Country0.0%
SIC Code0.0%
Tag0.0%
Account Type2.0%
Employees2.0%
Shipping City2.0%
Shipping Code2.0%
Shipping State2.0%
Shipping Street2.0%
Description5.9%
Field LabelDensity (%)
Annual Revenue7.8%
Billing Country13.7%
Billing City21.6%
Billing Code21.6%
Billing Street21.6%
Change Log Time56.9%
Industry62.7%
Website62.7%
Billing State74.5%
Phone80.4%
Last Activity Time96.1%
Account Number100.0%

Account

51 recordsContinued
AFD 29.5%
Field LabelDensity (%)
Locked100.0%
Field LabelDensity (%)

Call

20 records
AFD 56.2%
Field LabelDensity (%)
Caller ID0.0%
Dialled Number0.0%
Tag0.0%
Call Result5.0%
Description5.0%
Call Duration (in seconds)35.0%
Contact Name55.0%
Last Activity Time55.0%
Field LabelDensity (%)
Reminder65.0%
Call Agenda90.0%
Related To90.0%
Call Purpose100.0%
CTI Entry100.0%
Outgoing Call Status100.0%
Scheduled in CRM100.0%
Subject100.0%

Contact

131 records
AFD 36.7%
Field LabelDensity (%)
Description0.0%
Other Street0.0%
Other Zip0.0%
Secondary Email0.0%
Tag0.0%
Other City0.8%
Other Country0.8%
Other State0.8%
Salutation2.3%
Mobile3.1%
Mailing Zip3.8%
Mailing Street4.6%
Field LabelDensity (%)
Mailing Country5.3%
Mailing City6.9%
Mailing State9.2%
Lead Source18.3%
Title84.0%
Phone89.3%
Last Activity Time96.2%
Account Name96.9%
First Name97.7%
Layout98.5%
Email100.0%
Email Opt Out100.0%

Contact

131 recordsContinued
AFD 36.7%
Field LabelDensity (%)
Full Name100.0%
Field LabelDensity (%)

Deal

77 records
AFD 52.7%
Field LabelDensity (%)
Reason For Loss0.0%
Tag0.0%
Next Step1.3%
Description2.6%
Type7.8%
BA/Quote Sent10.4%
BA/Quote Signed11.7%
NDA Signed16.9%
Quote Total19.5%
Service22.1%
Lead Conversion Time24.7%
NDA Sent36.4%
Field LabelDensity (%)
Lead Source67.5%
Contact Name87.0%
Change Log Time88.3%
Product88.3%
Amount89.6%
Expected Revenue89.6%
Account Name100.0%
Last Activity Time100.0%
Locked100.0%
Overall Sales Duration100.0%
Probability (%)100.0%
Sales Cycle Duration100.0%

Lead

86 records
AFD 37.4%
Field LabelDensity (%)
Annual Revenue0.0%
Description0.0%
Salutation0.0%
Secondary Email0.0%
Tag0.0%
No. of Employees1.2%
Mobile2.3%
Website2.3%
Industry3.5%
Street5.8%
Zip Code5.8%
Title11.6%
Field LabelDensity (%)
Country16.3%
City22.1%
State30.2%
Interested In Products53.5%
Phone58.1%
Company72.1%
Lead Status72.1%
Last Activity Time84.9%
First Name96.5%
Lead Source97.7%
Email98.8%
Email Opt Out100.0%

Lead

86 recordsContinued
AFD 37.4%
Field LabelDensity (%)
Full Name100.0%
Field LabelDensity (%)

Meeting

53 records
AFD 24.3%
Field LabelDensity (%)
Check-In Address0.0%
Check-In City0.0%
Check-In Comment0.0%
Check-In Country0.0%
Check-In State0.0%
Check-In Sub-Locality0.0%
Check-In Time0.0%
Latitude0.0%
Longitude0.0%
Participants0.0%
Tag0.0%
Field LabelDensity (%)
Zip Code0.0%
Location1.9%
Online Meeting External UUID22.6%
Provider22.6%
Contact Name35.8%
Description62.3%
Last Activity Time75.5%
Related To90.6%
All day100.0%
Checked In Status100.0%

Task

111 records
AFD 70.6%
Field LabelDensity (%)
Tag0.0%
Contact Name24.3%
Description25.2%
Closed Time44.1%
Last Activity Time85.6%
Related To97.3%
Field LabelDensity (%)
Due Date100.0%
Locked100.0%
Priority100.0%
Send Notification Email100.0%
Status100.0%
Prepared by Niravu

Your CRM architecture is now mapped.

Next Steps
What this assessment represents
The first architectural map of the CRM
A baseline for system improvement
A foundation for future optimization
Assessment reference: ATLAS-48F0AA5F
Assessment date: April 09, 2026
Next Steps
Implement changes
Run Atlas again
Repeat
Niravu journey

Atlas provides the evidence map; use this report to guide prioritization and execution with confidence.