KII Business OS: proposal and scope of work
One operating system for KII.
Owned by KII.
Operations first, on-prem, human-approved. A 90-day engagement to install a KII-owned Business OS on KII's own infrastructure, prove it on the Operations loop, and hand over the source in KII's repository.
The engagement
USD 120,000
90 days. Four milestones. One on-site week in Zurich.
A small paid pilot at signature. After Milestone 1, KII may stop with no further fees and keep everything delivered to that point.
Prepared for
Dr. Reza Kordi
Managing Director, KII
Prepared by
Roberto H. Luna
Principal Architect and Engagement Lead
Agency MIOSA
Date and status
October 6, 2026
v1.0 for client review
Our position
KII owns the system. Operations proves it. Nothing in production changes without approval.
KII is not buying seats, a chatbot, or another tool to grow out of. It is commissioning one operating system for the company, running on KII's own infrastructure, that reuses KII's existing work and stays under KII's control.
01 / OWNERSHIP
KII owns the system
KII receives a fork of the BusinessOS platform under the Apache License 2.0 in KII's own repository, plus every KII-specific module, configuration, and document produced in the engagement. It can be rebranded as KII's own platform.
02 / OPERATIONS FIRST
A small vertical, proved early
Phase 1 starts with Operations: real signals, tickets, cases, and time billing, read through a mirror and run behind a human approval gate. The loop is proved on mirrored data before it goes near production.
03 / NO DISRUPTION
Current tools keep running
Autotask, KII's own ERP, ticketing, and Microsoft Teams stay in place. The system reads through read-only mirrors and proposes changes. A person approves before anything is applied.
90 daysSignature to full handover
4Milestones, each separately accepted
1On-site week in Zurich included
0Changes to production without approval
A small first payment, as requested: Milestone 1 is invoiced at signature and covers mobilization and the Operations pilot. If KII decides not to continue after Milestone 1, the engagement stops with no further fees and KII keeps everything delivered to that point.
Reading order
What this document covers.
Two companion documents: the Data Management Plan covers data handling, residency, and disposal. The Client Requirements and Roadmap document records KII's requirements and the sequence after Day 90. This document is the proposal and the scope of work.
The company and the loop
A small team, deep client relationships, and a working loop that deserves better tools.
KII TODAY
A boutique Swiss network engineering firm
- 12 people, with every function present in minimal form.
- About 20 long-term clients and strong relationships.
- Minimal marketing and no push to grow quickly.
- Developers are loaded with client projects and have no time to build internal tools.
- In-house AI experiments in Java and Python with no governance around them.
WHAT KII ASKED FOR
One system, owned by KII, that improves with KII
- Governed shared project context: people and agents on the same project, sessions visible, work can be taken over.
- Operations first, as a small vertical slice that proves it works.
- Reuse existing repositories and documentation instead of starting from interviews.
- No disruption to live operations, with a human in the loop before any production change.
- On-prem throughout, in KII's own data center.
01
SignalA client signal arrives from monitoring, a person, or a Teams message.02
TriageThe team classifies what it is and how urgent it is.03
TicketThe work becomes a tracked ticket with an owner.04
CaseRelated tickets and history collect into a case for the client.05
ResolutionAn engineer resolves it against the client's environment.06
Time billingThe time is captured and billed from the record of the work.
The stated risk, answered directly: KII does not want another tool the team invests time in and eventually outgrows. This system is not rented. KII owns the fork, the modules, and the documentation, so the tool grows with the company instead of being replaced.
KII-controlled production boundary
On-prem by default. Read-only by design. Human-approved before anything changes.
01 / SOURCES
KII's current estateAutotask and KII's own ERP, ticketing, time billing, Teams via Microsoft Graph, repositories and documentation, and in-house RAG.02 / MIRROR
Read-only mirror layerCurrent systems keep running. KII's Autotask and ERP mirrors are configured and accepted in Milestone 1.03 / KII BUSINESS OS
Workspaces and contextWorkspaces, company glossary, shared project context, and agents on KII's internal vLLM model.04 / APPROVAL GATE
Authorized KII roleAny change to a production system is proposed, reviewed, and approved by an authorized KII role first.05 / PRODUCTION
Apply with a receiptApproved changes are applied to production systems and recorded, with the approver and the time.
Runs on KII hardware
The system runs on-prem in KII's own data center, with no public cloud dependency for operations.
Internal model, research only
Operations run on KII's internal model served via vLLM. Frontier models are used only for research, and only where KII allows.
Teams stays
Microsoft Teams remains in place. The Teams connector for KII is configured and accepted in Milestone 2, through Microsoft Graph, which KII already uses.
Why the mirror layer matters: a read-only mirror means the system can learn from real operational data without touching production. Current tools are never put at risk while the new loop is proved.
People and agents, one workspace
People and agents work in the same workspace, on the same project.
This is the capability KII responded to first: not a private chatbot per person, but a governed place where the team and its agents share context, and where work can change hands without losing anything.
Shared canvas
Phase 1 delivers a shared canvas where a person and an agent work on the same project, with the same files, tasks, and context.
Cross-user session visibility
Configured and accepted in Milestone 2: sessions are visible to the team according to role, so the team can see what is happening and who is doing it.
Takeover with full context
Another person can take over a task with full context. Shifts, holidays, and handovers do not lose the reasoning behind the work.
Company glossary
Every person and agent uses KII's own terms. The glossary is part of the system, so agents speak KII's language, not a generic one.
01
OpenA person opens a session in the project workspace.02
Work with an agentThe agent works from the same project context and glossary.03
Visible by roleThe session is visible to the team according to role.04
Take overA colleague picks up the task with the full context.05
PersistContext, decisions, and history stay in the workspace.
On-prem team sync: Phase 1 delivers on-prem team sync, so the shared workspace and session visibility run inside KII's own data center. Data does not leave KII's infrastructure.
Control at three levels
Three levels of control. One approval gate before anything changes.
USER
Named identities
Every person and every agent has a named identity. Access is explicit, and nothing acts anonymously.
ROLE
Permissions follow the role
A user sees and can do what their role allows, not more. Roles are KII's roles, recorded in the system.
DATA
Data levels
Data levels control what each role may read and change. KII's data stays on KII infrastructure.
01
ProposeA person or agent proposes a change to a production system.02
RouteThe proposal goes to the authorized KII role for that system and data level.03
ReviewThe reviewer sees the proposed change, its source, and its effect.04
ApproveOnly an authorized KII role approves the change.05
ApplyThe approved change is applied to the production system.06
ReceiptThe change, the approver, and the time are recorded.
The rule that does not bend: no change reaches a production system without a person approving it first. The approval gate is enforced by the system, not by convention, and it is tested as an acceptance criterion in Milestone 1.
Reuse, not rewrite
KII's existing work comes in through APIs. Nothing is thrown away.
KII asked how its existing modules come into the system. The answer is API-first integration: existing code, repositories, experiments, and documentation are reused as the starting point, not replaced.
| Existing asset | How it comes into the KII Business OS |
|---|
| Modules in any language | Existing modules in Java, Python, or any other language connect through documented APIs. The code is reused, not rewritten. |
| Existing repositories | Reused as the working base. The system reads the code and context that already exists. |
| In-house RAG work | Reused as a source so KII does not end up maintaining a second knowledge base. |
| Current systems | Autotask and KII's ERP come in through read-only mirrors, configured and accepted in Milestone 1. |
| Teams | The Teams connector for KII is configured and accepted in Milestone 2, via Microsoft Graph. |
| Documentation | About 30 to 40 percent complete today. Agency MIOSA helps complete it in parallel during delivery. |
Documentation completed in parallel: the system never depends on undocumented knowledge. Documentation is finished alongside delivery, not left for later.
Nothing is migrated blindly: existing modules keep working where they are. The system orchestrates them through interfaces, so KII's team sees one system without a risky rewrite.
No lock-in, no outgrowing
KII owns its fork, its modules, and its documentation.
| Layer | License and ownership | Where it lives | What KII can do |
|---|
| KII Business OS fork | Apache License 2.0. KII's fork. | KII's own repository | Operate, modify, rebrand, extend, and continue without Agency MIOSA. |
| Optimal Engine component | MIT licensed. | In KII's repository and in the open | Use, inspect, and replace. No lock-in. |
| KII-specific modules and configuration | Belong to KII. | KII's repository | Keep, change, and reuse freely. |
| KII documentation | Belongs to KII. | KII's repository | Keep and extend. Completed in parallel during delivery. |
| KII data | Belongs to KII. | KII infrastructure | Stays on KII infrastructure under the Data Management Plan. |
Agency MIOSA contributes to KII's fork only with KII's permission. The source is always in KII's repository, so any qualified engineer KII chooses can continue the work.
REBRANDABLE
KII's own platform
KII can rebrand the system as its own platform, for example KII Management Platform, with KII's name and identity.
NO OUTGROWING
The tool grows with KII
Because KII owns the fork and the modules, the system improves with KII rather than being replaced when it stops fitting.
Fixed scope
One company, one foundation, four milestone waves.
DAYS 0-30Mobilize and Operations pilot on mirrored data
DAYS 30-45Operations live with real users and Teams
DAYS 45-70Second department wave plus SOP and documentation
DAYS 70-90Company rollout and full source handover
IN SCOPE
- KII only, with Operations as the first vertical.
- Foundation installed on KII's own infrastructure.
- Mirror layer for Autotask, KII's ERP, ticketing, and time billing.
- Teams connector via Microsoft Graph.
- Shared project context, glossary, and governance at user, role, and data levels.
- A second department wave chosen at kickoff.
- SOP and documentation completion, runbooks, and admin training.
- Full source handover in KII's repository.
OUT OF SCOPE
Unless separately contracted, the following are not part of this engagement:
- The cybersecurity company in the group.
- The Vietnam operation.
- The Hong Kong project.
- Accounting system migration. Accounting is integrated read-only later and migrated in a later phase on the roadmap.
- Additional on-site weeks beyond the one included.
- Expansion to other group companies.
Pilot exit: after Milestone 1 acceptance, KII may stop with no further fees, keep everything delivered to that point, and require Agency MIOSA to dispose of KII data per the Data Management Plan. Scope does not expand silently; added work is agreed in writing.
Day 0 is signature
Ninety days, four accepted milestones, target dates confirmed at kickoff.
| Gate | Window | Working output | Acceptance evidence | Payment |
|---|
| Mobilize | Days 0 to 10 | NDA and Data Management Plan countersigned, registration documents provided, access to repositories and documentation, environment plan, interviews scheduled. | Signed documents and confirmed access. | Included in M1 |
| On-site week | Target week of Oct 20 | Operations audit, company glossary and operating primitives, Operations workflow mapping, install of the foundation on KII infrastructure. | Foundation running on KII infrastructure. | Included |
| M1 Operations Pilot | Day 30 | Operations pilot running on mirrored data with human approval gates. | Pilot demonstrated with the approval gate enforced. | USD 30,000 at signature |
| M2 Operations Live | Day 45 | Real users, Teams integration via Microsoft Graph, shared project workspace with session handoff, role and data governance. | Named users working daily, takeover demonstrated. | USD 30,000 on acceptance |
| M3 Second Wave | Day 70 | Second department wave (chosen at kickoff), plus SOP and documentation completion. | Second department live, SOP accepted. | USD 30,000 on acceptance |
| M4 Rollout and Handover | Day 90 | Remaining in-scope departments, runbooks, admin training, full source handover in KII's repository. | Runbooks, training, and source handover accepted. | USD 30,000 on acceptance |
Weekly rhythm
- 30-minute interviews with team members.
- Friday review with KII, 30 to 60 minutes.
- Written weekly status.
- Recorded decisions.
Gate discipline
- No silent scope change.
- No production change without approval.
- No milestone accepted without evidence.
- Target dates confirmed at kickoff.
Each milestone is measured, not claimed
Every milestone is accepted against a concrete check.
| Milestone | Acceptance check |
|---|
| M1 Mobilization and Operations Pilot | The foundation is installed and running on KII infrastructure. The Operations pilot runs on the mirrored data for the representative cases agreed at kickoff. The approval gate is enforced on every production-bound change, and the company glossary is accepted. |
| M2 Operations Live | The named users agreed at kickoff are working daily in the workspace. Teams context is visible through the Microsoft Graph connector. A task takeover with full context is demonstrated. Role and data governance are enforced. |
| M3 Second Department Wave | The second department chosen at kickoff is working in the system. SOP and documentation are completed to the coverage agreed at kickoff and accepted by KII. |
| M4 Company Rollout and Handover | The remaining in-scope departments are live. Runbooks and admin training are accepted. The full source is handed over in KII's repository, and a restore drill is passed. |
Numbers that depend on KII are agreed at kickoff: the representative cases, the named users, the second department, and the documentation coverage are confirmed with KII at kickoff and recorded in the delivery baseline, so acceptance is measurable without inventing targets.
Evidence, not slides
Each check is demonstrated on the running system with KII present.
Written acceptance
Each milestone is accepted in writing before the next is invoiced.
Pilot exit honored
If M1 is accepted and KII stops, the engagement ends with no further fees.
Who does the work and who stands in
A named lead, a small senior team, and continuity built into the contract.
| Role | Accountability | Status |
|---|
Roberto H. Luna
Principal Architect and Engagement Lead | Product architecture, delivery governance, KII decisions, and the acceptance boundary. The single point of accountability for the engagement. | Named |
| Delivery lead | Day-to-day delivery, schedule, and coordination with KII's named owners. | Named at kickoff |
Senior engineers
15 to 20 years of experience | Implementation and integration of the foundation, mirrors, and modules. | Named at kickoff |
Data management lead
Enterprise data governance specialist | Data Management Plan, mirror layer, data levels, and data residency. | Named at kickoff |
Who stands in for Roberto: KII asked this directly. At least two engineers carry full context and access, so delivery does not depend on one person. The delivery lead is named at kickoff and owns the schedule when Roberto is not on site.
CONTINUITY PRACTICES
- Documentation-first delivery.
- Every decision recorded.
- At least two engineers with full context and access.
- Runbooks maintained from week one.
- Friday reviews recorded.
- Source always in KII's repository, so any qualified engineer can continue.
A working relationship before a critical project: the on-site week exists so KII can judge how the team works before the larger milestones, and so the team can learn Operations from the people who do it.
Fixed fee and milestone billing
USD 120,000 for 90 days. The on-site week is included.
TOTAL ENGAGEMENT
USD 120,000
A 90-day engagement with four milestones, each separately accepted. Exclusive of applicable taxes.
ON SITE
Included
One on-site week in Zurich (3 to 5 working days). Agency MIOSA covers its own travel and lodging for that week. Additional weeks only by written agreement.
| Milestone | Amount | Invoiced | Target acceptance |
|---|
| M1 Mobilization and Operations Pilot | USD 30,000 | At signature | Day 30 |
| M2 Operations Live | USD 30,000 | On acceptance | Day 45 |
| M3 Second Department Wave | USD 30,000 | On acceptance | Day 70 |
| M4 Company Rollout and Handover | USD 30,000 | On acceptance | Day 90 |
| Total | USD 120,000 | Milestone billing | Day 90 |
Pilot exit: after Milestone 1 acceptance, KII may stop with no further fees. KII keeps everything delivered to that point, and Agency MIOSA disposes of KII data per the Data Management Plan.
Taxes, terms, and data on exit: fees are exclusive of applicable taxes. Invoices are due within 14 days. On exit or completion, KII data is disposed of per the Data Management Plan, and the delivered source stays in KII's repository.
What KII provides, confirmed at kickoff
The fixed fee depends on timely decisions and usable access.
| Area | What KII provides | Confirmed |
|---|
| Named owners | Executive sponsor (Reza), engineering evaluator, business and budget owner, Operations owner, and security owner. | At kickoff |
| Access | Repositories, documentation, Autotask and ERP APIs, Teams via Microsoft Graph, the vLLM endpoint, and a data center environment for install. | Days 0 to 10 |
| Representative examples | Real signals, tickets, cases, and time entries, provided via the mirror and under the Data Management Plan. | At kickoff |
| Time and rhythm | 30-minute interviews per team member and Friday reviews. Year-end is KII's busiest period and is planned around. | At kickoff |
| Data residency | Swiss FADP and EU GDPR. Data stays on KII infrastructure. Remote access only through KII-approved methods. | At kickoff |
| On-site week | Week of October 20, 2026, or the first week Reza is back in Zurich (no earlier than October 19). | At kickoff |
ASSUMPTIONS
- KII provides the named owners and access on time.
- The mirror and Teams integration are technically reachable through existing APIs and Graph.
- KII's data center can host the foundation.
- Target dates are confirmed at kickoff.
IF AN INPUT IS LATE
- Delivery works on the parts that are unblocked.
- The schedule impact is documented and agreed.
- Blocked capability never bypasses policy or approval.
- No silent substitution of scope.
From proposal to a signed start
Review the proposal. Meet the team. Start on site.
KII
Before we start
- Review this proposal and the two companion documents.
- Request a call with reference clients if it is useful.
- Name the executive sponsor, engineering evaluator, business and budget owner, Operations owner, and security owner.
- Confirm the on-site week.
AGENCY MIOSA
At kickoff
- Countersign the NDA and Data Management Plan.
- Provide registration documents.
- Open access to repositories and tools.
- Schedule the 30-minute interviews.
- Install the foundation on KII infrastructure and begin the Operations pilot.
REFERENCE CLIENTS
See it working
KII has already seen a live demonstration. On request, KII can speak with owners of comparable systems delivered by Agency MIOSA before signing.
THE SEQUENCE
- Documents: this proposal, the Data Management Plan, and the Client Requirements and Roadmap.
- Internal review at KII.
- Sign the scope of work, the NDA, and the Data Management Plan.
- Access to tools and the data center environment.
- On-site week in Zurich, target week of October 20.
Signing set: the statement of work, the NDA, and the Data Management Plan. Final dates and named roles are recorded at kickoff.
KII's advantage will not come from having more tools. It will come from owning one operating system that knows how KII works, improves with KII, and never changes production without a person approving it.
Agency MIOSA