The cost mostly comes down to two things: how much of the operation you're automating, and whether we just build it or also operate it afterward. A single workflow, say, sending calibration-due recall notices on a schedule and logging who responded, is a small, contained build. A multi-part operations system that also generates certificates, logs equipment intake, and flags overdue instruments to a technician is bigger, because it has to read data from more places, make more decisions, and handle more exceptions correctly on its own. A full custom product, like a customer-facing portal where clients log in, request calibrations, and see certificate history, is bigger again: it needs its own database, logins, and ongoing upkeep. Build-only work stops once it's delivered and handed off. Build-and-operate means we keep it running, watch for failures, and fix what breaks, which is a different, ongoing commitment than a one-time build.
For a calibration lab specifically, the repetitive load usually breaks into a few pieces: reminding customers when their instruments are due for recalibration (which is really a recurring-revenue engine, not just an admin task), generating and formatting certificates once a calibration is done, and logging equipment as it comes in and out the door. Each piece can be automated on its own, or combined into one system that ties recall, intake, and certification together so nothing falls through the cracks between them. What can't be automated is the calibration itself: taking the measurement, judging whether a result is in tolerance, and putting a certified signature on it. That stays a qualified technician's job. The system's role is to remove the paperwork and chasing around that work, not the measurement.
We don't work from a price list. Each engagement is quoted on the value the system creates for that lab, which depends on things like how many customers you're tracking for recalls, how much staff time goes into formatting and sending certificates, and how often a recall gets missed and costs you repeat business. A rough way to size this up for your own lab: add up the hours someone currently spends scheduling recall notices, chasing overdue customers, formatting certificates, and logging intake by hand, and weigh that against what it's worth to never let a recall slip. The honest way to get a real number is a short conversation about your specific workflow, not a generic quote.