Pricing
Three ways to buy, with the real numbers on the page. A paid pilot at $25,000 to $75,000, a Pro subscription at $5,000 to $15,000 per month, and a custom Enterprise tier. Priced per facility, not per machine. This page also sets out what the fee does not buy, so you can rule us out without booking a call.
Every plan includes onboarding and a dedicated success engineer. Convert after your pilot and the full pilot fee credits toward your first year. The figure is confirmed in writing before kickoff.
$25k-$75k8-week engagement · scoped by lines & connectors
Prove ROI in one facility before scaling to the network.
★ Recommended
$5k-$15kper month · from $5k for a single facility
Full platform access with advanced analytics across your operation.
Customunlimited scale
Private deployment for regulated and multi-site operations.
Design-partner pricing - rates shown apply to the current cohort and are locked for your agreement term. No lock-in: either party can end the agreement with 30 days' written notice, and you leave with a full export of your data.
A spread of $25,000 to $75,000 is wide, and the spread is scope, not negotiation. Three things move the number, and you can estimate your own position in the range before you ever speak to us.
We scope this in the first conversation and quote a fixed figure before anything is signed. It does not move during the eight weeks. If the honest answer is that eight weeks will not prove anything on your scope, we say so then, not in week six. The mechanics of the engagement are laid out on the pilot page.
Publishing a price is only half of the job. Here is what the number does not buy. None of these are fees waiting behind a signature. They are boundaries, and they are better known now than in week three.
The integrations page lists exactly which connectors exist today, which is the fastest way to see whether your stack lands inside the included two or outside them.
This category usually charges per machine or per asset monitored. That model has a structural problem. It makes the tenth machine cost roughly what the first one did, so the cheapest configuration is always the one that sees the least. Teams end up rationing visibility to protect a budget line, which is precisely backwards: the machine nobody could justify connecting is often the one quietly losing the money.
KaizenFlow prices per facility. Pro starts at $5,000 per month for a single facility. Connect one line or connect the whole plant, and the subscription figure does not change. Adding machines makes the analysis better, because more of the plant is visible to the ensemble that ranks losses by dollar impact, and none of it changes what you pay that month.
The tradeoff is honest and worth stating: if you only ever intend to monitor two machines, a per-machine tool will be cheaper than a facility subscription. Per-facility pricing pays off when you want the whole plant in one queryable plane. It also assumes there are signals to read. Plants with older machines, no PLCs worth reading, and no ERP data are better served by Guidewheel's clip-on sensing, and we say so on our Guidewheel comparison. KaizenFlow needs signals to read.
We do not offer one, and the reason is not scarcity marketing. A trial that means anything has to connect to your MES, SCADA, ERP, or historian, map your tags, and baseline real production against your own cost rates. That is a fortnight of engineering before a single number is trustworthy. A self-serve sandbox would only ever show you our demo data, and our demo plants are fictional composites. You would learn nothing about your plant.
So the paid pilot is the trial. Eight weeks, a fixed fee, and it credits in full against your first year if you continue. In practice a partner who converts has paid for the pilot only if they walk away, and a partner who walks away still keeps the verified before and after savings report. That is the honest version of a free trial: you carry real risk only if we fail to find anything worth keeping.
Implementation is not a separate line item, because implementation is the pilot. Connecting, calibrating, mapping your cost drivers, and standing up the baseline are the work the pilot fee pays for. There is no onboarding charge stapled on afterwards, and onboarding plus a dedicated success engineer are included on every plan, pilot included.
There is no usage meter either. The pilot figure is agreed before kickoff with no usage-based surprises, and a busy quarter does not generate an invoice you did not plan for. Rates are locked for your agreement term. If we adjust pricing, it happens at renewal with at least 30 days' written notice, which is written into our terms rather than promised on a slide.
If a number ever moves, it moves because scope moved and you agreed to it in writing first.
There is no lock-in, and the exit is symmetric. Either party may terminate the agreement with 30 days' written notice. On termination we provide a data export for 30 days, and after that window your data is permanently deleted in line with our retention policy.
Your data is yours the whole time. Full export and API access are on every plan, not gated behind a tier, because a platform that holds your production history hostage is charging you for the exit rather than the product. Metrics are retained for 12 months by default and audit logs for 24 months.
Design-partner rates are locked for your agreement term. The full contractual language sits on the terms page, and the security posture behind the export and deletion commitments is on the security page.
The fee is the cost you can put in a budget. Team time is the one that actually kills projects, so here is the real ask during a pilot.
That is the list. No dedicated hire, no data-science team, no historian migration, and nothing for your team to install or maintain. Connections are read-only by default: KaizenFlow does not write to PLCs or send commands to the floor, so there is no change-management burden on your controls team and a connectivity outage never stops a line. Messy tags are normal, and cleaning enough of them to measure is our work in weeks 1 to 2, not homework we hand you.
If your IT or OT team wants the detail before granting anything, the security page covers isolation, encryption, roles, and retention in plain terms.
We do not quote a payback period. We are at design-partner stage with no customer results to stand behind, and a payback figure invented from a model is exactly the kind of number that makes a CFO stop trusting the rest of the page.
What we will do is show our working. The ROI calculator takes your facilities, revenue, downtime hours, and scrap rate and applies our modeled ranges: 8-18% unplanned downtime reduction, 5-12% scrap reduction, 4-11% throughput gain, and 3-7% energy reduction. Those are illustrative model outputs from our design-partner program, not achieved results, and the calculator states every assumption it uses in the open, including its implied production hours. Put Pro pricing at $5,000 to $15,000 per month against whatever it returns and you can do the arithmetic yourself, with our assumptions visible rather than buried.
Then the pilot replaces the model. Eight weeks in, the Savings Auditor reconciles what actually changed against the baseline you agreed in week one, and your finance team gets a report they can check line by line. That report is the only payback number we will ever stand behind, and it will be yours, not someone else's.
Almost nobody in this category publishes a number. The usual reasoning is that pricing depends on scope, which is true, and that a conversation is the right place to explain it, which is sometimes true. What follows from it is not: a buyer with a $40,000 budget spends three weeks in a discovery process to learn the entry point was never within reach.
We would rather you qualify us out in thirty seconds. If $5,000 per month is not real for your plant, you now know that without a call, and both of us keep the afternoon. If it is, you arrive at the first conversation already knowing the shape of the deal, and we can spend that hour on your lines instead of on a reveal.
The same reasoning is why we research and publish what is publicly known about other vendors' pricing, with sources: Guidewheel pricing, Tulip pricing, and L2L pricing. Those guides exist because the information should be findable, not because every plant should choose us. Several of them should not. The compare hub is where we say which ones, and why.
How much does KaizenFlow cost? There are three ways to buy. The pilot is a fixed $25,000 to $75,000 for an eight-week engagement covering one facility and two connectors. Pro runs $5,000 to $15,000 per month, starting at $5,000 for a single facility. Enterprise is custom and adds unlimited facilities, private VPC deployment, custom connectors and SSO, a dedicated CSM, and SLA commitments. Convert after a pilot and the pilot fee credits in full against your first year.
Do you charge per machine or per facility? Per facility. Pro starts at $5,000 per month for a single facility, and connecting more machines inside that facility does not change the figure. Per-machine pricing is common in this category, and we think it is the wrong shape, because it charges you more for giving the system more to see.
Is there a free trial? No. A real evaluation has to connect to your MES, SCADA, ERP, or historian and baseline real production, which is genuine work on both sides. We run a paid pilot instead, and the fee credits in full against your first year if you convert. If you stop, you keep the verified savings report.
Are there implementation fees or hidden costs? No. The pilot fee is fixed and agreed before kickoff, with no usage-based surprises, and it covers the connection, analysis, and verification work. Onboarding and a dedicated success engineer are included on every plan. Rates are locked for your agreement term, and any adjustment happens at renewal with at least 30 days' written notice.
What is not included in the price? Connector development beyond the two included in the pilot is scoped separately. Your team's execution time in weeks 6 to 8 is yours. Any hardware you later choose to add is not something we sell. Private VPC deployment, SSO, data residency, a dedicated CSM, and SLA commitments are Enterprise-tier. These are boundaries on what the fee buys, not hidden line items.
What is the contract term, and can we cancel? There is no lock-in. Either party may terminate with 30 days' written notice. After termination you get a 30-day window to export your data, and it is permanently deleted after that. Your data is yours throughout, with full export and API access on every plan.
What payback period should we expect? We do not quote one. At design-partner stage we have no customer results to stand behind, and we will not dress a model up as a track record. Run the ROI calculator on your own numbers instead, because it shows every assumption in the open. The eight-week pilot then replaces the model with measured numbers reconciled against your baseline.
Does the pilot fee credit toward the subscription? Yes, in full, against your first year if you convert to an annual agreement. Conversion is never automatic. At the end of week eight you hold a verified report and a decision, and if you stop, you keep the report.
Tell us the facility, the lines, and the systems you run. We will come back with a fixed pilot number, or tell you honestly that eight weeks will not prove anything on that scope.