Field service app pricing: FSM Pricing Index

Every row is a verbatim sentence read from the named source's own page through our fetch service on the date shown, hash-pinned to the stored read (the sha of the page's visible text; the raw page is mirrored to R2).

24 of the 42 named sources that could be read published a usable figure; 18 published none and are recorded as not published, never filled in; 1 could not be read (blocked, dead or unreachable) and count nowhere.

The headline figures (median, minimum, maximum, quartiles) are over ONE figure per source for each breakdown it prices, in GBP (a source's median where its page yielded several accepted sentences for one breakdown), so a page that gives figures for several breakdowns gives one for each and N counts 16 figures, never sentences; 238 candidate sentence(s) were refused by a reviewer with the reason recorded.

The fuller derivation this dataset is chartered to grow into (not yet what the figures above are; they are each source's own published figure as read): the median, minimum and maximum PUBLISHED price per user per month in sterling across every vendor that publishes one, normalised across the three pricing MODELS the market actually uses - per user, per job (ServiceM8), per team (HiveSuite) and per field worker with free office seats (iTrade) - to one comparable figure at 1, 5 and 20 engineers, with setup, onboarding, SMS and contract length added in.

Two figures nobody publishes: the share of vendors that publish any price at all, and the sterling premium a GB buyer pays where a vendor's GB storefront still quotes dollars.

238 candidate sentences on these pages were refused by a reviewer; each refusal and its reason is recorded in the review ledger.