The recap waits until Friday
After three visits in one day, it gets written at the end of the week, from memory.
Deals · Founding program
By the time you leave the hospital, the deal is already moving
With a handful of founding teams, we’re building everything that follows a hospital visit: the recap, a draft proposal, answers to the IT security questionnaire drawn from your own documents, and a follow-up for every stakeholder. Your rep reviews and sends. For every deal, you’ll know who has said yes, and who’s still missing.
Book a 30-minute call
Pick a time that suits you. Instant confirmation, reminder the day before.
A hospital deal isn’t lost during the visit: it goes cold afterward
A 12- to 18-month sales cycle. One head of department on board, then biomedical engineering, hospital IT, senior management, and purchasing to win over in turn. Every week without an answer lets the project cool off.
The IT security questionnaire stalls everything
Security, health data hosting, GDPR, interoperability: dozens of questions that hold up the deal for weeks.
Someone is always missing
Nobody has met biomedical engineering, purchasing knows nothing about the project, and you only find out at order time.
Your clinical champion moves on
The head of department who backed the project leaves, and nobody reaches out to their successor.
From the first visit to the committee, every step prepared
Prep
The day before: the department, its latest dated signals, the incumbent competitor, the people already met, and the questions to ask.
Debrief
As you walk out of the department: the visit recap, the objections, the people mentioned, and the next step.
Proposal
The goal: a draft proposal ready for review 30 minutes after the visit, in the department’s own words, built to circulate all the way to the committee.
IT security questionnaire
Security, hosting, GDPR, interoperability: every answer drawn from your own documents, with its source.
Decision map
For every deal: who has said yes, who is waiting on an answer, who hasn’t been met yet. Each follow-up is ready at the right moment.
Memory
Every visit you’ve made, linked to deals won and lost: the objections that keep coming up, what gets a department to sign.
Debrief · on your way out
The recap is ready before your next visit
Everything that matters for the next step is captured, along with who said it. Your rep corrects anything that needs it and never retypes a thing.
- From your video calls and your rep’s notes
- A hallway chat at a medical conference counts too: a voice memo will do (in progress)
- No patient data ever goes in
Debrief · Valmont General Hospital
Cardiology · visit on Thursday, October 8, 10:00 to 10:50 AM
-
Monitor patients remotely after discharge to reduce readmissions.
Source: visit notes
-
Not one extra minute for the nurses: training has to fit into shift handovers.
Source: visit notes
-
Biomedical engineering will sign off on maintenance, hospital IT on security.
Source: visit notes
-
Could go to the November equipment committee.
Source: visit notes
Next step
Draft proposal to the head of department by October 20; ask hospital IT for its questionnaire.
Noted in the recap, with both deadlines.Proposal · 30-minute goal
A draft proposal the head of department can pass around
They’ll find their own words, numbers and timeline in a clear document they can forward all the way to the committee. Your rep reviews it, settles scope, indicative price, and timing, then sends it.
- No quote to sign: the purchase follows the hospital’s own procurement process
- A file built to circulate internally
- Gaps get flagged, never made up
Draft proposal ready for review
Valmont General Hospital · cardiology
Visit on Thursday, October 8, ended at 10:50 AM
Fictional example Ready at 11:20 AM
To be forwarded to the committee: no quote to sign; the purchase follows the hospital’s procurement process.
What the department said, how the draft answers
“My nurses don’t have a single extra minute for a new tool.”
Section 2: on-site training during shift handovers, in two half-days.
“Hospital IT will have to approve it, and they take their time.”
Section 4: hospital IT’s security questionnaire will be completed as soon as it arrives.
For your rep to decide
- Scope: inpatient beds only, or the cardiac ICU too?
- Indicative price: list price, or the purchasing group’s contract price?
- Timeline: the November committee, or January?
Flagged, not made up
- Biomedical engineering contact not named: the question is ready for the cover email.
Sources
- Needs and timelineSource: October 8 recap
- Specifications and CE markingSource: your product sheets
IT security questionnaire
The goal: a security questionnaire ready for review within a day
Every answer is drawn from your own documents, with its source. Anything they don’t cover is left to your team, never guessed.
- Only from answers you have approved
- The source for every answer
- Unanswered questions are flagged
Security questionnaire
Valmont General Hospital · IT
48 questions: security, hosting, GDPR, interoperability
Fictional example Received Monday, ready Tuesday
45 answers drawn from your documents, 3 left to your team.
Questions and suggested answers
“Is health data hosted by a certified health data host (HDS)?”
Yes, certificate attached. Source: your security file, page 4.
“Does the device integrate with the electronic health record?”
Yes, through HL7 FHIR; list of connected EHR vendors attached. Source: your interoperability sheet.
Left to your team
- Data protection impact assessment: document missing, question ready for your data protection officer.
Documents used
- Security fileSource: approved September 2026 version
- Interoperability sheetSource: your technical documentation
Decision map
Know who has said yes, and who’s still missing
Head of department, nurse manager, biomedical engineering, hospital IT, purchasing: for every deal, every stakeholder, where they stand, and the next follow-up. If your champion moves on, a message to their successor is ready for review that same week.
Decision map · Valmont, cardiology
5 stakeholders · updated October 15
-
Champions the project; wants to take it to the November committee.
Source: October 8 visit
-
Agrees, as long as training fits into shift handovers.
Source: October 8 visit
-
Waiting for the maintenance sheet; follow-up ready for Tuesday.
Source: October 12 email
-
Security questionnaire returned on October 14.
Source: October 14 email
-
No contact yet: an introduction is ready, to go through the head of department.
Source: decision map
If your champion leaves
A message to their successor, ready for review that same week.
The job change is spotted, and the follow-up is ready for review.We prepare, your team decides
Nothing goes out without them
Your rep reviews everything before it goes out: draft proposal, answer to hospital IT, follow-up.
Three decisions, nothing more
Scope, indicative price, timeline: they decide from their phone, between visits.
Gaps get flagged
Missing information becomes a question to ask, never a guess.
Your answers, your documents
Technical answers only come from documents you have approved, every sentence with its source.
What gets recorded, and what stays yours
No one is recorded without their knowledge
Participants are told at the start and can say no. Without a recording, your rep’s notes are enough.
No patient data
Recaps, draft proposals and questionnaires cover the department and the project, never an individual patient.
Your data stays yours
Everything we prepare is delivered to you as documents; when the contract ends, we hand it all back.
Hosted in the European Union
Your data is hosted in Germany. You get the list of our subprocessors before kickoff.
Founding program
Build Deals with us
For four weeks, our team preps your next ten hospital visits and turns each one into a recap and a draft proposal the same day. We also complete three IT security questionnaires or committee files from your documents. You shape the product; we measure what it gets you.
- Backed by Station F
Spots are limited: we take on a few teams each quarter so we can hit our turnaround times. Your subscription only starts if you choose to, after the review.
Four-week pilot
- Prep and recap for your next 10 visits
- For each one, a draft proposal ready for review the same day
- 3 IT security questionnaires or committee files, completed from your documents
- A results review: turnaround times, documents sent without a rewrite, replies within 7 days
FAQ
Your questions, answered
Not as a self-serve product yet. We’re building Deals with a handful of founding teams. During the pilot, our team prepares your recaps and draft proposals the same day, and the product takes shape around your own visits.
It’s two-thirds drafted the day before, from what we know about the account, then completed with the meeting itself, so it uses the buyer’s own words. Your rep settles scope, price, and timing. During the program, we measure the actual turnaround and share it with you.
No. Nothing goes out until your rep has reviewed it. They’re the one who sends the proposal, the answer, or the follow-up.
A template doesn’t know your visits, your product sheets, your approved security answers, or the stakeholders on each deal. Deals starts from all of that, and your rep still has the final say.
Prices come from your catalog and your discount rules. For anything off-catalog, the proposal asks instead of guessing. During the program, our team checks every name, every price, and every scope item, and the final call stays with your rep.
No. Deals prepares the documents that move a deal forward: recap, draft proposal, IT security questionnaire, follow-ups. Full responses to public tenders are outside its scope.
That’s the program’s goal. It relies on a set of answers you have approved: your security file, hosting documents, and interoperability sheet. We build it with you at kickoff; anything it doesn’t cover is left to your team.
Today, recaps start from video calls and your rep’s notes. Voice memos, recorded on the way out of a meeting, are being built with our founding teams.
Participants are told at the start of the conversation and can say no. Without a recording, your rep’s notes are enough. We agree on retention periods with you before kickoff.
The tool prepares documents for them; it doesn’t score them. If your works council (CSE) needs to be informed, we prepare that with you during onboarding.
No. Deals prepares what needs to go into it. The connection to your CRM is built with you during the founding program.
It’s hosted in Germany, in the European Union, and everything we prepare belongs to you. You get the list of our subprocessors before kickoff. We don’t claim any certification we don’t hold. See our security and data page for the details.
Move your next hospital deal forward the moment you walk out
One call to look at this week’s visits and see whether the founding program is right for you. You’ll get our proposal the same day.