惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

C
Check Point Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 聂微东
月光博客
月光博客
博客园 - 司徒正美
爱范儿
爱范儿
aimingoo的专栏
aimingoo的专栏
量子位
Recent Announcements
Recent Announcements
V
V2EX
P
Proofpoint News Feed
小众软件
小众软件
云风的 BLOG
云风的 BLOG
腾讯CDC
宝玉的分享
宝玉的分享
Microsoft Azure Blog
Microsoft Azure Blog
大猫的无限游戏
大猫的无限游戏
Vercel News
Vercel News
The GitHub Blog
The GitHub Blog
A
About on SuperTechFans
B
Blog
博客园_首页
GbyAI
GbyAI
博客园 - Franky

Giant Robots Smashing Into Other Giant Robots

5 easy, actionable tips for software development in healthcare Announcing importmap-update: automated dependency updates for importmap-rails When to vibe code an app and when to hire someone Why leaders have to know about PMS 🩸 Is AI ruining my brain? Tech Leaders Meetup is coming to Edinburgh Designers already think in React Tech Leaders Meetups are back in London this autumn GPT and Claude go to heraldry school Inserting State Transitions in Postgres Don’t hire thoughtbot to write code AI makes creating software faster, but in regulated industries, judgment matters more Tech Leaders meetup in Amsterdam PMs Don't Need to Code, but They Do Need to Understand How healthcare tech teams innovate while balancing speed and security Can’t touch the DOM? Reach for :has() to style any element Buying Time, Choosing Words: Consulting Through Diplomatic Communication thoughtbot around the world, meet us at upcoming events Modeling State Transitions in Postgres Humid 1.0: React server-side rendering in Rails can be easy! A prototype is not a product. It's a conversation. New: The State of Software Delivery in Healthcare Sign in with Google for React Native What founders told us about working with AI tools for startups Join us: Building Secure Healthcare Systems Upcase has retired, but the learning continues The Bike Shed Ep 506: The Muppet Software Team Migrating to native stack navigation, with a surprise from iOS 26 Past and present thoughtbotters at LRUG this Monday The Bike Shed Ep 505: What is a “principal” or “staff” engineer?
Client success starts before kickoff
Lonna Spitaleri · 2026-09-14 · via Giant Robots Smashing Into Other Giant Robots

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 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 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?, 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.