The thirty-six questions a serious investor asks.

The CFO for a multi-ERP enterprise, the operating partner for a fund. Internal Audit champions, the CISO clears it because it is read-only. This is the working hypothesis, and it stays labeled a hypothesis until the evidence retires it.

Whoever owns the number that two systems disagree about: finance for working capital, the fund for portfolio EBITDA. A new category has no budget line, so the entry is an existing pain with an existing owner, not a new line item.

There is no published price, and the reason is the model: EOS is priced as a share of delivered value, with the mechanism and every fixed term published. Specific figures are set at scoping, against the customer's own systems.

The scoping conversation is free and thirty minutes. The assessment that follows is priced at scoping under the published structure. No number is anchored before anyone has found anything.

Read-only connection to systems already running. No migration, no write access, no new system of record. The remaining burden is access provisioning on the customer side. Production validation runs per engagement, and the assumptions register carries the status.

Unknown until the first one. This row fills with the pilot program's real elapsed time, whatever it turns out to be.

The register is clear of live conversations. One evaluation earlier this year closed without a response and is recorded as exactly that. A pipeline that counts silence as interest is lying to its own founder first.

That line belongs to the pilot program, and starting it is precisely what the largest allocation of the capital plan exists to do.

No denominator exists. The first cohort of assessments produces the first conversion rate, and it will be published as a measured figure, not a target.

Modeled figures are labeled synthetic everywhere they appear, and the commercial model shares value rather than charging for promise. The construct under design is named, an Outcome Warranty, and its terms ship with the first pilot contract. Until then it is design, and this row says design.

Eight connectors are conformed against specification fixtures and nine more are declared scaffolds; the counts are cumulative and dated, and production validation is precisely the milestone the published pilot charter exists to produce. A production estate behaving like the mock is the assumption the pilot tests first.

It does not exist yet. The demo object is synthetic and labeled at every appearance. Producing the first real one is the stated purpose of the first pilot, not a byproduct of it.

The demo tenant is the walkable one, every surface of it; production tenancy is provisioned per engagement under the pilot charter, and this row records the date the first one stands up.

Run at every seal and published: a failing connector is isolated by its breaker, a forged signature dies deterministically, a tampered thread reports its own break. Refusals are recorded rather than hidden. The walkthrough shows them.

Disagreement is preserved, never repaired in place. Quality information travels with the record, and a figure that cannot be traced is presented as exactly that. What live-tenant dirt does to throughput is untested, and is listed as such.

Each connector carries its own conformance suite, so vendor drift is detected by a failing case rather than a support ticket. The cost of keeping seventeen connectors current against vendor API churn is unmeasured until production, and the engineering allocation of the raise assumes it is real.

The method and the results are published in full: the shipped artifact executed cold, offline, no network, no vendor in the loop. The party is named in diligence rather than on a public page.

Nobody yet. It is funded inside the security and assurance allocation and scheduled after close. No penetration test result is claimed anywhere, because none exists.

Not started, and marked not claimed on every page that could imply otherwise. The published milestone is a completed observation window at month twelve post-close, funded in the same allocation as the penetration test.

The customer keeps everything that matters. Exported evidence packs verify offline without us, forever. The systems of record were never touched, because no write method exists. The standard behind the claims is published openly, so the verification survives the vendor.

The entity is a founder-held LLC and no priced round has occurred. The exact figure is a data-room disclosure.

Disclosed in the data room before any signature, alongside the cap table itself.

Any outstanding instrument is disclosed in the data room, in full text, before a signature. Nothing is summarized on a public page where a summary could flatter.

A closing condition of any priced round is the Delaware C-Corp conversion, and the clean table that comes with it. Both are in the legal allocation of the capital plan.

Disclosed in diligence with documentation, not asserted on a page that cannot carry the evidence.

Disclosed in diligence. The public commitment is narrower and checkable: the largest allocation of the raise is commercial proof, not compensation.

Disclosed in diligence. The estate is built and operated at founder scale today, which is what makes the current burn survivable and the raise a choice rather than a rescue.

The estate keeps operating at founder scale; the build does not stop, the commercial motion slows. The three-level structure exists partly for this case: the product-level raise on EOS is a smaller instrument aimed at the same three-pilot milestone.

Closed-loop prepaid service credit. Not a token, not a financial instrument. It is purchased in dollars through standard card processing and redeemed for services on the consumer estate. It settles through a single closed ledger operated by the company.

There is none, by design. No smart contract, no chain deployment, no on-chain asset. A search for an SNX token finds nothing because there is nothing to find, and that is the intended result, not an omission.

No token keys exist. The ledger is company-operated infrastructure, with payment flows verified the way the rest of the estate is verified: signature-checked, replay-idempotent, tested.

Not a meaningful quantity for a closed-loop credit. There is no float, no secondary market, no exchange listing, and none is planned. Credits exist when purchased and retire when redeemed.

None, because there is nothing to hold. A credit that cannot be traded cannot be accumulated as a position, by the company or anyone else.

It is operated as closed-loop prepaid credit: it cannot appreciate, cannot be sold on, and confers no claim on the company or its revenue. No legal opinion is claimed on this page; formal classification questions are handled with counsel in diligence, like every other legal instrument here.

Consumer-estate services settle in it. The enterprise product has no SNX surface anywhere in it, which you can verify by searching this site. In any valuation, treat it as consumer-side plumbing, not an asset.

It does not, and the architecture says so structurally. EOS is Web2, read-only, with no wallet anywhere in it. The Web3 side is the consumer brand's distribution and provenance layer, valued as optionality on the investor page, and held to the same evidence standard as everything else here. If EOS succeeds, Web3 is upside. EOS was built so that it never becomes a crutch.