EXECUTIVE OPERATING SYSTEM SHUGYO

See the company. Improve the decision rhythm.

Shugyo connects company context, a business-shaped ontology, operational signals, decisions, and action. Evidence remains traceable, and the model changes with the business.

CORE PRINCIPLES 01

Built around the way your organization works.

Adaptability

The digital twin changes with your organization, so a restructure does not require a new schema or migration project.

Complexity

Organizations use multiple systems and often define the same term differently. Shugyo reconciles those differences without flattening useful detail.

Scale

The same architecture supports a 50-person company or a 5,000-person enterprise without a rewrite.

THE FOUR LAYERS 02

The system has four connected layers.

Integration supplies source data. The ontology gives that data meaning, the twin records its current state, and the presentation layer makes it usable for action.

If one layer is missing, the results become unreliable.

INTEGRATION 03
LAYER 01

Connect your existing systems without moving the data.

Your data stays in the ERP, CRM, databases, spreadsheets, and project tools you already use. Shugyo connects to those systems where they are.

What we connect
  • Enterprise systems: ERP, CRM, HRIS
  • Databases: PostgreSQL, MySQL, BigQuery
  • Business tools: Salesforce, HubSpot, Jira
  • Custom APIs and internal systems
How it works
  • Bi-directional sync with configurable frequency
  • Data validation and quality checks
  • Shugyo maps to your schema without a migration
  • Clear audit trail of every data movement
The result

Shugyo creates one consistent data layer across connected systems.

Each metric includes its source.

ONTOLOGY 04
LAYER 02

The structured vocabulary that defines your organization.

AI needs a clear model of your business. The ontology defines which objects exist, how they relate, and how they move through each process.

What ontology contains
ElementDescriptionExample
EntitiesThe things that exist in your organizationInvoice, Client, Employee, Project
AttributesProperties of each objectAmount, status, due date, owner
RelationshipsHow objects connectInvoice belongs to Client, assigned to Employee
ProcessesHow objects move through statesDraft to verified to sent to paid
How we build it
  • AI reviews schemas, sample data, and existing documentation
  • It proposes the objects and relationships in the model
  • You review the model and apply your domain knowledge
  • Shugyo builds the knowledge graph from the approved ontology
What the ontology provides
  • A shared vocabulary for your data and AI
  • Consistent definitions across different systems
  • Automatic updates after each sync
  • Defined inputs for KPIs, analysis, and AI capabilities
THE DIGITAL TWIN KNOWLEDGE GRAPH
LIVING MODEL

A living model of your organization.

The ontology defines the structure. The digital twin fills it with current data about the objects, relationships, and events in your organization.

Nodes Specific instances, such as Invoice FV/2024/001 and Client "Company ABC"
Edges Relationships between nodes, such as an invoice belonging to a client
History Each change records the actor, value, and time
Queryable Ask questions in natural language, get answers from the graph
BELONGS_TO BELONGS_TO BELONGS_TO Client Company ABC Invoice FV/2024/001 Meeting 12.01 Email 15.01

The digital twin records what happened without adding interpretation.

PRESENTATION 05
LAYER 03

See the business through the processes you define.

The presentation layer turns digital-twin data into views built around the questions your team needs to answer.

Lenses (processes)

A lens defines which part of the organization to view and how to measure it.

Lens typeWhat it measuresExample
Flow processObjects moving through statesInvoice: draft to verified to paid
Activity processAggregated activities + correlationMeetings compared with sales conversion
Goal-based processDefined target + metrics + horizonIncrease retention by 10% in Q2
KPIs with AI assistance
  • Describe what you want to measure in business language
  • AI proposes a calculation method and query
  • See results on real data
  • Approve or iterate

Business users can define a KPI and inspect the calculation behind each number.

Views
Dashboards Current state at a glance
Trends How metrics change over time
Drill-downs Inspect the records behind a summary
Natural language Ask a question in plain language
ACTION 06
LAYER 04

Use the model to spot issues and act.

The action layer uses the ontology and current company data to answer questions and guide action. Each result can be traced to its source.

Anomaly detection

Get notified when a metric moves outside its expected range.

Predictive insights

Model "what if" scenarios before committing resources.

Process recommendations

Recommendations use measured bottleneck data.

Natural language queries

Ask for invoices stuck in verification for more than five days and get the matching records.

Alerts & notifications

Receive alerts for the metrics and events you choose.

How Shugyo grounds AI in company data

General AI tools do not know how your company defines its objects and processes. Shugyo supplies that context from the ontology and knowledge graph.

  • The ontology supplies your organization's vocabulary
  • The knowledge graph supplies the current state of the organization
  • Each answer can be traced to source data
  • Each answer includes reasoning you can inspect and question
ARCHITECTURE OVERVIEW 07

How Shugyo connects your systems.

Shugyo cleans and maps source data before storing it in the digital twin. Process views and the AI assistant use the same model.

Client systems
Where your data already lives
ERPCRMDatabasesSpreadsheetsOther systems
Data layer
Source data is cleaned, unified, and mapped Data moves through ingestion and transformation into the warehouse. Every metric is traceable to its origin.
AirbytedbtBigQuery
Digital twin
A living representation of your organization Graph database: nodes, relationships, and full history of every change.
Processes & KPIs
Lenses, metrics, trends, dashboards
AI assistant
Natural language, insights, alerts
PROCESS DEFINITION FRAMEWORK 08

Measure each process according to how it works.

01

Flow process

Track objects moving through defined states.

What it measures

Invoice counts by stage, time in stage, and handling time by owner.

Purchase Invoice Handling
Name Purchase Invoice Handling
Object Invoice (type: purchase)
Steps draft to verified to sent to paid
SLA max 14 days, entry to payment
02

Activity process

Correlate activities with outcomes.

What it measures

The relationship between client engagement, revenue, and specific sales activities.

Client Engagement
Name Client Engagement
Activities Meetings, Emails, Notes
Input Meetings/client/month, response time
Output Invoice value per client, upsells
Thesis More meetings correlate with higher sales value
03

Goal-based process

Set targets and track progress.

What it measures

Progress against the target, including drivers and blockers.

Q2 Retention Initiative
Name Q2 Retention Initiative
Goal Increase retention by 10%
Metrics Churn rate, NPS, support tickets
Horizon Q2 2025
SECURITY & COMPLIANCE 09

Security controls for enterprise deployment.

Data security

  • SOC 2 Type II in progress
  • Encrypted at rest and in transit
  • Regular audits & penetration testing

Access control

  • SSO support (SAML, OIDC)
  • Role-based access control
  • Audit logs for all data access

Data privacy

  • Your data stays yours
  • Clear data processing agreements
  • GDPR-compliant data handling

Deployment options

  • Cloud, managed by Shugyo.ai
  • Private cloud in your infrastructure
  • Hybrid with sensitive data on premises
IMPLEMENTATION TIMELINE 10

A typical rollout, week by week.

Weeks 1-2

Discovery

  • Understand your systems and data sources
  • Identify the first processes and metrics
  • Plan integration approach
Weeks 3-4

Integration

  • Connect data sources
  • Build the data layer
  • Validate data quality
Weeks 5-6

Ontology

  • AI-proposed organization model
  • Your review and refinement
  • Knowledge graph construction
Weeks 7-8

Activation

  • Define initial lenses and KPIs
  • Train users
  • Go live with monitoring
Ongoing

Evolution

  • Add new data sources
  • Refine ontology as you change
  • Build new processes and KPIs
TECHNICAL SPECIFICATIONS 11

Technical stack and performance targets.

ComponentTechnologyNotes
Supported ingestionAirbyteOptional path with 300+ connectors
Supported transformationdbtOptional, version-controlled, tested
Supported warehouseBigQueryUsed when the evidence path requires it
Graph databaseNeo4jACID compliant and optimized for graph queries
AI / LLMOpenAI / AnthropicSupports multiple model providers
APIREST + GraphQLProgrammatic access to Shugyo data
Performance targets
UI response < 500ms
API p95 < 800ms
Cache hit < 200ms
LLM Streaming in real time
REQUEST EARLY ACCESS

See how work moves through your organization.

Shugyo combines the four layers into a model you can trace to source data and use to understand day-to-day operations.