Lionel Q.
← Field notes

WHY THE CUSTOMER IS ASKING NOW.

Topic
Discovery
Reading time
3 min

A customer request should be read twice. The first reading tells you what they are asking for. The second tells you why they are asking now, and it comes down to their budget, their market or their team.

I am a solutions engineer working with around twenty enterprise accounts. Here are three cases read twice, then the three questions I took from them.

  1. 01

    The financial reason

    First reading. A customer's consumption climbs to nearly a hundred times its usual level. Their usage has not changed.

    Second reading. On their side, an internal job resends the same data every day. Their contract is billed on usage, and this technical fault becomes a budget line.

    What it changes. The customer had not asked for anything. I warned the account manager before the invoice arrived.

  2. 02

    The market reason

    First reading. A customer asks for a connection to a brand-new tool that our product does not support.

    Second reading. Their marketing team is already using it for its campaigns. Every day without the connection is a day of campaign without measurement.

    What it changes. I took the request to the product team with that deadline. Eight days after their question, the customer was using the connection.

  3. 03

    The team reason

    First reading. A contact asks for a feature to record who is responsible for each part of their setup.

    Second reading. They inherited this setup a year earlier. After several years, their team no longer knows who put what in place, and they built their own tool to find their way around.

    What it changes. I passed their request to product with that context: a team that had lost its memory, and the tool it had to build.

  4. 04

    Three questions before you answer

    Salespeople call this second reading the compelling event. Elay Cohen defines it as "a time sensitive response to an internal or external business pressure that drives action" (opens in a new tab). Greg Cooper, who leads a solutions engineering team, expects the best of them to understand the customer's business issues and see the bigger picture (opens in a new tab).

    Each reason has its question.

    ReasonQuestion to ask yourselfWhere to look
    FinancialHow does this customer pay, and does this request change their bill?Their billing model and their consumption
    MarketWhat changed in their market this month?Their announcements, their competitors, the regulation in their countries
    TeamWho decides on their side, and who has just arrived?The new names in the exchanges, and the ones who have stopped replying

    Answering them takes knowledge beyond the technical: reading a contract, following a market, understanding how a team decides.

    The technical answer is still needed. The second reading tells you who to talk to, and about what.

  5. 05

    Sources

← All field notes