How engagements work
An engagement is defined by two things that are easy to confuse. The outcome says what changes or gets delivered. The format says how much of my capacity is reserved for you, and over what period.
Everything on this page is a starting point that the proposal makes specific. The proposal, not this page, is the agreement.
Three decisions, in this order
Duration, effort and on-site attendance are never treated as interchangeable. They are decided separately:
- The outcomeWhat you will receive, and the acceptance criteria that say it has been delivered.
- The capacityHow many days are reserved for you, over what elapsed period.
- The placeWhere and how those days are used: on site, in live remote sessions, or in independent analysis and documentation.
Formats
Starting points, not fixed promises. The proposal sets the real figures.
| Format | Illustrative capacity | A good fit for |
|---|---|---|
| One-week sprint | Up to 5 working days | One bounded assessment, diagnostic or design question |
| Two-week deep dive | Up to 10 working days | A focused review plus documentation, design or knowledge transfer |
| One-month immersion | Up to 21 full days or 21 half-days | Embedded work with a team on a defined set of priorities |
| Quarterly partnership | For example, 2–4 days a month over 3 months | Continued architectural guidance, coaching and improvement |
| Semester partnership | For example, 2–4 days a month over 6 months | Continuity through several phases of change |
Twenty-one days is a ceiling set by the actual working calendar and availability, not a promise that every month has 21 days available. An immersion reserves capacity that cannot be offered to anyone else, and is priced as reserved capacity.
What a day means
Unless the proposal says otherwise, a full day means up to eight working hours and a half-day up to four. The proposal states how breaks, travel, preparation and reporting are treated, so that a day means the same thing to both of us.
Reserved days are not all on site
An engagement with ten reserved days does not mean ten days at your office. The capacity is a mix of client-site work, live remote sessions, independent analysis, and documentation and preparation, and the mix is agreed in advance.
- Day 1: On site
- Day 2: On site
- Day 3: Remote working session
- Day 4: Analysis and documentation
- Day 5: Analysis and documentation
- Day 6: On site
- Day 7: Remote working session
- Day 8: Analysis and documentation
- Day 9: Analysis and documentation
- Day 10: On site
Four days on site, two in remote working sessions, four in analysis and documentation. An illustrative allocation, not an additional promise.
Where the work happens
Time in the room is kept for what benefits from it: decisions, collaboration and learning. Analysis and writing happen in protected blocks, away from interruptions, which is where most of the quality comes from.
I am based in São Paulo. For clients elsewhere, on-site time is concentrated into planned visits rather than spread thinly across weeks, and travel time and expenses are stated in the proposal. I hold Brazilian and German citizenship and a valid United States visa.
How the work runs
The same backbone runs through every engagement, deeper or lighter depending on the outcome. Each phase ends with evidence that it is done.
| Phase | Work performed | Exit evidence |
|---|---|---|
| Qualify | Clarify the need, its urgency, and whether I am the right fit | A qualified problem and an agreed next step |
| Scope | Agree the boundary, deliverables, exclusions and access | An accepted statement of work |
| Discover | Review evidence and interview technical owners | An evidence and unknowns register |
| Analyse | Assess findings, or compare design options | Traceable findings and rationale |
| Co-create | Test assumptions in working sessions with your team | Reviewed decisions and actions |
| Hand over | Deliver the materials and enable the team | An acceptance record, and named ownership |
| Follow through | Review agreed progress, when it is purchased | An updated backlog and the next decisions |
These are working controls I apply, not a certified methodology, and they are not presented as one.
Quality rules
- Every recommendation is connected to an objective and to evidence.
- Facts, assumptions and hypotheses are kept apart, and marked.
- Priority is explained by impact, urgency, effort and dependencies, never by an unexplained score.
- Every action has an owner, or is flagged as having none yet.
Review and acceptance
Review is proportionate. Your technical owners verify the facts; your sponsor approves decisions and priorities; the designated reviewer accepts the deliverables.
Dissent, missing access and unresolved questions are recorded in the deliverable, not hidden behind a polished report.
How each kind of work is accepted
One acceptance test per service family:
| Assess | Findings have evidence, impact and prioritized next actions. |
|---|---|
| Document | The agreed artifacts are reviewed by the named owners and show the unknowns. |
| Diagnose | Investigation and hypothesis results are recorded, even if the root cause remains unresolved. |
| Design | Requirements, options, rationale and decisions are traceable. |
| Modernize | Phases, prerequisites and transition risks are explicit. |
| Enable | The agreed sessions and materials are delivered, with a practical way to check learning. |
How scope is bounded
A repeatable structure, not an identical answer for every environment. Eight dimensions are defined in every proposal before the fee is fixed:
| Dimension | Defined in the proposal |
|---|---|
| Technology boundary | The named platform, environment, sites and integrations covered |
| Depth | Review, high-level design, low-level engineering or execution |
| People | Number of interviews, workshop size and required participants |
| Artifacts | Number, format and depth of diagrams, runbooks and reports |
| Evidence | Available material, access method, and who collects it |
| Review | Reviewer, review window and included revision rounds |
| Service access | Scheduled sessions, response windows and escalation route |
| Change control | How additions, delays and revised assumptions are approved |
What every proposal states
- The scope, and the exclusions.
- Named deliverables, and the review and acceptance process.
- Reserved days, and the on-site mix.
- Your inputs, and the access needed.
- The schedule, and its dependencies.
- Confidentiality and data handling.
- How changes are authorized.
- Travel and expense treatment.
- Payment and cancellation terms.
- What happens when client delays or additional work change the plan.
Between sessions
Three questions have no default answer; each proposal settles them explicitly:
- Whether questions between scheduled sessions are included.
- Whether unused reserved capacity expires or rolls over.
- What happens when reserved time cannot be used because the environment, the access or the people are not ready.
Who does what
Responsibilities are named in every proposal:
- Me
- Technical scope, analysis, architecture and technical enablement.
- Your sponsor
- Business priorities and access: convening the people and unblocking what is needed.
- Your technical owners
- Validating operational detail.
- Your implementation owners
- Executing authorized changes, unless implementation is contracted separately.
- A partner facilitator
- Her own agreed facilitation scope, when a joint module is included.
- Specialist partners
- Explicit gaps in expertise, with their responsibilities disclosed in the proposal.
Your information
- Client material is kept in an agreed, access-controlled location.
- Only what is needed is collected. Credentials and personal data are avoided unless they are essential and agreed.
- Retention and deletion are agreed at the start, and carried out at the end.
- Confidential client information is never placed into third-party tools, AI services included, without your authorization.
- Ownership and reuse rights are stated for bespoke deliverables, for reusable templates and for any vendor training content.
Changes to live systems
An advisory engagement does not, by itself, authorize any change. A change to a live system follows your approved change process and named authority, with testing, maintenance windows and recovery arrangements defined in an implementation scope.
What an engagement is not
- A design review is not round-the-clock support.
- An assessment is not a security guarantee.
- An advisory partnership is not unlimited access. Escalation routes, response times and any after-hours commitment are defined in writing.
Fees
Fees price the outcome and the capacity reserved for you, not only the hours spent on site. A clearly bounded sprint has a fixed fee; a partnership has a recurring fee for a defined amount of reserved monthly capacity. Work beyond the agreed scope is a change request, approved by you before it starts.
Fees are quoted after a scoping conversation, because they depend on the boundary, the depth and the on-site mix described above. There is no hourly meter.
When the obstacle is people, not technology
Some technical problems are also problems of collaboration, decision-making or change. For those, a partner facilitator can run a separate, coordinated workstream. It is optional, arranged only when there is a concrete need, and described under Technical and team resilience.