$ man how-to/workspace-red-flag

A go-to-market engineer at an agency managing 9-10 client workspaces has roughly 4 hours per week per client. That is 40 hours divided by 10 clients. In reality, it is less - meetings, internal syncs, reporting, and context-switching eat another 20-30% of the time. Four hours per week is enough to maintain existing campaigns. Check the dashboards. Swap a subject line. Reply to "looks good, let us set up a call" messages. But it is not enough to engineer. Engineering means building new enrichment workflows, testing qualification hypotheses, analyzing reply patterns, optimizing send timing, and iterating on ICP criteria. The result is predictable. Campaigns plateau at month 3 because nobody has time to optimize them. The agency reports activity metrics (emails sent, open rates) because outcome metrics (qualified meetings, pipeline generated) require deeper analysis that 4 hours per week does not support.

PATTERN

Maintenance is checking dashboards, pausing underperformers, and launching the next campaign from the same template. It is necessary but it does not compound. Month 6 looks like month 1 with different lead lists. Engineering is analyzing why Campaign A generated 3x the meetings of Campaign B, isolating the variable (was it the ICP segment? the messaging angle? the send cadence?), and building that insight into every future campaign. Engineering means the system gets smarter over time. At 3-4 clients, a go-to-market engineer has enough time to do both. Maintain the running campaigns and engineer improvements. At 9-10 clients, there is only time for maintenance. The agency bills the same rate regardless. This is not a criticism of the engineers. They are doing the best they can with the capacity they have. It is a criticism of the model. The agency optimizes for revenue per engineer (more clients = more revenue). The client needs depth per engagement (fewer clients = better results).

ANTI-PATTERN

Ask your agency: how many clients does my go-to-market engineer manage? If they dodge the question or say "we have a team model," push harder. Someone is responsible for your campaigns. How many other campaigns are they responsible for? Other signals: your campaigns have not been meaningfully updated in weeks. Reporting is templated - same metrics, same format, same insights every month. When you ask for a new campaign type, the turnaround is weeks, not days. Your go-to-market engineer cannot recall specific details about your ICP without checking notes. These are not signs of a bad engineer. They are signs of an overloaded one. The capacity constraint manifests as generic work, slow iteration, and plateau-level performance. If you are paying premium rates for maintenance-level output, the workspace ratio is probably why.

PRO TIP

An independent go-to-market engineer consultant typically works with 2-4 clients maximum. That is a deliberate capacity constraint. Fewer clients means deeper engagement. Each client gets 10-15 hours per week of engineering attention, not 4 hours of maintenance. The tradeoff is cost. An independent consultant charges more per hour than an agency allocates per client. But the output-per-dollar is higher because the work compounds. Month 3 is not a repeat of month 1 - it is building on three months of iterative optimization. The other advantage is ownership. An independent consultant builds in your accounts, documents everything, and transfers ownership. When the engagement ends, you have infrastructure that runs independently. You do not start from zero. The question to ask yourself: do you want 4 hours of maintenance per week from a shared resource, or 10-15 hours of engineering from a dedicated one? The answer depends on your pipeline goals and budget, but at least now you know the tradeoff exists.