One company structure
Represent the organization, executive circles, departments, teams, roles, people, projects, and recurring work without flattening them into a single prompt library.
x
Merydian
Pritt Investment Partners / Implementation brief
Model the company.
Prove one department.
Then expand.
A governed BusinessOS foundation that connects Pritt's people, current agents, business knowledge, and one real operating workflow.
Phase 1 investment
USD 20,000
One company operating foundation plus one accepted department proof. The pilot department is selected during kickoff.
MIOSA x MERYDIAN
What we heard
Pritt does not need another disconnected AI tool. It needs one operating model that makes the current system usable by the company.
Use the existing agents
Bring forward the useful role concepts, agent instructions, soul files, commands, and operating knowledge Pritt has already created.
Local work, shared truth
Let authorized users work locally while approved company context, permissions, decisions, and evidence remain governed.
Role-aware interfaces
Show each person the modules, context, tasks, tools, and approvals required for their role instead of exposing the entire system.
One proof before expansion
Start with Operations or Marketing, execute one real workflow with named users, and prove the result before adding departments.
Pritt retains control
Pritt owns its accounts, data, credentials, cloud, business records, and accepted custom implementation artifacts.
Current assets
AgentsRole conceptsBusiness documentsToolsExecutive intent
become
A governed operating system
MIOSA x MERYDIAN
How the parts work together
BusinessOS becomes the operating surface. Optimal Engine supplies governed context. Pritt's infrastructure supplies the shared boundary.
01 / PEOPLE
BusinessOS
Each authorized user works through role-aware modules on their computer.
- Current agents and tools
- Department modules
- Tasks, decisions, and evidence
- Local model options
02 / CONTEXT
Optimal Engine
The company model determines which context applies and what each agent may do.
- Organization and workspaces
- Roles and permissions
- Facts, signals, and memory
- Policy and provenance
03 / SHARED
Pritt infrastructure
Pritt controls the cloud accounts, shared services, databases, and approved integrations.
- Team synchronization
- Hosted integrations
- Shared applications
- Security and observability
Control principleLocal-first execution, Pritt-owned data, explicit synchronization, inspectable agent actions.
Open foundationBusinessOS + Optimal Engine
Open-source product and context foundations Pritt can inspect and operate.
Service layerMIOSA
Deployment, orchestration, managed runtime, and implementation services used where selected.
DeliveryMerydian
Client coordination, implementation support, adoption, and operating handoff.
MIOSA x MERYDIAN
Discovery is part of implementation
We cannot design the correct interface until the team shows us where the work starts, who owns it, and what a good result looks like.
Pritt provides
- Organization mapCurrent companies, executive circles, departments, teams, reporting lines, and decision authority.
- User and role rosterThe first users, their responsibilities, permissions, and the work they own.
- Current agent packageAgent instructions, soul files, prompts, commands, tools, and known limitations.
- System inventoryCurrent applications, repositories, data sources, integrations, model providers, and cloud services.
- Real operating sampleOne workflow from its original input through review, output, handoff, and final decision.
- Acceptance evidenceSample documents, expected outputs, known failures, security constraints, and measurable success criteria.
MIOSA x MERYDIAN
One engagement, one acceptance decision
The USD 20,000 Phase 1 builds the company foundation and proves one department workflow with real users.
Discover
Map the organization, people, current tools, agents, workflows, boundaries, and expected outputs.
Model
Define the glossary, taxonomy, ontology, workspace structure, permissions, and acceptance rules.
Build
Configure BusinessOS, Optimal Engine, selected modules, current agents, tools, sources, and interfaces.
Pilot
Run one Operations or Marketing workflow with named users and controlled correction cycles.
Accept
Verify the output, permissions, evidence, handoff, documentation, and expansion decision.
Phase 1 investmentUSD 20,000
Timeline, payment schedule, named owners, and the selected pilot workflow are confirmed in the signed statement of work.
Included
- Company language and hierarchy model
- One governed Optimal Engine workspace
- BusinessOS configuration for named pilot users
- Selected current agents and agreed integrations
- One complete department operating loop
- Testing, documentation, handoff, and acceptance record
Not included without written expansion
- All nine executive circles or all departments
- Unlimited integrations or company-wide migration
- Third-party subscriptions, cloud, or model consumption
- Open-ended agent training or content production
- Production service levels or recurring maintenance
- Additional workflows after the accepted pilot
MIOSA x MERYDIAN
What completion means
Phase 1 is complete when named users can execute the agreed workflow and Pritt can inspect, correct, and own the result.
Usable
Named pilot users can enter the workflow through the agreed interface and complete their assigned actions.
Correctly scoped
The selected role, department, data boundary, and approval path behave as documented.
Inspectable
Agent actions, retrieved context, outputs, corrections, and decisions produce an auditable evidence trail.
Comparable
The output is reviewed against the real examples and success criteria agreed during discovery.
Documented
Known limitations, unresolved issues, operating instructions, and handoff responsibilities are recorded.
Accepted
Pritt records written acceptance, requests an in-scope correction, or authorizes the next phase.
Pritt controlsCompany accounts, cloud, credentials, business data, source materials, decisions, and accepted custom artifacts.
Open source remains openBusinessOS and Optimal Engine remain governed by their applicable open-source licenses.
Third-party services remain separateModel, cloud, communications, and software providers remain subject to their own accounts and terms.
MIOSA x MERYDIAN
Proposed alignment meeting
Use the next meeting to make five decisions, not to repeat the first conversation.
10 min
Confirm the business outcome
Define the exact result Pritt expects the first operating loop to improve.
10 min
Select the pilot department
Choose Operations or Marketing using pain, access, operator availability, and measurable value.
15 min
Walk through the current system
Review one real workflow, current agents, data sources, tools, handoffs, and known failures.
10 min
Set the operating boundary
Identify what remains local, what runs in Pritt's cloud, what synchronizes, and what requires approval.
15 min
Lock owners and next actions
Confirm participants, access package, security review, timeline, SOW details, and kickoff readiness.
Meeting output
Selected department, named workflow, required inputs, owners, assumptions, acceptance criteria, and a confirmed path to the signed SOW.
Scheduling
Reply with two times that work for Scott and the required owners.
The session should include the department owner and an operator. A technical or security owner should join the boundary portion.
x
Merydian
How we move forward
Approve one foundation. Prove one department. Expand only from evidence.
Review
Pritt reviews the proposed scope, exclusions, ownership model, and acceptance criteria.
Align
The teams hold the working session and confirm the pilot department, workflow, owners, and inputs.
Contract
MIOSA x Merydian issues the final statement of work with dates, payment schedule, and named responsibilities.
Kick off
Pritt provides the current-state package and the paid discovery and implementation work begins.
Phase 1USD 20,000
Company operating foundation plus one department proof.
Optional after acceptanceSupport from USD 5,000 / month
Only under a separate written support agreement with defined capacity and response expectations.