Who will actually be working on my project — and will it be the same people who pitched me?

Why the pitch team and the build team are often different people

Sales and delivery are usually separate functions. The person who closed your deal may be a business development lead or account executive with no technical role in your project. Meanwhile, the engineers assigned to you are chosen based on current availability — not necessarily the seniority or domain expertise you saw in the sales meeting.

This is especially common in mid-to-large U.S. agencies and offshore development shops operating under a U.S. brand. It's not always bad practice, but it becomes a problem when the handoff is invisible to you.

What this means in practice

• Quality gaps: The senior architect who answered your technical questions may never touch your codebase.
• Context loss: Business goals you explained carefully during the pitch have to be re-explained — sometimes multiple times.
• Mid-project swaps: Developers get reassigned to other clients. You may meet your third lead engineer six weeks in.
• Timezone and communication mismatch: For U.S. buyers, this often surfaces when a stateside salesperson was your main contact and the actual team is operating on a 10-12 hour offset with limited overlap.

What to ask before signing anything

1. Who specifically will be working on this engagement? Ask for names and LinkedIn profiles, not job titles.
2. What is your policy on team continuity? If someone leaves or gets reassigned, what's the process?
3. Can I meet the team before we start? A 30-minute intro call with the actual lead engineer and project manager tells you a lot.
4. Will you name the core team in the contract? Reputable firms will agree to this for key roles.
5. How do you handle subcontracting? Some firms pass work to third parties without disclosure. Ask directly.

What a transparent engagement looks like

The best firms introduce you to the delivery team during or immediately after scoping — before the contract is finalized. You know who the project lead is, who the senior engineer is, and who your point of contact is for day-to-day questions. Team changes are communicated proactively, not discovered by accident.

CodeNicely operates with a dedicated-team model: the same people who assess and scope your project are the ones who build it, and team composition is disclosed before work begins. That's one reason clients based in the U.S. working with a team in India tend to find the arrangement predictable rather than opaque — you know who you're talking to, and when.

The honest tradeoff

Smaller studios offer more team continuity but may have narrower specializations. Larger agencies have deeper bench depth but higher substitution risk. The right answer depends on your project's complexity and how much relationship continuity matters to you — both are legitimate tradeoffs, just ones you should make with full information.