01 / CONNECT THE CONTEXT
See the relationship behind the record.
Bring account activity, pipeline and meeting context into a working view. Choose the modules and source connections relevant to your team.
PRICING / BUILT AROUND YOUR BUSINESS
Intelligence that fits.
A plan that adds up.
A business intelligence layer, assembled around the way you work. Choose your modules, scope the implementation, and decide who runs the infrastructure.
Build your starting point01 / Modules02 / Implementation03 / Environment
BUILD AROUND YOUR BUSINESS
Your modules.
Your way to run them.
Select a starting point. Watch the access and implementation estimates come together.
WHAT YOU’RE INVESTING IN
Better context.
More useful decisions.
The value comes from connecting the information, workflows and people that already run your business. Start with a concrete problem and an agreed outcome.
02 / MAKE IT ACTIONABLE
Give the next step somewhere to go.
Define the commitments, ownership and reporting that matter. Judge the implementation by whether your team can use it in an actual workflow.
03 / FIT YOUR OPERATION
Pay for a defined starting scope.
Separate access from implementation and provider costs. Add modules when they solve a real need, with capacity and support agreed before launch.
IMPLEMENTATION / THE WORK BEHIND THE WORKSPACE
Start with a workflow.
Finish with a usable system.
Software access is one part. Implementation is the work to make your starting configuration useful: agreed deliverables, acceptance milestones and a clear handover.
- Discover your workflow and define launch criteria
- Configure fields, pipelines, objects and permissions
- Map data and perform the agreed import or migration
- Set up the specified integrations and source connections
- Train your team and document the handover
SCOPE FIRST. THEN THE NUMBER.
A focused launch or a deeper engagement.
Starting estimates in the explorer cover focused module implementations. Multiple source systems, messy data, custom workflows and bespoke integrations need a tailored scope.
Setup can be arranged in 2–4 agreed milestone payments. Monthly access starts on the agreed date after all setup installments are paid.
Talk through your implementationEach deliverable is confirmed in the proposal. The explorer adds module starting estimates for planning; a combined engagement may be scoped differently. Ongoing custom development and new integrations are separate engagements.
HOSTED SAAS / LICENSED SELF-HOSTING
Choose your modules.
Choose your environment.
Both follow the shared product direction. The difference is who operates the service, how it is licensed, and where your data lives.
Let us run it.
Hosted SaaS · recurring module access
A managed environment for teams that want to focus on the work. Your organization has its own scoped records, access and configured connections.
- Application operation and updates within the agreement
- Backup, recovery and service scope agreed before launch
- Implementation priced separately from ongoing access
Run it in your environment.
Self-hosted · custom license and support quote
For organizations with an infrastructure team or a requirement to control the installation. You run your own database, credentials and connected accounts.
- Implementation and software licensing are scoped together
- Your team owns hosting, monitoring and recovery
- Optional support and upgrade assistance by agreement
| Decision | Hosted SaaS | Licensed self-hosting |
|---|---|---|
| Environment | We operate the managed cloud service. | Your organization controls the installation and infrastructure. |
| Updates | Our team manages application updates within the service agreement. | Your team schedules supported releases; upgrade assistance can be scoped. |
| Backups + recovery | Backup scope and recovery targets are agreed in your service agreement. | Your team operates and tests recovery, or contracts for assistance. |
| Security + access | We operate the service. You manage workspace access and connected accounts. | Your team operates patching, monitoring, access, hosting and credentials. |
| Commercial model | Implementation + recurring module access; external providers are separate. | Implementation + software licensing + optional support; infrastructure and providers are separate. |
Self-hosting includes infrastructure and operating costs as well as the software license. AI models, meeting tools, email, enrichment, ad platforms and other third-party services may carry their own subscriptions or usage charges. Provider ownership, included allowances and spending limits are confirmed in your proposal. Product updates carry code; customer records and production credentials stay with their organization.
BEFORE WE START
Good questions.
Clear expectations.
Do we have to buy CRM?
No. CRM is one module in the Deepwater business intelligence layer. Signal, Funnel and Cards can be discussed separately. Signal and Funnel need their own configured source access.
What does the recurring estimate include?
The selected hosted module access at the displayed planning rates. The CRM estimate includes five human users, with additional users shown separately in the calculation. Capacity, connections, support and provider allowances are confirmed in the proposal. Cards is an example team package with app access arranged separately.
Why is implementation separate?
Because useful workflows need configuration, data mapping, connections and a handover. Separating that work makes the launch scope visible and keeps ongoing access distinct from a migration or bespoke development project.
Can our existing tools stay?
We scope the connections around your existing systems and the modules you choose. We confirm each integration before promising a workflow. Cards is currently a separate app; automatic CRM sync and shared sign-in are not yet available.
Is there an annual discount?
The explorer shows monthly planning estimates and does not apply an annual discount. Any annual commitment, prepayment option or combined-module agreement must be confirmed in a written proposal.
Can we move from hosted to self-hosted?
We can scope the transition, data export and deployment together. Licensing, infrastructure, credentials, integration connections and operating responsibilities need review.
Does the sample plan collect payment?
No. The sample plan creates no invoice, subscription or account access. Final scope, availability, payment milestones and recurring start date are confirmed with you first.
START WITH THE PROBLEM YOU WANT TO SOLVE
A clearer view.
A practical next step.
Tell us what needs to work better. We’ll turn the module choice, implementation and hosting decision into one clear proposal.
Plan your implementation