Business plan — CryptoBook.space (Virtus Labs)

Date: 18 September 2026
Company context: Virtus Blockchain Labs operates tokensmarketcap.com, virtusblockchainlabs.com, and cryptobook.space on a single Ubuntu VPS (hostname vmi3003269, IPv4 173.249.19.205).
This plan’s job: decide what cryptobook.space becomes. It is a plan not to invent a company that the market will not pay.

1. Company and assets

Asset	Role today	Notes
virtusblockchainlabs.com	Agency / engineering brand	Theme source of truth (black, `#e91e8a`)
tokensmarketcap.com	Live crypto data product	Real audience (not measured in this pack’s 7-day cryptobook log)
academy.tokensmarketcap.com	Intended learning product	Currently 404
cryptobook.space	Crypto social (posts, rooms, LiveKit)	~65 unique IPs / 7 days. Social is to be taken out of the strategy, not necessarily yanked off nginx today
cryptobook.com	Separate IONOS host `217.160.223.94`	Not this VPS. Apache basic-auth. Out of scope until DNS is pointed here
VPS	94 GB RAM, 678 GB disk, nginx 80/443, Postgres/Redis/Mongo localhost	Apps bind `127.0.0.1`. No extra public ports

Offer we will not pretend to sell: a new “agent governance” SaaS on a leftover social domain.

2. Mission for this domain

Original operator brief (condensed):

Replace CryptoBook social.
New project in agentic AI or quantum computing.
Same look as Virtus.
SaaS, card-swipe, high demand, US-legal, not high-risk under the EU AI Act, runnable on this VPS, profitable for operator and user, 60-second start, no scam.

Restated mission after the study: do not ship a product that fails demand. Use the domain as a Virtus property. Only attach a SaaS when a buyer already pays someone this week for that job.

3. The offer (current)

There is no SaaS offer. Recommended commercial posture:

Internal: this document pack is the project deliverable for September 2026.
Public (optional): a holding page in Virtus chrome: social product retired or paused; Virtus Labs continues; no fake waitlist, no fake logos, no fake SOC 2.

If a later GO names a product, the website spec (06-website-spec.md) is the implementation contract.

4. Market (one paragraph)

Consumer AI spend is $40B in 2026 (Menlo, 16 Sep 2026). 55% of US AI users pay; regular agent users 92% pay. They pay Cursor, Claude, Copilot, Lindy, Lovable — labor replacement. Agentic infrastructure (traces, MCP gateways, scanners, receipts) is either free OSS, bundled into the IDE they already pay, or enterprise sales (Okta Agent SSO is $0 extra on core SSO, GA 24 Aug 2026). Quantum vendor revenue is hardware and QPU minutes (IBM Open Plan free; PayGo $96/min). A 1-VPS classroom cannot compete with free real QPUs.

Full study: 02-market-study.md.

5. Products we will not build

See also 10-strategic-options.md and the kill list in the market study.

Hosted MCP / LLM reverse proxy (key honeypot; Permit.io / Portkey / LiteLLM).
Slip / Hallpass / blast-card / signed-receipt SaaS.
Langfuse / Helicone / LangSmith clone.
Agent SSO / “control plane.”
Quantum classroom, simulator-as-SaaS, PQC badge.
Freelance escrow / receipt coins / prepaid LLM wallet (money transmission).
Browser agents that log into third-party sites (CFAA path).
“AI Act / SOC 2 / HIPAA compliant” as a claim.
A second CryptoBook social.

6. Go-to-market (until a GO)

Do not run ads, fake launch tweets, or Product Hunt for a product that does not exist.

If option B (holding page) is chosen:

One page, Virtus look, English first.
CTA: virtusblockchainlabs.com and/or tokensmarketcap.com.
No email capture unless we will actually email.

If option C (TMC audience) is chosen later, marketing starts from existing TMC users, not from cryptobook.space SEO.

7. Operations and 12-month calendar (honest)

Window	Action
Week of 18 Sep 2026	Freeze Slip. Keep social live or swap to holding page only after operator says so.
Q4 2026	No SaaS build on cryptobook.space unless a demand-first GO is written. Optional: fix academy.tokensmarketcap.com 404 as a TMC project, not as this pivot.
2027	Re-open only with a named buyer, incumbent, price, and 60-second job.

Costs of doing nothing on this domain: nginx and the old Node cluster already run. Incremental cost of NO-GO is founder time not wasted plus RAM if we later stop the unused cryptobook cluster (4× Node workers on :3000).

8. Organization

Solo / Virtus operator. No sales team. No invented US Delaware entity in public copy. Governing law: to be confirmed by counsel; VPS is in Germany; do not print a fake jurisdiction.

9. Risk register (top)

Risk	If we ignore the study	Mitigation
Ship Slip anyway	Zero WTP; looks like a scam next to Permit.io	NO-GO is binding until replaced by a dated GO memo
cryptobook brand	Crypto-social leftover, expired-cert history on .com	Product name ≠ CryptoBook if a later SaaS ships
Legal overclaim	“Compliant,” “auditor,” “proves the work”	`08-legal-posture.md`
Domain DNS	.com is not this VPS	Do not advertise cryptobook.com until A record is 173.249.19.205

10. Ask of the operator

Pick A, B, C, or D in 10-strategic-options.md. Do not ask engineering to “just put something live” on cryptobook.space.