❌ Problem: Documents, Estimates, Invoices, Tasks, etc, are tied to Contacts, not Opportunities Today, Estimates, Documents, and Invoices are technically sent to a Contact, but in 95% of real use cases, they are meant for the Opportunity. Why does this not make sense: Opportunities are where the actual sales process happens, not at the contact level. Opportunity fields are useless when everything is Contact-focused. Using contact-level fields for Opportunities leads to awkward workarounds. Sales teams think in terms of deals/projects (Opportunities), not people (Contacts). We lose context and tracking when documents are tied to contacts instead of the opportunity they belong to. Data should still be accessible at the Contact level, but always tied to the right Opportunity. ✅ Suggested Solution: Make Opportunities the primary object for sending and managing documents, estimates, invoices, tasks, etc. And if this doesn't work for all users, offer it as a toggle setting. But this logic fits any lead-driven business. ➕ Make the opportunity as the main / default receiver of Estimates, Documents and Invoices. ➕ Add the ability to easily Send Estimate, Document, or Invoice directly from the Opportunity card. ➕ Allow switching between Contact-based and Opportunity-based workflows. ➕ Opportunity workflows would finally allow the intended use of Custom Opportunity Values. ➕ Add activity history in Opportunity view (similar to what we have in Contact conversations). 🔥 Project Management: Convert Opportunities to Projects (or Custom Objects?) An Opportunity is essentially a project before it becomes a signed contract/won opportunity. The platform should reflect this. I don't know how this would be done or how it would make sense for GHL's existing roadmap with Custom Object, but this would make sense on a structural level. ➕ Allowing for automatically creating projects on signed / Won. ➕ Link Opportunity fields to Custom Object fields. ➕ Link Opportunity tasks to Project tasks (or Custom Object tasks?). ➕ Now the Opportunity-based workflows become a project-based (or Custom object-based) workflow. 👉🏼 Please let me know if this does or doesn't make sense and why!
