✅ Make Opportunities make sense again
I
Iver Aune
❌ 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!
Log In
Activity Feed
Sort by
I
Iver Aune
Just a quick thought for the Contact to Opportunity transition.
We have created and are using a lot of contact fields instead of opportunity fields as a workaround for the previous lack of support.
➕ Would it make sense to add a "Convert from Contact field to Opportunity field" functionality? So we can transition existing builds from Contact to Opportunity without rebuilding everything for every sub-account?
➕ Not only converting Contact fields to Opportunity fields, but also updating all the used keys from eg. {{contact.job_size}} to {{opportunity.job_size}} in email templates, snippets, documents, etc?
👉🏼 This feature would save us hours and hours.
Big bonus if we can do this in bulk. Flow: Checkbox select custom fields, select convert (under bulk action), select type (Opportunity), select folder, convert.
S
Samuel Burgos
Just copy the data model in Hubspot, is easy, make all the objects mains. We can optmized with rules and association tags. Is the only topic i need for choose GHL and not Hubspot
M
Michael Carpenter
100% Bitrix24 has a similar mindset they have the Modern CRM and Classic CRM toggle button that switches the layout.
I
Iver Aune
Michael Carpenter Thats what we want too! We already got the Opportunities and Pipeline settings!
I
Iver Aune
B
Bryce Claudin
This would help make opportunities make sense as well...
D
Daniel Proczko
Love this as well. All sales pros think in terms of opportunities. Plus a single contact can have multiple opportunities available and each opportunity is it's own individual instance, with it's own contexts, documents, etc. If I had to manage multiple sale opportunities from a single contact card that would be confusing to identify which documents, tasks, etc went with which opportunities.
I
Iver Aune
👉🏼 If it makes sense to have Custom Object-based workflows (which are in beta now), it super makes sense to have Opportunity-based workflows!
K
Keith Besherse
Iver Aune, Yes Opportunity object workflows and Company object workflows before Custom Object workflows! We have been asking for years. Core Platform Sales & Marketing RevEx Group Chase Buckner Shivam HighLevel Varun Vairavan Shaun Clark
C
Cameron Arsenault
LOVE this Iver Aune!!
Pallavi Kothari - please take a look at this!
K
Kenny Butt
100% AGREE!!
VERY WELL SAID!!
I
Iver Aune
Introduce Project Management by converting Won Opportunities into Projects (or Custom Objects)
Load More
→