Cost tracks scope. Automating one workflow, such as chasing a family for sign-off on a design proof or flagging a cemetery permit that's close to its deadline, is a small, contained build. Tying that together with paperwork tracking and install-date coordination into one system that reads your CRM and updates your calendar is a bigger job, because it has to coordinate across more tools and more decision points. And if what you actually need is a full web product, an online proofing portal with customer logins and payment, that's a different category of build again: real software, not a workflow.
The second driver is whether we build it and hand it over, or build it and keep running it. A build-only project ends at deployment. Build-and-operate means we keep watching after launch: catching a proof that's gone quiet, a cemetery office that hasn't replied, an install date that's drifting, and fixing or flagging it before it becomes a problem for a family waiting on a headstone. Some of this can't be handed to a system at all, and we'll say so. Talking a family through a design revision, or making the final judgment call on how a proof looks before approval, needs a person. What we automate is the tracking and chasing around those moments, not the moments themselves.
We don't publish a price list because the honest number depends on your scope and on build-only versus build-and-operate, and one figure for every monument company would be a guess dressed up as fact. We price each engagement on the value the system creates for you. To judge whether it's worth it, look at how much staff time currently goes into approvals, permits, and scheduling, and weigh that against having a system own the follow-up so your team only steps in for decisions that need a person. A short conversation about your specific workflow is what gets you an actual number.