Working session with Lincoln Durham (Quarra Stone) to clarify Salesforce lead/opportunity logic, review recent configuration changes, and discuss active client projects. The call surfaced a key workflow misunderstanding that had been causing data duplication, and produced several concrete decisions and action items.
Attendees:
- Lincoln Durham — Quarra Stone (external)
- Karly Oykhman — Asymmetric
- Mark Hope — Asymmetric
- Avokerie Onorimuo — Asymmetric
Source recording: Fathom
The team aligned on the correct Salesforce data model after Lincoln identified that his sales team had been creating new leads for new projects from existing contacts (e.g., Monty Foreman), causing duplicate records.
Correct logic going forward:
- Leads → New contacts only. Someone you've never worked with before.
- Opportunities → Existing contacts with new projects. Do not create a new lead; create a new opportunity directly.
- New contacts at existing accounts → Add as a contact to the existing account, then create an opportunity.
Lincoln will communicate this distinction to his sales team directly.
"Leads are really only for new relationships. And if it's someone you're already working with, it's immediately an opportunity." — Lincoln Durham
Lead conversion remains restricted to prevent premature conversions. Salespeople can create leads and opportunities but cannot convert leads themselves. This setting stays in place.
To maintain data quality while allowing salespeople to create opportunities freely, an approval flow will be built. Opportunities created by salespeople will enter an "unapproved" state and require Lincoln's review before becoming active.
This replaces the previous intent to restrict opportunity creation entirely.
The default task subject dropdown is too limited for Quarra Stone's workflow. Resolution:
- Lincoln will provide a list of desired subject options (confirmed: "Develop Estimate" is one).
- Mark will add an optional free-text field called "Task Details" to the task object, allowing detailed instructions without bloating the subject dropdown.
The Salesforce Outlook add-in will be demonstrated to the Quarra Stone team. The add-in prompts users to log emails and allows selection of the correct opportunity when a contact is tied to multiple records.
| Owner | Action |
|---|---|
| Karly | Email American re: lead list service — $0.50/name (name, title, company, LinkedIn); request search criteria |
| Karly | Call Wisconsin Masonic to reconnect expired Square plugin token |
| Karly | Email Wisconsin Masonic quoting ~$1,500 for WooCommerce donation store build |
| Karly | Build Salesforce opportunity approval flow for Lincoln's review |
| Karly | Schedule Outlook-to-Salesforce demo with Mark + Lincoln |
| Karly | Schedule next working session with Mark (November) |
| Mark | Add optional "Task Details" text field to the task object |
| Mark | Participate in Salesforce process guide creation with Karly |
| Lincoln | Email sales team clarifying lead vs. opportunity rules |
| Lincoln | Provide Karly with desired task subject dropdown options |
| Lincoln | Review drafted opportunity stage guidance and send feedback |
| Lincoln | Schedule call with Veeth (Fathom) to unblock prospect folder creation |
On the lead vs. opportunity confusion:
"I feel bad, because I feel like you guys have understood that the entire time. And I'm like, the lead's got to be the project that we're pursuing." — Lincoln Durham
On the approval flow approach:
"They can create it, but it's not approved. It's like an unapproved opportunity... That keeps those opportunities from people just willy-nilly creating opportunities and causing anarchy." — Mark Hope
On the government shutdown:
"The public projects and the academic projects that have often been an important part of our backbone are now not the safe haven that they once were. You've got to follow the money." — Lincoln Durham