{
  "id": 8307548,
  "title": "The bottleneck in AI-assisted client work isn't the code",
  "url": "https://urgent.news/2026/09/18/the-bottleneck-in-ai-assisted-client-work-isnt-the-code",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-18T20:52:07.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/briefgate/the-bottleneck-in-ai-assisted-client-work-isnt-the-code-2g9p"
  },
  "original_language": "en",
  "account": "The bottleneck in AI-assisted client work isn't the code. During the past year, the nature of client projects I build small websites and apps for underwent a significant shift. A five-page site, once taking a few days to complete, now emerges almost entirely through the assistance of Claude Code. However, despite this reduction in coding time, the overall project timeline remains unchanged at six weeks. This transformation has brought the bottleneck in the work process to a different area - outside of the editor.\n\nIn the past, I would send a single email at the beginning of a project requesting the logo, company copy, photos, and access to current hosting. To me, this seemed reasonable: four things and ten minutes of work. However, this approach turned out to be flawed. The \"company copy\" wasn't a task, but a writing assignment without a brief or end. Choosing photos required a decision, and determining access to current hosting necessitated finding out who the hosting service was. These seemingly simple lines expanded into small research projects on the client's side, with no clear finish line. Meanwhile, the client was dealing with tasks that were actually due that day, and my email often became their homework with no structure or deadline, leading to their loss of focus.\n\nTo rectify this, I revised my approach, writing the request in a way that made every line clear and easily understandable, even if the format was not immediately obvious. For instance, instead of saying \"send me your logo,\" I specified \"logo — SVG or PNG at least 1000px wide. If all you have is the PDF your designer sent, send me that and I'll pull it out.\" Similarly, instead of asking for \"something about the company,\" I provided a sample paragraph to serve as a guide. By being specific in my requests, I found that the client could complete them one by one, as opposed to postponing the project due to vague instructions.\n\nAnother improvement I made was to stop asking for everything at once. Breaking down the project into smaller, manageable tasks minimized delays and confusion. Additionally, I agreed to check in on the project at predetermined times (Tuesday and Friday) until everything was in place. By setting clear expectations and a schedule, I eliminated the need for reminders and made the project management process more efficient. Moreover, handling passwords and credentials with care became a top priority, leading to the use of a password manager to share one-time access links instead of sending passwords in emails.\n\nImplementing these changes required some effort initially, such as creating a checklist template, setting up calendar reminders, and establishing separate secure links for login credentials. However, this method worked well and scaled up to handle multiple simultaneous projects. I later developed a tool called BriefGate to automate these processes, enabling clients to submit a single link with no account creation, automated follow-ups, and secure storage for login credentials. While the tool provides additional value, the core improvements - specific requests, upfront reminders, and secure credential handling - yield significant benefits without requiring any additional software.",
  "summary": "I build small websites and apps for clients, and over the last year the shape of that work changed completely. A five-page site used to be a few days of typing. Now I describe it to Claude Code and most of it exists by the evening. What didn't change is everything the project needs from someone who isn't me. The logo, sitting in a folder on a laptop nobody has opened since 2019. The \"about us\"…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}