MIOSA icon MIOSA x Merydian Phase 1 proposal
Client discussion draft
22.07.26 / revision 2
Subject to written agreement

Pritt Investment Partners

Build the operating foundation, then prove it inside one department.

A USD 20,000 Phase 1 engagement that turns Pritt's current agents, business knowledge, roles, and one real operating workflow into a governed BusinessOS implementation.

Phase 1 investmentUSD 20,000 for the company foundation and one accepted department operating proof.

Expansion gateAdditional departments begin only after real users validate the first workflow and Pritt accepts the result.

MIOSAxMerydian
01 / Executive decision

The decision in front of Pritt

Do not start with nine agents or nine departments. Start by making Pritt's operating model explicit, then prove one complete loop.

30Approximate people operating across Pritt's company structure.
9Executive circles represented by human leaders and specialized AI roles.
1Department selected for the first operational proof.
$20KOne Phase 1 investment with a single delivery and acceptance record.

The system must know where work lives, who owns it, which context applies, what the expected output is, and how the result returns as evidence.

What Pritt already has

Agents, role concepts, operating knowledge, and executive intent

Those assets are valuable inputs. They are not yet a shared operating system for employees.

What Phase 1 creates

A governed company model and one accepted department workflow

BusinessOS becomes the interface. Optimal Engine becomes the context, memory, policy, and evidence layer.

Recommended pilot: choose Operations or Marketing based on operator commitment, accessible data, visible pain, and a measurable workflow.
MIOSAxMerydian
02 / Discovery is implementation

How the architecture becomes correct

We define the language of the business before configuring the software that operates it.

Discovery to architecture flow
Glossary

What words mean

Canonical definitions for departments, roles, projects, decisions, risks, documents, signals, and outcomes.

Taxonomy

How work is classified

Shared types for entities, workflows, documents, signals, statuses, priorities, and operating events.

Ontology

How work relates

Ownership, authority, dependencies, evidence, handoffs, permissions, and relationships between operating objects.

Why this matters: without the language and relationship model, the interface can look complete while agents retrieve the wrong context, act with the wrong authority, or create outputs that nobody owns.
MIOSAxMerydian
03 / Where work lives

Organization to evidence

Pritt's company structure becomes an explicit hierarchy, not a collection of prompts and disconnected files.

Organization and work location model
LayerWhat it controlsExample
OrganizationPrittIdentity, company policies, shared definitions, cloud boundary, and global authority.Pritt Investment Partners
WorkspaceDepartmentOperational context, members, modules, agents, permissions, rhythm, and department memory.Operations or Marketing
NodeWork objectProject, client, asset, workflow, offer, decision, risk, or recurring operating object.Capital project or campaign
SignalChange or requestWhat happened, what is needed, who should respond, and what evidence must return.Approval request or exception
Memory objectAccepted knowledgeFacts, decisions, lessons, commitments, and provenance that can safely inform future work.Accepted investment criterion
Boundary decision: discovery determines what remains local, what synchronizes to Pritt's cloud, who can see it, and which actions require approval.
MIOSAxMerydian
04 / Operating loop

From input to learned outcome

Every pilot workflow is designed backward from the outcome Pritt needs to observe.

Input, governed process, output, and outcome flow
Inputs

What enters the system

Requests, meetings, email, documents, CRM records, financial data, forms, alerts, and human instructions.

Governed process

What the system does

Classify, retrieve context, select the agent, apply policy, request approval, execute, and record evidence.

Outputs

What people receive

Documents, decisions, tasks, recommendations, updated records, messages, dashboards, and escalations.

Outcome and feedback

What proves value

Accepted work, corrected assumptions, cycle time, completion, revenue, risk reduction, and reusable memory.

Acceptance principle: a workflow is complete when a named user can produce the expected result, inspect how it happened, correct it, and return the result to the system as evidence.
MIOSAxMerydian
05 / Department second brain

One department, one governed operating memory

The pilot gives a department a usable second brain connected to real work, not a loose collection of prompts.

Department second brain reference architecture
What is deliberately not assumed: the selected department, source systems, model provider, integrations, approval model, and final interface are decided with Pritt during the paid discovery workstream.
MIOSAxMerydian
06 / Pilot evidence

Inspection, not black-box automation

The first department should make its operating work more visible before the team tries to scale it.

Illustrative department pilot evidence dashboard
Phase 1 outcome: Pritt receives a configured, inspectable proof for one department with a named outcome, role boundaries, real work evidence, and a clear acceptance decision.
MIOSAxMerydian
07 / Phase 1 delivery

One engagement, one accepted foundation

The USD 20,000 Phase 1 covers discovery, implementation, and one department proof with real users.

Phase 1 commercial and delivery sequence
Discover Model the company

Workshops, glossary, taxonomy, ontology, organization and workspace architecture, current-state intake, and boundary decisions.

Build Configure the system

BusinessOS, Optimal Engine, one governed workspace, selected modules, current agents, approved tools, and agreed integrations.

Prove Run one department

Named users, real work, controlled corrections, evidence, documentation, handoff, and one recorded acceptance decision.

GateEvidence requiredDecision
Architecture confirmationDuring Phase 1Approved language, hierarchy, workflow model, boundaries, artifacts, and implementation plan.Confirm the department implementation.
Pilot acceptancePhase 1 completionNamed users complete the agreed workflow and the evidence, permissions, corrections, and handoff are recorded.Accept, request an in-scope correction, or plan expansion.
Not included unless added in writing: additional departments, unlimited integrations, company-wide migration, third-party fees, cloud consumption, production service levels, and continuing operational support.
MIOSAxMerydian
08 / Continuing support

Optional after Phase 1 acceptance

Pritt can own the accepted system directly or retain the team for continuing operation and expansion.

Maintenance and support From USD 5,000 / month

System health review, dependency updates, incident response during agreed hours, minor corrections, documentation upkeep, and a monthly operating review. Capacity and response targets require a signed support schedule.

Optimization and expansion From USD 10,000 / month

Everything in maintenance plus active workflow optimization, controlled module enhancements, agent evaluation, data-quality work, analytics, and preparation for additional department implementations.

Pritt-owned path

Operate internally

  • Pritt owns its accounts, credentials, cloud, business data, and accepted artifacts.
  • The team completes handoff and documents the operating boundary.
  • New work is authorized as a project when needed.
Managed path

Retain MIOSA x Merydian

  • Choose support based on actual operating needs.
  • Define capacity, response expectations, exclusions, and renewal terms.
  • Review evidence monthly before increasing scope.
No automatic commitment: recurring service begins only after Phase 1 acceptance and a separate written support agreement.
MIOSAxMerydian
09 / Alignment meeting

The next working session

Use one 60-minute meeting to choose the pilot, confirm the inputs, and authorize the statement of work.

00-10Confirm the business objective

Define the current failure, desired result, urgency, and executive outcome.

10-20Select the first department

Choose Operations or Marketing and name one workflow with visible value.

20-35Inspect the current system

Review the org chart, users, agents, tools, sources, examples, and known constraints.

35-45Set ownership and boundaries

Confirm operators, approvers, data ownership, local and cloud placement, security, and access.

45-55Confirm delivery and acceptance

Align on scope, exclusions, success evidence, timing, payment schedule, and correction rules.

55-60Assign immediate actions

Name owners, dates, missing inputs, and the statement-of-work approval path.

Pritt before the meeting

Send the current-state package and confirm attendees.

Propose two meeting times, invite the executive sponsor, department owner, operator, and technical or security owner, and share the materials listed on the next page.

MIOSA x Merydian before the meeting

Prepare the decision agenda and draft implementation boundary.

Review the submitted materials, identify open questions, prepare the draft system map, and convert accepted decisions into the statement of work.

Meeting output: selected department, named workflow, owners, required inputs, system boundary, acceptance criteria, target dates, and the agreed path to signature and kickoff.
MIOSAxMerydian
10 / Start correctly

First client working session

Bring the people who own the work, the current system, and one real example from beginning to end.

Pritt sends before the session
  • Current organization chart
  • Department roster and authority
  • Existing agent commands and soul files
  • Current tools, systems, and integrations
  • Sample documents and expected outputs
  • One workflow with real source material
  • Security and cloud requirements
  • Known pain, failures, and success measures
Required participants
  • Scott as executive sponsor and acceptance authority.
  • The selected department owner.
  • At least one operator who performs the workflow.
  • Pritt's technical or security owner.
  • MIOSA architecture lead and Merydian delivery lead.
Working output: one accepted language map, workflow map, boundary map, artifact register, implementation backlog, and decision record.

Reply with two meeting times and the preferred pilot department. The team will confirm the session, review the current-state package, and prepare the decision agenda.

How we move forward: align in the working session, convert the accepted decisions into a signed statement of work, receive the initial payment, and schedule Phase 1 kickoff.