We turn down projects regularly. Not because we don't need the work, but because taking on the wrong engagement is worse for everyone involved than not taking it on at all.
This is worth explaining, because the reasoning behind it is the same reasoning that shapes how we work with the clients we do take on.
When the budget doesn't match the expectation
The most common version of this is a client who wants a Growth Build, a properly engineered store with a commercial roadmap, at a price that reflects a basic theme customisation.
We understand why this happens. Most merchants haven't had enough experience with different levels of Shopify development to know what quality costs. They've seen agencies quote widely varying numbers for similar-sounding briefs and assumed the variance is mostly margin. Sometimes it is. Often it isn't.
When the gap between what the brief requires and what the budget allows is too large to bridge without compromising on something material (the quality of the build, the depth of the roadmap, the time spent in discovery), we say so directly. Sometimes that leads to a scoped-down engagement that works for both sides. Sometimes it doesn't, and the client goes elsewhere.
What we don't do is take the project, cut corners to fit the budget, and deliver something that doesn't perform. That produces a client who's unhappy, a store that doesn't work, and a case study we can't be proud of.
When the store isn't ready for what they're asking for
Occasionally a merchant comes to us wanting a specific feature or engagement that their store isn't actually ready for.
The most common version is a brand wanting a Growth Build + Roadmap when what they actually need is to validate their product and business model first. A finely engineered Shopify store with a six-month commercial roadmap is a meaningful investment. If the product hasn't found its market yet, that investment is premature. The store will need to be rebuilt again once the model is clearer, and the roadmap will need to be rewritten from scratch.
In these cases, we'll say what we see. Sometimes that means recommending a more modest starting point and coming back to the Growth Build when the fundamentals are in place. Sometimes it means the client decides they're further along than we think. Either way, they leave the conversation with an honest perspective they can make a decision from.
When the timeline isn't realistic
We work to a delivery standard that requires adequate time. An 8 to 12 week build that a client needs in four weeks is not a build we'll do in four weeks by working faster. It's a build that will be missing something (discovery depth, testing coverage, integration quality) that matters.
When a timeline is driven by an arbitrary deadline rather than a genuine commercial need, we push back. When it's driven by a real constraint (a product launch, a retail partnership, a seasonal peak), we look at what can genuinely be delivered in that window and scope accordingly. If the real scope doesn't fit the real timeline, we say so before taking the money.
Rushed builds create problems that the client lives with long after the deadline has passed.
When the brief is outside our scope
WebMaze builds and maximises Shopify stores. We don't run paid media. We don't manage SEO campaigns. We don't create content. We don't manage social channels.
Sometimes a client comes to us wanting all of those things wrapped into a single engagement. We refer them to the specialists who do those things well. If they also need Shopify development, we can work alongside those specialists as the store's execution partner. But we're not going to take on work outside our scope and deliver it to a standard we can't stand behind.
This is a boundaries issue as much as a capability one. Agencies that say yes to everything tend to be mediocre at most of it. The discipline of staying in your lane, and being genuinely excellent within it, is what produces work worth talking about.
When the working relationship won't work
This one is harder to articulate but important to be honest about.
Some clients need a development team that will execute whatever they're told, without pushback, on demand. That's a legitimate need. It's not how we work.
We come to engagements with observations. We flag things we see in the store that aren't performing. We push back when a brief has a flaw. We ask questions about the commercial rationale behind a request when the answer isn't obvious. Some clients find this valuable. Others find it frustrating.
When it's clear early in a conversation that what a client wants is pure execution without perspective, or that the relationship dynamic isn't going to support honest communication, we acknowledge it and refer them on. A relationship that starts with misaligned expectations tends to get worse, not better.
What this means for clients we do take on
The reason for being selective is not exclusivity for its own sake. It's that the quality of what we deliver is directly tied to the conditions under which we deliver it.
A client with a realistic budget, a clear brief, and an appetite for honest communication gets a team that's fully invested in their store's performance. A client where the engagement is compromised from the start gets something less, and so do we.
The engagements we're proudest of, the stores that perform, the clients who come back, the case studies that actually say something, are the ones where the conditions were right from the first conversation.
That starts with being honest about fit before any work begins.
If you're not sure whether a WebMaze engagement is the right fit for what you're trying to do, the best thing to do is tell us about your store. We'll give you a direct, honest read, including if we think something else would serve you better.