During the pre-signing meet & greet with [1], the sales director Erica Lathrop surfaced several compounding workflow problems centered on Eldermark — their CRM of record. The agreed solution is for AAG (Asymmetric) to receive admin access to Eldermark and own the integration end-to-end, establishing it as a single source of truth for all lead and marketing data.
This article documents the pain points discovered, the integration approach agreed upon, and the downstream marketing workflow changes that depend on it.
Leads submitted through The Cordwainer's website are not automatically captured in Eldermark. Erica manually copies contact details (name, phone, email) from form notifications into the CRM — a process that is frequently delayed by the demands of an active sales role.
Consequences:
- Leads may sit unlogged for 1–3 days
- Timestamps in the CRM don't reflect actual inquiry dates, making pipeline reporting unreliable
- Hot leads risk falling through the cracks entirely if Erica is pulled into appointments or tours
The current email workflow requires Erica to manually export a contact list from Eldermark approximately once per month, then hand it off to the previous agency for use in MailChimp.
Critical flaw: Any lead acquired in the 30 days since the last export is excluded from outgoing campaigns — meaning the most recently engaged, highest-intent prospects receive no nurture communications.
The previous agency used a proprietary dashboard called Further, which does not sync with Eldermark. This forced Erica to monitor two separate systems and manually reconcile lead data between them. Further also pushed its own dashboard as the primary interface, creating friction and duplication rather than consolidation.
The previous agency enforced a 2-campaign-per-month cap, which prevented agile responses to time-sensitive opportunities. A concrete example surfaced in the meeting: when The Cordwainer wanted to run a last-minute respite care push ahead of the holidays, the agency told them to wait until the following month because their hours were exhausted.
AAG will be provisioned as an admin user in Eldermark. This enables:
Erica noted she is doing "the basics" of Eldermark and suspects there are underutilized features. The integration work should include a CRM audit alongside the automation build.
Web form submissions should flow directly into Eldermark without manual intervention. The specific mechanism (native Eldermark webhook, Zapier, or direct API) will depend on what the web form platform supports and what Eldermark exposes at the admin level.
Target state: A lead submits a form → a contact record is created in Eldermark within minutes, timestamped accurately, and tagged by source.
Once leads flow into Eldermark automatically and AAG has admin access, email campaigns can be built against live, dynamic segments rather than monthly static exports. This ensures:
The Further dashboard should be deprecated as a lead management interface. All lead tracking, reporting, and campaign coordination should route through Eldermark. This removes the dual-system burden from Erica and gives AAG a single integration target.
| Capability | Before Integration | After Integration |
|---|---|---|
| Lead capture from web forms | Manual copy-paste, delayed | Automatic, real-time |
| Email list freshness | Monthly static export | Live dynamic segments |
| Welcome sequence for new inquiries | None (lapsed) | Automated on lead creation |
| Campaign flexibility | 2/month cap, hour-gated | Need-driven, no cap |
| Reporting accuracy | CRM dates ≠ inquiry dates | Timestamps reflect actual activity |
| Systems to monitor | Eldermark + Further | Eldermark only |
The integration is a prerequisite for the [2] approach AAG proposed. Campaigns planned backward from event dates (Chamber of Commerce lunches, prospect open houses, professional cocktail events) require that: