What was said
What this says
Current to 13 Oct 26Proposal call on a company-wide Enterprise deal. Privacy and security review must come before any signature. The £155k is total deal value with implementation, not the annual price. Expected close is 29 Dec 2026.
What happened: Jordan Pike walked Kristin Lindahl and Eric Halvorsen through an Enterprise proposal across the Minnesota and Wisconsin communities. No decision was sought on the call.
Customer view: Kristin is convinced by the one view per community and has seen it on their own data. Eric will not sign before privacy and security approve, and told Jordan not to rush that review.
Commercial: The £155k deal amount is total deal value with implementation included. Jordan said it is not the annual price, and the written proposal will split subscription and implementation.
Watch: The privacy lead has seen only the outline, not the proposal. Kristin also needs the picture clear before the board meeting, and the close date is a forecast that may move.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Jordan Pike sends the one-page summary and full proposal, with annual and implementation lines split, early next week.
- Kristin Lindahl books the privacy and security review session this week and names the attendees.
- Jordan Pike brings the security material to the review call and tells Eric once privacy has signed off.
Risks
Current to 9 Oct 26- The privacy lead has not seen the full proposal, and Eric will not sign before privacy and security approve.
- Resident information in the indexed systems could slow or reshape the Enterprise scope.
- The 29 Dec 2026 close is a BB-Demo forecast and Eric said to move it rather than rush privacy.
Opportunities
Current to 9 Oct 26- Company-wide Enterprise across the Minnesota and Wisconsin communities, with family relations and community sales first.
- Kristin is already convinced by the single view per community, so the review is the main gate.
Transcript
- Jordan Pike NoneHi Kristin, hi Eric. Can you both hear me okay?
- Kristin Lindahl NoneLoud and clear. Eric's just getting his camera going.
- Eric Halvorsen NoneHere. Good afternoon.
- Jordan Pike NoneGood afternoon, Eric. Thanks for making time on a Friday. Here's where we are. The agenda is the proposal, the scope and the all-in number, then what has to happen before a decision. We have thirty-five minutes and I'll watch the clock.
- Eric Halvorsen NoneWhat decision do you need from me today?
- Jordan Pike NoneFair question, and to be transparent, none today. What I need is for you to tell me whether this shape is right, so I can get the paperwork to you in good order.
- Kristin Lindahl NoneCan I jump in with one thing first? It's quick. Earlier this week a daughter called one of our communities about her mother's room, and then emailed our sales team, and then filed a complaint with family relations. Three people, three answers. What did the family hear from us? Honestly, three different things.
- Jordan Pike NoneThat's exactly the thing the brain is for. One place where the enquiry, the complaint and the contract sit together for that community.
- Kristin Lindahl NoneRight. That's the whole reason we're here.
- Jordan Pike NoneSo, the proposal. It's Enterprise, company-wide across your communities in Minnesota and Wisconsin. The sources we'd connect are your CRM, the helpdesk, your email and the place your contracts live. Everything is built and run inside your own Snowflake account.
- Eric Halvorsen NoneInside our account. Meaning what?
- Jordan Pike NoneMeaning the data does not leave your environment. We don't copy it to a system of ours. Your team asks questions, the brain answers from your data, and your security people can see where it sits.
- Eric Halvorsen NoneWhat's the risk?
- Jordan Pike NoneTwo I'd name. One, resident information. Those records will be in some of these systems, so your privacy and security reviewer will want to look at what we index and who can query it. Two, rollout. If the communities see it as extra work, it dies. We'd start with family relations and community sales, not everyone at once.
- Kristin Lindahl NoneAnd on the first one, I want to be careful. I don't put anything about residents in email. Ever. So when we do the review, let's do it on a call, with the right people in the room.
- Jordan Pike NoneAgreed. I'd rather do it live and walk them through it, including the parts that are awkward. I won't hide anything from your security team.
- Eric Halvorsen NoneHas our privacy lead signed off?
- Kristin Lindahl NoneNot yet, Eric. She's seen the outline. She hasn't seen the proposal. I'm not pushing past her review, and I'd like her to see the full document before anything goes near you for signature.
- Eric Halvorsen NoneGood. I don't sign before privacy and security approve.
- Jordan Pike NoneUnderstood, and that's how we'd sequence it. Review first, then the order form.
- Kristin Lindahl NoneCan we talk about the number? I know Eric will ask.
- Eric Halvorsen NoneI'm asking. What's the all-in?
- Jordan Pike NoneThe deal amount in the proposal is £155,000. That's the total value of the deal, with the implementation included. I want to be clear, that is not the annual price. In the written proposal I'll show the annual subscription and the implementation as separate lines so you can see both.
- Eric Halvorsen NoneSo the one hundred fifty-five is the whole first stretch, not a yearly run rate.
- Jordan Pike NoneCorrect. Total deal value. The yearly figure comes out of the split, and it will be in black and white.
- Eric Halvorsen NoneKeep it simple. One page for me.
- Jordan Pike NoneGot it. One page for you, and the full document for the reviewer.
- Kristin Lindahl NoneI need this before the board meeting, to be honest. Not signed, but the picture clear. The board will ask what we'd be buying and what it changes for families.
- Jordan Pike NoneThen what would make this a yes for you, Kristin? Is it the security review, the price, or seeing it on your own communities again?
- Kristin Lindahl NoneSecurity first. Then the price, which is Eric's. I've seen it on our data, I'm convinced about the one view per community.
- Eric Halvorsen NoneThe community directors. Do they have to do anything?
- Jordan Pike NoneVery little at the start. They ask questions and read answers. The setup work sits with us and your IT. Kristin, I'd suggest we loop in a couple of community directors during rollout.
- Kristin Lindahl NoneYes. Let's loop in the community director from the pilot group. She'll tell us straight if it creates work.
- Eric Halvorsen NoneTimeline.
- Jordan Pike NoneIn my forecast the expected close is Tuesday 29 December 2026. That gives your reviewer time, and it keeps you ahead of year end. If the review runs longer, I'd rather move the date than rush it.
- Eric Halvorsen NoneMove it if needed. Do not rush privacy.
- Jordan Pike NoneAgreed, no rushing. So let me play back the next steps. I send you the one-page summary and the full proposal early next week, with the annual and implementation lines split out. Kristin, you book the review session with your privacy and security lead, and I bring our security material to that call.
- Kristin Lindahl NoneYes. I'll get the session on the calendar this week, and I'll tell you who's attending.
- Jordan Pike NonePerfect. And Eric, from you, nothing until the review is done?
- Eric Halvorsen NoneCorrect. Send me the page. Tell me when privacy has signed off.
- Kristin Lindahl NoneI'll tell you, Eric. And I won't commit anything on budget before you've seen it.
- Jordan Pike NoneThanks, both. That's a clear plan and we're a few minutes under the time. Have a good weekend.
- Kristin Lindahl NoneYou too, Jordan. Thanks, everyone.
- Eric Halvorsen NoneThank you.