Skip to content

For investors

Target

This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.

Business model

Three revenue lines on one platform (commercial model):

  1. The Factory as a platform — editions sold to organizations (internal budget control, usage-based, seat plans), metered on runs, tokens, instances and seats.
  2. Generated products operated as a managed service — recurring revenue per operated product under Managed and ManagedPlus editions (decision D33).
  3. A marketplace — distribution of qualified agents, skills, templates and products with publisher revenue shares (later stage).

The same SaaS foundations (tenants, products catalog, entitlements, billing, metering) serve all three and the products ConnectSoft ships to its customers, so the commercial stack is built once.

Market

Every organization adopting agents faces the same governance gap; software delivery is where it shows first and where ConnectSoft already sells. The design targets twenty-nine verticals from the prototype set with one generation path (examples); the Config Platform and SaaS control plane prototypes are the most mature.

The moat: owned intelligence

Models are replaceable; what an organization accumulates is not. The Factory keeps, per tenant, the published assets (agents, skills, workflows, tools, profiles, templates with evaluation evidence), the knowledge and memory (sources, indexes, promoted procedures with consent), and the execution history (runs, receipts, audit, usage). A model provider change is a profile change; a competitor cannot copy years of evaluated assets and evidence.

flowchart LR
    M[Models · replaceable profiles] --> A
    subgraph Owned [Owned by the organization]
      A[Published assets with evidence] --> K[Knowledge · memory · consent]
      K --> H[Execution history · receipts · audit]
    end
    H --> V[Value compounds per tenant]
Hold "Alt" / "Option" to enable pan & zoom

Capability dependencies, without dates

What must exist before what, as a dependency view rather than a roadmap (capability dependencies, ecosystem composition):

flowchart TB
    E[Existing estate · templates · identity · SaaS foundations · messaging · AI extensions] --> C[Control plane · runs · approvals · assets]
    C --> R[Agent runtime · model gateway · tool executor]
    R --> K[Knowledge · memory · context]
    R --> G[Governance · policy · audit · secrets]
    C --> D[Delivery · provisioning · observability]
    D --> F[Fleet operations · managed products]
    C --> S[Studio]
    F --> MK[Marketplace · later]
Hold "Alt" / "Option" to enable pan & zoom

Evidence of what exists

Exists in production use Specified, not built
43 templates, about 125 libraries; the clean-architecture kernel; Pulumi programs; pipelines run control, approvals, asset publication
Authorization Server (OpenIddict) and Identity service agent runtime, model gateway, tool executor, sandboxes
SaaS foundations (tenants, products, entitlements, billing, metering) as templates knowledge platform, memory promotion, repository intelligence
Messaging port with Orleans, MassTransit and NServiceBus adapters; NHibernate persistence governance engine, audit chain, secret broker
AI extensions on the Microsoft Agent Framework; MCP library observability projections, evaluation, feedback
A production product (DerechHaLev) built from the estate delivery, provisioning, fleet operations, Studio, marketplace

The site's model report counts the specification; the home page states what is real today.