Client Discovery in Ten Minutes Changes the Credit File
This is Article 4 of 6 in the Q-Lana Customer Centricity series. Client discovery across five lenses takes about ten minutes and changes what the credit file says. A construction subcontractor case shows the script and its action summary.
Client discovery done well takes about ten minutes and changes what the credit file says. Read a hundred credit files and the same sentence keeps appearing: the client has requested a working capital facility. That sentence records what the client asked for, but not why. The committee then decides on a request instead of a problem. Monitoring afterwards watches the facility, not the cause.
This article sets out a five-lens script that fixes this without lengthening the meeting. It ends with a credit memo that names the client's real need.
The Relationship Loop Behind Client Discovery
Client relationships run as a loop rather than a line. Discovery is the first of five stages.

- Discover and diagnose, quarterly or on a trigger.
- Co-design the solution, the same week.
- Approve and onboard, within days.
- Run and review, monthly.
- Renew, grow or course-correct, quarterly.
What the system does and what the RM does
Each stage splits deliberately between the system and the relationship manager (RM). The system compiles the client view, ranks the alerts, runs risk appetite checks and prefills documents. The RM reads the client, structures the solution and holds the conversation. The RM also makes the judgement and owns any override.
The brief that starts the conversation
Ninety days pass, or a trigger fires, and the RM receives a one-page brief. It shows three trends, any early warnings and any risk appetite deviation, in plain language. The conversation then starts from evidence instead of a product. AI does not change this journey. It changes tempo and memory, closing the gap between a signal and an action. The bank remembers every signal, action and outcome, whoever the RM happens to be.
Five Lenses of Client Discovery
The script is a diagnostic tool, not a questionnaire. It has five lenses, each taking about two minutes. Ask the questions close to word for word, then adapt to the person in front of you. No product is mentioned at any point.
Cash-flow rhythm
For cash-flow rhythm, ask the client to walk you through a typical year. When is cash tightest, and when is it plentiful? Then ask how long it takes from paying for inputs to being paid. Is that gap getting longer? Listen for seasonality, a lengthening cash conversion cycle and reliance on the overdraft.
Bottlenecks
For bottlenecks, ask which single constraint, removed tomorrow, would help the business most. Is it capacity, capital or people? Listen for a capacity ceiling, a capital shortage or one operational choke point. Ask what business they turned down recently, and why.
Risk spikes
Ask what keeps the owner awake at night and what could go wrong quickly. Then ask how exposed the business is to exchange rates, a key customer or a key supplier. Follow with the sharpest question in the script. If your biggest customer paid sixty days late, what would happen?
Data reality
For data reality, ask how the client keeps its books. Could it share month-end figures, a bank feed or an ERP export each month? How current are its tax filings and management accounts? The answer decides whether monthly covenant testing is realistic, before anyone writes the covenant.
Win condition
For the win condition, ask what must be true in twelve months for the client to call this a success. Steadier cash, more capacity, less currency pain or a cleaner balance sheet? Then ask what it costs them not to solve the problem. That question separates a diagnosis from a wish list.
What Ten Minutes of Client Discovery Produced

Take a construction subcontractor with about RON 95 million of revenue and 210 staff. The RM runs the script.
Lens one
Cash is tightest in spring, during mobilization. The completion certificate takes sixty days to sign off and payment comes thirty days after that. The client holds ten per cent retention until project close. That is not a working-capital request. It is a certification-driven cash gap with a ninety-day cycle attached, and it is measurable.
Lens two
They have been offered a ring-road subcontract, nearly double their usual job size. It needs two more pavers. They cannot carry the equipment and the working capital at the same time. A capital expenditure need colliding with a working-capital need, which is a structuring problem rather than a credit problem.
Lens three
Three general contractors provide about seventy per cent of the work. Fuel and bitumen prices move without warning. Concentration and input-price risk, both quantified in one answer.
Lens four
Monthly management accounts, tax filings current, annual audit, ERP-based, and they could provide a monthly export. Monthly covenant testing is therefore realistic.
Lens five
Take the ring-road job. Do not miss spring payroll. Have the two pavers paid down on a schedule that matches the work.
What goes into the credit memo
Ten minutes produced three archetype flags, a combined structure to design and a monitoring routine the client has agreed to. The memo will not say "working capital request". It will describe a certification-driven cash gap, in the client's own words, confirmed by a ninety-day receivables cycle. A credit committee can test that statement. It cannot test a request.
The Action Summary That Closes Client Discovery
The script ends in an action summary with four fields, and the discipline of filling it is what stops the insight evaporating.
Diagnosed archetypes, named from the library. Data signals, the measurable evidence for each. Next steps, specific enough to act on. Owners and timeline, with a date.
For the subcontractor: working-capital strain, lumpy capex and customer concentration; certification-driven receivables cycle, equipment need against a contracted pipeline, top three buyers at roughly seventy per cent; assemble a milestone-based working-capital facility and an equipment term loan, draft a concentration covenant, confirm the monthly data feed; owned by the relationship manager and the credit analyst, solution pack within the week.
That is a traceable follow-up rather than an anecdote, and it is the difference between a good meeting and a meeting that changed something.
A Structured Conversation Lowers Risk
The script looks like a relationship technique. In practice, it manages credit risk in four ways.
It finds exposures the financials miss
A ninety-day certification cycle does not appear as a line in the accounts. It appears as a working capital position that looks worse than the business really is. Discovery explains the number before the credit analyst misreads it.
It tests monitoring before the covenant is written
The data reality lens shows whether monthly testing is possible. That stops the bank writing covenants it will never be able to enforce. Portfolio monitoring then starts from a data feed the client has already agreed.
It records the client's own measure of success
The win condition becomes the 30, 60 and 90-day plan and the review agenda. A client who set the target engages differently when the review comes round.
It makes insight comparable across the book
When every RM uses the same five lenses, insights become comparable across clients, sectors and time. A thousand conversations become a dataset. The EBA guidelines on loan origination also expect sufficient, accurate and current information on each borrower.
Training RMs in client discovery
The script is simple, but it does not run itself. Banks that succeed treat curiosity as a professional skill with a standard, not a personality trait.
Three ways to make the script stick
Start with training on the five lenses and on what to listen for behind each answer. Add shadow reviews, where a colleague sits in on a real meeting. The debrief then focuses on the diagnosis, not the rapport. Finally, hold peer clinics where RMs bring a conversation that went badly and the group works through it.
Building This in Your Team
The Q-Lana Financial Skills Campus is launching Customer-Centric SME and Corporate Finance, a class for RMs and credit teams. It covers the diagnosis-first conversation and the structuring decisions that follow from it. It also shows how to keep both inside the risk appetite framework. Practitioners who carry an SME book teach it on your own files.
Next in This Series
The next article is about what happens to that diagnosis once it becomes a proposal, and the enforcement layer that keeps every recommendation inside policy without slowing anyone down.
Run the Discovery Script
The script works on paper, but it works better as a guided form. The form flags the archetype behind each answer and compiles the action summary for you.
Q-Lana · Customer Centricity
The Five-Lens Discovery Script
Ten questions, five lenses, about two minutes each. Capture what the client says, flag the archetype behind each answer, and the script compiles a four-field action summary you can print and drop into the file. No product mentioned.
Discovery action summary
Diagnosed archetypes
Data signals
Next steps
Owners and timeline
The Q-Lana white paper Customer Centricity in SME and Corporate Lending sets out the full script. It includes all ten questions, what to listen for and a complete worked conversation.
All Articles in This Series
- Customer Centricity in SME Lending Is a Risk Strategy
- SME Lending Operating Model Built on Solution Pods
- Solution Toolkits Settle the Risk Before the Client Asks
- Client Discovery in Ten Minutes Changes the Credit File (this article)
- Let AI Handle Credit Policy Enforcement and Free Your RMs
- RM Incentives Decide Whether Customer Centricity Sticks
Follow Q-Lana
One short email a week on credit risk, lending and impact finance, free. Or browse more guides in the Q-Lana Knowledge Center.
Get Q-Lana Weekly
One short email a week on credit risk, lending and impact finance, free. Or browse more guides in the Q-Lana Knowledge Center.