wiki/clients/current/cordwainer/2026-03-02-crm-discovery-call.md Layer 2 article Client: The Cordwainer 551 words Updated: 2026-02-26
↓ MD ↓ PDF
cordwainer crm discovery lead-management operations karly asymmetric

CRM Discovery Call — Lead-to-Customer Process Mapping (2026-03-02)

Overview

A discovery call scheduled for March 2, 2026 (noted as "next Tuesday" in the [1]) with the [2] team. The primary objective is to map their current lead-to-customer workflow end-to-end before proposing any CRM improvements or integrations.

Karly will lead the call with Mark attending in support.

Objective

Gain a clear, ground-level understanding of how Cordwainer currently handles leads — from first contact through to close — including how their CRM system(s) interact with each other and with their website. This understanding is a prerequisite for proposing a more efficient, integrated workflow.

As Mark framed it in the pre-call discussion:

"If we can get somebody to walk us through it — okay, you get a lead, what do you do, where does it go, who does what, then what, then what — and if we can get that laid out, then we can come back and say, here's a way to do it cheaper, faster, and more efficiently."

Key Questions to Answer

Context & Background

As of the February 26 planning call, Asymmetric has had limited visibility into how Cordwainer's CRM is actually set up. Karly noted she has been inside the system but doesn't have a clear picture of how it's configured or how data flows through it. No formal CRM work has been scoped or delivered yet — this call is the starting point.

Cordwainer is flagged as an at-risk account requiring increased attention. Karly is taking over as primary account lead. See [3] for full account status.

Planned Approach

  1. Walk-through format — Ask the Cordwainer team to demonstrate their live process rather than describe it abstractly. Follow the lead through each step.
  2. Map the flow — Document the full lead-to-customer journey as it currently exists.
  3. Identify gaps — Note where systems don't talk to each other, where manual effort is high, and where leads may be lost.
  4. Defer recommendations — Do not propose solutions on this call. Return with a proposal after the team has had time to analyze the workflow.

Attendees

Action Items