As an Amazon Associate we earn from qualifying purchases.
dealing wiht scope creep in client-based MakerMechanics projects is seriously testing my patience. I’m building a custom automated watering system for a client’s greenhouse, and what started as a simple moisture sensor and programmed valve setup is rapidly expanding. Now they’re talking about integrating weather data, remote monitoring via an app (which I don't specialize in), and soil pH sensing.
it feels like every conversation adds another layer of complexity that wasn't in the original agreement. I've tried to be accommodating, figuring a little adaptability is good for client relationships. But at this point, it's threatening to derail the entire project timeline and, frankly, my profit margin.
Anyone else in a similar situation? How do you effectively manage this? Do you have a go-to clause in your contract for dealing with expanding requirements, or is it more about ongoing communication and carefully (and firmly) restating the initial scope? I'm considering suggesting phasing the project, tackling the original scope first and then addressing "nice to have" features in a future iteration, but I'm worried about losing the client to someone who promises them the moon upfront.