Purchasing often wants a single line: connect this, quote that. Pricing work that has no written scope as an implementation project is the wrong order. When the need is broad or only partly defined, the default first paid step is offer A: a paid assessment and roadmap. There are no prices on the site.

This note is the reasoning behind the method on the Approach page. Phase titles match the proposal template. The job is to turn an unclear need into a 90-day / 6-month / 12-month plan before anyone writes an implementation, support, or procurement proposal.

What offer A delivers

Offer A is an inventory of the current environment. Endpoints, servers, network, identity, backup, and field systems go into one file. Deliverables are a current-state summary, a risk and priority matrix, a 90-day / 6-month / 12-month roadmap, and a management presentation. Senior judgement is what is sold; it is not a dump of hours.

A fixed price does not hold until “look at everything” is narrowed. We first ask which environment is actually in the assessment, who can sign, and whether a cutover window is tied to till close. The output is a written scope note that tells the next phase where to start.

The assessment is not an implementation project. After the inventory is written, modernisation (B), a monthly support fee or call-out (C / D), and procurement (E) open as later proposals. We do not fold several lines into one “do all of it” sentence. A “no signal” complaint at the fourth branch is rarely an order for a stronger access point; SSID, VLAN, guest network, DHCP, and who is on call belong to the same operating picture. Drawing that picture is offer A’s work.

The management summary is the document purchasing will actually read. Ranked risk and dated bands sit there. “Buy this box” does not become a procurement line until risk and dependencies are written. That split keeps the next order from walking through the wrong door.

Outside the assessment fee

The assessment fee does not include:

Hardware sourcing and purchasing
Implementation, installation, migration, or cutover
Third-party software or licensing costs
Ongoing operational support (no retainer inside this fee)

Hardware sits outside this fee for a commercial reason, not as padding. The full supplier cost is collected before the order; the service margin is separate. The company does not finance customer hardware from its own cash. “Buy this” written before VLAN, identity, and backup are on paper produces the next outage and the wrong purchase order. Unless the proposal says otherwise, installation, purchasing, and run-state operations are later phases.

Licences follow the same order. A seat count is not a design. Who is in which box, whether former accounts are closed, and whether passwords still live on paper all go into the inventory. We do not put a one-line fixed price on “we will migrate the tenant” without that file.

Ongoing support is not an annex to the assessment fee either. A monthly fee (retainer) or a signed call-out model states hours, a response window, out-of-scope work, and travel as separate lines. The on-call number sits in the proposal. When the assessment is delivered, operations have not yet been sold.

Four phases

Phase titles follow the proposal template. The numbers live in the heading. The meeting after commercial acceptance is not a numbered phase.

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. The output is a written scope note that says which sites and which systems the next phase will actually touch.

On a six-site operator, Phase 1 asks how many locations are in this assessment, which are storage or seasonal, who can sign, and whether a cutover window is tied to till close. Perhaps network and identity at all six; perhaps only three shops plus the hub. The output tells Phase 2 which door to walk through.

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. Missing documents are recorded as risk in the next phase; they are not ignored.

Interviews and technical review are planned against the number of sites. A crew walking six doors in one pass is not the promise of this phase. A signing authority from the hub and at least one site lead at the opening meeting is enough; the field tour follows the scope note.

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. The split management needs in order to decide is produced here; the roadmap is the next phase.

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 site; it is a dated band in the pack. If the presentation is accepted, the order and the opening meeting are separate steps. Implementation (B), support (C / D), and procurement (E) are not an annex to this fee; they are priced as later proposals.

After acceptance

Once the proposal is accepted: commercial approval and order, then the opening meeting, information gathering and site planning, then assessment, reporting, and the management presentation. Kickoff is not a relabel of Phase 1. The meeting after commercial acceptance is not a numbered phase; field work does not start before the scope note exists.

The split is practical. If commercial approval is not in place, the field team waits. If the order is not in place, licences and boxes are not discussed. The opening meeting is the moment the signing authority and a site lead sit at the same table — the start of planning after acceptance, not a rerun of the Phase 1 scope conversation.

Implementation and modernisation (B), on-site or remote support — retainer or on-demand (C / D), and hardware and software procurement coordination (E) are outside this assessment. Each is a separate proposal. Delivery of the assessment does not automatically open a “install it now” line; B is written from the items in Phase 4.

How to write

Write to info@akillitrakya.com to pin down scope. The fields on the Contact page are enough for a pre-proposal file: name, company, number of sites (1 / 2–5 / 6–20 / 20+), user band, need (assessment / implementation / support / procurement / other), a short message, and an optional callback number. Writing is a pre-contract request under the privacy notice. There are no prices on the site; a price sits in a proposal after scope is written.