Apps
Every application starts populated.
Install what you need, or build it. Either way it runs on the same foundation, reaches the companies you already work with, and talks to whatever they are running.
What they do
Four areas, to start.
The first applications are being built against these. We name each one when it ships, not when it starts.
Fundraising
Deals
People
Growth
How an app works
Every app has three sides.
This is what makes it an ecosystem rather than a plugin folder — and what the many-to-many install problem is actually about.
01
The builder
Publishes the app and supports it. Sees every organization and member that installed it, and shows the contact details people reach them on.
02
The provider
An organization that installs the app to offer something with it — a raise, a process, a benefit.
03
The participant
The member or client on the other side. Installs the app once, and can then connect to any provider offering it — without installing it again.
Install once. Connect to any of them.
Say two firms both offer the same app. You install the participant side once, to work with the first. When the second starts offering it, you can connect straight away — there is no second copy to install and no second account to keep.
The organization that built the app sees every organization and member running it, and publishes the contact details people reach them on. That is how support works without the platform standing in the middle of it.
Building something on the network?
The framework is how we build our own applications. It opens up from there.