Make ownership explicit
At project start we agree where code, solutions, configuration and documentation live, who can access them and what is handed over. We can work in the customer's tenant or repository where appropriate.
You are not only choosing a developer. You are choosing a supplier.
In enterprise delivery, technical skill is only one part of the decision. Access, ownership, production control and handover matter just as much.
Supplier principles
Six things worth clarifying before development begins.
Controls should match business risk and fit the customer's existing IT and security model.
Access should follow need
Permissions are matched to the work rather than starting from broad admin access. We prefer named or appropriate service identities and avoid unnecessary tenant-wide privileges.
Use a controlled path to production
Depending on project risk, DEV/TEST/PROD, solution lifecycle, source control, UAT and controlled deployment provide a traceable release path.
Agree data boundaries early
We clarify what data is involved, where it may be stored and which services are approved. This is especially important for AI-enabled functionality.
Handover is more than a file export
The handover package is scaled to the project and can include architecture/dependencies, deployment and operations guidance, ownership and critical failure paths.
Define the support model
A fixed project, warranty period, continuous development and operational support require different responsibilities. We define the model explicitly in the engagement.
Procurement / vendor onboarding
Core supplier information should be easy to find.
Legal name: mySHP Solutions Betéti Társaság
Registered office: 2314 Halásztelek, Bíró László utca 18. 1., Hungary
Company registration no.: 13-06-073318
Tax no.: 29018460-2-13
Contact: info@myshp.hu
NDA, data-processing or customer-specific security questionnaires are handled in the context of the actual engagement.
Imprint and official company information →Privacy notice →
Technical due diligence
Before production, there should be something concrete to review.
For Power Platform this often includes environments, solution lifecycle, connection ownership, permissions, monitoring, testing and documentation.
For custom/integration work it maps to source control, CI/CD, secrets, API contracts, logging and operational ownership.
Enterprise delivery standard →Interactive production checklist →
First step
Show us the process you would like to make simpler.
In a 30-minute call we look at how it works today, what is worth automating, where AI can help, and what should stay simple.