Why we build in the open: you see the code, the hosting and the bills
What building in the open means in a client relationship: repository, previews, accounts and invoices all visible.
The short answer
Building in the open means that at any moment a client can see everything about their digital estate without asking us: the repository and every change in its history, every preview of every change before it went live, the hosting and service accounts with their invoices, the monitoring dashboards and the monthly report that draws on all of it. It removes the information gap that many agency relationships quietly depend on, where the client knows what they are told and the agency knows the rest. It makes every claim in the report checkable. It costs us a little convenience, and it produces a kind of trust that no presentation can, because there is nothing to take on faith. The test is simple: could the client show a new partner everything tomorrow without asking us for anything?
What is visible, and where
| What | Where the client sees it | What it shows |
|---|---|---|
| Code and history | The repository in the client’s account | Every change, who made it, when, why |
| Changes before they are live | Preview links per change | Exactly what will ship, on a phone |
| Deployments | The platform’s deployment history in the client’s account | What went live when, and the ability to roll back |
| Hosting and services | A named account at each provider, whoever holds it | Configuration, usage, and the provider’s price for what runs there |
| Monitoring | Dashboards in the client’s accounts | Uptime, errors, speed, alerts |
| Data flows | The setup document and the data map | Where personal data goes, hop by hop |
| The work itself | The monthly report | Incidents, updates, changes, numbers, all traceable to the above |
| Our access | The access lists in every account | Exactly what we can do, removable in a click |
What it changes
- For the client: no dependence on our word; nothing to negotiate for at exit; the ability to bring in a second opinion at any time.
- For us: work done as if it will be read, because it can be; a relationship without an information advantage to defend.
- For a successor: everything needed, already in the client’s hands, from day one.
- For an auditor or a buyer: the estate is demonstrably the client’s, with a history.
Why it is our position
Because taking over an estate built the closed way costs the client what the gap always costs: months of discovery, disputes over what was done, and accounts that have to be recovered. Building in the open prevents all of it, at the price of our convenience, and we think that is the right trade. It also matches the rest of how we work: a written answer to who holds which account and what moves it, checkable guarantees, previews for every change. Transparency is the same principle applied to information.
What this means for you
Expect to be able to see everything: code, previews, deployments, accounts, invoices, monitoring, data flows, and a report that traces to all of them. You may rarely look, and that is fine; what matters is that you can, that a successor can, and that nothing about your digital estate depends on asking. If your current arrangement fails the tomorrow test, that is the first thing to change.
Frequently asked questions
Why would a partner want the client to see everything?
Because trust built on visibility is stronger than trust built on assurance, and because a client who can see the code, the previews, the accounts and the bills has no reason to wonder. It also disciplines the work: everything we do is visible, so everything we do is done as if it will be read. The convenience we give up is small; the relationship it produces is not.
Do clients actually look at the code?
Rarely, and that is fine. What matters is that they can, and that a new partner or an auditor can. The repository history, the previews, the deployment log and the provider invoices are there when a question arises, and their existence is what makes the monthly report believable. Visibility is a property, not a chore.
What if we do not understand what we are looking at?
The setup document explains what is where in plain language, and the monthly report translates the activity into what it means for the business. You do not need to read code to benefit from being able to see it; you need to know it is yours, it is there, and anyone you choose can read it on your behalf.