A brokerage workspace layered on your CRM — client needs, a provider roster, and the intros that connect them.
Record types
The structured data this adds to your pod.
Need
A client's stated ask — the demand The Arch brokers a provider against.
- Status
- Domain
- Urgency
- Budget Range
- Requester
- Confidentiality
- Evidence Quote
- Source Message ID
- +1
Intro
The middleman brokerage artifact — connects a requester to a provider for a need, and bills the match as a deal.
- Stage
- Requester
- Provider
- Need
- Synap fee model
- Synap success fee rate
- Synap fixed fee
- Expected client gain
- +6
Solution Provider
A company or person that provides a capability The Arch can broker a client need against.
- Status
- Domains
- Capacity
- Pricing Notes
- Geography
- Notes
Views
- NeedsBoard
- IntrosBoard
- ProvidersTable
Automations
- Intro MatcherOnce a day, match each shareable open client need against the solution-provider roster, propose an intro for the best fit, and post a match brief to The Arch's internal team chann…
Relationships
- Need CompanyNeeded by
- Intro NeedResolves
- Intro CompanyRequester
- Intro CompanyProvider
- Intro DealBilled as
First conversation
After install, your agent sets the project up with you. It starts here:
Capture the two sides of the brokerage — the live client NEEDS and the SOLUTION-PROVIDER roster — so the matcher has real demand and real supply to connect, and every intro traces back to a stated need and a named provider.
- “Which client needs are open right now, and whose needs are they?”
- “Which of those needs are shareable, and which must stay confidential?”
- “Which solution providers can you connect clients to, and what do they cover?”
Builds on
- CRMAdds a needs → intros brokerage workflow onto your CRM workspace.
- FoundationProvides the pod-wide client/partner role vocabulary the CRM base reuses.