Client information request / Operations first

What we need from KII to start.

Fill this in and send it back, or answer by email if that is easier. We start the day the agreement is signed and these items are in hand. Almost everything here is a name, a link, or a date.

90Days, signature to handover

4Milestones, each accepted separately

1On-site week in Zurich, included

0Production changes without approval

The four steps

01 SEND DETAILS

Return this documentOr reply by email with the same points. Sections 2 to 7 are the whole request.

02 REVIEW AND AGREE

Review the work, then one signatureYour security owner reviews the data plan, then MIOSA sends the agreement for one signature. Day 0 starts at signature.

03 GRANT ACCESS

Open the doorsRead-only access to the systems listed on page 4, through your approved method.

04 ON-SITE WEEK

One week in ZurichIncluded in the price. We pick the dates in section 7 and confirm them.

What is inside

02 Company and contract details

06 Data and security

03 People and contacts

07 Operations examples and scheduling

04 Systems and access

08 Roadmap, Day 0 to Day 90

05 Infrastructure for the on-prem install

09 Kickoff checklist

IF SOMETHING IS MISSING

Send what you have and mark the rest open. We close the gaps together on the first Friday review.

IF THE PILOT DOES NOT FIT

Stop after Milestone 1 with no further fees, and keep everything delivered to that point.

WHO OWNS IT

KII owns the platform, with the full source handed over in KII's own repository by Day 90.

HOW TO SEND IT BACK

Return the filled document, or email the same points to roberto@miosa.ai. Partial answers are welcome, and the rest can be marked open.

WHAT HAPPENS TO YOUR ANSWERS

They become the environment plan, the access plan, and the interview schedule in the first ten days, and the first Friday review records them as the baseline.

Agency MIOSA is the delivery practice of MIOSA LLC. Prepared by Roberto H. Luna, Chief Executive Officer and Engagement Lead, roberto@miosa.ai.

Who we contract with and how we bill

Your company and contract details.

These are the fields that go straight into the agreement. If a field does not apply, write "not applicable" and we will leave it out.

Full legal entity name

Legal form (for example AG or GmbH)

Registered address

Commercial register number or UID

VAT number

Country of registration

Authorized signatory: name, title, email

Country of invoice and notice address for the agreement

Invoicing

Item	Your answer
Billing contact and invoice email
Purchase order or invoicing requirements PO number, portal, reference format, or anything else the invoice must carry
Preferred invoice currency Fees are stated in USD. Tell us if you need the invoice in another currency and we will confirm the exchange basis.

Anything else on this section

Notes: other entities, subsidiaries, or contract requirements

Why we ask: the agreement is signed with the legal entity named here, invoices go to the contact named here, and notices under the agreement go to the address named here. One page now avoids an amendment later.

One name per role

People and contacts.

One name per row, with the person who decides. Where a role is shared, list the decision maker here and the others in the notes column.

Role	Name	Email	Phone	Decides
Executive sponsor				Scope, milestone acceptance, date changes
Engineering evaluator				Architecture and technical acceptance
Business and budget owner				Invoices and any scope change
Operations owner				The Operations pilot and daily acceptance
Security and data owner				Access methods, data handling, Restricted Data
Microsoft 365 and Teams admin				Microsoft Graph consent and tenant policy
Data center and infrastructure owner				Install environment, network path, internal model
Accounting contact Later phase				Read-only accounting integration, after Day 90
Day-to-day project contact				Scheduling, examples, and the weekly status

A second person for each decision, optional

Role	Second person	Email	Notes
Executive sponsor
Operations owner
Security and data owner

Anything else on this section

Notes: who is available for a 30-minute interview, and any role we have missed

What this unlocks: the named people set the 30-minute interview schedule, join the Friday review, and approve access. A missing name is the most common reason a first week goes slowly.

Read-only is enough to start

Systems and access.

Your current tools keep running. We read through a mirror layer, and nothing writes to a production system without your approval. Tell us who owns each system and tick the box when access is ready.

System	What we need	Access type	Ready
Autotask	Accounts, contracts, tickets, and time entries	Read-only mirror	□
KII ERP (in progress)	Current schema, APIs, and a staging environment	Read-only mirror, API	□
Ticketing	Ticket sources, status fields, priorities, escalation paths	Read-only mirror	□
Time billing	Time entries and the billing rules tied to tickets and cases	Read-only mirror	□
Microsoft Teams via Microsoft Graph	An app registration with tenant consent for meetings and channels	Microsoft Graph API	□
Repositories	The Git host and the repositories to read, then a KII-owned repository for the fork:	Read, then admin on the KII repository	□
Documentation location	Where the current documentation lives, so we reuse it instead of rewriting it:	Read-only	□
Internal RAG	The current retrieval setup, sources, and embedding approach	Read-only, API	□
Accounting systems Later phase	Read-only integration after Day 90. Migration is out of scope for these 90 days.	Read-only, later phase	□
Other systems Add rows as needed			□

Anything else on this section

Notes: access restrictions, approval steps, or systems we have not listed

How access is granted: system by system, read-only by default, through your approved method only, with each account reviewed at every milestone and removed when it is no longer needed.

Do not email: passwords, shared administrator credentials, or unredacted client data. We will ask for credentials through your approved method and store them under the Data Management Plan.

The platform runs in your data center

Infrastructure for the on-prem install.

The platform runs on your hardware, with your internal model. Give us the shape of the environment and we will write the environment plan in the first ten days.

Server or VM for the platform: CPU, RAM, storage

Server OS and version

GPU for the internal model: model name, GPU type, memory

vLLM endpoint: URL format, port, authentication

Network access for our engineers: VPN or approved remote access

Backup and monitoring expectations

Environments: test and production, and who approves a change to each

Install window: when our engineers may work on the servers

Anything else on this section

Notes: hardware not yet available, other environments, or timing constraints

If some of this is not settled yet

Tell us what is still open. The on-site week is where the environment plan is written with your infrastructure owner. If the GPU or the vLLM endpoint is not ready, say so in section 7 and we will sequence around it without moving the milestones.

Set the boundary before production data

Data and security.

KII decides what is Restricted Data. We follow that instruction for the whole engagement.

Restricted Data category	Description	Owner

Add rows as needed. Example: any client configuration or credential material that must stay inside your data center.

Data classification policy: levels, labels, and what may enter the platform

Notices or consents your clients require (Swiss FADP and EU GDPR)

Retention requirements

Incident contacts: name, email, phone

Certifications or audits KII must satisfy

Security questionnaire, if KII has one: who receives it and who reviews the answers

Anything else on this section

Notes: rules we should know about, or documents you will send us

Restricted Data is never sent to third-party AI providers (see the Data Management Plan). It is handled only on KII infrastructure, or only with KII's internal model.

Real work, and the dates

Operations examples and scheduling.

We measure the system against your real work, not a demo set. Tick each item you can provide and add where to find it.

□ SAMPLE SIGNALS

A small set of real signals, with the routing you expect for each.

Where to find it

□ TICKETS

Open and closed tickets across priorities, with one escalation example.

Where to find it

□ CASES

Representative cases with owner and history, including one that went wrong.

Where to find it

□ TIME ENTRIES

Time entries tied to tickets and cases, with the billing rules.

Where to find it

□ ONE HANDOVER

One task that moves from one person to another, and the context each needs.

Where to find it

□ ONE CLIENT REPORT

One periodic report KII sends to a client, with its source data.

Where to find it

How these are handled: read through the mirror layer, under the Data Management Plan. Nothing is copied out of your estate unless you approve it.

Scheduling

30-minute interviews: who, and when they are available

Friday review slot: day, time, timezone

On-site week: preferred dates (day 1 to day 5), location, and who joins

Building access or visitor requirements

Anything else on this section

Notes: constraints on the interviews, the examples, or the on-site week

Reza is back in Zurich no earlier than October 19. Our preference is the week of October 20, and we will confirm the exact dates with you.

90 days, 4 milestones at USD 30,000, USD 120,000 total

From signature to a governed, owned platform, one department at a time.

DAYS 0 TO 10Mobilize (remote)

ON-SITE WEEKOperations audit and install

DAY 30M1 Operations pilot

DAY 45M2 Operations live

DAY 70M3 Second department wave

DAY 90M4 Company rollout and handover

Milestone	Days	What is delivered	Acceptance	Invoice
M1 Mobilization and Operations Pilot	Days 0 to 30	NDA signed, agreement signed once (Exhibits A and B attached), access, environment plan, 30-minute interviews, one on-site week, foundation installed on KII infrastructure, Operations pilot running on mirrored data with human approval gates.	Operations pilot runs on mirrored data with approval gates, confirmed in the Friday review.	USD 30,000 at signature
M2 Operations Live	Day 45	Real users live, Microsoft Teams integration via Microsoft Graph, shared project workspace with session handoff, role and data governance.	Accepted with real users working in the system.	USD 30,000 on acceptance
M3 Second Department Wave	Day 70	The second department chosen at kickoff, plus SOP and documentation completion.	Department live and SOP accepted.	USD 30,000 on acceptance
M4 Company Rollout and Handover	Day 90	Remaining in-scope departments, runbooks, admin training, and full source handover in KII's own repository.	Handover accepted and admin training complete.	USD 30,000 on acceptance

Change control: fixed-price change orders only

KII asks in writing. MIOSA returns an impact assessment within 3 business days. KII then chooses one of three paths.

PATH 1 / SWAP

Trade it outDrop in-scope work of equal size and take the new item instead, at no cost. Nothing is added to the price.

PATH 2 / DEFER

Add it to the roadmapPut it after Day 90 and plan it as a later phase, quoted separately when KII is ready.

PATH 3 / ADD

Sign a change orderSign a fixed-price change order and the work starts only after signature. Billed on signature unless the order states otherwise.

After Day 90, quoted separately

ACCOUNTING

Accounting system integration and migration, planned as a later phase.

AGENT AUTOMATION

Deeper agent automation where the first 90 days show it is worth it.

OTHER COMPANIES

Optional expansion to other group companies, each under a separate agreement.

Nothing outside the signed scope is started. Messages, meetings, demos, and proposals never expand scope on their own. Dates move when KII dependencies (access, decisions, examples, reviews) are late, by the length of the delay. Nothing after Day 90 is included in the price. Weekly rhythm throughout: a Friday review of 30 to 60 minutes, a written weekly status, and recorded decisions.

Kickoff checklist

We are ready to start when these five lines are checked.

One page to close the request. When all five lines carry a date, we confirm the kickoff and begin the first ten days.

Item	Ready	Owner	Date
This information request returned and complete	□
Agreement signed once (Exhibits A and B)	□
Data Management Plan reviewed	□
Access granted for the listed systems	□
On-site week dates confirmed	□

01 DAY 0

The agreement is signed

Day 0 starts at signature, and Milestone 1 is invoiced at signature.

02 DAYS 0 TO 10

We turn answers into plans

The confirmed answers become the environment plan, the access plan, and the interview schedule.

03 FIRST FRIDAY

The baseline is recorded

The first Friday review records what was confirmed, so nothing is carried in someone's memory.

Open items

Anything still open, and the date you expect an answer

Returned by

Name and role

Date

This request is not signed. It is returned with the information, and it is not part of the agreement.

Send it to: Roberto H. Luna, roberto@miosa.ai. Partial answers are welcome. Send what you have and mark the rest open, and we will close the gaps together on the first Friday review.