Testing protocol
How We Test Calculator Builders
We use one repeatable model across every product, then adjust the final recommendation to the use case the product is designed to solve.
1. Define the test calculator
The reference project includes numeric and choice inputs, validation, a multi-variable formula, conditional result text, a lead field, a website embed and an operational handoff. Specialist products may receive an additional scenario when their differentiator requires it.
2. Evaluate calculation capability
We examine formula syntax, conditional logic, reusable variables, validation, data handling, result presentation and how easily another person can audit the model.
- Formula range and transparency
- Logic and validation
- Result personalization
- Error handling and reproducibility
3. Evaluate the commercial workflow
We check how the tool captures consented data, maps fields, segments users, passes context to another system and supports relevant follow-up. An integration is not treated as built-in automation.
- Lead capture and consent
- Qualification and segmentation
- CRM or marketing handoff
- Automated follow-up and attribution
4. Record evidence and losses
A test note contains the date, plan context, source, capability result and limitation. We publish the decision-relevant loss, not only the strengths. Pricing is rechecked against official public information before a material update.