The biggest cost driver is scope. A fabricator's repetitive work usually splits into separate jobs: turning a customer's rough dimensions into a quote, booking template appointments, coordinating slab selection between the customer and the yard, and scheduling install crews around cure times and site access. Automating one of these, say quote generation from dimensions, is a contained build. Automating several as one connected system, where a quote can flow into a scheduled template visit and then into install booking without anyone retyping information at each handoff, is bigger because the pieces have to talk to each other and to whatever software you already run: CRM, calendar, texting, invoicing.
The other driver is build-only versus build-and-operate. Build-only means Precipitate designs and ships the system and your team owns it afterward, including any breakage, any reconnection when a tool changes, and any tuning as your process shifts. Build-and-operate means Precipitate keeps it running: checking that quote requests are turning into quotes, that an unanswered slab-selection message gets a retry or gets escalated to a person, that a scheduling conflict gets caught before a crew shows up at the wrong address. Precipitate's default is to operate what it builds rather than hand it off and disappear, which is part of why operating costs more than a one-time build.
Because the value a system creates for a small shop differs from what it creates for a fabricator running several crews and a busy showroom, Precipitate prices each engagement on that value instead of publishing a rate card. To judge whether it's worth it, look at where dimensions, slab photos, and scheduling details are currently handled by phone, text, or sticky note, and how often that handoff causes a delay, a double-booking, or a customer who never hears back. If that happens often enough to matter, a short conversation about your specific workflow is the fastest way to find out what it would take and cost.