A business sponsor
Owns the customer action and the definition of “done enough”.
Method
How we work
Small, measurable projects. If the system cannot support it, we say so before we build.
Four stages
- 1
We understand the opportunity
The customer action, the systems involved and what success would look like in measurable terms — with a baseline you already have or can collect.
- 2
We define the connection
Sources, tools, permissions and confirmation rules. Non-goals are written down.
- 3
We implement and test
Build against real interfaces. Check answers, errors and handoffs. Sample data is labelled as sample data.
- 4
We launch and maintain
Release with the operating model you approved, or hand over if you operate it yourselves.
Who sits in the room
A system owner
Can grant access and explain what the interface will not do.
An operator
Will live with the connection after launch.
Working principles
- Stay within authorized data.
- Do not invent customers, results or certifications.
- Say so before building if a system cannot support the action.
- Measure against a baseline; do not advertise unverified percentages.
Questions about the method
How long is a first project?
It depends on access and on how clear the first action is. Consulting can precede build when that is still fuzzy.
Do you work only with MCP?
MCP is one pattern. Integrations and assistant apps are others. The method is the same: action, system, permission, test.