Skip to content
Moweb
Editorial standards

what we publish How we source.

Moweb does not publish a statistic it cannot attribute to a named source or to its own engagement data. This page says what that means in practice, and what we removed from this site to comply with it.

Trusted by 500+ Clients

EA FoodsNuskin Elite TeamLex GroupMeat Member ClubEmpowerLet's Be RAWBuy Fine DiamondsCatch-UpCollection atEleganzEpocheTasksKalali MotorsKing Jada HotelKrystalKukeNafasiArtNext Big Idea ClubPeswaPayRTH TVVennotex

The rule

We do not publish a figure we cannot attribute. Not a percentage, not a multiplier, not a timeline presented as a guarantee, and not a client result. If a claim cannot be traced to a named source or to work we have done and are permitted to describe, it does not go on the site.

What we removed, and why

In 2026 we audited every page on this site against that rule. Most of the content had been carried over from years of marketing copy, and a great deal of it did not survive.

Claims removed from moweb.com during the 2026 editorial audit
WhatBeforeAfterWhy
Unsourced percentage claims77222The 22 that remain are attributed in the article that carries them.
Analyst citations1590“Gartner predicts” and similar, none of which named a report anyone could open. We deleted the sentence rather than the attribution - a forecast presented as fact is worse than no forecast.
Invented engagement metricsSeveral0Figures like “95% semantic search accuracy” and “1,284 invoices per agent run” appeared on the homepage. No client produced them.
Self-published review markupPresentRemovedOur own Clutch rating was marked up as structured review data on our own site. The rating is real; publishing it as first-party review markup is not how it should be read.

What we do publish

  • Figures from our own engagement data, labelled as ours.
  • Figures from named, linked, primary sources - regulations, standards bodies and published research, not a secondhand summary of them.
  • Certifications we actually hold: ISO/IEC 27001:2022 and CMMI Level 3.
  • Client results only where that client has approved the specific figure for publication.

What we do not publish

  • Percentages without a source.
  • Results attributed to clients who have not approved the number.
  • Certifications we do not hold. To be explicit: Moweb is not SOC 2 certified. Where our pages discuss SOC 2, they describe control evidence we help clients produce for their own audit, not a report we hold.
  • Case study metrics for anonymised engagements. Four of our AI case studies are anonymised at the clients’ request and carry no figures at all, which is why they read the way they do.

Authorship

Every article names the person who wrote it, with their role and the subjects they publish on. Author pages list that person’s full output on this site, so a byline can be checked rather than taken on trust. See our authors.

Corrections

Factual errors are corrected in place with a dated note rather than quietly edited out. If something here is wrong, tell us and we will fix it and say that we did: contact us.

Last reviewed 11 August 2026. Counts on this page were taken from the published content on that date.

Work with us

Ask us something we would have to source.

If a claim on this site matters to a decision you are making, ask where it came from. That is what the rule above is for.

ISO 27001:2022
Information security
CMMI Level 3
Engineering process
1 business day reply
Senior engineer reads first

We never share your details. Replies inside one business day.

Start a project