Software company · acquisition integration
The builder had left.
The business still depended on the integration.
Two portals, an undocumented integration and no original repository. How we reconstructed the behavior and checked a 60-workflow update.
Reconstructed behavior + dependency review
No stale IDs in the 60-workflow update check.
That check does not cover every behavior across both portals.
The starting point
The integration had outlasted its owner.
An acquisition left a software company with two HubSpot portals and an undocumented integration. The original author and repository were unavailable. The team needed to understand what the integration did before changing the systems around it.
The immediate task was to reconstruct the behavior and identify which workflows depended on the existing connections.
The delivery
Understand the dependencies. Then make the change.
We reconstructed the integration’s behavior and inspected the workflow dependencies. That gave us a basis for deciding which references needed to change and what to check afterward.
The work included a 60-workflow update. The validation check found no stale IDs in that update.
The decision behind the work
A working connection still needs an understandable owner.
When the original builder is gone, a proposed change can affect more than the integration itself. A workflow may still point to an old record or depend on behavior that nobody has documented.
In this engagement, tracing those dependencies made the update reviewable. The check supported a specific conclusion about the references changed; it did not establish that every possible behavior across both portals had been tested.
What changed
The team could inspect the change.
The delivered work made the inherited integration more understandable and verified the references in the 60-workflow update. That is the concrete result recorded for this engagement.
If you are inheriting a system, bring one integration, the change you need to make and any examples of its current behavior. We can establish what is known, what needs checking and the responsibility a useful next step requires.
Let’s talk
What needs to work better?
What have you inherited, or what keeps getting stuck?
Tell me what is happening, what you have already tried and why it matters now. We’ll talk through the result you need and who will own it with us.
A free 30-minute conversation to identify the problem, separate what we know from what needs checking, and agree a useful next step. You’ll receive a written recap, whether or not we work together.
Included when you choose to email me.