Should I Consider Terminating a Challenging Client Engagement?

Navigating complex client projects can sometimes lead to significant stress and uncertainty about the future. Recently, I’ve been involved in a project that has raised some important questions about whether to continue or step away, especially when complications escalate unexpectedly. I’d like to share my experience and seek advice on how best to proceed.

Initial Project Scope and Execution

Earlier this year, a client I previously developed a website for approached me with a new goal: they wanted to list and sell products online. I recommended launching a Shopify store linked to their existing website, a solution I’ve implemented successfully for multiple clients. The key enhancement they requested was tiered wholesale pricing—something easily attainable through off-the-shelf Shopify apps.

I drafted a comprehensive contract outlining the project scope, including my role in selecting and installing an appropriate app without custom development. Upon approval, I proceeded with designing prototypes and building the Shopify store based on an existing theme. However, gathering product data from the client proved challenging—they provided the content, but communication was slow and inconsistent, requiring me to spend extra hours chasing information and verifying details.

Additional Demands & Project Delays

To keep the project on track, I ended up handling much of the data entry and content refinement myself, leading to additional work beyond the original scope. Although the client agreed this should be billed as extra work, I am still awaiting payment, which I consider deserved given the circumstances.

Unexpected Complications and a New Stakeholder

Things took a turn when the client’s partner, unfamiliar with the project’s earlier details, stepped in. She provided a lengthy list of requested changes—many of which contradicted previously approved elements—and introduced complex new features such as customer account restrictions, quote generation, purchase order management, and credit limits, inspired by larger competitors’ wholesale systems. These additions are ambitious and will require significant development efforts.

Timeline and Feasibility Concerns

The new stakeholder expects these extensive modifications within just two weeks. As a solo developer, I sense that meeting such a tight deadline with the scope of requested features may be unrealistic, especially considering the depth of customization needed. While some features could be integrated via existing apps, the overall complexity and the divergent expectations pose serious concerns.

Professional Reflection and Client Relationship

This situation has left me questioning whether I should continue with this project. The increasing demands, the involvement of an additional stakeholder with different expectations, and the aggressive timeline create a challenging environment. I worry that attempting to fulfill