Discuss your project

Technology consulting & delivery

Change what your business runs on. Keep control of it.

Security, access, infrastructure and workflow projects, each with an agreed scope, a named technical lead and checks before handover.

Discuss your projectHow a project runs

First conversation free. Scope and price in writing before any access.

Delivered on Microsoft 365, Azure and the systems you already run.

A controlled change: scope, approval and validation sit above the current systems on the left, a server with mailboxes and files, and the target platform on the right, a cloud with mail and records, with the validation check completed.

How we workScope, approval and validation sit above every change. The systems you run today stay untouched until the checks on the target have passed.

Three kinds of work

Start with the work you need.

Each path leads to a page that names the actual jobs, what is checked and what you receive at the end.

How you know the work is good

Judge it by what you can inspect.

The method is written down, the sample records open and the demo can be broken on purpose. Read it the way your technical owner would.

How a project runs

A first conversation, free. An agreed scope with a named technical lead in the proposal. The price fixed in writing before we are given access. Checks before handover.

How we work
What is checked

Release checks, access test matrices and ownership maps. Constructed inspection records on the service pages show the standard before you buy.

See sample deliverables
What you keep

A System guide: what was agreed, what changed, what was tested and what remains open. With it, the scripts and check results behind the work.

Try it yourself

An employee onboarding and offboarding workflow you can run in the browser: approvals, a step that fails, and a retry that does not repeat finished work.

Open the demo
Read the thinking

Sixteen technical articles on MFA bypass, token theft, admin roles, mail server exits and shadow AI.

Read Insights
What a System guide containsA handover document with four sections: what was agreed, what changed, what was tested and what remains open. Comparison scripts and check results are attached to it.At handoverIllustrationSystem guideagreed · changed · tested · openWhat was agreedWhat changedWhat was testedWhat remains openComparison scriptsCheck results
System guideThe handover document your team keeps. Open items stay listed as open; nothing is marked done that was not tested.

Samples and the demo are constructed examples. Completed projects, prior experience and illustrative examples are kept separate on the Results page.

Completed project · Migrations

Finding the gaps after a file migration.

After a move to SharePoint, file differences and access problems needed investigation. We compared original and migrated files, traced the sync and long-path problems, and documented the fixes and the migration settings.

Problem
After a move to SharePoint, file differences and access issues needed investigation. Sync behavior and long project paths were part of the problem.
Work
Investigated sync and path problems, compared original and migrated files, and documented fixes and migration settings.
Handover
A System guide covering the migration setup, file comparison scripts, check results and a list of unresolved issues.

Anonymized completed project. Some exceptions remained.

Read the project
Original files compared with migrated filesFive original files are compared with their migrated copies. Four match. One fails because its path is too long, and it is added to the list of exceptions.File comparisonIllustrationORIGINALMIGRATEDPath too longAdded to the exceptions list

Illustration · constructed paths

Act while you still have choices.

Tell us what needs to change, what must keep working and the deadline.

Discuss your project[email protected]

First conversation free. Scope and price in writing before any access.