What it says
What this says
Current to 11 Oct 26Draft first proposal from Jordan Pike dated 25 Feb 2026 for the Growth tier. Annual subscription £50k, total deal value £62k including the one-off implementation fee. Service levels are only described as standard Growth, with no figures stated.
What it is: a first-draft proposal, marked "Status: Draft", not an order form. It proposes the Growth tier for the referral-relations and patient-services teams as the first two teams.
Commits: nothing binding. It states the Growth subscription as "£50k" annual, in advance, and a total of "£62k" that "Includes the one-off implementation fee. Not an annual price." No discount is applied.
Unusual: it sits under a business associate agreement to be put in place before patient-related data is connected. It also flags that credits covering data freshness are an Enterprise matter.
Not settled: first-wave connectors, the named sponsor, user count beyond the allowance, data residency or add-ons, and the business associate agreement wording. Connector go-live commitments are to be agreed before signature. Availability and P1 response figures are not stated.
As found in this document
Current to 9 Oct 26- Price£50,000Source: object_read:doc_079_002
- Growth subscription£50,000, Annual, in advance. This is the annual price.£50,000, Annual, in advance. This is the annual price. · Source: object_read:doc_079_002
- Total deal value£62,000, Includes the one-off implementation fee. Not an annual price.£62,000, Includes the one-off implementation fee. Not an annual price. · Source: object_read:doc_079_002
- DiscountNo discount is applied in this draft.No discount is applied in this draft. · Source: object_read:doc_079_002
- Payment termsStandard payment terms apply, and quarterly billing is available on request.Standard payment terms apply, and quarterly billing is available on request. · Source: object_read:doc_079_002
- Service levelsThe standard Growth service levels applyThe standard Growth service levels apply · Source: object_read:doc_079_002
- Connector go-liveConnectors named in the order form will carry a go-live commitment, and we will agree those commitments with you before signature.Connectors named in the order form will carry a go-live commitment, and we will agree those commitments with you before signature. · Source: object_read:doc_079_002
The document
Body
Quarrington Care Network - Proposal v1
Status: Draft
| Item | Detail |
|---|---|
| Customer | Quarrington Care Network |
| Document date | 25 Feb 2026 |
| Version | 1 |
| Author | Jordan Pike, Account Executive, US, BB-Demo |
| Customer success lead | Hollie Grieve, BB-Demo |
| Proposed tier | Growth |
This is a first draft. Some points are still open and are listed at the end so we can settle them together before anything goes to an order form.
1. Context
Quarrington Care Network runs home-health and hospice services from Chicago, with about sixty branches across Illinois, Indiana and Wisconsin. As a HIPAA-regulated operator, you work with a long list of referring hospitals, and each one touches several of your teams: referral relations, patient services and the people who own the contracts.
To be transparent, here's what we heard. Today each of those teams sees only its own slice of a referring hospital. Calls sit in one place, tickets in another and contract terms in a third. Answering a simple question about a hospital means somebody stitching those views together by hand.
2. What we propose
Read the whole document (5,631 characters)
We propose the company brain on our Growth tier: one AI-queryable layer over your CRM, call recorder, email, helpdesk and contract data, built and run inside your own Snowflake account. Your data stays in your environment.
The outcome we are aiming for is simple. The referral-relations team and the patient-services team ask one question about a referring hospital and see its calls, tickets and contracts together.
Scope
- Pages, chat and search across the connected sources.
- The dashboards builder, included in Growth, so your teams can build the views they need for each referring hospital.
- Quarterly business reviews with Hollie Grieve, to check usage and value against what you set out to achieve.
- The Growth user allowance and the Growth connector allowance, covering the referral-relations and patient-services teams as the first two teams.
- A fixed-fee implementation, delivered to the standard Growth timeline.
Healthcare and security
This engagement sits under a business associate agreement, which we will put in place before any patient-related data is connected. Here's where we are on security: we will be open with your security team throughout. Any question they raise gets a straight answer, including the ones where the answer is "not yet" or "not in this tier". We would rather your reviewers hear that from us early than find it late.
3. Pricing
| Line | Amount | Notes |
|---|---|---|
| Growth subscription | £50k | Annual, in advance. This is the annual price. |
| Implementation | Included in the total below | One-off, fixed fee |
| Total deal value | £62k | Includes the one-off implementation fee. Not an annual price. |
Two points to keep straight, because they are easy to blur:
- The annual subscription is £50k. That is what recurs each year.
- The total deal value of £62k is the first-year picture. It adds the one-off implementation fee to the annual subscription, and the implementation fee does not recur.
No discount is applied in this draft. Standard payment terms apply, and quarterly billing is available on request.
4. Service levels
The standard Growth service levels apply:
- Availability at the standard Growth level.
- First response to a priority one issue at the Growth response time.
- Nightly refresh complete before the start of your business day, on business days.
- Service credits for availability, as set out for Growth.
If your team needs something stronger, for example faster response times or credits that also cover data freshness, that is an Enterprise conversation, and we would rather raise it now than after signature.
5. Implementation approach
| Phase | What happens | Owner |
|---|---|---|
| Kick-off | Confirm the two first teams, the connected systems and the referring hospitals that matter most | Jordan Pike with your sponsor |
| Connect | Connect the CRM, call recorder, email and helpdesk inside your Snowflake account | BB-Demo implementation team |
| Validate | Your teams test real questions about real referring hospitals | Quarrington Care Network team leads |
| Go live | Teams start asking the brain; dashboards built for each team | Hollie Grieve |
Connectors named in the order form will carry a go-live commitment, and we will agree those commitments with you before signature.
6. How we will know it is working
We suggest agreeing three simple measures up front:
- Questions asked by the referral-relations and patient-services teams, month on month.
- How many different people ask them, so the value does not rest on one person.
- Time taken to answer a typical question about a referring hospital, compared with today.
Those are what Hollie will review with you at each quarterly review.
7. Next steps
- You review this draft and tell us what is missing or wrong.
- Your security team sends us their questions and we answer them in writing.
- We settle the open points below.
- We issue an order form under our master agreement, with the business associate agreement alongside it.
What would make this a yes? That is the question I would like your team to answer when you read this.
8. Open points in this draft
- Which systems are in the first wave of connectors, and which wait.
- The named sponsor on your side.
- Whether either team needs a user count beyond the Growth allowance.
- Whether data residency or other add-ons are needed.
- The business associate agreement wording and who reviews it for you.
Thanks, Jordan
Unusual terms
Current to 9 Oct 26- business associate agreement before patient data connected
- total deal value includes one-off implementation fee