Four teams, one integration, four different questions of it
The engineer asks whether it can be shipped without one client per system. Sales asks whether the answer to “do you support ours” is yes. Support asks which request failed for which customer. Finance asks what the books actually say. It is one connection underneath all four.
Start with the team whose week this changes
Four pages, one per role, each pointing at the capabilities and workflows that role actually meets.
One connection underneath, four different questions of it
| The team | What it asks of the integration | What answers it |
|---|---|---|
| Product & Engineering | Can we ship this without writing one client per system? | Common Data Model |
| Go-to-Market | When a prospect names their system, is the answer yes? | The connected systems |
| Customer Success | Which request failed, for which customer, and when? | Unified Logging & Monitoring |
| Financial Teams | What do the books say, without waiting for an export? | The MCP server |
The questions do not translate into each other, which is why one page cannot answer all four. What does not change between them is the connection: the customer authenticates once, and the same object model serves the engineer building against it, the answer sales gives on a call and the request support looks up afterwards.
A team page is the reader, a use case is the workflow
Three axes cross on this site and each answers a different question. A use case is a workflow end to end, the same one whoever cares about it. An industry page is the company you are. A team page is the job you do inside that company, and it hands the mechanics off to the other two instead of restating them.
Which is why the same reader often needs two of them: a construction platform and a payables platform sit in different industries, and their engineers ask exactly the same question about how many clients they have to write. What they have in common is the team, not the market.
Common questions
Why are these pages split by team rather than by feature?
How is a team page different from a use case page?
And how is it different from an industry page?
Is every one of these four pages published?
Which team should read which page first?
Build once on the Unified API.
See how one integration for every team works for your integration, or dive into the technical reference.