Founder of Goodspeed
Vague Scopes and Unrealistic Promises
Before evaluating specific vendors, you need a mental checklist of what "trouble" looks like. The earliest signals show up in how an agency scopes work and how they talk about their own capabilities.
A trustworthy Claude agency will push back on under-defined requirements instead of rubber-stamping them. Watch for:
Proposals without deliverables or milestones—just a flat fee and a timeline.
"We can build anything" responses to specific technical questions about MCP, tool use, or evals.
Guaranteed outcomes ("99% accuracy", "fully autonomous agent") without describing how they'll measure it.
Quoted pricing before discovery—no serious agency commits to a number before understanding your data, integrations, and constraints.
Why Early Warning Signs Matter?
The scoping conversation is a preview of the whole engagement. Agencies that skip discovery to win the deal usually skip evals and documentation to ship on time. By the time you notice, you're already three invoices in. Treating vague scoping as a dealbreaker saves you from the much larger cost of rework.
Here's what one of our clients said: "The previous agency promised a working agent in six weeks and delivered a demo that broke on edge cases. Goodspeed spent the first week just on discovery—and we've never looked back."
Tip: If an agency won't commit to a discovery phase, treat the whole proposal as marketing, not engineering.
Missing or Shallow Portfolio
Once you've filtered out obvious mismatches, dig into the middle of the funnel—portfolios, processes, and the first few interactions. This is where most red flags actually live.
Ask to see real Claude deployments, not blog posts or generic AI demos. A shallow portfolio—stock screenshots, no named clients, or "NDA" blocking every case study—is a warning.
How-to: Ask for at least one deep-dive walkthrough: architecture, eval results, and the decisions behind them. If the agency can't narrate their own build, they probably didn't lead it.
No Clear Process or Documentation
Claude projects involve prompt iteration, tool design, evals, and production hardening. Without a documented process, quality depends entirely on the individual on the keyboard that week.
How-to: Ask how they version prompts, run regression evals, and hand off documentation. "We figure it out per project" is a red flag.
Poor Communication from Day One
Sales-cycle behavior is the best version of the working relationship you'll ever get. Slow replies, missed meetings, or generic answers during the pitch almost always get worse after the contract is signed.
How-to: Track response times, meeting preparedness, and whether the team follows through on small commitments—notes, recordings, scope edits.
Here's what one of our clients said: "What sold us on Goodspeed wasn't the pitch—it was how quickly they shared a written recap of our first call. That single habit told us everything."
Overreliance on Buzzwords
If every answer comes back as "agentic", "AGI-ready", or "multi-modal orchestration" without a concrete implementation detail, the team may be selling vibes, not capability.
How-to: Ask follow-up questions at one level deeper. A real Claude Code developer can talk about tool schemas, context management, and failure modes without the buzzwords.
Lack of Technical Depth in Discovery Calls
Absence of Verifiable Reviews
Evasive Answers About Ownership and Handover
Final Thoughts
Red flags are rarely loud—they're quiet inconsistencies that compound. Treating each warning sign as a data point, rather than a single dealbreaker, gives you a clearer picture of whether an agency can actually deliver.
Recap of Core Steps
Watch for vague scopes, unrealistic promises, and pre-discovery pricing in proposals.
Pressure-test portfolios, process documentation, and early communication before signing.
Demand technical depth, verifiable reviews, and clean ownership terms in final diligence.
Next Steps
A short checklist used consistently beats a long one used once. Pair this guide with the companion reads below to sharpen your diligence before your next shortlist call.
For deeper insights:
Check What Questions To Ask A Claude Developer Before Saying YES to stress-test any agency's technical depth.
Read How to Evaluate the Credibility of a Claude Development Agency for a structured credibility framework.
Spotting red flags is less about paranoia and more about pattern recognition. Slow down, ask sharper questions, and trust the small signals—they almost always tell the truth.
If you'd rather work with a team that welcomes scrutiny, book a free consultation with Goodspeed.
Written By
Founder of Goodspeed