Why we decline project work that breaks the retainer
Capacity limits protect the clients already on retainer.
We regularly decline project work that would stretch the team thinner than the retainer model allows. That is not a marketing line - it is a capacity decision, and it is core to how GNShift works.
We run small on purpose. Every client gets a senior-led team that knows their stack. The moment we say yes to a build that needs staffing we do not have, that promise breaks.
Most of what we decline falls into two buckets: scope too large for our bench, or a timeline too aggressive for the quality bar we hold. A hard-deadline commerce migration with no discovery room, or a Webflow rebuild with dozens of unique templates and a compressed calendar, usually needs a staffing model we do not run.
Saying no protects the work already underway
Retainer clients pay for continuity - the same people who built the system help maintain it. That only works if those people are not simultaneously ramping on too many new builds. When we decline project work, retainer clients get more attention, clearer response times, and fewer context switches on their account.
Every yes to the wrong project is a no to the right one already on retainer.
We refer work we cannot take well. Strong teams exist for large one-off builds. Our edge is depth on Webflow and Medusa for teams that want a long-term partner, not a one-time vendor.
What we look for instead
The engagements we say yes to look like retainers: ongoing commerce work, CMS evolution, performance and conversion iteration. Projects with a clear finish line and a team on the other side that wants to keep working together after launch. That is the model. Declining the wrong work is the retainer doing its job.
When should you break a CMS collection into multiple?
When two kinds of content genuinely have different fields and different places they get used — not just because one has slightly more variety.
How do you handle nested references in Webflow?
Keep references to one hop wherever possible. If you find yourself needing two hops to render a single field, flatten the second collection into the first.
Do CMS items count toward site plan limits?
Yes — every collection item counts toward your CMS item limit regardless of whether it renders a page.
Enjoyed this? We build the systems we write about.
Fixed monthly retainers on Webflow and Medusa JS — by the same people who wrote this.