Why we don't do discovery calls with junior staff only

A common agency pattern is having junior staff run initial discovery calls, gathering requirements to hand off to whoever actually scopes and prices the project. We don't do this, and the reasoning is worth explaining because it directly affects how useful a prospective client's first conversation with us actually is.

A junior staffer gathering requirements can capture what's said, but can't reliably identify what's missing, what's ambiguous, or what will turn into a costly change request later, because that judgment comes from having scoped and delivered a lot of similar projects before. Those are exactly the judgment calls that determine whether a fixed-price quote ends up accurate months into a project.

A discovery call that ends with "I'll pass this along to our team" means the client has to wait for a second, more substantive conversation anyway, or worse, gets a quote based on a second-hand summary of what they actually said. Having a senior lead on the first call means real questions get real answers immediately, and the client walks away with an accurate sense of scope and cost sooner rather than later.

Whoever would actually lead the project, if it moves forward, is on that first call asking questions specific to what they'd need to know to scope it accurately, not a generic intake script. A prospective client can usually tell the difference within the first few minutes, and it changes the whole tone of the conversation from a sales pitch to a real planning discussion.

This means senior staff time gets spent on calls that don't convert into signed projects, which is a real cost. We accept it because the alternative, a worse first impression and less accurate early scoping, costs more in the relationships and projects it damages than it saves in senior staff hours across a year of these calls.

Junior team members do join discovery calls, just not as the lead, sitting in specifically to learn how scoping conversations actually work by observing a senior lead handle them directly. This is a deliberate part of how we train people into eventually running these calls themselves, rather than excluding them from the process entirely.

One prospective client told us directly, after signing, that our founder-level discovery call was the deciding factor over a competing agency that had sent a business development representative to their equivalent first call. The quality of that first conversation carried real, tangible weight in their decision.

As the team has grown, "senior" now means several people capable of leading a discovery call competently, not just one founder personally handling every single one. The principle that matters is scoping experience in the room, not that it's literally always the same specific person.

We've occasionally lost smaller, less complex projects to competitors willing to move faster with a lighter-weight initial process. We accept that tradeoff deliberately, since the projects we're best suited for tend to be exactly the ones where getting the scoping conversation right upfront matters most.

Even for smaller projects, a senior team member leads the initial call, though the follow-through and day-to-day execution afterward may involve a broader team. The principle isn't that seniority handles everything, it's that the judgment calls made in scoping specifically benefit from real experience, regardless of project size.

Clients have told us directly that a strong first call gave them confidence about ongoing responsiveness too, reasoning that a studio careful about who leads a sales conversation is likely similarly careful about who's actually assigned to deliver the work. That inference isn't guaranteed, but it's not wrong either in our case.

We don't have a controlled experiment proving this policy causes better outcomes, since we've applied it consistently rather than testing it against an alternative. What we do have is a clear pattern across years of projects: engagements that started with a strong, senior-led discovery call have had meaningfully fewer scope disputes and unplanned change requests than the handful of early projects, before this became firm policy, that started with a more junior-led intake process.

That correlation doesn't prove causation on its own, but it's consistent enough, and intuitive enough given what actually happens differently in those calls, that we've never seriously reconsidered the policy despite its real cost in senior staff time on calls that don't always convert into signed work.

We also apply a version of this same principle to how we staff the actual delivery of a project once it's signed, ensuring a senior team member remains genuinely accountable for quality and direction throughout, even as junior team members handle a meaningful share of the hands-on execution day to day. The discovery call policy is really just the most visible, earliest expression of a broader studio-wide principle: experienced judgment stays involved at every stage where real judgment calls actually get made, not just at the very beginning of a client relationship.

Occasionally a returning client, or one referred directly by someone we've already worked with, wants to skip straight to a proposal without a formal discovery conversation. We push back gently even here, since even a well-informed referral can be missing details that materially change scope, and a short call is cheap insurance against a proposal built on an incomplete picture of what's actually needed.

A returning client from years earlier isn't quite a first-time prospect and isn't quite a current client either, and we treat that first call accordingly, still senior-led, but focused on what's changed both in their business and in our own team and process since the last engagement, rather than starting completely from scratch as if no history existed between us.

This has occasionally surfaced useful context a brand-new client wouldn't have, like knowing which past decisions worked well and which didn't, which shapes the new scoping conversation in ways a first-time discovery call simply can't replicate.