A bad software engagement does not just waste money — it can set a business back twelve months, hand your idea to a vendor who treats it carelessly, and leave you with code you can't maintain or hand off to anyone else. The industry is full of agencies that look excellent at the proposal stage and disappear once the project gets hard.

These are the specific signals, drawn from pattern-matching across dozens of vendor relationships, that reliably predict a painful engagement. Some of them are easy to miss in a slick sales process. None of them are excusable.

They quote a price before understanding the project

If an agency responds to your project description with a quote inside 24 hours — especially a confident flat-fee quote — without asking clarifying questions, they are not pricing your project. They are pricing a project they have done before and assuming yours is the same. This assumption causes the single most common form of scope disaster in software: a quote built on misunderstood requirements that gets renegotiated upward six weeks in.

A trustworthy vendor takes time to ask questions. They may conduct a paid discovery sprint before quoting the build. That process costs you a small amount upfront and saves a very large amount later. See how to write a software project brief that gets accurate quotes — the clearer your brief, the easier it is to tell who is reading it seriously.

They cannot name a single technical tradeoff they've made

Ask an agency: "What's a technology choice you made on a recent project that you'd reconsider today, and why?" Great teams have a real answer. They have opinions about frameworks, about architectural decisions, about the cost of moving fast early. An agency that pivots to "we always use the best tool for the job" — without naming what that tool is or why — is telling you they do not think at that level.

Related: can they explain their last major technical decision in language a non-technical founder can follow? If no — or if the explanation requires you to know what a serverless architecture is before they'll engage with you — that is a communication failure that will compound throughout the project.

The portfolio does not include real clients you can call

Most agency portfolios are curated for aesthetics, not verifiability. Logos of past clients, screenshots of products, a few testimonials. What you want: the name of a client, their contact info, and permission to call them. If an agency can't give you at least two past clients you can speak with directly, that portfolio is marketing, not evidence. If they have NDAs across the board, ask them to broker an introduction — a confident agency with happy clients can usually arrange that.

They promise a fixed timeline for an unfixed scope

Timelines are set by scope and resources. If the scope is not fully defined — and in the early stages of most projects, it is not — any timeline is a guess. An agency that commits to "six weeks to launch" before the spec is locked is guaranteeing a timeline for a project that does not yet exist. The real deadline slips once the project gets real. For a deeper look at how this dynamic plays out, read how to prevent scope creep on a software project.

They can't explain who specifically will work on your project

You hire an agency — but who, specifically, is building your product? A senior team of four, or two junior developers and a project manager who subcontracts the rest? Ask: "Who will be the lead developer on this engagement, and can I speak with them before we sign?" An agency that hedges on this answer has staffing practices you should understand before committing. Many agencies have excellent senior talent on the sales call and a very different team on the execution.

There is no plan for what happens after launch

Software is not a deliverable — it is a living system that will need fixes, updates, security patches, and scaling work from day one of real usage. An agency that only talks about the build, never about post-launch support, maintenance pricing, or how you'd transition to an in-house team later, is not thinking about your long-term interests. Ask explicitly: "What does the relationship look like 90 days after launch?" Their answer tells you everything about whether they are a partner or a vendor. For protection beyond this, see what happens if your developer disappears.

The TTGC approach: no red flags by design

At Through The Glass Creatives, Ravve Jay Prevendido has built the agency specifically to eliminate the patterns above. Discovery is always scoped and paid. Quotes follow specs, not conversations. Ravve personally leads every technical engagement — there is no handoff to a junior team after the sale. And every engagement includes an explicit post-launch plan with documented handover materials, because TTGC's goal is client independence, not client dependency.

The agency that is too eager to start building is the agency that hasn't done enough thinking. Enthusiasm is not a substitute for process.