For investors & partners

Four useful products.
One shared foundation.

Not Organic is building software for writing, learning, relationships, and everyday communication, with account and service infrastructure that can be reused across the portfolio.

The interwoven Not Organic knot
A shared foundation for distinct products.

Build the common parts once.

A writing tool and a tutor should feel different. Signing in, managing a balance, and understanding a charge should feel familiar.

Each product starts with a specific job: help someone write, understand an idea, build a relationship, or manage communication. The shared layer handles recurring infrastructure work such as authorization, credit accounting, and routing paid requests.

The investment thesis is that reuse can reduce the work needed to launch and maintain a portfolio. Whether that produces better retention, lower acquisition costs, or stronger margins must be established with operating data.

Different reasons to come back.

These are the products’ intended uses. Availability and feature maturity vary by product; this overview does not assert that every integration is deployed.

A business model you can inspect.

Product subscriptions

The catalog supports recurring plans and scoped credit allowances. The commercial case depends on paid adoption, retention, and the real cost of supplying those allowances. No revenue, subscriber, or fundraising figures are represented here.

Metered hosted services

The pricing code applies a 20% markup to upstream usage cost. That is a pricing rule, not a claim of 20% gross margin or a guarantee of profitability.

Illustrative usage economics

Upstream cost
$1.00
Price after 20% markup
$1.20
Difference before other costs
$0.20

$0.20 ÷ $1.20 = 16.7% before payment fees, hosting, support, taxes, credits, and losses. Actual gross margin requires those costs and realized revenue.

Pre-request reservations and post-request reconciliation help manage spending. They do not eliminate provider overruns, reconciliation failures, chargebacks, or operating costs.

Separate the foundation from the results.

Implemented in the repository

Scoped token exchange, device-bound request proofs, shared account records, a credit ledger, usage reconciliation, encrypted stored responses, and a TypeScript SDK.

Read the integration docs →

Requires operating proof

A working end-to-end purchase, signed payment notification, credit grant, metered debit, refund, and reconciliation. A passing unit test does not establish that a deployed payment flow works.

See the readiness checklist →

Commercial outcomes to measure

Activation, paid conversion, cohort retention, cross-product use, acquisition cost, contribution margin, support load, and incident frequency. This page makes no claim about current values.

The questions worth asking early.

Focus and distribution

A portfolio can spread a team too thin. Each product needs a credible route to users and evidence that it solves a recurring problem.

Shared infrastructure risk

Reuse can also concentrate outages and security exposure. Account boundaries, recovery, and independent product failure modes need testing.

Provider and payment dependence

Model pricing, vendor availability, fees, and merchant approval can change economics or interrupt a feature.

Trust and sensitive information

Learning, relationships, and personal communications require clear consent, privacy controls, and measured claims about AI capabilities.

Start with the evidence.

Technical and commercial diligence should answer the same question: what works, for whom, and at what cost?

Useful diligence topics include a product demonstration, architecture and security review, measured usage and retention, the payment lifecycle, operating costs, and the planned use of capital. No round size, valuation, committed investors, or investment terms are announced on this page.

Company overview · Updated 5 September 2026. This page is informational and is not an offer of securities.