The main driver is scope. A single workflow, say turning photographed items into priced listings, is a contained build. A fuller system that also handles sale scheduling, updates to client families, and announcements to your buyer email list touches more tools and more decisions, so it costs more to build and more to keep reliable. Some of this work is judgment heavy: pricing a sentimental item, or telling a grieving family their timeline changed, is not something we hand to software. We map the manual work first and say plainly which parts a system can own and which still need a person.
The second driver is whether it is build-only or build-and-operate. A build-only project hands you a working system and stops there. Build-and-operate means we keep running it: watching for failures, fixing what breaks, adjusting as your sale schedule and vendor tools change. Operating costs more over time than a one-time build, but for estate sale work, where sales happen on tight, real deadlines and a broken listing feed or a missed family update has real consequences, most owners end up wanting the system actually run, not just handed over.
We do not have a price list, and we are not going to invent a number here. Pricing is quoted per engagement, based on the value the system creates for your business, not billed by the hour. The way to judge whether it is worth it is to look at how much of your week goes into repetitive coordination: listing photos, syncing calendars, answering the same family questions, sending the same announcement emails, versus judgment calls only you should make. If that repetitive share is large, a short conversation about your actual workflow is the fastest way to find out what it would take and whether it makes sense.