Contact the Capital & Compute Editorial Team
Reach the Capital & Compute editorial team with questions, corrections, story tips, or partnership inquiries about our coverage.
The fastest way to reach us is email. We read everything and aim to reply to genuine inquiries within a few business days.
What to write about
- Corrections: found an error or stale number? Tell us and we'll fix it and note the correction.
- Tips & story ideas: pricing changes, harness behaviour, or jurisdictional developments worth covering.
- Tool submissions & corrections: to get a product into one of our directories, or to flag an outdated price or wrong specification, see how to submit or correct an entry. Both are free.
- Advertising & partnerships: inquiries about display advertising or sponsorship. What is and is not for sale is set out on our sponsorship page.
- Privacy requests: to exercise any of the data rights described in our privacy policy.
What happens to a correction
Corrections are read first, and they are welcome even when they are inconvenient. The most useful report names the page, quotes the specific claim, and points at a source that contradicts it. A factual error gets fixed and noted on the piece rather than silently edited away; a figure that was accurate when published but has since moved gets an update and a revised date. The distinction, and the rest of the policy, is set out in our editorial standards.
Because much of this site is maintained datasets rather than prose, a correction to a price, a benchmark score or a specification is as valuable as one to an article, and often more so: a single wrong number in a tracker propagates into every post that cites it.
What makes a useful tip
The most actionable tips are specific and checkable: a provider changing rates, a benchmark version quietly swapping its task set, a harness behaving differently from its documentation, a filing that says something the accompanying press release does not. A link to the primary source is worth more than a summary. Tips are not published as scoops without independent verification against a primary source, so please say whether something is public, and whether you want to be credited or left out.
What not to send
To save you time, a few things are declined as a matter of policy rather than case by case. Guest posts and contributed articles are not accepted; everything here is written by the editorial team. Paid link insertions and requests to add a link to an existing post are declined, whatever the offer. Directory placement is not for sale, and no position in any ranking or comparison can be bought. Getting a product listed is free through the submissions page, and the criteria there are the only route in. What is genuinely available commercially is set out on the sponsorship page.
Before you write: things you can answer yourself
A few questions arrive often enough to be worth answering here. Start here is the guided entry point into the archive if you are not sure where to begin, and the tools page lists every free tracker and calculator on the site. If you want the underlying numbers rather than the page, each tracker publishes its data as JSON at a stable URL. If you want to know how a figure was arrived at, the method is on the page itself and the general rules are in our editorial standards.
If a price or benchmark score looks wrong, check the as-of date on the tracker before writing: every figure here is a dated snapshot, and the most common report we receive is a number that was correct when it was checked and has since moved. That is still worth telling us, it is just an update rather than a correction.
Press, citation and republication
Journalists and researchers are welcome to quote figures and analysis from this site with attribution and a link back. Where you are quoting a tracker, please carry the as-of date with the number: prices and benchmark scores here are dated snapshots, and a figure reproduced without its date will be wrong sooner than you expect. The underlying data is available as JSON at stable URLs, which is usually easier than transcribing from the page.
Requests to republish a full article are considered case by case and are usually declined in favour of a summary with a link, for the ordinary reason that duplicate copies compete with the original. If you need a chart or a dataset for a report, ask, and say what it is for.
Security reports
This is a static site with no user accounts, no comments, and no server-side application, so the attack surface is small. If you do find something, email the address above with enough detail to reproduce it and please give us a reasonable window to fix it before publishing. Reports made in good faith are welcome. Automated scanner output with no reproduction steps, and reports whose remedy is a purchase, will not get a reply.
Response times and privacy
This is a small operation, so replies take a few business days and every message is read by a person. Corrections and privacy requests are prioritised over everything else. Correspondence in English is easiest to act on quickly.
Messages are used only to respond to the matter raised and are not added to any marketing list. For how information you send is handled, retained and deleted, and for how to exercise your data rights, see our privacy policy.