PerkOS

12 slides · click any slide to present from there

Built for a concise strategic conversation · no financial amounts

01From business problem to accountable AI team.
PerkOSCompany overview

AI teams for real business work

From business problem toaccountable AI team.

PerkOS discovers where AI can create value, assembles the right team, and provides the operating layer to put that team to work.

2026.08perkos.xyz
02AI adoption has a translation gap.
PerkOSThe problem
02 / 12
Two niches, one gap

AI adoption has a translation gap.

Take two businesses that look nothing alike. An independent medical practice, and an auto parts distributor selling to workshops. Both lose revenue in exactly the same place.

01

The work arrives as a message

A patient asks for an appointment. A workshop asks whether a part fits a 2018 pickup. Neither arrives as structured data.

02

The answer needs private context

It depends on the schedule and the insurance rules, or on the catalog, the stock, and that customer's price list.

03

One person is the bottleneck

The front desk answers the phone while patients wait. The counter quotes one workshop while three others go unanswered.

04

Slow answers are lost revenue

An unconfirmed appointment becomes a no-show. A quote that takes two hours becomes someone else's sale.

Two industries with nothing in common, and the same operating shape: unstructured demand meeting private context, with one person in the middle.
Company overview · 2026.08perkos.xyz
03The model is not the product.
PerkOSInvestment thesis
03 / 12
Our thesis

The model is not the product.The operating system around it is.

PerkOS is the control plane between business intent and AI execution: context, teams, workflows, approvals, evidence, and infrastructure in one system.

PerkOS

Operating layer

Business context
People + agents
Control + trust
Outcomes + evidence
Company overview · 2026.08perkos.xyz
04One continuous operating loop,
PerkOSThe system
04 / 12
How PerkOS works

One continuous operating loop, not another point solution.

01

Discover

Understand the business and find the highest-value opportunity.

02

Design

Turn evidence into a private, structured solution blueprint.

03

Assemble

Configure the right roles, knowledge, tools, and runtime.

04

Operate

Coordinate work through projects, tasks, chat, and approvals.

05

Improve

Use artifacts and outcomes to strengthen the next deployment.

Feeds the next cycle

Business-first. Start with a measurable need, not a model.

Human-controlled. Approvals and boundaries remain explicit.

Runtime-agnostic. Use PerkOS-managed or external AI runtimes.

Company overview · 2026.08perkos.xyz
05Three surfaces. One system.
PerkOSProduct architecture
05 / 12
Product surfaces

Three surfaces. One system.

01 · DISCOVER

PerkOS Grow

Adaptive business diagnostics turn unstructured needs into opportunity maps, reports, and a private machine-readable solution artifact.

Public intake · human-readable report · internal JSON
02 · OPERATE

PerkOS App

Organizations launch teams, create projects, coordinate tasks, maintain project context, and communicate with every participant.

Projects · tasks · documents · chat · approvals
03 · CONNECT

PerkOS Infrastructure

A runtime-neutral foundation connects managed agents and external OpenClaw, Hermes, or custom runtimes without owning their model choices.

A2A · model gateway · Knowledge · identity · settlement
Each surface is valuable alone. Together they create the discovery-to-operation flywheel.
Company overview · 2026.08perkos.xyz
06What is live today.
PerkOSExecution
06 / 12
Built and running

What is live today.

Production foundation

The current platform already spans discovery, operations, runtime connectivity, context, models, and knowledge. The next phase connects these pieces into one repeatable customer journey.

Adaptive discovery

Grow interviews, email verification, localized reports, private PDF and JSON artifacts.

Project operations

Organizations, projects, tasks, documents, direct chat, project chat, and team rosters.

External runtimes

Official install and repair flows for OpenClaw and Hermes with two-way PerkOS Chat.

Context plane

Authoritative project, conversation, roster, task, and evidence context before execution.

Model gateway

Multi-provider routing, metering, concurrency control, and bring-your-own-model support.

Knowledge layer

Research requests, evidence metadata, retrieval, and reusable organizational knowledge.

“Live” describes deployed product capabilities and production acceptance tests. It does not imply commercial revenue or customer volume.

Company overview · 2026.08perkos.xyz
07A real heterogeneous team, not a staged chatbot demo.
PerkOSProof of architecture
07 / 12
PerkOS Council

A real heterogeneous team, not a staged chatbot demo.

Project team

PerkOS Council

Connected
PerkOSOpenClaw · coordinator
AliceOpenClaw · external
BragiOpenClaw · external
AthenaHermes · external
MimirOpenClaw · external
Tyr + IdunnOpenClaw · external
Runtime-owned model routing. PerkOS coordinates work without forcing the agent's model.

Two-way communication

Messages travel from Project Chat to each external runtime and replies return visibly to the same conversation.

Authoritative context

Every run receives the current project roster, coordinator, tasks, documents, and conversation scope.

Isolation by design

Tenant, project, conversation, credential, and runtime boundaries prevent context from bleeding between users.

Company overview · 2026.08perkos.xyz
08Land with a problem. Expand with results.
PerkOSBusiness model
08 / 12
Commercial engine

Land with a problem. Expand with results.

Both niches buy the same way: a small operator with a visible, expensive bottleneck, an owner who decides in a single conversation, and a workflow that either pays back in weeks or does not.

ENTRY

Diagnose

One workflow, measured. Appointments confirmed per week, or quotes answered per day.

LAUNCH

Deploy

The practice or the counter goes live on its own schedule, catalog, price lists, and approval rules.

RECURRING

Operate

The team returns every day to the same inbox, board, and approvals. Usage grows with the business.

EXPANSION

Compound

Recalls and billing follow appointments. Backorders and receivables follow quoting.

Setup and workflow configuration
Monthly operation per practice or counter
Channel partners and vertical software
Company overview · 2026.08perkos.xyz
09Start where the pain is specific. Scale what repeats.
PerkOSGo to market
09 / 12
Two beachheads

Start where the pain is specific. Scale what repeats.

Our wedge is two niches, not a list of industries.

Independent medical practices, and auto parts distributors selling B2B to workshops. Both are small, both are decided by the owner, and both run on inbound requests that a person has to translate by hand.

Grow is the front door: a diagnostic that qualifies the business and produces the deployment brief.
01

Independent medical practices

One to five doctors, where the front desk sits between the patient and the schedule, and a no-show costs a full slot.

02

Auto parts distributors

Counters selling to workshops, where the first quote wins the order and the catalog lives in someone's head.

03

Channel partners

The people already inside these businesses: practice management software, parts catalog providers, accountants, and local consultants.

04

Template flywheel

Every deployment sharpens the playbook for the next one, so the tenth costs a fraction of the first.

Company overview · 2026.08perkos.xyz
10The moat is the closed loop.
PerkOSDefensibility
10 / 12
The compounding advantage

The moat is the closed loop.

Point tools can copy a feature. PerkOS compounds across discovery, solution design, execution context, runtime interoperability, and verifiable operations.

Discovery data

Structured evidence about what businesses actually need.

LAYER 1

Solution blueprints

Reusable private patterns that map needs to roles and workflows.

LAYER 2

Context plane

Current project truth delivered safely to every participating runtime.

LAYER 3

Runtime network

Managed and external agents connected without model lock-in.

LAYER 4

Trust rails

Identity, authorization, usage, receipts, and optional settlement.

LAYER 5
More deployments → better blueprints → faster outcomes → stronger distribution.
Compounding system
Company overview · 2026.08perkos.xyz
11The next twelve months.
PerkOSRoadmap
11 / 12
Where we are going

The next twelve months.

Forward plan

The roadmap moves from connecting today's products to making successful solutions repeatable, scalable, and increasingly self-improving.

1 month

Close the discovery-to-deployment loop

  • Native Grow workflow inside PerkOS
  • Private blueprint and reviewer path
  • Unified onboarding and observability
3 months

Make solutions repeatable

  • Vertical solution templates
  • Outcome measurement loop
  • Design-partner deployment playbook
6 months

Scale the operating layer

  • Multi-tenant orchestration at scale
  • Private solution catalog
  • Usage, billing, and partner controls
12 months

Compound into a network

  • Self-improving solution network
  • Cross-organization agent services
  • Optional machine-to-machine commerce
Company overview · 2026.08perkos.xyz
12Every business should be able to operate with an AI team.
PerkOS

The vision

Every business should be able to operate with anAI team.

PerkOS is building the system that turns business intent into accountable AI work, from the first question to the operating team.

Design partners Ecosystem partners Strategic partners