NoCRM

NoCRM

Action-focused lead management designed for salespeople who want to track prospects without heavyweight CRM overhead. Leads move through pipeline steps until closed. Each account lives on its own subdomain configured in the connection.

Entity Model

• Leads — the core entity. Each lead has a title, amount, status, assigned user, and current Step in a Pipeline. Leads move through steps until won, lost, or abandoned.
• Pipelines — sales funnels with ordered Steps (e.g. Contacted → Qualified → Proposal → Won). Multiple pipelines supported.
• Steps — stages within a pipeline. Each step has a name and position. Leads progress through steps linearly.
• Categories — labels for classifying leads (e.g. product line, region, source).
• Fields — custom fields defined at the account level. Applied to all leads.
• Predefined Tags — account-level tags for quick lead classification.
• Clients (Folders) — grouping mechanism for organizing leads by company/client. Each client has an id used for scoping.
• Users — team members with roles. Each lead is assigned to one user.
• Teams — groups of users for organizational structure.
• Prospecting Lists — pre-qualified prospect data imported for cold outreach. Leads are created from prospecting list rows.
• Follow-ups — reminders/tasks tied to a specific user. Require user_id to query.
• Webhooks — outbound event notifications. Webhook Events list available event types.
• Activities — predefined activity types (call, email, meeting, etc.) used when logging interactions on leads.

Workflows

1. Pipeline overview: Enumerate pipelines and steps to learn stage order, then scan leads to see volume per stage.
2. Lead lifecycle: Pull the lead directory, inspect step/status, advance the step as the deal progresses, attach follow-ups for next actions.
3. Prospecting funnel: Pull prospecting lists for source material, convert rows into leads, then slice leads by category or tag.
4. Team workload: Enumerate users first, then enumerate each seller’s follow-ups to see pending work.
5. Configuration audit: Walk custom fields, categories, tags, and activity types to understand the workspace schema.

Gotchas

• Follow-ups require user_id: Discover valid user ids from the team directory before querying reminders—follow-ups are always user-scoped.
• Limited server-side filters on big lead lists: Narrow by step or status in follow-up passes when the broad list is noisy.
• Lead amounts are optional: Not all leads have monetary values. Amount can be null.
• Webhook events: Enumerate webhook event types before creating webhook subscriptions.