---
title: Client success starts before kickoff
teaser: Client success starts before kickoff, in how well we understand the problem,
  carry context forward, and set the right team up to deliver.
tags: client success,delivery,communication,sales,consulting,playbook
author: Lonna Spitaleri
published_on: 2026-09-14
---

Client success is established long before kickoff, during the work happening in business development and even before the contract is signed.

By the time a project begins, there have already been meetings, follow-ups, internal conversations, and decisions about what the engagement should actually look like. All of that creates context the delivery team eventually inherits.

If that context is clear before kickoff, the project has a much better starting point. Teams shouldn’t spend the first few weeks rebuilding what was already learned during sales or asking the client to explain the same problem again.

## Good sales work creates a better starting point

At thoughtbot, we try to carry what we learn during the sales process directly into delivery.

One way we do that is through a dynamic project brief built from the client’s intake form, sales call notes, transcripts, and internal conversations. Instead of treating the handoff as a summary written at the end, the brief evolves as we learn more about the client, their goals, and what they’re trying to solve.

That kind of continuity matters. [The 90/10 Rule](https://thoughtbot.com/blog/the-90-10-rule) talks about communication as part of consulting itself, and I think that starts well before an engagement begins.

## The team should fit the client, not just the project

We also ask clients how they want to work with us before we put the team together. Our onboarding survey helps us understand things like communication preferences, collaboration style, and what they need from the relationship.

That information helps us think beyond simply matching technical skills to a project. We want to put the right people on the work for that particular client.

And those people matter. thoughtbot’s consultants bring years of experience working across products, teams, and organizations. They’re not just there to execute a list of requirements. They bring judgment, ask questions, challenge assumptions when needed, and help clients make better decisions along the way.

Our [internal consulting course](https://thoughtbot.com/blog/thoughtbot-s-internal-consulting-course-is-now-public) goes deeper into how we think about defining success, building trust, and communicating clearly throughout that relationship.

## Someone is accountable for the outcome

Once the work begins, we also have Delivery Leads whose role is to help make sure the engagement continues moving toward the outcome the client signed up for.

That creates another layer of continuity between what was discussed during sales and what actually happens during delivery. The goal isn’t just to staff a project and hand it off. It’s to make sure the original goals stay visible as the work evolves.

That connects closely with [You’ve hired a consultant developer. Now what?](https://thoughtbot.com/blog/you-have-hired-a-consultant-developer-now-what), which talks about the clarity and communication that help consulting engagements start strong.

## Success starts before kickoff

This is where I think thoughtbot feels different from a more traditional agency model.

Client success isn’t something we start thinking about once a team has been assigned. We’re collecting context before the contract is signed, carrying that context into onboarding, intentionally putting the right consultants on the work, and keeping someone accountable for the outcome throughout delivery.

By the time kickoff happens, the client shouldn’t feel like they’re starting over with a new team.

The relationship is already underway, the context is already there, and client success should already be in motion.