Editorial Standards

Editorial Policy

What we publish, how we verify it, who pays for it, and what we do when we get it wrong.

Mission and audience

CTO Accelerator publishes research for engineering leaders making high-stakes technology decisions — vendor selection, architecture, modernization strategy, due diligence. Our audience is CTOs, VPs of Engineering, technical investors, and the senior engineers who inform their decisions. Everything we publish is written for that reader.

Independence

CTO Accelerator is published by Sphere, an enterprise technology consulting firm. The publication is funded by Sphere — not by vendor advertising, sponsored content, affiliate links, or paid placements. Sphere does not accept payment for inclusion in vendor comparisons, favorable scoring, or removal of unfavorable analysis.

What this means

When you read "Vendor X scored 8.4" on this site, that score reflects the evaluator's judgment under our published methodology — not a commercial relationship between Sphere and Vendor X. When Sphere itself appears in a comparison, we disclose that prominently and apply the same scoring rules.

Sourcing standards

Every published statistic, range, or claim falls into one of three categories:

We do not pass off secondary research as primary. We do not invent percentages. If a number is approximate, we say so or we publish a range.

Author identification

Articles are bylined to the Sphere Research Team — the editorial and research arm of Sphere's CTO Accelerator. As we mature, we are progressively bylining individual articles to named senior engineers and consulting principals at Sphere, with verifiable credentials and LinkedIn-linked bios. Where guest contributors author content, they are named at the top of the article with their relevant background and any relationship they hold with Sphere or with the vendors discussed.

Conflict of interest

Sphere is a vendor of enterprise technology consulting services. As a result, several conflicts are structurally present:

See our methodology page for the controls applied to vendor scoring, including external editorial review where appropriate.

Updates and changelog

Every article carries a "Last Updated" date in the article header. Substantive revisions — anything that changes a score, a price range, or a recommendation — are appended as a changelog at the bottom of the article with a date and short description of what changed and why.

Cosmetic edits (typos, formatting) do not generate changelog entries. Adding new sections or new vendors does, even when the original analysis is unchanged.

Corrections

We publish corrections openly. If a published claim is wrong, we update the article, append a correction note dated and signed by an editor, and — for material corrections — add a notice at the top of the article so that readers who already saw the incorrect version are aware.

To request a correction, email editorial@ctoaccelerator.com with the article URL, the specific claim, and the evidence that the claim is incorrect. We respond within 5 business days, regardless of whether we agree with the correction.

AI-assisted content

Some of our research workflows use large language models for drafting, summarization, fact-checking against named sources, or formatting. Every published article is reviewed by a human editor before publication. We do not publish unedited AI output and we do not fabricate citations.

Vendor and reader feedback

Vendors who believe a comparison is inaccurate or out of date can request review through our contact form. We review submissions within 30 days and respond regardless of whether the request leads to an article update. We do not remove published analysis under commercial pressure.

Readers who find errors, want to suggest topics, or want to provide their own data for published cost guides can reach us at the same address. Anonymized reader contributions appear in some published cost ranges; we do not publish identifying information without consent.

Comments and community

We do not currently host on-site comments. Reader feedback is welcomed via email, and is reflected in updates and corrections rather than a public comment thread. As the publication grows we may revisit this.

Privacy

We collect basic analytics (Google Analytics) to understand which articles are useful. We do not sell reader data, run third-party advertising, or use behavioral retargeting. Newsletter subscribers receive only the weekly brief and unsubscribe links work on every email.