Editorial Standards
Last updated
These standards govern everything published on siliconcent. They exist to make the publication credible to readers, accurate over time, and defensible against complaints from the companies we cover.
Sourcing
Every numerical claim ties to one of:
- An SEC filing: 10-K, 10-Q, S-1, S-4, 8-K, proxy, 13D/G, or 13F.
- An earnings call transcript.
- A press release issued by the company concerned.
- A court filing in a public docket.
- A government statistical release (BLS, the Fed, OECD, and similar).
- Documented operator data from the author’s own businesses.
We do not use aggregator blogs as primary citations, we do not cite “industry experts” without naming them, and we do not lean on “sources familiar with the matter” unless we are doing genuine primary reporting.
Accuracy and corrections
We aim for zero numerical errors and accept that we are human. When a published post contains an error, we correct it inline with a dated correction block at the top, explaining what was wrong and what the correct value is. We do not silently edit substantive claims: where an error materially changed the argument, the original text stays visible. Minor fixes (typos, broken links, formatting) are made without notation. To report an error, email support@colsonsuperapps.com.
Methodology disclosure
Any post that forecasts revenue, multiples, or outcomes, models a DCF or comparable-company valuation, estimates the probability of an event such as a deal closing or a regulatory ruling, or computes a unit-economics output from inputs, includes a methodology section stating its inputs, assumptions, sensitivity, and what is deliberately not modeled. A reader should be able to disagree with a specific assumption, not the whole post. Forecasts remain forecasts: nothing here is a guarantee of an outcome.
Conflicts of interest
- The author currently holds no long or short positions in single tech equities covered on siliconcent. Index-fund and broad-market exposure is incidental. If single-name positions are ever taken, they will be disclosed and re-disclosed inline on any post substantially covering the issuer.
- The author operates several businesses: TYPEMUSE (consumer SaaS), PDF9to5 (B2B SaaS), the ColsonSuperApps mobile portfolio, ColsonSuperApps LLC, and Syrosin LLC. When a post cites operator data from any of them, the source is disclosed inline.
- Affiliate relationships are disclosed at the top of any post containing affiliate links. Sponsor relationships are disclosed inline, and sponsor placements are visually distinct from editorial.
The editorial firewall
Sponsors cannot read a post before publication, influence which topics we cover, get advance warning of critical coverage, or pull a placement after a critical post about their company or category. Sponsors can buy ad inventory at published rates, provide their own copy for clearly labeled sponsor placements, and request performance reporting on those placements. This firewall is non-negotiable.
Authorship and expertise
Articles are written by Colson, a multi-product operator who reads public filings as primary sources and runs the same unit economics he analyzes in them. Author credentials are published on the About page and attached to each article for transparency (E-E-A-T).
AI usage
This publication uses AI tools in research and drafting. The author edits every post before publication, and nothing ships without human review. We do not run AI-generated text without verification. Where AI assistance is load-bearing, such as searching across many filings, we disclose it. We do not fake AI involvement for credibility, and we do not hide it when it is material.
Comments and criticism
We welcome corrections and disagreement at support@colsonsuperapps.com and respond to substantive critiques promptly. Personal attacks, harassment, and bad-faith engagement are ignored. A threat of legal action is not a correction: we evaluate the underlying claim, not the threat.