Execution evidence · case study
Every claim on this page is tagged with where it comes from. Nothing here is presented as audited, and nothing here belongs to Neeno.
Wellls is the founder team's execution proof and the reference implementation behind Neeno's methodology. It is not Neeno revenue, and it is not an asset owned by Neeno. Wellls figures must never be combined with Neeno figures, summed into a single number, or carried into a Neeno valuation — unless and until ownership, transfer, licence or revenue-share rights are documented in favour of Neeno.
What Wellls does evidence is narrower and still valuable: that this team can take a thesis to a launched, paying consumer product quickly, using the one-operator-plus-agents model Neeno intends to teach and productise.
Evidence status system
Verifiable today on public pages or profiles. Anyone can check it without access to the company.
Stated directly by Dmitry in working discussion. Reliable as a statement of intent or fact by the founder, but not independently evidenced.
Present in project materials, a staging build or project correspondence. It is externally unverified and may still require reconciliation.
A financial figure supplied by management without a supporting primary document. Treat as an indication, not as reporting.
The claim cannot be relied on for diligence until a specific artefact is produced. The artefact is named alongside the claim.
A design, term or operating choice under discussion; not agreed and not a current fact.
An intended outcome. It is not a forecast, promise or demonstrated result unless separately evidenced.
An unresolved input that must remain explicit rather than being filled in for presentation.
Primary public destinations used to verify the product and legal-page statements:
The sequence below is drawn from Neeno's own case materials describing how Wellls was built and launched. Dates are relative; no calendar dates are asserted.
Market evidence, offer and product system are assembled under a single operator working with a system of agents — the model Neeno intends to teach.
Artefact required: repository history or dated project records establishing the start date.Thirty-three days from build start to first launch. This is the headline execution claim and the one most worth evidencing precisely.
Artefact required: deployment or store records, first-payment timestamp, dated launch announcement.First recurring revenue recorded four days after launch.
Artefact required: payment-processor export covering the first week.The internal case states MRR above $20,000 at approximately one month, but does not establish whether that period starts from build, launch or another event. This is a separate source record.
Artefact required: monthly MRR series with an explicit definition of MRR and of the start date.A separate internal statement reported at week fifteen. Its metric definition and the period's start date are not stated.
Artefact required: gross and net revenue by month, with refunds and chargebacks separated.Dmitry has reported that Wellls has reached approximately $100,000 MRR and that the trajectory may be disclosed. No primary financial document supports this figure yet, so it appears everywhere in these materials as management-reported with verification pending — never as reporting, and never as Neeno revenue.
Artefact required: processor and bank statements or management accounts for the trailing months, reconciled to a subscriber count.Two internal statements must remain separate until their metric definitions and time origins are evidenced:
No growth, flatness, consistency or conflict can be inferred from these statements. They are not a time series and are not connected on a financial axis.
Until this is resolved, each statement is shown as a separate semantic record. The approximately $100,000 MRR statement remains management-reported with primary-document verification pending. No growth rate is computed.
The following must be supplied for a Wellls metrics appendix. None of it has been provided.
| Item | Why it is required | Status |
|---|---|---|
| Month-by-month MRR | Establishes the trajectory rather than two endpoints, and fixes the definition of MRR being used. | Not supplied |
| Gross and net revenue | Distinguishes headline billings from what the business actually keeps. | Not supplied |
| Refunds and chargebacks | Consumer health products can carry material refund rates; net-of-refunds revenue is the only meaningful figure. | Not supplied |
| Paid subscribers | Reconciles revenue to a customer count and an implied price point. | Not supplied |
| Churn and retention | Determines whether the revenue is durable or front-loaded. | Not supplied |
| Acquisition spend and CAC | Tells whether growth is bought or earned. No CAC figure is stated anywhere in these materials because none has been supplied. | Not supplied |
| Contribution margin | Separates a real business from revenue generated at a loss. | Not supplied |
| Processor, bank or management-account confirmation | Converts every figure above from management-reported to evidenced. | Not supplied |
Two permissions are required before any of this material is used beyond a private discussion:
This page deliberately excludes private correspondence, personal identifiers, screenshots of private channels and any third-party personal data gathered during research. None of that belongs in an investor artefact.
Investor contact: business@qntrs.com