The first week with a new client: ask for one thing at a time

A new client is at their most willing in the first week. They have just said yes, they want the work to start, and they will do what you ask. Most teams spend that goodwill on a single welcome email that asks for a signed agreement, a questionnaire, logo files, logins, a kickoff time and a billing contact, all at once.

The client does the easy two, means to come back for the rest, and you spend the second week chasing. The work was never the problem. The order was.

One request, then the next

People finish a list when they can see the next item and nothing else is competing with it. So the first week should read like a short queue, not a wall.

A sequence that works for most service businesses:

Sign the agreement. Nothing else should be open until this is done. It is the one step both sides need before anything else makes sense.
Answer the questionnaire. The questions you would otherwise ask on a call, written down once.
Send the files. Brand assets, documents, access. Ask for these after the questionnaire, because the answers often change what you need.
Book the kickoff. By now you have read their answers, so the call is about decisions, not collecting facts.

In Upclient each of these is a task with one thing to do on it: a contract to sign, a form to fill in, an upload, an embedded booking page. The client’s portal home shows a Start here card with the single most urgent task and a button named for the action, such as Review & sign or Fill out form. They never have to work out where to begin.

Keep later steps out of sight

The quickest way to slow a client down is to show them everything that will ever be asked of them.

Two settings do most of the work here:

Drafts. A task in Draft is never shown to the client. Prepare the whole project up front and publish each task when its turn comes.
Planned stages. Clients only see a stage once it is Active or Completed. Discovery can be open while Design and Launch stay internal until you get there.

Your own work belongs on the same project but not in the client’s view. Tasks are either Visible to client or Team only, and new tasks start as Team only, so “Set up the shared drive” and “Draft the proposal deck” never appear in the portal by accident.

Say exactly what you need

“Send us your brand assets” produces a zip file of everything, or nothing. A request the client can finish in one sitting names the thing and the format:

“Upload your logo as SVG or AI, plus any brand guidelines PDF.”
“Give us view access to your analytics account. Steps are below.”
“Tell us who signs off on copy, with their email.”

If you cannot write the request this specifically, the client cannot answer it.

Review before you move on

Some answers need a second look before the next step opens. Turn on Requires review for those tasks. When the client finishes, the task moves to In review and the reviewer, or the project owner if none is chosen, gets one “Ready for review” email.

If something is missing, Request changes sends the client your note by email and puts it at the top of the task in the portal. The task goes back to them with a clear reason, which is kinder than a vague “can you take another look?” in a thread.

Look at it as the client

Before you invite anyone, open Preview Portal on the project and read it as the person on the other side. It shows the portal as that contact will see it. Check three things:

Is there one obvious first step?
Does every task title start with a verb?
Is anything visible that only your team should see?

Five minutes here saves the awkward email later.

Do it once

When the first week runs well for one client, save the project as a template. The next project starts with the same stages, tasks, forms and contract already in place, and you only add the client.