Two different plan prices should stop a church software purchase until the vendor explains, in writing, which figure applies and what each plan includes. A discrepancy may be a typo, but it also tests whether billing, product claims, and internal records can be trusted.
In 1999, NASA’s Mars Climate Orbiter was approaching Mars when the navigation figures no longer agreed with the spacecraft’s expected path. One team had produced thrust data in pound-force seconds. Another system treated the data as newton seconds.
The difference was small on each calculation. Across the journey, it accumulated.
When two records describe one product
NASA’s Jet Propulsion Laboratory in Pasadena managed the mission, while Lockheed Martin built the spacecraft in Denver. On September 23, 1999, the orbiter passed much closer to Mars than planned. NASA lost contact with it.
The investigation board, chaired by Arthur Stephenson, identified the failure to use metric units in one part of the ground software as the primary cause. NASA documented the findings in its Mars Climate Orbiter Mishap Investigation Board Phase I Report.
Two teams had records that looked usable inside their own workflows. The mission failed where those records met.
A church administrator minutes away from a leadership meeting faces a much smaller consequence, but the decision mechanism is similar. One ChurchWork page shows one plan price. Another approved document shows a different figure. The administrator cannot tell whether the difference comes from an old page, monthly versus annual billing, a member limit, or a feature that moved between plans.
The dangerous response is to choose the more convenient figure and keep preparing the presentation.
The useful response is to pause and reconcile the records.
What the price needs to explain
A plan price has meaning only when it is tied to a defined offer. Church leadership needs to know what the church receives, what triggers an additional charge, and which capabilities are available today.
For ChurchWork, that means checking the price beside the practical work the platform supports: conference registration, QR check-in, bus coordination, groups, branch management, and member communications. It also means separating available capabilities from work still in progress.
Online Giving should not be presented as processing real payments today because its card capture remains in a test implementation. AI Analytics should not appear as a usable Premium feature because the current product does not provide that capability. A higher plan price cannot carry features that leadership will be unable to use after approval.
Before the meeting, the administrator should create one short comparison table containing:
- The plan name and billing period.
- The published price and the date it was checked.
- Member, messaging, or storage limits that affect the total cost.
- Features available in the current product.
- Features described as planned, beta, or unavailable.
- Any setup, messaging, or payment-processing costs requiring separate confirmation.
This is the same discipline described in Church Software Pricing: How Nana Yaa Tied Every Charge to a Clear Outcome. Leadership can evaluate a cost more confidently when each charge maps to work the church needs done.
Treat the discrepancy as a trust test
The administrator does not need to accuse the vendor of hiding something. A calm written question is enough:
“We found two different prices for the same plan. Please confirm the current price, billing period, included limits, and available features in writing.”
The quality of the response matters as much as the corrected number.
A trustworthy response identifies the outdated record, corrects it, and explains the offer without vague promises. A weak response introduces a third figure, avoids confirming feature availability, or relies on verbal assurances that cannot be added to the approval pack.
Churches should apply the same check to every vendor under consideration. The plain-language comparison framework for church management software pricing in Ghana offers a practical structure for comparing published prices, limits, setup effort, messaging costs, and current capabilities.
A low monthly figure can become expensive when essential functions sit outside the plan. A higher figure can still be reasonable when it covers the church’s real requirements and removes separate tools. Leadership needs the complete cost attached to a clearly defined outcome.
Take one verified number into the room
The Mars Climate Orbiter did not fail because nobody could calculate. It failed because incompatible records crossed an operational boundary without being reconciled.
A leadership presentation is another boundary. Marketing pages, pricing tables, internal notes, and verbal explanations become a budget decision. Conflicting figures should be resolved before they cross that line.
If confirmation does not arrive before the meeting, present the price as unverified. Show both figures, explain what remains unclear, and recommend delaying the purchase decision until the vendor provides one dated answer.
That pause protects the administrator’s credibility and gives leadership a sound basis for approval. One verified figure is more useful than the most attractive figure on the screen.
Comments
No comments yet.