Home › Avoiding lock-in
How do you avoid depending on one Power BI builder?
By insisting everything lives in your environment and nothing lives in the builder's head. The workspace in your tenant, the code in your repository, the definitions in a catalogue outside the report file. Get that right and you can change supplier without starting over. Ask it up front, because afterwards you have no position left.
Where dependence creeps in
| Where it goes wrong | How you notice | What it should be |
|---|---|---|
| Workspace at the supplier | You cannot get to it yourself | In your own tenant |
| No version control | A file with v3 final in the name | A repository with history |
| Logic in the report | Every report calculates slightly differently | Definitions in the data layer |
| Knowledge in one person | Everything stops when they leave | Recorded and handed over |
What a handover really means
A folder of files is not a handover. What should be there: the source file or the code, a description of the model and the measures, the definitions of the figures with an owner attached, and the agreements on refresh and permissions.
And then a conversation in which someone explains it to whoever takes over. Without that conversation, the rest is an archive nobody opens.
He integrated seamlessly, was highly proactive, and consistently drove work forward with strong ownership and minimal direction.
Half an hour is enough to know whether we fit
No slide deck and no quote at the end. We walk through your sources, your definitions and your biggest frustration.
Book half an hourFrequently asked questions
How do you avoid depending on one Power BI builder?
By insisting everything lives in your environment and nothing lives in the builder’s head. The workspace in your tenant, the code in your repository, the definitions in a catalogue outside the report file. Get that right and you can change supplier without starting over.
What do you ask a supplier before you start?
Where will this live, who owns the code, what do I get if we stop, and how do you record definitions. A party without a clear answer builds something that only works at their place. Put those answers on paper, not only in conversation.
What belongs in a proper handover?
The source file or the code, a description of the model and the measures, the definitions of the figures with an owner attached, and the agreements on refresh and permissions. Plus an hour in which someone explains it to their successor. Without that last part the rest is an archive.
Why is logic in the report a problem?
Because that logic only exists in that file. A second report gets a slightly different definition of the same term, and then the argument about which number is right starts again. Definitions belong outside the report, somewhere the organisation can read them.
Do you work that way?
Yes. What we build sits in your Microsoft environment and your GitHub. Every phase has its own fixed price and ends with a go or no-go. If it stops there, you keep what has been built and can continue with another party.