IT for operating businesses

Keep the work moving. IT shouldn't feel like a fire drill.

The till should open without a dead line. The day shouldn't start with no coverage. We write the picture first — current environment, risks, a 90-day / 6-month / 12-month roadmap — so endpoints, network, cameras, and Microsoft 365 can run together. That is the paid assessment. Implementation, support, and procurement are separate jobs. No prices on the site.

Till and scanner — an unnamed working morning.

The till should open without a dead line. No prices on the site; the first step is a paid assessment.

Write the picture first. Then put the work in order.

Who this is for

One site or several — it does not matter. Retail, logistics, clinics, manufacturing. The field reality is endpoints, network, cameras, and Microsoft 365 running at once.

Not a cheap break-fix quote. We write the picture first.

No logos. No signage. The rooms where work stops if the line drops.

Separate commercial lines

Work after the assessment is not a second priced grid. Each line is its own proposal.

  • B

    Implementation / modernization

    After assessment, or when scope is already tight. Workstreams are split. We do not write a large fixed price before discovery.

  • C

    Support

    A monthly support fee (retainer), billed in advance. Hours, response window, and out-of-scope extras are written.

  • E

    Procurement

    One hundred percent of supplier cost before the order; the service margin is separate. We do not fund the client’s hardware from company cash.

The five commercial models are listed in full on Services.

What we sell / what we refuse

We sell

The paid assessment and roadmap is the default first step. Once scope is tight we write separate proposals for endpoint, server, network, firewall and Wi-Fi delivery; Microsoft 365 and identity advisory; and IT integration of cameras and line-of-business applications. On-site or remote support is a monthly fee or a written call-out; procurement starts after the supplier cost is in.

We refuse

We do not write an unscoped “fix everything” fixed price. We do not take walk-in consumer PC repair. We do not publish client names, logos, or identifiable site photographs.

Recording, ceiling — unnamed.

Assessment is four phases

Paid assessment in four phases — schematic.
  1. Phase 1 — Start and scope confirmation

    The opening meeting names critical stakeholders, site count, user band, and why the work is being asked now. Scope, priority and expectations are the output; “look at everything” is narrowed here. This phase is not labelled kickoff. Field scanning does not start before commercial acceptance.

  2. Phase 2 — Information gathering and environment analysis

    Interviews and questionnaires, review of existing documents and inventories, and on-site or remote technical review sit here. Endpoints, servers, network, identity, backup and field systems go into one file. Site count breaks the single-discovery assumption: each location is not a separate photograph; it is part of one operating picture.

  3. Phase 3 — Findings and risk assessment

    Technical and operational findings are classified. Critical risk, work that can be done immediately, and longer-range work are split. This phase is not a product list; “buy this box” becomes a procurement line only after risk and dependencies are written.

  4. Phase 4 — Roadmap and management summary

    Short-, medium- and long-term actions, ranked workstreams, procurement and implementation items, and the management presentation are the deliverables. 90 days / 6 months / 12 months is not a slogan on this page; it is a dated band in the pack. If the presentation is accepted, the order and the opening meeting are separate steps.

Operational notes and practice

  1. Cameras are part of the IT environment

    A camera order often arrives as a separate vendor, a separate password, and a disk nobody can name. Recording belongs on the same network, identity, and backup file. Who watches, where the stream lands, and who owns an outage — those three lines are written before any box list.

  2. Using the lzcat Command

    This command is an alias of `xz --format lzma --decompress --stdout`.

  3. Using the docker-inspect Command

    Return low-level information on Docker objects. More information: <https://docs.docker.com/reference/cli/docker/inspect/>.

Anonymized practice

We inventory the environment and write a 90-day / 6-month / 12-month roadmap.

Contracted on-site support, with hours and response window written as commercial lines.

The company is a new legal entity. The founder previously held direct technical responsibility, in a separate practice, for hundreds of endpoints and dozens of virtual workloads, with no known claims, major incidents, or data breaches.

Write to pin down scope

We do not publish prices on the site. Paid assessment is the default first step.

Request an assessment +90 541 859 25 87