Customer Relationship Management

Contacts, companies, deals, pipelines, activities, tasks, and — depending on the product — email campaigns and reporting.

For teams already living in a CRM with configured pipelines and reports, replacement is disruptive. The Forge can consume the CRM's customer and pipeline state so operations, communication, and billing work off the same record — or, for teams whose CRM has become an over-priced contact list, The Forge can absorb the CRM's function entirely.

• Contacts and companies with source attribution
• Deals and pipeline stage
• Activities and notes
• Owner assignments
• Custom fields where mapped

• Won-deal handoffs to operations
• Communication events (calls, SMS, email) attached to the contact
• Job / project status back to the deal
• Revenue back to the deal for attribution

• Deal won
• Deal stage changed
• New contact received from an intake source
• Owner reassigned
• Activity logged

• Copying won deals into a scheduling or job system
• Sending updates to the CRM after operations finishes
• Duplicating contact records across sales, operations, and billing
• Maintaining separate follow-up lists

• Sales and marketing leader
• Owner / executive
• Operations manager
• Office administrator

• Deals won by source, campaign, or referral
• Revenue delivered vs. deal amount won
• Time from deal-won to work-started
• Rep-level operational conversion

• Standard OAuth against the CRM.
• Read scope requested by default; write scope only where the customer opts in.
• Deleted contacts in the CRM are respected in The Forge.

• Complex CRM automations may not have direct equivalents in The Forge and remain in the CRM.
• Custom-field parity depends on mapping done during setup.
• Some CRM products throttle writes on lower plan tiers.

The Forge can consolidate lightweight CRMs (contact list + basic pipeline) once the operation is stable. Sales-heavy CRMs with configured reporting usually remain.