What it says
What this says
Current to 11 Oct 26Draft proposal dated 6 Oct 2026 to expand the existing Growth subscription for £12,000 annual, billed annually in advance, ending 29 Apr 2027. It is not an offer until an order form is executed. Scope is unconfirmed.
What it is: a first-draft proposal from Jordan Pike, Account Executive, US, with Hollie Grieve as customer success manager. It states "Not an offer until an order form is executed."
Commits: nothing binding yet. It proposes the same Growth service levels, including "nightly refresh completing by 07:00 customer local time on business days", annual billing in advance and thirty-day payment terms from the existing agreement.
Unusual: the proposed term ends with the existing contract on 29 Apr 2027, to give one renewal conversation. No discount and no separate implementation fee are shown.
Not settled: which teams, users or connectors the expansion covers, whether the business associate agreement needs an amendment, finance's view of term alignment, and who signs. The text gives no availability percentage or P1 response time, only "the standard Growth level".
As found in this document
Current to 9 Oct 26- Date end29 Apr 2027Source: object_read:doc_079_012
- Price£12,000Source: object_read:doc_079_012
- Price£12,000Source: object_read:doc_079_012
- BillingAnnual subscription, billed annually in advanceAnnual subscription, billed annually in advance · Source: object_read:doc_079_012
- Payment termsthirty-day terms from invoiceSource: object_read:doc_079_012
- Nightly refreshcomplete by 07:00 customer local time on business dayscomplete by 07:00 customer local time on business days · Source: object_read:doc_079_012
- Proposed term end29 Apr 2027Source: object_read:doc_079_012
- Service creditsservice credits for availability, as set out in your order formservice credits for availability, as set out in your order form · Source: object_read:doc_079_012
The document
Body
Quarrington Care Network - Proposal v1
Status: Draft for internal review and discussion with the customer. Not an offer until an order form is executed.
| Prepared for | Quarrington Care Network, Chicago |
| Prepared by | Jordan Pike, Account Executive, US, BB-Demo |
| Customer success manager | Hollie Grieve |
| Draft date | 6 Oct 2026 |
| Proposal type | Expansion of an existing Growth subscription |
1. Context
Quarrington Care Network became a BB-Demo customer on 30 Apr 2026. It is a home-health and hospice operator with about sixty branches across Illinois, Indiana and Wisconsin, working under HIPAA. The company brain runs inside your own Snowflake account, and the Growth subscription is covered by a business associate agreement.
The starting point was simple: the referral-relations and patient-services teams needed to see each referring hospital's calls, tickets and contracts in one place, without reconciling systems by hand. Since go-live the brain has been used steadily, and use has grown strongly compared with the prior quarter. Support demand has been light, with no high-priority tickets and no overdue invoices.
Read the whole document (5,307 characters)
To be transparent, this proposal is a first draft. It sets out the shape of the expansion so we can agree it with your team before anything goes into an order form.
2. What you have today
| Item | Detail |
|---|---|
| Tier | Growth |
| Licensed users | 40 |
| Contracted annual recurring revenue | £50,000 |
| Contract end | 29 Apr 2027 |
| Teams using the brain | Referral relations and patient services |
| Data protection | Business associate agreement in place |
The Growth tier includes pages, chat and search, the dashboards builder and quarterly business reviews. The existing contract and its executed order form remain the authority on current terms. This proposal does not change them.
3. What we are proposing
We propose an expansion of the existing Growth subscription so that more of the organisation can work from the same view of each referring hospital and partner.
- Same tier. The expansion sits on Growth. It is not a move to Enterprise.
- Same environment. The brain continues to run inside your Snowflake account, so your data stays under your control and your security posture is unchanged.
- Same working model. Implementation follows the pattern used in your first deployment: connect the sources, check the data with your team, then bring users in.
- Same support model. The standard Growth service levels apply, including the nightly refresh completing by 07:00 customer local time on business days.
The exact additional users, teams or connectors are still to be confirmed with you. See the open points in section 7.
4. Pricing
| Line | Basis | Amount |
|---|---|---|
| Growth expansion | Annual subscription, billed annually in advance | £12,000 |
| Total deal amount | £12,000 |
Notes on the pricing:
- The £12,000 is the annual price of the expansion and is the full value of this deal. No separate implementation fee is shown in this draft.
- No discount is applied in this draft.
- Payment terms follow your existing agreement, which are thirty-day terms from invoice.
- Any figure here is subject to the executed order form.
5. Term and billing
We propose that the expansion runs alongside your existing subscription and ends with it on 29 Apr 2027, so that you have one renewal conversation rather than two. Hollie will own the renewal notice and the review ahead of that date.
Invoicing is annual in advance, as with your current subscription.
6. Service levels
The expansion carries the same service levels as your current Growth subscription:
- availability at the standard Growth level;
- first response on P1 issues at the standard Growth level, in business hours;
- nightly refresh complete by 07:00 customer local time on business days;
- service credits for availability, as set out in your order form.
If your security or compliance team would like these restated in the new order form, we will do that.
7. Open points
These need to be settled before this draft becomes an order form:
- Scope. Which teams and which additional users or connectors the expansion covers, so the line in section 4 matches what you will actually use.
- Term alignment. Confirmation that ending with the existing contract on 29 Apr 2027 suits your finance team.
- Business associate agreement. Whether the existing agreement covers the expanded scope as it stands or needs a short amendment. We will take this up with your security team directly, and we will flag anything that comes up.
- Sign-off. Who at Quarrington Care Network approves the order form.
8. Next steps
| Step | Owner | Timing |
|---|---|---|
| Review this draft internally | Jordan Pike | This week |
| Walk through scope and open points with your team | Jordan Pike and Hollie Grieve | Next week |
| Issue v2 of the proposal with confirmed scope | Jordan Pike | After the scope call |
| Order form for signature | Jordan Pike | Once v2 is agreed |
Here's where we are: the commercial shape is clear, and the scope is the main thing left to pin down. What would make this a yes? Tell us what you need to see, and we will build v2 around it.
Thanks, Jordan
Unusual terms
Current to 9 Oct 26- Term co-terminous with existing contract
- No implementation fee shown
- Not an offer until an order form is executed