SalePiper1. Start with a workspace.
Open SalePiper and sign in with Intergraph. In your workspace, choose Set up SalePiper to install the sales program and create collections for shared contacts and deals.
Your personal workspace is created on sign-in. Workspace owners can also manage team membership and collection access. Users must have signed in before their verified Intergraph account identifiers can be added.
2. Add the participants.
Create organizations for the buyer and seller. Add people or represented agents as appropriate for your work. These contact records describe participants; they are not login accounts or permission grants.
Keep the people and organizations involved in a deal connected to that deal’s record, rather than relying on a separate, unstructured note to explain the relationship.
3. Create a deal and record context.
Create a deal with a title, buyer and seller. New deals begin in Identified. Record interactions with a summary, source and evidence status, and add a next action with a due date.
Complete a next action by recording its result. Interactions and actions remain linked to the deal, alongside its attributed changes.
4. Move forward with explicit commands.
| Command | What it records |
|---|---|
| Qualify | Move from Identified to Qualifying with required supporting evidence. |
| Propose | Move from Qualifying to Proposal and record a request to prepare a proposal for review. |
| Win | Record a Won outcome from Proposal, with supporting evidence. |
| Lose | Record a Lost outcome from an open stage, with supporting evidence. |
Commands depend on the current state, required input, record revision and your permissions. A direct patch cannot bypass the declared lifecycle.
A recorded interaction or outcome is attributed information, not independent verification of a real-world event. A proposal work request is an intent; it does not send a proposal or authorize an external tool.
5. Connect an agent with the right access.
Use an MCP client that supports OAuth authorization-code flow with PKCE. Add the underlying WoN remote server:
https://api.wealthofnetworks.com/mcpThe authorization flow opens a consent screen in SalePiper. Choose a workspace, exact collections and scopes. Begin with read-only access, then approve write capabilities when needed. Program-definition changes require separate authorization and administrator access.
Do not give an agent your browser cookie or Intergraph sign-in credential. An approved connection receives its own WoN tokens. External agents operate in their own runtimes and remain responsible for any separate tool authority.
For REST operations, OAuth details and program definitions, use the WoN developer guide and Relationship Protocol documentation.
6. Keep access deliberate.
Adding a teammate to a workspace does not automatically grant access to every collection. Approving an agent does not silently add future collections to its grant. Use the product’s access controls to review permissions and revoke connections you no longer need.
The initial release includes contact and deal management, interactions, due-dated actions, declarative commands, permissions and history. It does not include hosted model execution, automatic outreach, automatic contact merging or third-party CRM synchronization.