Lionel Q.
← Field notes

WHY CUSTOMERS STAY: SIX LEVERS FOR A SOLUTIONS ENGINEER.

Topic
Customers
Reading time
3 min

A customer stays when their solutions engineer understands their system and stands up for them inside the vendor. I drew six levers from my work with around twenty enterprise accounts. Answering fast and staying present during an incident remain the baseline.

  1. 01

    The principle

    In the Harvard Business Review, Matthew Dixon, Karen Freeman and Nicholas Toman studied more than 75,000 people. According to them, the effort a customer has to make predicts loyalty better than satisfaction measures do. Having to contact a vendor again about the same problem weighs the most.

    Fast support reduces that effort on every ticket. A solutions engineer reduces it at the root: they prevent the next ticket.

  2. 02

    The six levers

    1. Know their implementation better than they do. Learn how their sources, transformations and destinations connect. One customer saw records being rejected and looked for the fault on our side. It came from their own configuration: an empty identifier. A regular implementation review keeps that knowledge current.
    2. Solve it yourself, with proof. Reproduce the problem, read the code, check the documentation before you answer. On a browser-side session issue, I reproduced the case in a sandbox and read the SDK code. The customer received two verified workarounds, and the engineers received a precise question.
    3. Advocate for their request internally. Write it up as a use case: the context, the need, the customer's workaround. The product team then decides. They weigh the request against those of other customers, the direction of the market and their own view of the technology. Go back to the customer with the answer, even when it is no.
    4. Tell the truth about the product. Correct a wrong answer, even when it came from your side, and state the limits. An automated assistant had given a customer an inaccurate answer, and my next message started with "small correction". To another customer, I wrote that a feature was on the roadmap, with no date. The customer then believes you on everything else.
    5. Clear the blockers before the renewal. List the open technical points well ahead of the deadline and work through them one by one. One customer announced in February, during an onsite visit, that they would build part of the tool in-house and would not renew. They renewed for a year in July.
    6. Communicate clearly, with empathy. Write for someone who has a problem to solve: what is happening, what you are doing, what you need from them. During an incident, a customer wrote: "Thank you for thinking along and making things easier for us." Empathy keeps professional limits: you stand up for the customer without promising what the vendor will not deliver.
  3. 03

    The results

    The method works, and my customers have said so in writing. I reread 162 messages they sent me across 12 accounts. Of the 56 that express an opinion, leaving out simple follow-ups, 50 are positive: 89%.

    MeasureResult
    Accounts with no negative message5 out of 12
    Signed renewals I could trace3, including one after an announced refusal and one on an account flagged at risk

    SurveyMonkey (opens in a new tab) places scores between 75% and 89% in the range where most customers are satisfied, and puts the norm for software companies between 70% and 80%.

    Customers name the levers in their own words. One wrote: "Thanks for this quick debugging and the transparency." Another, after an incident: "You saved us here!"

    These results belong to a whole team: engineers, product, account managers. The six levers are the part a solutions engineer controls.

  4. 04

    Sources

← All field notes