Methodology
Software recommendations you can inspect.
Our goal is not to produce a mysterious score. It is to make the evidence, assumptions, exclusions, and trade-offs behind a shortlist understandable.
We start with the decision
A useful recommendation depends on context. Team size, workflow, budget, integrations, compliance requirements, migration constraints, and the capabilities that are genuinely essential all change the answer.
- Define the requirement. Separate essential requirements from preferences and identify hard constraints.
- Collect product evidence. Record product capabilities, plan limits, pricing rules, integrations, and operational considerations.
- Verify material claims. Prefer official documentation and record when each claim was checked.
- Apply transparent rules. Score relevant fit factors and exclude products that fail essential requirements.
- Explain the result. Present advantages, disadvantages, uncertainties, and next checks alongside the recommendation.
Fit scoring
Scores reflect company-size fit, a currency-aware budget band, productivity ecosystem, preferred operating style, and selected capabilities. The same rules are applied to every researched product. A score is a shortlist signal, not a customer rating or guarantee.
The current model starts at 55 points and applies the following published adjustments. The final result is limited to 1–99. These rules run entirely in the browser.
| Factor | Adjustment |
|---|---|
| Company size | +8 when the product covers the selected size; otherwise −10. |
| Reference-plan budget | +9 inside the selected currency-aware budget band. Above-budget plans receive a penalty from −8 to −20 based on the difference. |
| Productivity ecosystem | +6 for compatibility or no preference, plus another +5 for a product built around the selected ecosystem. A mismatch receives −8. |
| Operating style | The relevant editorial fit rating adjusts the score by −6, −3, 0, +3, or +6 for a 1–5 rating. |
| Each selected capability | Each 1–5 editorial fit rating applies the same −6 to +6 adjustment. |
| Ties | Lower reference price breaks a tie only when both plans use the same currency. Cross-currency ties are ordered by product name, never by nominal price. |
Budget bands currently use separate USD and AUD caps. Where a stored plan uses another currency, the USD cap is only a reference classification—not a converted price. The Finder explains the selected reference plan and keeps displayed currencies unchanged.
A product without an affiliate program can rank above a commercial partner. In some cases, the responsible recommendation will be to keep the current system.
Evidence quality
Material claims should include their source, the date checked, and a confidence assessment. Official pricing and product documentation are preferred for factual capabilities. Subjective claims such as implementation effort require broader evidence and will be labelled accordingly.
StackFitIQ provides official-source analysis and transparent decision guidance rather than claiming personal product use. Read how we analyze CRMs and how to test a shortlist with your own workflow.
Pricing estimates
Software pricing is often conditional. Estimates will identify currency, billing period, user count, minimum seats, contact limits, required add-ons, and other material assumptions. Visitors should confirm final pricing with the vendor before purchasing.
Corrections and updates
Software changes quickly. Records will carry verification dates, and material corrections will be prioritised when evidence changes. You can report an outdated claim through our contact page.