ost studios put a person between you and the work — someone whose job is to relay your notes to a team you never talk to directly. It's not malicious; it's how you staff a large org without every client pinging every engineer. But it has a cost you pay on every single request: a question gets summarized before it reaches the person who can actually answer it, and the answer gets summarized again on the way back. Nuance dies in both directions.
Whenyouwritetous,you'rewritingtothepersonwhowillopenthefilefiveminuteslater.
This isn't a promise of instant replies at all hours — we're a studio, not a support desk. It's a promise that there is no lossy hop in between. If a request is ambiguous, the person building it asks you directly, in the moment they hit the ambiguity, instead of guessing and finding out three weeks later in a review call that it wasn't what you meant.
The account-manager model fails quietly. Nobody lies to you — the manager genuinely believes they relayed your feedback accurately, and the engineer genuinely believes they built what was described to them. The gap only becomes visible once the wrong thing ships. Direct access doesn't make us better listeners than anyone else. It just removes the step where a good-faith summary can drift from what you actually said.
Removing a relay person should shorten the path to an answer, not replace project management with a stream of private messages. A healthy direct-access model still has one written place for decisions, named owners, agreed response times, and a regular summary of scope, risks, and next steps. The difference is that the person answering can inspect the work and explain the consequence instead of translating somebody else’s update.
- Questions reach someone able to inspect the design, code, data, or deployment involved.
- Decisions are written down with their effect on cost, timing, and acceptance.
- The client knows who is responsible when several disciplines touch the same feature.
- Urgent production faults use a defined support route rather than whichever chat was active last.
An account manager can be valuable on a large programme with many teams, stakeholders, and reporting obligations. The problem is not the job title; it is an organisation in which the only client contact cannot answer technical questions and the people doing the work never hear the original requirement.
- Who will attend discovery, and will those people work on the project after the contract is signed?
- Where are decisions and scope changes recorded?
- Who can explain a technical tradeoff directly when it affects the business?
- What happens if the person who knows the project is unavailable?
- Who owns communication after launch?