Skip to main content

Who actually works on the project?

Ask follow-up

Each team has a lead that is usually senior person with most amount of work.

The senior team named at scope is the team that ships. We do not hand agency work to juniors and supervise from a distance.

  • Minimum seniority is enforced. Our core engineering team has shipped production systems for years - not "five plus" as a tagline, but verifiable through the work we point to in the case studies.
  • The same team works the engagement end-to-end. Discovery, scope, build, QA, release. No re-briefing of new people each sprint. Continuity is the value, not a rotation pool.
  • The project lead is named in writing. One senior engineer owns the agency relationship for the engagement. If continuity changes for any reason, we tell you before you ask.
  • Specialists are added explicitly when the work calls for them. Mobile platform engineer, integrations specialist, infrastructure lead. They join the team as named contributors, not as subcontracted tickets.

What this means for the agency: the engineer answering your weekly sync is the engineer reviewing the pull request. There is no account-management layer between the agency and the people doing the work.