Built by the architects who
documented estates by hand.

SolutionPilot grew out of Solution Pilot IT, a consulting practice that has designed, migrated and operated cloud platforms for banks, a global payment network and the Government of Ontario since 2015. Every one of those programmes had the same weak point: the documentation lagged the estate. This application is the answer we always wanted to hand our clients.

Since 2015 Banks, payments, government Two people on every engagement

Two people.
Every engagement.

Small on purpose. The people who scope your pilot are the people who design, build and hand over the application.

Sebastian Cwiek, co-founder · ceo · architectCO-FOUNDER · CEO · ARCHITECT

Sebastian Cwiek

Leads architecture and delivery. Architect on the programmes below, from Scotiabank’s first cloud platform in 2015 to the Government of Ontario’s platform engineering, and the author of the customer-owned application model behind SolutionPilot.

AZURE ARCHITECTUREPLATFORM ENGINEERINGCUSTOMER-OWNED DELIVERY
Samir Muskin, system designer · ai and automationSYSTEM DESIGNER · AI AND AUTOMATION

Samir Muskin

Designs the systems and the automation around them: AI enablement, workflow automation and the operating model that keeps an application useful long after it has been handed over.

SYSTEM DESIGNAI ENABLEMENTWORKFLOW AUTOMATION
SOLUTION PILOT IT
THE PRACTICE

Consulting first, product second.

The practice designs and migrates cloud platforms for regulated organisations. SolutionPilot is the application we kept rebuilding for each client: system maps, architecture records and evidence-backed workflows, now delivered into your environment and handed over.

The programmes
the product is built on.

Enterprise cloud work delivered under Solution Pilot IT. Each one taught us something the application now does for you.

2025
SNCPA Accounting logo

SNCPA Accounting

Modernising accounting operations with Microsoft 365. Hardened the Microsoft 365 tenant with multi-factor authentication, conditional access and data-loss prevention, then automated approvals, client onboarding and internal communications with Power Automate.

MICROSOFT 365SECURITYAUTOMATION
2023
Government of Ontario logo

Government of Ontario

Enterprise cloud transformation and platform engineering. Migrated the business registration platform to Azure (about 5 TB of sensitive personal data), designed the managed file transfer network to major financial institutions, delivered the DIRECT drug management system on multi-region AKS and moved an Oracle platform supporting 180 applications.

AZUREAKSPLATFORM ENGINEERING
2020
Mastercard logo

Mastercard

Enterprise-scale DevOps transformation and cloud modernisation. Standardised delivery for more than 50 business-critical Java microservices in Azure, reducing 39 Azure DevOps pipelines to 9, moved over 5 TB of client data into Cosmos DB and led the expansion into new Azure regions.

DEVOPSMICROSERVICESTERRAFORM
2015
Scotiabank logo

Scotiabank

Pioneering cloud transformation in financial services. Helped establish the bank’s first public and private cloud with infrastructure-as-code, and onboarded iTrade, Adobe Experience Manager, eTeller and PPM with hardened, automated VM provisioning that met bank security standards.

FIRST CLOUD PLATFORMIACMIGRATION

“Working with Solution Pilot IT, we felt more like a partner than a customer.” Adithya Sudarsan, CEO of SNCPA

The same rules
on every engagement.

The product enforces what the practice learned the hard way.

SOURCES
Read-only by default

No write access is needed to document an estate.

We start from approved, read-only sources and agreed data boundaries. The application observes; your team decides.

EVIDENCE
Evidence on every claim

Observed facts stay separate from engineering judgment.

Source references and review states show what was seen, when, and who accepted it, so a record can be trusted years later.

HANDOVER
Handed over, not hosted

The application is yours to run and to evolve.

You receive the source, the deployment assets and the operating documentation. Support and further development are scoped separately.

Start with one
private pilot.

Prove the workflow on a contained scope, agree success criteria before access, and leave with a working application plus an approved architecture baseline.

01One agreed Azure scopeCustomer-controlled, read-only access
02One or two priority systemsSelected for operational value
03Two initial documentation viewsAligned to your team and standards
04Source code and operating handoverAcceptance criteria agreed up front
Design the pilot

No tenant access is needed for the first conversation. See the product ↗