About

Who publishes CrewStack

We are a small independent research desk covering business software for US trade contractors. This page tells you exactly who we are, how we work, and what you should not expect from us.

Last updated 4 November 2026

What we do

We test contractor software, record what the vendors actually charge, and publish the result — including the parts vendors prefer not to explain, like per-user overage, implementation fees, processing rates and data-export terms. Our coverage starts with roofing and expands trade by trade.

What makes us different

What we are not

We are not contractors, licensed tradespeople, or accountants. We have not run a crew through a storm season on any platform. Where our assessment rests on documented user reports rather than our own hands-on use — which is the case for quote-only enterprise products — the article says so in that section, in plain language.

We are also an online research desk, not a US-registered business. If that matters to you, it should: it means we cannot walk into a vendor's office, and it means we lean on paperwork — screenshots, saved pricing pages, dated notes — instead of meetings.

How we make money

Affiliate commissions and display advertising. No vendor pays for a ranking, a review or a mention, and no vendor sees an article before it is published. Full detail is on our methodology page.

Corrections

If a price on this site is wrong, we fix it — usually the same day — and we note the change rather than editing silently. Tell us here.

Editorial standards in one paragraph

Prices come from vendor pages on the date shown. Reported ranges are labelled as reported, with the source type named. Features are described from our own use or the vendor's own documentation. Scores are our editorial judgement on eight published criteria and are not a measure of market share or revenue.

CS
By the CrewStack software desk

We buy trials, screenshot vendor pricing pages and re-check them on the 1st of every month. Vendors never see an article before publication. How we test →