Offer

A written proposal before any paid work.

Vladislav Sapoval offers three ways to commission digital operations work. Each one is scoped to an operating area you can name. The fee, the timeline, and the boundary are in the proposal you see before you accept.

Engagement

Diagnostic

A bounded study of one operating area. It produces a written picture of how the work moves today and a recommended change, without asking the organization to rebuild everything at once.

Included

A defined operating area, agreed before the work starts.
Conversations with the people who run that area, plus a review of the artifacts they already use.
A written current picture, the main constraint, and a recommended next change.
A readout with the people who can act on it.

Cadence

Usually a few weeks. The exact length depends on access to people and materials, and it is stated in the proposal.

Boundary

A diagnostic describes and recommends. It does not silently turn into implementation, software buying, or staffing of the queue.

Engagement

Build cycle

A defined cycle to design and stage one operating area with the client team. The cycle ends with materials the team can run, not with a slide that still needs translating.

Included

Working sessions with the people who do the work.
The design for one service area: path, ownership, exceptions, and the review.
The documents listed for the services in scope.
A staged introduction of the change, sized so the live operation can absorb it.

Cadence

The proposal names the weeks, the sessions, and the week the materials are due. Changes to that boundary are written.

Boundary

The cycle does not include purchasing software, negotiating vendor contracts, or placing the practice inside the team as unnamed extra staff.

Engagement

Stewardship

A lighter rhythm after a diagnostic or a build cycle. It keeps the model honest as volume, tools, or priorities shift.

Included

A scheduled review of exceptions, measures, and decisions that drifted.
Adjustments to the path, the runbooks, or the cadence.
A short written note after each review.
A clear point of contact between reviews for questions that cannot wait.

Cadence

Typically a monthly rhythm. The proposal states the hours and the notice period for ending the rhythm.

Boundary

Stewardship supports the managers who own the operation. It does not replace them, and it is not an open-ended retainer for unrelated tasks.

What you receive in writing

The proposal states the operating area, the format, the fee, the payment rhythm, the timeline, the deliverables, and what is out of scope. It also names the people the work needs from your side and any access it requires. You accept by a written reply. Paid work starts after that acceptance and not before.

There is no universal price list. A small internal workflow and a multi-team customer operation are not the same assignment, and publishing one number would misrepresent both. The opening briefing is a conversation to confirm fit. It is not charged as a workshop.

Commercial terms that apply to every format

Either side may decline after the briefing or after reading the proposal.
A change that replaces the scope is written as a revision. It is not absorbed silently.
Travel or other expenses, if any are relevant, are agreed before they are incurred.
Invoices follow the payment rhythm in the proposal. The website does not take payment.
Confidentiality terms can be signed before detailed material is shared.

Outside this offer

The practice does not sell software licenses, manage advertising, provide legal or financial advice, or supply unnamed staff to clear a backlog. Practical automation, when it is part of a cycle, is limited to steps with a stable rule, data you have the right to use, and a person who remains accountable. Those limits are also described in the service notes.

If you want a proposal, describe the operating area on the contact form. The reply will say whether a diagnostic, a build cycle, stewardship, or no engagement is the honest next step.