All articles

How to onboard a new client without losing details in email threads

Client portals and onboarding Nadya Neykova Updated 5 minute read

Short answer: Start the client record at the first conversation and keep every email, call note and agreement on it. When the deal is won, create the onboarding tasks and the handover document from that record, ask the client for everything you need in one form, and show them what's still missing on one page instead of in follow-up emails.

Disclosure: I co-founded Teamo and Opsters, the agency Teamo was built out of.

Why do details get lost between sales and delivery?

Details usually get lost before delivery even starts:

  • What was promised lives in one person's inbox. The salesperson knows the client wants reports on Mondays, but the delivery team never sees that email.
  • Requests for access and content go out one by one. Logins, brand files and contact names arrive over weeks, each in its own thread.
  • Nobody owns the checklist. Each new client gets a slightly different start, depending on who remembers what.

The fix is to keep everything about the client in one place from day one, and to start every onboarding the same way.

Step 1: Start the client record at the first conversation

Create the client the moment a real conversation starts, not when the contract is signed. Put the deal under it, and keep notes from every call there.

In Teamo, a client is a record, and its deals, tasks, contacts and invoices sit under it as separate lists (activity groups). With the Inbox add-on, Gmail or Outlook emails, WhatsApp and LinkedIn messages are linked to the client automatically when the sender matches a contact. By the time the deal is won, the whole conversation is already on the record.

Step 2: Write down what you agreed before delivery starts

The handover from sales to delivery is where details get lost. Write it down in a fixed format, so every client gets the same one. At Opsters, the handover covers who the client is, what was discussed and sold, the priorities and first plan, access to their systems, and the agenda for the first meeting.

In Teamo, the handover can be a document on the client record, started from a template whose variables fill in the client's name and the deal. At Opsters, a Claude routine writes ours from the client record once the deal closes; the full template is in Inside an automation agency: from signed deal to paid invoice without losing track.

Step 3: Create the onboarding tasks when the deal is won

Don't rebuild the checklist for every client. Let the win start it.

How client onboarding runs in Teamo Onboarding in Teamo, from won deal to kickoff Everything stays on the client record, so nothing waits in someone's inbox. 1 Deal marked Won On the client's Deals group 2 Tasks created An automation adds onboarding tasks and notifies the lead 3 One intake form Answers and files arrive as records 4 Portal shows gaps The client sees what's waiting for them 5 Kickoff Handover, tasks and answers in one place Starts by itself

In Teamo, an automation can do this: when a deal's status changes to Won, create the onboarding tasks under the client (one "Create an activity" step per task, such as "Get access to their systems" or "Schedule the kickoff") and notify the delivery lead. Every new client then starts with the same tasks and the same owners.

Step 4: Ask for everything you need in one form

Send one form with everything you need from the client, instead of a chain of emails: logins or access, brand files, main contacts, goals, dates.

In Teamo, the form is a block on the client's portal (a portal can hold just the form), and every answer arrives as a record, or a row under the client, in the module you choose, with any uploaded files. Mark the answers you can't start without as required.

Step 5: Show the client what's still missing

Clients forget what they owe you, and chasing by email is slow. Give them a page that shows it.

In Teamo, the client's portal can list their onboarding tasks filtered to "Waiting for you", next to the request form, and a comment on a task lands on that task instead of in a new email thread. The setup is in How to give clients a portal where they see project status.

Step 6: Run the kickoff from the client record

Open the client record in the kickoff meeting: the handover has the agenda, the tasks show what's done, and the form answers show what you have. After the call, put the summary into the client's documents. When something needs action, leave a comment on the record that tags the person who has to do it, so it lands with them instead of staying in a summary nobody rereads.

How do you do this without Teamo?

Keep the same rules with other tools: one client folder or CRM record from the first conversation, one handover template, one onboarding checklist you copy for every client, and one intake form. The weak point is that the pieces live in different places, so someone has to copy emails into the CRM, start the checklist by hand and chase answers by email.

FAQ

What should a client onboarding process include? A client record started at the first conversation, a written handover from sales to delivery, a standard set of onboarding tasks, one intake form for everything you need from the client, and a kickoff meeting with an agenda.

Can client onboarding be automated? Partly. The tasks and reminders can start automatically when a deal is won, through an automation. The handover document can be drafted automatically too, by an assistant such as Claude connected over MCP, as Opsters does. The conversations, the kickoff and judging what the client really needs stay with people.

How do I get clients to send what I need? Ask for everything in one form instead of separate emails, mark the essentials as required, and show the client on their portal what's still waiting for them.

Who should own client onboarding? The delivery lead owns the checklist from the won deal onward; sales owns the handover document.

See your own setup in Teamo

Sign up, answer a few questions about your business, and Amo builds your setup.