Working With a Development Agency

If you don't have technical co-founders, you'll likely work with an external development agency. Choosing the right one and managing the relationship well makes the difference between success and disaster.

How to Evaluate an Agency

Portfolio of relevant work. Does the agency have examples of projects similar to what you're building? If you're building a SaaS product, have they built SaaS products? If you're building a marketplace, have they built marketplaces? Similar experience means they've solved problems you'll face.

Ask to speak with past clients. References should be clients willing to talk about both the good and the challenges. If they only have glowing reviews, dig deeper.

Technical approach and process. How do they approach development? Do they do design before development? Do they have a requirements gathering process? Do they have testing and QA? Ask about their process—it reveals how serious they are.

Who actually works on your project? This is critical. If the person who pitched your project is not the person who will work on it, that's a red flag. The salesperson is often different from the execution team, but you want to meet the team that will actually build your product.

Team composition and stability. Is the core team permanent or is staff constantly churning? High turnover is a warning sign. Ask about team size, experience levels, and whether they use subcontractors or do the work in-house.

Communication and transparency. Do they provide regular updates? Can you see work in progress? Do they proactively flag risks or do they wait until deadlines are missed? Good agencies communicate frequently and transparently.

Technology expertise. Have they built with the technology stack you want to use? If you want to use React and Node.js, do they have deep expertise or are they learning it on your project?

Red Flags

Won't show you past work. Professional agencies have portfolios and references. If they're secretive about past projects, that's suspicious.

Promises a fixed price before seeing requirements. If they quote before you've defined scope, they're guessing. A good agency says: "We can do requirements gathering first, then estimate" or "Based on what you've told us, initial estimate is $X-$Y range."

No discovery or requirements phase. If they want to start coding immediately, that's dangerous. Good projects start with discovery and requirements gathering.

High staff turnover. If you ask about their team and they mention recent departures, ask about it. Some turnover is normal. Constant turnover suggests problems with management or culture.

Vague about process. If they can't clearly explain their development process, testing process, or how they handle changes mid-project, that's a warning.

Unrealistic timelines. If they promise to build in half the time of other agencies, be skeptical. Either they're optimistic (and will miss deadlines) or they're planning to cut corners.

Green Flags

Asks hard questions about your requirements. Before quoting, a good agency digs into your requirements. They want to understand the problem deeply. This is time investment that suggests they care about getting it right.

Has a clear development process. They explain their approach to requirements, design, development, testing, and deployment. They have checklists and standards.

Transparent about team structure. They tell you who will work on your project, their experience level, and who the backup is if someone leaves.

Proposes a discovery phase. "We recommend 2 weeks of discovery to understand your requirements deeply, then we can give you a more accurate estimate." This is professional.

Discusses testing and QA. They talk about how they test, how they handle bugs, quality assurance processes. Not all agencies give this serious attention.

References you can actually call. They provide client references (not just links) who are willing to discuss both positives and challenges. Vague references are suspicious.

Key Questions to Ask

On team and people:

• Who will be my day-to-day contact?
• How much of their time will be allocated to my project?
• What happens if a key person leaves mid-project?
• Do you use subcontractors or do work in-house?
• What's your average staff retention rate?

On process and communication:

• What does your development process look like?
• How do you gather requirements?
• What communication cadence can we expect? (Daily? Weekly? As-needed?)
• Can we see progress (staging environments, demos)?
• How do you handle change requests mid-project?

On timeline and costs:

• What's your proposal process and timeline?
• What payment terms do you require?
• How do you handle scope changes and their impact on budget/timeline?
• Is there a penalty if you miss the deadline? (Usually not, but it's fair to ask.)

Managing the Agency Relationship

Weekly check-ins. Meet weekly with your agency contact (or more frequently if things are moving fast). Review progress, discuss blockers, align on next steps.

Staging environment for review. Don't wait until launch to see what's being built. Ask for a staging environment where you can review work-in-progress regularly.

Milestone sign-offs. At each milestone, review the work before the next payment is released. Don't pay if you haven't verified the work meets expectations.

Document decisions and changes. When you discuss a change or a decision is made, document it. Send an email: "We discussed adding X feature today. Here's my understanding of scope, timeline, and cost impact. Please confirm." This prevents misunderstandings.

Escalate issues early. If something doesn't feel right, bring it up immediately. Don't wait until a milestone deadline. Early escalation gives time to fix problems.

Provide timely feedback. If the agency is waiting on you for decisions or requirements, provide them promptly. Don't be the bottleneck.

The Offshore Agency Risk

Many agencies are offshore (India, Philippines, Eastern Europe, etc.). This is not automatically bad, but there are specific risks:

Communication time zones. When you need an answer, they're sleeping. Complex discussions require real-time conversation. Time zone differences slow communication.

Cultural differences in expectations. Different countries have different standards for what "done" means. Some cultures are indirect in communication (they won't tell you they don't understand something). Some are uncomfortable pushing back on clients.

Quality variance. Good offshore agencies are excellent. Bad ones are really bad. There's more variance than with local agencies.

Turnover. Staff at offshore agencies sometimes leave for better opportunities. If your dedicated developer leaves, the agency replaces them, but there's knowledge loss.

Offshore agencies work well when:

• You have very clear, well-documented requirements (less need for real-time discussion)
• You work asynchronously (document decisions, don't expect real-time responses)
• You've worked with the agency before (trust is established)

Offshore agencies are risky when:

• You need frequent, real-time collaboration
• You have ambiguous requirements that need discussion
• You need senior expertise (juniors are cheaper offshore, but quality matters for complex work)

When to Walk Away

If an agency:

• Misses major milestones without explanation or plan to fix
• Won't communicate or is defensive about delays
• Delivers significantly lower quality than expected
• Ignores your requirements and builds something different
• Won't discuss or escalate issues

Then you have a problem. Most contracts allow termination, though you'll owe for work done. It's better to walk away and start with a new agency than to stay with one that's not delivering.