Bring the brief. Get a decision.
Use this page for Cloud, Security, Microsoft 365, licensing, FinOps, and AI implementation work. You will get a direct answer from the founder, not a sales desk.
Send the working context
Short is fine. Specific is better. Do not send credentials here.
Service: Custom Ai Integration · Tier: Essential
Better briefs get faster answers
What to include
Keep credentials out of the first message. A high-signal summary is enough to decide whether this should become a workshop, quoted scope, or referral.
The desired outcome
Name the decision you need, the deadline, and what would make the work successful.
The technical boundary
Tenant, cloud, data residency, compliance scope, current vendors, and what cannot be changed.
The artefact you need
Workshop plan, implementation scope, migration path, runbook, Terraform, or handover pack.
After submit
A clear next step, or a clear no.
The contact flow exists to protect your time and mine. If the work is not a fit, you will not get dragged through a sales cycle.
- STEP 01Within one business day
Brief review
Michal reviews the brief and decides whether it fits the ITSailor delivery lanes.
- STEP 0230 minutes
Scope call
We clarify risks, access constraints, budget range, and whether a workshop or quoted scope is the right path.
- STEP 03No vague follow-up
Written next step
You receive a workshop link, a scoped proposal, a decline, or a referral to a better-fit provider.
- STEP 04For accepted work
Exit Kit standard
Every implementation closes with the documentation, config, and handover needed to leave cleanly.
EU intake path
Briefs are treated as confidential architecture material from the first message.
NDA available
Use the form for non-sensitive context. Ask for an NDA before sending diagrams or credentials.
No support hotline
Incident escalation is reserved for active retainer clients with signed procedures.