Live user-test workspaceModule status and submitted evidence are saved to this selected test profile.
Manager reviewproduction
Galide
Galide Workspace / AE Academy / Discovery

Module 05 · Field guide

  1. Thread
  2. Trace
  3. Next step

Discovery Call Guide

Understand the customer’s environment, expose the lifecycle gap, and earn the right next step. Use the prompts selectively—the goal is a useful conversation, not a completed questionnaire.

↳

Successful discovery produces: a credible problem or trigger, enough operational detail to evaluate fit, the people and process behind the decision, and one owned next commitment.

Learn before you lead

Prepare, then run the right call

Lead with the customer’s operating reality, not a company overview. Validate one likely gap, position only what is relevant, and leave with one concrete next action.

Five-minute preparation

  • Research the account for a refresh, move, acquisition, growth event, cleanup, or other likely trigger.
  • Map attendees, their likely ownership, and any missing stakeholder.
  • Set one hypothesis about the pain to validate—not a feature list to present.
  • Choose the smallest useful next step before the call starts.

What creates momentum

  • A defined upcoming refresh, upgrade, cleanup, move, offboarding issue, or remote-return problem.
  • Manual reconciliation, incomplete certificates, MDM or lock exceptions, delays, or unclear recovery value.
  • A customer willing to share an asset list, photos, an owner introduction, or a dated working session.

What to avoid

  • Feature-dumping, leading with certifications, or assuming the attendee owns every asset category.
  • Introducing remote returns, ServiceNow, ESG, or recovery value before the customer makes them relevant.
  • Promising exact value, turnaround, or reporting details before inventory and conditions are reviewed.

Standard 30-minute discovery

0–3 min
Open and set the agenda

Confirm the discussion scope and agree that the call should determine whether a practical next step exists.

3–13 min
Understand the environment

Explore the trigger, asset mix, condition, locations, current process, and readiness to move equipment.

13–20 min
Position selectively

Explain only the Galide path that matches what the customer has shared.

20–26 min
Clarify value and decision path

Test recovery goals, documentation needs, decision criteria, stakeholders, and timing.

26–30 min
Secure the next action

Agree on an asset list, photos, stakeholder introduction, pilot, or working session—with an owner and date.

Short formats

10 min
Executive or JNUC micro-discovery

Context → impact → relevant outcome → specific action. Ask only four to six questions.

15 min
Introductory discovery

Set the agenda, find the trigger, map the current process, qualify scope, position selectively, and close.

30 min
Standard discovery

Use when there is enough interest and time to evaluate fit, operating detail, stakeholders, and the next commitment.

Natural call talk track
  1. Open

    “Thanks for making the time. I’d like to understand how retired equipment moves through your organization, where the process is difficult, and whether there is a practical way Galide can help. Does that sound right?”

  2. Find the event

    “What typically creates the next volume of retired equipment: a refresh, offboarding, an office or data-center event, or periodic cleanouts?”

  3. Understand today

    “How do you handle that today—from collection through data handling, reporting, and final disposition?”

  4. Surface the gap

    “What is working well today, and where do you still have manual work, risk, delays, or limited visibility?”

  5. Confirm ownership

    “Who owns the assets, the operating process, and the final vendor decision? I want to make sure the right people are involved.”

  6. Close

    “The simplest next step is to review the next project using an asset list, photos, or a short working session. Can we confirm the owner and date?”

Required discovery areas

Follow the customer’s lifecycle

Start broad, follow meaningful signals, and go deeper only where the answer changes qualification, solution design, economics, or the next step.

Ask → listen → clarify

Use the customer’s language before introducing Galide terminology.

Separate fact from assumption

Confirm what is known, estimated, owned, or still unresolved.

Close every open loop

Leave with an action, owner, date, and definition of success.

01EnvironmentFleet, ownership, locations, refresh motion, current process⌄
  • Can you walk me through your endpoint environment and who owns the device lifecycle today?Listen for IT, workplace, procurement, security, HR, finance, and outside vendors.
  • What is the fleet mix—Mac, Windows, mobile, or other hardware—and is it company-owned, leased, or mixed?
  • Where are users and devices located: offices, remote employees, multiple states, or international?
  • How do refreshes happen today—scheduled cycles, performance-based replacements, lease events, or ad hoc requests?
  • What happens to a device after it leaves the user, and which internal teams or vendors touch it?
02Asset volumeInstalled base, retirement volume, cadence, condition, visibility⌄
  • About how many devices are active today, and how many do you expect to retire over the next 12 months?
  • What models, ages, specifications, and condition should we expect in the next disposition group?
  • Do assets move in predictable batches, continuous offboarding returns, or occasional large events?
  • Which other asset categories or accessories need a disposition path?
  • How complete is the current asset inventory, and can you produce an asset list for a representative batch?A usable asset list is often the bridge from interest to a test pickup or valuation path.
03MDM + Activation LockManagement platform, release ownership, failure handling⌄
  • Which management platforms are in use—Jamf, Intune, Kandji, Workspace ONE, or something else?
  • Who owns removing devices from MDM, Apple Business Manager, and any other enrollment or identity systems?
  • How do you prevent or clear Activation Lock and user-linked accounts before disposition?
  • At what point in the return process is device release performed, and how is completion verified?
  • What happens when a device is offline, damaged, user-locked, or missing the information required for release?
  • Who can resolve release exceptions quickly, and what response time can the team support?
04LogisticsOrigin points, remote returns, packaging, transport, storage⌄
  • Are assets returning from centralized offices, remote employees, warehouses, or a mix?
  • Which states, countries, facilities, or legal entities are in scope?
  • Who supplies packaging and labels, and what usually prevents employees from completing a return?
  • Do you need employee communications, return reminders, pickup scheduling, or recovery escalation?
  • Where do returned devices sit, for how long, and what visibility exists while they are waiting?
  • What pickup, shipping, custody, and receipt documentation does your team need?
05Security + reportingSanitization, chain of custody, certificates, audit requirements⌄
  • What data-sanitization or destruction standard must be met?
  • Which certificates, serial-level records, or audit trails are required?
  • Are there regulatory, contractual, insurance, or customer requirements that shape disposition?
  • How should failed wipes, damaged drives, lost assets, or other exceptions be handled and escalated?
  • Who consumes the final reporting—security, audit, finance, sustainability, leadership, or customers?
06Decision processStakeholders, ownership, criteria, procurement, economics⌄
  • Who is involved in evaluating and approving a new lifecycle or disposition partner?
  • Who owns the final decision, and who will own day-to-day success after launch?
  • What will matter most in the decision—security, recovery rate, employee experience, speed, reporting, cost, or global coverage?
  • Is there an incumbent vendor, active contract, internal process, or prior experience we need to understand?
  • What procurement, legal, security review, insurance, or vendor-onboarding steps are required?
  • How will the team judge the economics—cost avoidance, recovered value, net proceeds, service cost, or another measure?
07Timing + urgencyTrigger, deadline, dependencies, pilot path, consequence⌄
  • What changed or triggered the conversation now?
  • Is there a refresh, lease return, audit, office change, budget deadline, or other fixed date?
  • Which internal decisions, systems, asset lists, contracts, or teams could affect the timeline?
  • Could a test pickup or representative batch create enough evidence for a broader decision?
  • What happens if the current process remains unchanged for the next six to twelve months?
08Next stepAction, owner, date, inputs, success criteria⌄
  • Based on what we discussed, what is the smallest useful next action: asset list, test pickup, solution review, stakeholder meeting, or another step?
  • What information or access does each side need to provide before that step?
  • What would make the next step successful enough to support a decision?
  • Who owns each action, and by what specific date?
  • When should we reconvene, and who else needs to be present?

Post-call judgment

Qualification read

Select the posture that best reflects the evidence. Interest alone is not qualification.

Position selectively

Match the message to the evidence

Do not introduce every service. Connect one or two relevant strengths to the customer’s stated operating need.

Audit, security, or control

Lead with serial-level documentation, chain of custody, data-process requirements, and MDM or lock release before resale. Do not open with broad sustainability claims.

Refresh or endpoint transition

Lead with a structured buyback and disposition path, realistic grading assumptions, centralized pickup, and net economics. Ask for models, quantities, age, condition, accessories, and warranty status.

Remote workforce

Lead with return kits, prepaid labels, return tracking, and flexible routing. Confirm whether assets return to the company or go directly to Galide.

ServiceNow-led operations

Lead with reducing portal and spreadsheet work, initiating disposition from the system of record, and attaching post-processing records. Discuss only after confirming ServiceNow is active and relevant.

Infrastructure or data center

Lead with a disposition plan based on models, quantities, data-bearing components, access constraints, and timing. Request a list or photos; do not assume all equipment has value.

Sustainability requirement

Lead with reporting Galide can substantiate: category and weight reporting, recycling documentation, and available impact metrics. Confirm the required format before committing to a custom report.

Segment-specific emphasis
  1. Education

    Lead with Chromebook or iPad transitions, centralized logistics, MDM release, individual documentation, and required sustainability reporting.

  2. Enterprise IT

    Lead with upcoming refreshes, office or data-center work, recovery value, audit trail, and less manual coordination.

  3. Distributed workforce

    Lead with remote return kits, recovery tracking, flexible routing, and a clean employee experience.

When a concern comes up
  1. Existing vendor

    “If the process is working, we are not asking you to change it simply to change it. Where, if anywhere, do you still have manual reconciliation, audit risk, limited reporting, or a future refresh we could compare?”

  2. Broken equipment

    “We can support secure, documented recycling. Before assuming there is no recovery value, would it help to review the next newer devices, infrastructure equipment, or upgrade removals so we can be clear about what is and is not realistic?”

  3. No project yet

    “That is completely fine. Rather than force a project, let’s identify the next likely trigger and reconnect when it is closer. Who should be included when that event appears?”

Close with evidence

Choose one concrete next step

Interest is not an outcome. The next step needs an action, a customer owner, a Galide owner, and a date.

Asset list

Galide returns a preliminary recovery and disposition assessment.

Photos or models

Use for infrastructure or data-center assessment when a usable list is not available.

Stakeholder introduction

Bring in the endpoint, security, asset-management, procurement, or executive owner.

Pilot

Test the process on a discrete refresh, cleanup, or location.

Working session

Review logistics, reporting, ServiceNow, remote-return, or operating requirements.

When the conversation turns to Galide
  1. Explain the path

    “Galide gives retired equipment a controlled next step. We coordinate the appropriate pickup or return path, receive and audit the equipment, handle the agreed data process, document the outcome, and provide recovery and settlement reporting. The exact path depends on the asset mix, condition, locations, and MDM or lock requirements.”

  2. Discuss value

    “I do not want to give you a misleading number. Recovery value depends on model, age, specifications, quantity, market timing, and readiness to leave the environment. Condition, missing components, MDM or Activation Lock issues, and incomplete asset data can change the result. A rough asset list gives us a credible preliminary recovery review instead of a guess.”

  3. Ask for the list

    “If you can send a first-pass asset list with device type, model if available, quantity, condition, location, and MDM or lock status, we can review what looks recoverable, what needs action first, and the recommended path. When can you realistically send it?”

Post-call recap email template

Subject: Next steps: [Company] + Galide Hi [Name], Thank you again for the conversation today. I appreciated learning more about [trigger / initiative] and the need to improve [stated pain point]. Based on what you shared, Galide can help with [relevant capability 1] and [relevant capability 2]. As agreed, the next step is [specific action] by [owner / date]. We will provide [quote, disposition plan, supporting materials, or meeting invite]. Please let me know if anyone else should be included in the next conversation. Best, [Name]

Complete within one business day

Salesforce capture + handoff

Record the commercial truth in Salesforce. An Opportunity begins only once discovery confirms an asset-list or test-pickup path; earlier calls belong in the prospect, account, contact, and activity record.

Required CRM confirmation

Generated discovery summary

Use “Copy summary” to refresh this view and place the structured notes on your clipboard.

Discovery capture map
  1. Why now

    Capture the trigger, signal date, stated need, and qualification path in the account activity. Add to the Opportunity after the asset-list or test-pickup path is confirmed.

  2. Scope and volume

    Capture asset types, estimated count, condition, scope hypothesis, and asset-list availability.

  3. Locations and pickup

    Capture geography, consolidation point, pickup model, on-site constraints, and target timing.

  4. Security and controls

    Capture security notes, chain-of-custody requirements, and MDM, Jamf, lock, or relevant system context.

  5. Stakeholders

    Capture the operational owner, asset owner, security or compliance contact, procurement path, decision-maker, and influencers.

  6. Next action

    Capture the exact action, owners, due date, follow-up meeting, and what Galide will provide.

Use the configured Salesforce labels in the final workflow. This reference describes the required information, not unconfirmed field API names.

Live-call quick reference

Keep the conversation moving

The objective is one clear next action with an owner and date. Ask only the questions that change qualification, solution design, or the next step.

Open

“I’d like to understand how you handle retired equipment, where the process is difficult, and whether there is a practical way Galide can help.”

Find the event

Refresh, move, upgrade, cleanup, offboarding, or another lifecycle transition.

Ask 4–6

Assets and quantity; locations; current process; security or MDM controls; provider; stakeholders; timing.

Listen for

Manual reconciliation, missing certificates, MDM-locked assets, remote returns, unclear recovery value, or reporting needs.

Match

Security → documentation. Refresh → recovery. Remote → return kits. ServiceNow → less manual work. Infrastructure → a model-and-quantity plan.

Close

“The simplest next step is [asset list / photos / introduction / pilot / working session]. Can we confirm the owner and date?”

Summary copied