Saltar al contenido principal

SOURCE-LINKED CLAIMS

The numbers behind Dcrayon

Every number we print: on this site, in a sales deck, in a founder essay: is pulled from a query you could re-run. Four claims, four sources, one quarterly refresh schedule. Last verified 2026-06-01. Next refresh due 2026-07-15.

Four claims we stand behind

Every claim below has a bold form and a conservative form. We use the bold form when the audience is close enough to verify; we use the conservative form on cold outreach so we under-promise by design. Either form is defendable against this page on the date stamped at the top.

Claim 01
As of 2026-06-01

84% of paying-client revenue is repeat business

84
percent
Public form

Bold: 84 percent. Conservative public form: 60 percent or more.

Definition + data

Counted as: paying customers with two or more paid invoices, share of total paid revenue from that cohort. SQL pull against the HRMS production invoices table on 2026-06-01. 147 paying customers total, 82 repeat, Rs 1.04 Cr total paid, Rs 87.7 lakh repeat.

Source

Query: Team AI repo: data/queries/repeat-revenue-2026-q2.sql
Audit doc: Team AI repo: posts/2026-06-01-dcrayons-defendable-numbers-sources.md (section 4)

Claim 02
As of 2026-06-01

10 years operating

10
years
Public form

Bold: 10 years. Conservative form: a decade.

Definition + data

Dcrayon Consultancy Private Limited registered 2016. Counting completed calendar years through 2026-06-01 gives 10. The DCrayon Inc. US entity was registered later; the headline counts the Indian parent.

Source

Query: MCA registration filing (year of incorporation 2016)
Audit doc: Team AI repo: posts/2026-06-01-dcrayons-defendable-numbers-sources.md (section 2)

Claim 03
As of 2026-06-01

88-person team across functional departments

88
people
Public form

Bold: 88 people. Conservative form on outbound: 60+ specialists. Background note: 60 is the count of billable specialists; 88 is total headcount including operations + leadership.

Definition + data

Live count from the HRMS users table on 2026-06-01 (88 rows where deleted_at is null). 79 customer-facing roles are active; 9 carry leadership / operations / finance functions. Split is published in the source doc.

Source

Query: HRMS users table on AWS 144 (live)
Audit doc: Team AI repo: posts/2026-06-01-dcrayons-defendable-numbers-sources.md (section 1)

Claim 04
As of 2026-06-01

Active client book read live; 523 records ever; 148 paid

523
client records ever
Public form

The 'active clients' figure shown across this site is read LIVE from the CRM customer list (crm.clients, status = Active) on every render, so it is never a stale hardcoded number. Conservative roll-up: 200 or more clients across India, UK, US, UAE. Specific cuts: 523 client records ever opened; 148 have paid at least one invoice; 79 are on an active paid retainer this month.

Definition + data

The site-wide 'active clients' number is the live count of crm.clients where status = Active (the current client book), so the public figure and the CRM never drift. 523 = all client records ever opened, incl. churned (prior HRMS pull on 2026-06-01). 148 = customers with at least one paid invoice. 79 = customers on an active paid monthly retainer right now. 70 paying customers YTD 2026 (up from 55 in 2025 and 37 in 2024).

Source

Query: crm.clients (live) + HRMS invoices (historical)
Audit doc: Team AI repo: posts/2026-06-01-dcrayons-defendable-numbers-sources.md (section 3)

How we refresh these

The four queries above re-run on a fixed quarterly cadence. Next scheduled refresh: 2026-07-15. If a number drops below the published bold figure at the next refresh, the bold figure on this page comes down within 48 hours of the pull and the conservative public form takes over until the next quarterly window.

If you find a public Dcrayon claim that does not match this page, tell us. Email info@dcrayons.app with the URL and the figure; we either fix the public copy or open the source query for you.

Want a number we have not published yet?

On a discovery call we will share the cuts you actually care about: managed Meta spend by vertical, repeat-cohort retention by tenure, share-of-answer by AI engine. We do not publish them because they are buyer-specific.