Most D2C founders only learn what a bad Shopify agency looks like after they've already paid for one. Projects stall. Scopes bloat. The site launches six months late with technical debt baked into the foundation. By then, the contract is signed and the leverage is gone. This post exists to help you avoid that situation entirely. Before you commit to a Shopify agency — whether it's for a new build, a platform migration, or a CRO-driven redesign — run through these 12 warning signs. They're drawn from the patterns that consistently separate weak partners from capable ones. By maintaining a rigorous internal evaluation protocol, you shift the power dynamic away from opaque service providers toward a transparent, performance-oriented partnership. Assessing the operational maturity of a development firm requires looking beyond their glossy case studies to understand the mechanical realities of their project management, code quality standards, and long-term business scalability.
The Project Supply Agency Vetting Checklist
Use this before signing any Shopify development contract. Each item below is a filter, not a formality. This framework serves as a critical defense layer, allowing leadership teams to quantify the hidden risks associated with external development talent and ensuring that budget allocations directly correlate with measurable technical output rather than speculative promises.
Red Flags in the Sales and Discovery Process
1. They skip a discovery phase entirely — or charge nothing for it?
Discovery is where a competent agency learns your business: your catalog structure, your integrations, your customer journey, your edge cases. If an agency moves straight from introductory call to proposal without asking substantive questions, they're either guessing at scope or padding it to cover their uncertainty. Paid discovery isn't a red flag. Skipped discovery almost always is. A professional discovery process must involve technical architects and business analysts who probe into your specific data architecture, current API limitations, and long-term marketing objectives. When an agency attempts to bypass this, they are essentially ignoring the unique constraints of your store, which almost guarantees that the resulting codebase will lack the flexibility required to scale. Without deep discovery, you are paying for assumptions that inevitably crumble upon real-world deployment, leading to endless fix cycles and budget overruns that could have been avoided with a simple upfront analysis.
2. The proposal arrived within 24 hours — was it actually tailored?
A detailed, well-reasoned Shopify proposal takes time to write. If you receive a polished document the morning after your first call, look closely. Generic proposals with your company name dropped into the header are a signal that the agency is running a volume-based sales process, not a fit-based one. Templated scopes lead to misaligned builds. Genuine proposal engineering requires mapping your unique requirements to specific development sprints, resource allocations, and technical milestones. If you are receiving a commoditized document, the agency is likely using a "one-size-fits-all" delivery model that fails to account for the nuances of your tech stack, third-party middleware, or custom integration needs. High-performing agencies understand that a proposal is a technical commitment; they spend time evaluating your current store's health before making promises they intend to keep.
3. They can't explain what they won't do?
Ask directly: "What types of projects or clients are outside your wheelhouse?" A strong agency has clear boundaries — specific platforms, project scales, or business models they don't serve well. An agency that claims to do everything well does nothing well by default. Expertise is defined as much by what a team chooses to decline as by what they accept. If an agency claims they can handle everything from high-volume custom B2B headless setups to basic theme tweaks with equal efficiency, they lack the specialized workflows necessary for high-level Shopify execution. True specialists identify specific problem spaces where they provide maximum ROI; by avoiding generalized service models, they ensure their developers remain deeply focused on the current iteration of the Shopify platform, liquid templating, and modern storefront API standards.
Red Flags in Portfolio and Proof
4. Their Shopify portfolio is thin, anonymous, or outdated?
Case studies don't need to be elaborate, but they should exist and be verifiable. If an agency's portfolio shows three stores with no client names, no context, and screenshots from 2021, ask why. Legitimate confidentiality happens — but it shouldn't apply to every single project. Ask for live store URLs. Click through. Check the mobile experience, page load speed, and checkout flow. The work speaks. A lack of transparent portfolio items often masks a reliance on white-label outsourcing or an inability to maintain long-term relationships with clients. When evaluating these case studies, look for evidence of complex liquid logic, custom apps, or unique integration solutions that demonstrate real engineering capability rather than mere template installation. Transparency in work history is the simplest indicator of professional accountability.
5. They can't provide a reference from a comparable project?
Not just any reference — one from a project similar to yours in scope, industry, or complexity. If an agency has done solid work for brands like yours, they'll have someone willing to take a 15-minute call. If they deflect, offer generic testimonials, or say all their clients prefer anonymity, treat that with skepticism. A credible agency views past clients as their most powerful sales asset and will facilitate introductions to demonstrate their reliability. When you do get to speak with a reference, ask pointed questions about how the agency handled unforeseen bugs during the build, their response time during mission-critical errors, and their capacity to adapt when the business requirements changed mid-sprint. A company that cannot provide this level of social proof is likely hiding a history of project failures or poor communication standards.
6. Their own digital presence is weak?
This isn't about having a beautiful agency website. It's about coherence. An agency that advises on Shopify stores, conversion optimization, or ecommerce growth should demonstrate at least baseline competence in their own positioning, content, and technical execution. If the agency site has broken links, no published work, and a contact form that leads nowhere, take note. Your agency's digital footprint is their own personal store; if they cannot manage their own front-end performance, documentation, or brand messaging, they are fundamentally unequipped to manage the multi-million dollar revenue engine that is your ecommerce site. Look for evidence of thought leadership through technical blog posts or documentation, as these are strong indicators that the agency invests in the ongoing education and refinement of their own internal development culture.
Red Flags in Scope and Contracts
7. The contract has no clear change order process?
Scope creep is the most common source of blown budgets and strained relationships on Shopify builds. Every professional contract should define how out-of-scope requests are identified, priced, and approved before work begins. If a contract doesn't address this, you're working without a safety net. This is non-negotiable. Request it explicitly if it's absent. A formal change order protocol ensures that both parties maintain a shared understanding of what constitutes "extra" work versus what is a defect fix. Without this framework, you leave the door open for arbitrary billing and project stalling, where the agency may demand more funds without providing a clear explanation of the additional labor involved. Always ensure the process includes a mandatory written sign-off that itemizes the new scope and the associated timeline impact.
8. They own the code until final payment — or beyond?
Some agencies retain IP ownership until the final invoice is cleared. That's relatively standard. What's not acceptable is an agency that retains rights to your theme, custom code, or integrations after the project closes, or that requires you to keep them on retainer as a condition of receiving your own files. Read the IP clauses. Get legal eyes on this if needed. You should have full, unrestricted ownership of your intellectual property upon final payment, including access to version control repositories like GitHub or Bitbucket. Any language in the contract that suggests a recurring fee to access your own proprietary assets is a red flag indicating a "vendor lock-in" strategy, which prevents you from switching developers or optimizing your stack in the future.
9. The timeline has no milestones or defined deliverables?
"We'll have it done in 10 weeks" is not a project plan. A serious agency will break the engagement into phases — discovery, design, development, QA, launch — with defined deliverables and sign-off points at each stage. Vague timelines protect the agency, not you. A project plan should act as a transparent roadmap, detailing exactly what functionality is expected at every checkpoint. Without granular milestones, you are essentially flying blind, unable to assess whether the project is on track until the deadline passes. Demand a Gantt chart or a phased project management dashboard that allows you to monitor progress in real-time. If an agency resists this level of visibility, they are likely concealing inefficiencies or lack of organization within their internal team.
Red Flags in Communication and Team Structure
10. You'll never speak directly to the developer?
Sales-to-delivery handoffs are normal. Having a dedicated account manager is fine. But if the agency structure means you will never have direct contact with the person actually building your store — no shared Slack, no technical calls, no access when something breaks — you have no visibility into your own project. Insist on at least one introductory call with the lead developer before signing. A project thrives on clear communication between the business owner and the technical implementer, as this alignment prevents the "telephone game" where requirements are misinterpreted by account managers who lack the necessary coding experience. When you have access to the developer, you gain the ability to provide immediate feedback on technical constraints, allowing for faster iterations and higher quality builds that strictly adhere to your functional requirements.
11. They offshore work without disclosing it?
Offshore development isn't inherently a problem. Undisclosed offshore work is. If an agency prices like a senior domestic team but quietly routes builds through a junior offshore studio, you're getting a mismatch in accountability, quality control, and communication bandwidth. Ask directly: who builds the work, where are they based, and what does their QA process look like? Lack of transparency regarding team structure is the most common way agencies inflate profit margins at the expense of your project's integrity. When you know who is working on your project, you can better understand the time zone overlap, communication expectations, and the specific QA workflows being utilized. True partners are proud of their team's location and expertise; if they hide it, assume there is a reason for the secrecy.
12. They can't articulate a post-launch support model?
Launch day is when real problems surface. Page speed regressions, checkout errors, integration failures under actual traffic — these are not hypothetical. If an agency doesn't have a defined process for post-launch support (even a time-limited warranty period), you're taking on all the risk once the final invoice is paid. Get the support terms in writing, including response time expectations and what's covered. An agency should provide a formal "hyper-care" period immediately following launch, during which they monitor performance metrics and resolve any critical issues that arise. Without a clear commitment to support, you are abandoned at the most vulnerable point of the project lifecycle, potentially leaving your store's stability and revenue at risk while the agency moves on to the next client.
Common Trade-Offs Worth Understanding
Vetting an agency thoroughly takes time. Some founders skip the process to move fast, which is understandable under pressure. The trade-off is downstream: a rushed hire often produces a slower build, more revisions, and a higher total cost than a careful hire would have. The other common trade-off is price versus process. Agencies with structured discovery, clear contracts, and defined communication protocols tend to cost more upfront. They also tend to produce better outcomes, fewer surprises, and cleaner handoffs. Choosing the lowest bid without evaluating process quality is a false economy on most Shopify builds above basic complexity. A few other tensions worth naming:
Speed vs. diligence. Fast proposals save your time today and often cost more of it later.
Relationships vs. references. A warm referral from your network is valuable, but it's not a substitute for reviewing actual work.
Flexibility vs. accountability. Agencies that are highly accommodating in the sales process are sometimes avoiding hard conversations that will surface during delivery instead.
These trade-offs are fundamental to the service industry; smart founders learn that paying for process is essentially paying for insurance. When you opt for a cheaper, less process-driven firm, you are inadvertently accepting the burden of managing their internal disorganization, which often consumes more time and resources than the original savings justify.
