Research methodology

How each page is made.

Stackmark publishes structured, sourced research on ERP and finance software in the form an analyst note would take. This page states, for each kind of page, what gets a record in, how often it is checked, and the things the site will not do.

8 page typesReviewed September 2026

01The rule behind every page

Every fact carries a source. A vendor, module or partner record lists the URLs it was built from, and a fact that cannot be cited is not recorded. Analysis — the positioning line on a profile, the demonstration questions on a module page — is written here and is marked as Stackmark’s own. Where the site counts something, the denominator is printed beside the count.

02Vendor profile

Where
/erp/ · 53 pages
Inclusion rule
A system is profiled when its stated company-size fit, deployment models and module list can each be cited to the vendor’s own published material. A record with a fact that cannot be cited is not committed; the dataset test fails the build. Inclusion cannot be bought, and no vendor is asked to pay, brief or approve.
Refresh cycle
The dataset is reviewed each quarter against the cited pages; the review month is printed on every page. A change to a record rebuilds every page that reads it.

03Head-to-head

Where
/compare/ · 327 pages
Inclusion rule
A pair is generated only where two profiled systems state an overlapping size fit and sit within one cost band of each other, so every head-to-head is one a buying committee could plausibly face. Not every combination is published.
Refresh cycle
Derived from the vendor records; changes with them.

04Module coverage

Where
/modules/ · 16 pages
Inclusion rule
A module is documented when Stackmark has written a definition of its scope in its own words and at least two demonstration questions for it. Coverage counts are the number of profiled systems that document the module, always shown against the total profiled.
Refresh cycle
Definitions and questions are editorial and revised as the market moves; counts are recomputed at every build.

05Partner directory

Where
/find-a-partner/ · 2738 firms
Inclusion rule
A firm is listed when it appears on a partner directory Stackmark can read and cite — the vendor’s own wherever it publishes one, and a named third-party directory where it does not. Records carry the countries, specialisms and tier that directory states; a tier is only recorded when its source is on the vendor’s own domain, and where none is stated the record says “not stated” rather than inferring one. Ratings and satisfaction scores printed by these directories are not recorded at all. Lists are alphabetical within the stated tier; Stackmark holds no quality data on these firms and ranks none of them. A firm gets a page of its own when it holds the highest tier its vendor publishes (263 today), and a country gets one where a directory lists five or more firms there (86 today) — both are limits on how many pages this site can generate, not judgements. Every listed firm appears in full on its vendor’s directory page regardless.
Refresh cycle
Harvested from 4 source directories, one serial request a second with each firm's record dated from the day its own page was read, and reviewed each quarter.

06Which vendors publish a partner tier

Where
/find-a-partner/ · 2 of 7 publish one
Inclusion rule
A tier is only ever the vendor's own word, cited to the vendor's own page. Microsoft Dynamics 365 and Odoo publish a per-firm tier that can be read and cited, so those records carry one. Acumatica, Oracle Fusion Cloud ERP, Oracle NetSuite, Sage, SAP do not: their directories either publish no tier at all or decline automated access, and Stackmark does not work around a site that declines it — no spoofed agents, no header games, no undocumented internal interfaces. Records from those directories say "no tier published", which is a different statement from "no tier held" and the site keeps the two apart. Coverage is therefore uneven by vendor, and that is the honest outcome rather than a gap to be padded.
Refresh cycle
Re-checked whenever a directory changes what it publishes.

07Finance stack

Where
/stack/ · 14 products · 5 categories · 36 category and system pages
Inclusion rule
A product is listed when it states an integration with a system Stackmark profiles, on a page that can be cited: the system’s own marketplace listing where one exists, otherwise the product’s own integration page — and the table says which of the two it is. Stackmark has not tested any integration and makes no claim about how well one works. A price is recorded as published only where the product publishes a figure, with the page that shows it; everything else says “on quotation”. No product pays to be listed, no ordering is for sale, and no link in this directory is an affiliate or referral link — a test rejects any URL in the dataset carrying a referral or campaign parameter.
Refresh cycle
Integrations are re-checked against their cited pages each quarter; a page that has moved is a correction.

08Glossary

Where
/glossary/ · 303 terms
Inclusion rule
A term is added when it recurs in evaluations and has a definition Stackmark can write without leaning on a vendor’s framing. Each entry says why the term bears on the buying decision.
Refresh cycle
Continuous.

09Cost estimator and benchmark

Where
/tools/cost-estimator/ · Two tools
Inclusion rule
The estimator publishes a modelled range from stated assumptions, printed beside every result; it is not a quote and never simulates one. The benchmark counts profiled systems that fit a stated profile against the total profiled. It is coverage of this dataset, not market share.
Refresh cycle
The model’s parameters are versioned in the repository and reviewed with the dataset.

10What Stackmark does not do

  • No scores, stars, ranks, quadrants or top-N lists. A score implies a judgement Stackmark has not made and cannot cite.
  • No market-share or adoption claims. Stackmark holds no adoption data and reports none.
  • No invented prices. Cost is recorded as a band and modelled as a range; a list price appears only where the vendor publishes one, with its URL and date.
  • No testimonials, customer logos or “trusted by” bands.
  • No email gate on any export, template or page.
  • No affiliate links in editorial content, and no paid placement outside the labelled sponsor slot.
  • No sharing of a reader’s details with a vendor or partner.

11Corrections and disputes

A vendor may correct a fact about its own product at any time by pointing to the published page that contradicts ours; placement, wording of analysis and inclusion are not open to negotiation. Corrections are published on the corrections log with the date, the page, what it said and what it says now. How the site is funded is set out on how we make money.