Please sign in with Google to access the platform.
Access Pending
Your access to Sales CRM is pending admin approval.
Please contact Satdeep or Lakshya to activate your account.
UndrAds Sales
🔔0
Active RemindersClear All
No active reminders.
0 Leads
Lead
Total: $0 | W: $0
Connection Made
Total: $0 | W: $0
Proposal Sent
Total: $0 | W: $0
Agreement Sent
Total: $0 | W: $0
Churned (Sales)
Total: $0 | W: $0
Onboarding Requisite
Total: $0 | W: $0
Onboarding
Total: $0 | W: $0
Live Unstable
Total: $0 | W: $0
Live Stable
Total: $0 | W: $0
Churned (Ops)
Total: $0 | W: $0
Sales Analytics
Active Deals
0
Total Pipeline
$0
Expected Rev
$0
Closed Won
$0
Win Rate %
0%
Activity Volume (This Month)
Leads Created
0
Publishers Added
0
Contacts (POCs) Created
0
Meetings Booked
0
Deals count by Stage
Pipeline Value ($) by Stage
Deal Status (Win / Loss Ratio)
Deals by Product Type
Salespeople Performance
Salesperson
Active Deals
Meetings (Month)
Leads (Month)
Pubs (Month)
POCs (Month)
Closed Won Value
Business Directory
Manage company profiles and points of contact
Company Name
Owner
Phone
Website
LinkedIn
Downloads (Monthly)
Contact Name
Company
Title / Role
Email
Mobile Phone
Telegram / Zalo
Frequently Asked Questions (FAQ)
Everything you need to know about the UndrAds Sales CRM platform
📋 Form & Mandatory Fields
What fields are required to create a Publisher (Company)?
To register a new company/publisher profile, the following fields are strictly mandatory:
Company Name: The official name of the publisher.
Owner: The salesperson responsible for managing this publisher.
Website: The primary domain URL (e.g., publisher.com). Note: The website domain must be unique; duplicates are not allowed.
Primary Contact (POC): A Point of Contact must be associated with the publisher. If no POC exists, you can click + New to create one inline.
Game HQ (Country/City): The physical headquarters location of the publisher.
All other fields (such as phone, LinkedIn, App Store/Play Store URLs, billing address, etc.) are optional.
What fields are required to create a Point of Contact (POC)?
To register a contact person, the following fields are mandatory:
First Name & Last Name: The contact's full name.
Title / Role: The job role or title (e.g., Ad Ops Director or UA Manager).
Owner: The salesperson who owns the contact relationship.
You can optionally link a POC to an existing Publisher. Other contact coordinates (Email, Mobile, LinkedIn, Telegram, Zalo, Teams, mailing address) are optional but highly recommended.
What fields are required to create a Deal / Lead?
To register a new sales opportunity (lead/deal) on the Kanban pipeline, the following fields are mandatory:
Deal Name: A descriptive title for the deal.
Owner: The salesperson running the deal.
Publisher / Company: The associated company (select from registered publishers).
Amount ($): The gross deal amount/value.
Closing Date: The anticipated target date for closing the deal.
Stage: The current step in the pipeline (defaults to Lead).
Product: The monetization product (select from Applovin MAX, AdMob Adapter, H5 AdX, Website AdX, Website HB, Video VAST).
Note: If you set the stage to Onboarding, all Ops Onboarding fields (Child Network Code, MCM Email, Revshare %, and Communication Channel) also become mandatory to push the card.
⚡ Automated Pipeline Workflows
How does the automatic creation of cards in the Onboarding pipeline work?
Moving a lead to the Onboarding stage automatically triggers a backend transition that creates a corresponding card in the Ops Onboarding board. Here is how it functions under the hood:
Stage Trigger: When you drag a card to Onboarding in the Sales pipeline (or set its stage in the edit dialog), you will be prompted to enter additional onboarding parameters (Child Network Code, MCM Email, Revshare %, and Communication Channel).
Database Hook: A Firestore database Cloud Function trigger runs on the backend. It verifies that the lead's stage is transitioning to onboarding and that onboardingCreated is falsy.
Naming Convention: The new card created on the Ops Onboarding Kanban board is automatically named after the Publisher Name (e.g., Gaming Hub) to keep operational tasks publisher-centric. If the publisher name is missing, it falls back to the App Name, then the Deal Name.
Audit Trail:
A system comment is automatically appended in the Ops Onboarding account comments history: 🤖 System: Automatically created from Sales Lead "[Deal Name]" (App: "[App Name]") (Owner: [Owner Email]).
A corresponding system comment is created in the Sales Lead: 🤖 System: Lead reached Onboarding. Created onboarding card "[Publisher Name]" in Ops Pipeline..
Linking & Flags: The Sales Lead is updated with onboardingCreated: true and onboardingAccountId: [OpsCardId] to prevent duplicate creation.
Deletion Recovery: If the operational onboarding card is deleted on the Ops board, a deletion trigger resets the lead flags in the Sales CRM (sets onboardingCreated: false, clears the ID, and adds a comment notifying the sales team) so it can be pushed again if needed.
🔌 LinkedIn Chrome Extension
What is the LinkedIn Tracker Chrome Extension?
The Undrads CRM LinkedIn Tracker (v1.3.0) is a custom-built Chrome extension that integrates your LinkedIn outreach messages and InMails directly with the Sales CRM. It scans active messaging windows on LinkedIn and automatically archives matching client touchpoints under the corresponding Sales Lead in Firestore.
How to install and set up the LinkedIn Chrome Extension?
Follow these simple steps to install and activate the extension on your computer:
Download the Extension: Click the button below to download the extension ZIP archive. Save it to your computer. ⬇️ Download LinkedIn Extension
Extract the files: Locate the downloaded chrome-extension.zip and extract its contents into a dedicated folder (e.g., a folder named Undrads-Extension).
Open Extensions page: Open Google Chrome and navigate to chrome://extensions/ in your address bar.
Enable Developer Mode: Toggle the Developer mode switch in the upper-right corner of the Extensions page.
Load Unpacked: Click the Load unpacked button that appears in the upper-left corner.
Select Folder: Browse and select the extracted folder (the one containing manifest.json). The extension will install immediately.
Log In / Handshake: Keep your Undrads CRM web tab open. The extension will automatically handshake with the tab, capture your auth credentials, and update its sync credentials in the background.
Once installed, whenever you converse on LinkedIn with a point of contact whose profile URL matches a POC in the CRM database, a floating overlay (Undrads CRM Sync) will appear in the bottom-right of LinkedIn, showing whether the profile is matched, and automatically syncing chat history to the lead's communication timeline.
🔌 Model Context Protocol (MCP) Server
What is the CRM MCP Server?
The Model Context Protocol (MCP) server connects the CRM database directly to AI coding tools and assistants (such as Cursor, Roo Code, Cline, or Claude Desktop). This allows AI assistants in your IDE to safely fetch leads, update stages, add notes, and perform bulk operations on the CRM database on your behalf.
What tools are available via the MCP server?
The undrads-crm MCP server exposes 10 tools to AI agents:
list_leads: Lists and filters all deals/leads in the database. Supports pagination and desc sorting.
list_publishers: Lists all publishers (companies) in the database with sorting and pagination.
list_pocs: Lists all Points of Contact (POCs) in the database with sorting and pagination.
update_lead_stage: Updates a deal's stage (e.g., to connection-made, onboarding) and writes a system audit trace.
add_deal_remark: Appends text notes to a lead's history.
search_publishers: Searches publishers by name or domain.
search_pocs: Searches contacts by name or email.
create_publisher: Creates a new publisher with website/location validation.
create_poc: Creates a point of contact.
create_lead: Creates a new opportunity card on the board.
How do I connect Claude Desktop or Cursor to the MCP server?
To configure your AI client, click the 🔌 MCP button in the CRM top header. This displays a setup modal containing tailored configuration scripts and copyable commands for Claude Desktop, Cursor, and Roo Code/Cline, as well as raw SSE connection URLs.
📊 CRM Snapshot
How does the CRM Snapshot work?
The CRM Snapshot is a dynamic historical analysis tool accessible via the 📊 CRM Snapshot... dropdown in the top header of the Pipeline. It allows you to select any month in the last year to inspect pipeline performance for that period:
Active Leads Identification: The system automatically extracts all deals that were either created in that month, updated in that month, or had a closing date within that month.
Won / Lost Metrics: By analyzing stage transition audit trails in lead comments, it categorizes leads into:
New Leads: Deals created during that calendar month.
Closed Won: Deals that transitioned to onboarding, live-unstable, or live-stable in that month.
Closed Lost: Deals that transitioned to churned-sales or churned-ops in that month.
Audit Timeline: Aggregates all transition audit comments (e.g., assignee movements) in chronological order for that month.
Salesperson Filter: Filters the entire snapshot view to display metrics and lists for a specific salesperson.
🔍 Search & Sort Operations
What search and sort options are available in the Pipeline view?
The main Pipeline board supports the following filters and ordering controls:
Salesperson Filter: Select a team member to only show deals assigned to them.
Search Bar: Type keywords in the search bar. It performs a case-insensitive check matching your query against:
Deal Name
App Name
Associated Publisher (Company) Name
Sorting options:
Sort: Created Date (Default: descending, newest leads first).
Sort: Alphabetical (A-Z by Deal Name).
Sort: Closing Date (Ascending, earliest closing dates first).
This CRM includes a Model Context Protocol (MCP) server that is fully cloud-hosted. It enables AI assistants (like Claude or Antigravity) to view and modify the CRM database securely over HTTPS using SSE (Server-Sent Events) with zero local files or keys required.
1. Select Your AI Tool
2. Setup Instructions
Connect your Antigravity IDE to the cloud CRM database:
1Open your Manage MCPs tab in Antigravity
2Click View raw config at the top
3Paste the following JSON block under mcpServers
💡 No Node.js or proxy required — Antigravity connects directly over HTTPS.
2. System Requirements
Node.js (v18+) is required on your machine to run the client-side proxy wrapper (mcp-remote). Download it from: nodejs.org.
3. Installation Method
Choose your operating system, copy the command, paste it into your Terminal/PowerShell, and press Enter:
Open your Claude Desktop configuration file and append the following configuration:
💡 Windows Store Users: If you installed Claude from the Microsoft Store, the config is at: %USERPROFILE%\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json
🔄 After installing, completely Restart Claude Desktop for the changes to take effect.
2. Setup Instructions
Connect Cursor Editor to the cloud CRM database:
1Go to Cursor Settings → Features → MCP
2Click + Add New MCP Server
3Set Name to undrads-crm, Type to command, and paste this command:
⚠️ Requires Node.js v18+ installed. Download from nodejs.org.
2. Setup Instructions
Connect Roo Code / Cline (VS Code Extension) to the cloud CRM database:
1Open the MCP panel (plug icon 🔌 in the VS Code sidebar)
2Click the gear ⚙️ icon to edit mcpSettings.json
3Paste the following JSON block under mcpServers
💡 Connects directly via SSE — no Node.js proxy required.
2. Connection URL
For any other SSE-compatible AI agent or MCP client, use this direct connection URL:
🔗 This is a standard Streamable HTTP endpoint. Configure your client to connect to this URL using its MCP/SSE settings.
Once connected, the AI assistant automatically learns and can call the following 8 tools in the CRM database. Here is how you can use them step-by-step:
🔍 1. List & Inspect Deals (list_leads)
Lists opportunities in your sales funnel. You can filter by stage (e.g. lead, proposal-sent, onboarding, live-stable).
Try asking: "Show me all the deals that are currently in the connection-made stage."
🚀 2. Move / Update Deal Stage (update_lead_stage)
Moves a deal to a new stage and leaves a system audit trail. If moving to churned stages, a reason is required.
Try asking: "Move lead 'XYZ Game App' to onboarding" OR "Mark XYZ as churned-sales because they decided to develop in-house."
💬 3. Add Remarks / Notes (add_deal_remark)
Appends a note or status update to the activity timeline of a specific deal.
Try asking: "Add a remark to XYZ saying the client requested a follow-up demo next Wednesday at 2pm."
🏢 4. Find Publisher Details (search_publishers)
Searches for registered companies/publishers in the database by name or website domain.
Try asking: "Find publisher records for company 'Gaming Hub' or search for 'hub.com'."
👤 5. Find Contact Details (search_pocs)
Searches for Point of Contacts (POCs) in the database by first name, last name, or email address.
Try asking: "Find contact details for 'John Doe' or search for contacts with email 'test.com'."
➕ 6. Create Company/Publisher (create_publisher)
Registers a new publisher. Validates website domain to prevent duplicates. App Store and Play Store URLs are completely optional.
Try asking: "Create a publisher named Skyward Games, website skywardgames.com, based in London, and primary POC ID 'BhJQgztKKDychxpGR2PJ'."
👤 7. Create Point of Contact (create_poc)
Registers a contact person/POC and links them optionally to a publisher. Note that the contact's job title/role is required.
Try asking: "Create a contact John Doe (Ad Ops Director) with email john@skywardgames.com for Skyward Games."
📊 8. Create Deal / Lead (create_lead)
Creates a new deal on the Kanban board with pricing, closing dates, product type, and default system audit logs.
Try asking: "Create a lead called 'Skyward SDK Integration', for publisher ID 'Vnpa3AnCt4K35yMiLl1I', worth $12000, closing date 2026-07-15, product 'Applovin MAX'."
🧪 9. Testing Your Connection
Once the status shows Enabled in the IDE and all green toggles are active, ask your AI Coding Assistant in the chat window to test the connection:
Try asking: "Please use the undrads-crm list_leads tool to verify the connection and show me the first 2 leads."
