How to get up to speed on a new client quickly

You've won the work and you have two days to absorb a week of reading. Here's the order that actually works — what to read first, what to ask them, what to find yourself — so the first meeting is the one where you already know their business.

Getting up to speed on a new client is not a research problem. Given a week you could read everything. You don't have a week — you have the gaps between your existing commitments, and a first meeting on Thursday where the client will decide, in about ten minutes, whether they've hired someone who understands their business or someone they'll have to explain it to.

So the question isn't what should I read. It's what order, what to skip, and what to ask them instead of reading at all. Below is a sequence that holds up under real time pressure, followed by the part most advice leaves out — what happens in week three, when you have all the material and can no longer remember which document said what.

1. Start with the commercial documents, not the company story

Most people begin with the client's website. Start with the paperwork instead — it's shorter, it's specific to you, and it's the only material that describes what you're on the hook for:

Half an hour here reframes everything you read afterwards, because you now know which parts of their business are actually relevant to your engagement — and which are interesting but irrelevant.

2. Then read the last ninety days in their own words

The highest-yield reading you will do is the client's own language, recent. Not analyst coverage, not the industry primer — their emails during the sales process, the deck they sent you, the last board or investor update, the notes from the discovery call, whatever internal document they shared to explain the problem.

Two things come out of it. First, the vocabulary: what they call their customers, their product lines, their regions, the internal name for the project everyone refers to by initials. Using their words correctly in the first meeting does more for your credibility than any amount of market research, and using the wrong ones quietly marks you as an outsider for weeks. Second, the live tensions: read for what's repeated, what's hedged, and what someone pointedly didn't answer.

3. Give the outside view forty-five minutes — not a day

Public research is infinitely expandable and has the lowest yield per hour, so timebox it hard. In forty-five minutes:

Stop when the timer goes. Reading a fifth competitor profile feels productive and changes nothing about Thursday.

4. Decide what to ask them and what to find yourself

This is the split that separates a fast start from a slow one. The rule of thumb: never ask them for something they've published; always ask them for anything that requires judgement. Asking for the public thing reads as laziness. Guessing at the internal thing wastes a week and is usually wrong.

Find it yourself before the first meeting Ask them directly
How they make money, and who their customers are What "good" looks like six months from now — and who decides that it's good
Product lines, pricing, recent announcements, published numbers Who else has to be convinced, and who can quietly stop this
Names, titles and tenure of the people you'll work with What's been tried before, and why it didn't stick
The market they operate in and their named competitors What must not break while we do this work
What their customers say about them publicly How they want to be updated, how often, and who should be on which threads

The right-hand column is not small talk. Those five answers are the engagement. Ask them in the first meeting, write down the exact words, and reread them before every review for the next three months.

5. Ask for the internal reading list — it saves you a day

One request, in your first email, does more than a day of searching. Ask for what they'd hand to a new person joining their own team, and be specific about the kinds of thing you mean:

Most clients send more than you asked for. That's the point: it's better to receive forty documents in week one than to discover the important one in month two. It does create the recall problem we get to below — but material you haven't been given can't be recalled at all.

6. Write the one-page brief you'll actually reread

Reading without writing doesn't stick. At the end of your two days, produce one page — for you, not for them:

Writing it is the studying. Rereading it for five minutes before each of the first few meetings is what keeps you sounding current while the details are still new. It's the same discipline as a proper pre-meeting prep pass, just front-loaded.

7. Arrive with questions only someone who read it would ask

Don't open by reciting their business back to them — it's their business, and summarising their website proves nothing. Show the reading through the questions instead:

That is what the angle sounds like in practice: the first meeting where you already know their business — not because you memorised more, but because you read the right things and spent your questions on what you couldn't read.

The part nobody warns you about: week three

Here's where the standard advice stops being useful. Getting the material is the easy half. The hard half is that it arrives as forty emails, three decks, a contract, an onboarding call you took rough notes in, and a folder someone shared once — and by week three you can no longer remember which of those said what.

The failures are specific and all cost you credibility:

Notice that none of these are research failures. They're recall failures, and no amount of extra reading fixes them. Neither does a tidier folder tree — filing tells you where a document is, not what it said, and the question in week three is always "which document said that?"

A different answer: keep it in one place and ask it questions

This is the problem Equerry is built for. Instead of organising the onboarding pile harder, you hand it over once and ask for it later — with the source attached, so you can quote it back accurately.

For someone two days into a new account, that looks like:

It holds what you hand it — the threads you forward or CC, the files you share, the notes and voice memos you save — and, if you switch on the pre-meeting brief, a short forward window of your calendar: the titles, times, locations and attendee names of what's coming up. There's no sign-in to your mailbox and nothing listening to your calls; you choose what it sees. Related reading: how to keep client emails and documents findable, and how to hold context across several clients at once.

What to do with your two days

Do that and the first meeting stops being an examination. You'll know what you were hired for, you'll speak their language, and the only questions you bring are the ones they're the only source for — which is exactly how someone who understands the business sounds.

Frequently asked questions

What should I read first when starting with a new client?

Read the commercial documents first — the signed contract or statement of work, the proposal it came from, and any handover notes from whoever sold the work. They tell you what you're actually accountable for, by when, and what was promised in the room. Only then read the client's own words from the last ninety days: their emails during the sales process, the deck they sent, the last board or investor update. Public research — website, pricing, recent news — comes third and should be timeboxed, because it's the most expandable and the least specific to the work you just won.

How long does it take to get up to speed on a new account?

You can be credible in the first meeting after roughly a day of focused reading, and genuinely useful within two to three weeks. The first day buys you vocabulary, the commercial shape of the engagement, and the names of the people involved — enough to ask good questions rather than basic ones. What takes weeks is judgement: knowing which of their stated priorities is real, who actually decides, and what's been tried before. Don't try to close that gap by reading more; close it by asking better questions early and writing down the answers.

What questions should I ask a new client at the start?

Ask only for what you can't find yourself, and ask for judgement rather than facts: what does good look like six months from now, and who decides that it's good? Who else has to be convinced? What's been tried before and why didn't it stick? What must not break while we do this? How do you want to be updated, and how often? Then ask for their internal reading — "send me anything you'd give a new person joining your team" reliably produces more than a request for specific documents. Never ask them for something published on their own website; it reads as not having done the work.

How do I keep track of everything a new client sends me?

Route it all to one place the moment it arrives rather than filing it later, and make sure that place lets you get back to the source, not just a summary — in week three the question is always "which document said that?" This is the part where folders quietly fail: forty emails, three decks and a contract are easy to store and hard to recall accurately. The alternative is to hand the material to an assistant that keeps it and answers questions about it. With Equerry you forward or CC the threads, share the PDFs from your phone, and dictate a note after a call — then ask later and get the answer with a source chip back to the exact email or document it came from.

Last updated 2026-08-29.