CareSwift growth playbook

Add permanent (301) redirects from /demo, /request-demo and every old path to the closest live page: /demo to /book-demo, /how-careswift-works and /faq to the homepage sections, /financial-benefits to the homepage agency section. Then update the website and demo links on the YC profile and launch post to careswift.com/book-demo, and check the LinkedIn, X and Crunchbase links the YC profile lists. Add a helpful 404 page with a "Book a 20-minute demo" button so no future broken link is a dead end.

The YC profile and launch post are among the most visited and most trusted pages about an early startup, and buyers who click a demo link from them already intend to talk. A redirect turns every one of those clicks back into a booking chance, and it also returns the search value of the old links to the live pages.

[ ] /demo -> /book-demo (301)
[ ] /request-demo -> /book-demo
[ ] /how-careswift-works -> /#how-it-works
[ ] /financial-benefits -> /#for-agencies
[ ] /faq -> /#faq
[ ] /hipaa-compliance -> /security
[ ] /contact -> /book-demo
[ ] Test apex and www
[ ] YC profile and launch post links updated
[ ] 404 page with a demo button

• A redirect sends visitors to the wrong section

  Map each old page to the closest topic and test by hand.

• Other old links are missed

  Log 404s for a month and redirect any that recur.

• Your websiteOld URLs (fetched twice on November 10, 2026): careswift.com/demo and www.careswift.com/demo return 404 Not Found, as do /how-careswift-works, /financial-benefits and /faq. The working demo page is /book-demo.Source
• Y CombinatorYC company profile: Summer 2025 batch, team of 2, New York City; the CEO is a current EMT who worked four years in the NYC 911 ambulance system. The profile's demo link and the YC launch post both send visitors to careswift.com/demo. The launch post still describes an AI copilot that plugs into existing ePCR systems, with dictation and auto-filled fields, for agencies from small volunteer squads to large ones.Source
• Your websiteThe previous site is still live at careswift.pages.dev (copyright 2025), with /how-careswift-works and /financial-benefits. It claims narratives in "under 2 minutes", documentation-related denials cut "by up to 75%", over 200 hours reclaimed per provider a year, "hundreds" of EMTs using it and up to $219,000 more revenue per ambulance a year, with "Expected ROI within 60-90 days based on current customer results" and no sources.Source
• Your websiteBook-demo page: a 20-minute call where you "meet directly with a CareSwift founder", a date picker and a "Request another time" link. The page has no proof points, customer names or security summary.Source

Replace each pending note with a firm statement or remove the line until it is true: state the default retention preset, and state what the Trust Center covers today (or say "available on request during security review"). Remove the milestone note from the homepage banner. Add a "last updated" date to the security page, and set a rule that no internal codes go on public pages.

Security review is often the slowest step in selling to an agency that handles PHI. A page that answers firmly removes questions before they reach the founder's inbox, and it matches the careful, precise tone of the rest of the site.

• Stating a default before it is confirmed

  Remove the line instead of guessing.

• Your websiteSecurity, Data, and AI Practices page: HIPAA compliant for approved agency deployments; a BAA is signed before any PHI; a separate environment per agency; retention presets of 30, 90 or 365 days, with unfinished drafts deleted after seven days of inactivity; CareSwift support has no PHI access by default; a Vanta-hosted Trust Center. Two lines still carry internal "pending" notes with project milestone codes (on the default retention preset and on the Trust Center scope). No SOC 2 report, subprocessor list, hosting region or MFA detail is published.Source
• PageSpeedGoogle PageSpeed (mobile, November 10, 2026): performance 100 (desktop 100), LCP 1.2 s, CLS 0, 306 KB, no third-party scripts. Accessibility 98, with one issue: "Heading elements are not in a sequentially-descending order". The largest element on screen is the top banner "Looking for CareSwift's separate ePCR product?". There is no real-visitor (field) data yet, and the homepage has no social share image.Source

Redirect every careswift.pages.dev page to its closest careswift.com page (or take the project offline and leave a single redirect). Keep only claims you can back up: move the time-saving story to the new site in the form you can prove from your own data (for example, time to finalization in CareSwift), and drop revenue promises until a pilot measures them.

One consistent story builds trust with chiefs and with the compliance reviewers who read every claim. It also stops the old site competing with careswift.com in search.

• Losing a page that still brings visitors

  Redirect rather than delete, so the visitors reach the new site.

• #1 Fix the 404 behind the "Book a demo" links on CareSwift's Y Combinator profile and launch post

• Your websiteThe previous site is still live at careswift.pages.dev (copyright 2025), with /how-careswift-works and /financial-benefits. It claims narratives in "under 2 minutes", documentation-related denials cut "by up to 75%", over 200 hours reclaimed per provider a year, "hundreds" of EMTs using it and up to $219,000 more revenue per ambulance a year, with "Expected ROI within 60-90 days based on current customer results" and no sources.Source
• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source
• Site historyChanges since December 10, 2025: the headline moved from "AI Scribe + Compliance for Ambulance Reports" to "Faster EMS narratives. Your agency's standards."; the site moved from Framer to Next.js and dropped Google Analytics, PostHog and Crisp chat. No analytics tool is detected on the site now.Source

Add /book-demo and /security to the sitemap and generate it from the routes so new pages are included. Add a share image (headline plus a product screenshot with synthetic data) and titles and descriptions for each page. Fix the heading order the accessibility audit flags.

Search engines and AI assistants find and describe the pages buyers need, and every shared link looks like a real product. Accessibility fixes also matter to public-sector buyers.

• Screenshot shows real data

  Use only synthetic call details.

• Your websiteSitemap: 3 URLs (homepage, privacy policy, terms). /book-demo and /security are linked from every page but not listed. There is no blog, case study, pricing, FAQ or per-ePCR page.Source
• PageSpeedGoogle PageSpeed (mobile, November 10, 2026): performance 100 (desktop 100), LCP 1.2 s, CLS 0, 306 KB, no third-party scripts. Accessibility 98, with one issue: "Heading elements are not in a sequentially-descending order". The largest element on screen is the top banner "Looking for CareSwift's separate ePCR product?". There is no real-visitor (field) data yet, and the homepage has no social share image.Source

Add one lightweight, cookie-free analytics tool on the marketing site only (never inside the PHI app), plus 404 logging and three events: demo page viewed, date chosen, booking made. Tag every outbound and YC link with UTM parameters so each source can be counted. Review a one-page funnel every Monday.

With two or three people selling, knowing which source produces booked demos decides where the founder's time goes. It also proves whether ideas 1 and 3 worked.

• Tracking near PHI

  Keep analytics off the app domain; marketing pages only.

• Site historyChanges since December 10, 2025: the headline moved from "AI Scribe + Compliance for Ambulance Reports" to "Faster EMS narratives. Your agency's standards."; the site moved from Framer to Next.js and dropped Google Analytics, PostHog and Crisp chat. No analytics tool is detected on the site now.Source
• Your websiteOld URLs (fetched twice on November 10, 2026): careswift.com/demo and www.careswift.com/demo return 404 Not Found, as do /how-careswift-works, /financial-benefits and /faq. The working demo page is /book-demo.Source

Decide the two-product story. If the ePCR is not for sale yet, remove the banner and add a single footer link or an "early access" FAQ answer. If it is, give it its own page on careswift.com that explains how it relates to the narrative product. Either way, the headline should be the first thing a visitor reads.

The first line decides whether a visitor reads on. A clear single message keeps attention on the product that is ready to buy.

• ePCR prospects lose their way in

  Keep a clear footer link and an FAQ answer.

• PageSpeedGoogle PageSpeed (mobile, November 10, 2026): performance 100 (desktop 100), LCP 1.2 s, CLS 0, 306 KB, no third-party scripts. Accessibility 98, with one issue: "Heading elements are not in a sequentially-descending order". The largest element on screen is the top banner "Looking for CareSwift's separate ePCR product?". There is no real-visitor (field) data yet, and the homepage has no social share image.Source
• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source

Pick one agency that will go on record. Agree the baseline (late charts, sendbacks, supervisor follow-up, time to finalization), measure 60 days, and publish a one-page result with a quote from the chief or QA lead. Add it to the homepage, the book-demo page and outbound emails. If no agency will be named yet, publish an anonymized "mid-size private ambulance service" version.

Chiefs buy what peers have already proven. One measured, named result does more for a two-person sales team than any feature list, and it answers the question every demo starts with.

• Agencies are cautious about being named

  Offer an anonymized version, or a quote from the QA lead only.

• The result is small

  Publish the honest number and the method; buyers trust a modest measured gain.

• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source
• PressHUGE Magazine feature (February 5, 2026 edition): names no CareSwift customers, pilots or deployments, and says the writer wants to see pilot programs and crew adoption; describes ImageTrend and ESO as the dominant US EMS documentation platforms; NYC crews may run 8 to 12 calls in a 12-hour shift.Source
• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source

Add a short "How pricing works" section and page: what drives the price (number of providers, call types configured, deployment support), a typical starting range or per-provider figure, what is included (configuration, synthetic testing, training, BAA) and that crews are never charged. Add a one-page budget sheet chiefs can attach to a purchase request.

A range lets buyers qualify themselves and lets the founder spend demo time on the agencies that can buy. It also answers the first question procurement asks.

• A public number anchors negotiations

  Publish a starting point and the drivers, not a fixed rate card.

• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source
• Competitor researchESO Auto-Generated Narrative (press release, June 25, 2025): launched in May 2025; more than 35,700 hours saved in the first month; more than 1,670 EMS agencies adopted it; included for existing ESO EHR customers; it builds the narrative from chart data, and a provider must review and approve it.See the research Source
• Competitor researchTwofold EMS chart and narrative generator: free for a week, then $19 for the first month; sold to individual medics as well as agencies; narratives are copied or exported into the ePCR; rated 4.8 from 3,079 reviews; a BAA at signup; says it works without full connectivity.See the research Source

Assemble one packet, shared on request through the Trust Center: completed standard questionnaire answers, the subprocessor list, hosting region, encryption and authentication summary, access-control model (already on the security page), incident process, retention presets, the BAA template and the audit status with a date. Offer it on the book-demo page and in the follow-up email after every demo.

Security review is a common place where small-vendor deals stall. Answering before you are asked shortens the time from demo to signed BAA and makes a small team look ready.

• Claiming audits not yet done

  State status and date honestly.

• #2 Take the internal "pending" notes off the security page and the homepage banner

• Your websiteSecurity, Data, and AI Practices page: HIPAA compliant for approved agency deployments; a BAA is signed before any PHI; a separate environment per agency; retention presets of 30, 90 or 365 days, with unfinished drafts deleted after seven days of inactivity; CareSwift support has no PHI access by default; a Vanta-hosted Trust Center. Two lines still carry internal "pending" notes with project milestone codes (on the default retention preset and on the Trust Center scope). No SOC 2 report, subprocessor list, hosting region or MFA detail is published.Source
• Your websiteBook-demo page: a 20-minute call where you "meet directly with a CareSwift founder", a date picker and a "Request another time" link. The page has no proof points, customer names or security summary.Source

Write one fair page: how each tool builds a narrative (from chart data versus from call details plus agency-approved questions), who controls the writing rules, what happens when the chart is missing details, and where CareSwift fits for agencies not on ESO or with strict agency standards. Repeat the format for ImageTrend users and for personal AI tools, which the homepage already argues against.

Comparison searches come from buyers close to a decision, and a calm, factual page lets the founder skip the objection on calls.

• Out-of-date claims about a rival

  Date the page and quote only their published material.

• Competitor researchESO Auto-Generated Narrative (press release, June 25, 2025): launched in May 2025; more than 35,700 hours saved in the first month; more than 1,670 EMS agencies adopted it; included for existing ESO EHR customers; it builds the narrative from chart data, and a provider must review and approve it.See the research Source
• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source
• PressHUGE Magazine feature (February 5, 2026 edition): names no CareSwift customers, pilots or deployments, and says the writer wants to see pilot programs and crew adoption; describes ImageTrend and ESO as the dominant US EMS documentation platforms; NYC crews may run 8 to 12 calls in a 12-hour shift.Source

For each ePCR CareSwift has tested, publish a short page: a screen recording with synthetic data of a narrative going from CareSwift into that system's narrative field, the browsers and devices tested, formatting notes and a demo button. Describe the systems factually and avoid implying a partnership.

Pages that match how buyers search bring qualified visitors, and showing the exact workflow removes the biggest practical doubt.

• An ePCR update breaks the flow shown

  Date each page and retest quarterly.

• #4 List /book-demo and /security in the sitemap, add a share image and fix the heading order

• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source
• Your websiteSitemap: 3 URLs (homepage, privacy policy, terms). /book-demo and /security are linked from every page but not listed. There is no blog, case study, pricing, FAQ or per-ePCR page.Source

Give crews a short page and a one-page PDF to forward to their chief or QA lead: what changes for the agency, the governance and BAA story, and a link that books a demo tagged with the referring medic. Thank medics whose referral becomes a pilot (for example, agency-branded gear or a continuing-education donation), within the rules of their employer.

Chiefs listen to their own crews, and a medic who already uses the product is the most credible voice CareSwift has.

• Gifts conflict with employer rules

  Keep thanks small and offer a donation option.

• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source
• Competitor researchTwofold EMS chart and narrative generator: free for a week, then $19 for the first month; sold to individual medics as well as agencies; narratives are copied or exported into the ePCR; rated 4.8 from 3,079 reviews; a BAA at signup; says it works without full connectivity.See the research Source
• App StoreiOS app "CareSwift" (CARESWIFT INC): free, listed under Utilities, described as "an AI platform that helps EMTs write better documentation"; 5.0 from 3 ratings and no written reviews; version 1.0 on September 23, 2025, now at 1.1.10.Source

Each week, post one short piece built on a synthetic call: a weak narrative, the missing details a QA reviewer would flag, the clarifying questions that fix it, and the better result. Publish on LinkedIn and on a careswift.com/notes page, and send the best ones to prospects.

Practical examples from a peer earn attention from crews and QA leads, give outbound a reason to reach out, and give search and AI assistants something to cite.

• A post reads as clinical advice

  Frame it as documentation practice and defer to local protocol.

• Y CombinatorYC company profile: Summer 2025 batch, team of 2, New York City; the CEO is a current EMT who worked four years in the NYC 911 ambulance system. The profile's demo link and the YC launch post both send visitors to careswift.com/demo. The launch post still describes an AI copilot that plugs into existing ePCR systems, with dictation and auto-filled fields, for agencies from small volunteer squads to large ones.Source
• Past job postFounding EMS Sales Development Representative (posted May 26, 2026, closed June 24, 2026; still shown on the YC jobs page): prospect EMS agencies, ambulance services and fire departments; run cold call, email and LinkedIn outreach to agency chiefs and operations directors; book demos for the founder, who closes; build a repeatable outbound process.Source
• Your websiteSitemap: 3 URLs (homepage, privacy policy, terms). /book-demo and /security are linked from every page but not listed. There is no blog, case study, pricing, FAQ or per-ePCR page.Source

Publish 8 to 10 starter sets as simple pages and a downloadable sheet: the essential details for the call type, the clarifying questions CareSwift asks when one is missing, and a sample narrative built from a synthetic call. Invite agencies to send their own rules for a free mock-up of their configuration, which becomes the demo.

It turns the hidden part of the product into something a QA lead can share internally, and a request for a mock-up is a warmer lead than a cold demo booking.

• Sets read as clinical standards

  Label them as documentation starting points that each agency approves.

• Agency rules shared by mistake

  Use only generic content; never publish a customer's configuration.

• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source
• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source

Package it: one shift or station, up to a set number of providers, three call types, 60 days, a fixed fee credited against the first year, and a written go/no-go based on the agreed baseline. Publish the outline on the site and offer it at the end of every demo.

Agencies find it easier to approve a small, time-boxed, measured pilot than an open-ended deployment, and every finished pilot produces the proof in idea 5.

• Pilots that never convert

  Agree the go/no-go criteria and the year-one price before starting.

• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source
• PressHUGE Magazine feature (February 5, 2026 edition): names no CareSwift customers, pilots or deployments, and says the writer wants to see pilot programs and crew adoption; describes ImageTrend and ESO as the dominant US EMS documentation platforms; NYC crews may run 8 to 12 calls in a 12-hour shift.Source

Approach a few regional EMS billing companies with a referral partnership: they introduce CareSwift to client agencies whose narratives often need follow-up, and CareSwift gives them an agency-approved view of which details are now asked for by call type. Make no billing-outcome claims; measure follow-up requests jointly with one agency.

Billing partners have trusted relationships with many agencies at once and a direct reason to want cleaner narratives, so one partner can bring several warm introductions.

• Billing or referral rules

  Have counsel review any fee arrangement before signing.

• Your websiteThe previous site is still live at careswift.pages.dev (copyright 2025), with /how-careswift-works and /financial-benefits. It claims narratives in "under 2 minutes", documentation-related denials cut "by up to 75%", over 200 hours reclaimed per provider a year, "hundreds" of EMTs using it and up to $219,000 more revenue per ambulance a year, with "Expected ROI within 60-90 days based on current customer results" and no sources.Source
• Past job postFounding EMS Sales Development Representative (posted May 26, 2026, closed June 24, 2026; still shown on the YC jobs page): prospect EMS agencies, ambulance services and fire departments; run cold call, email and LinkedIn outreach to agency chiefs and operations directors; book demos for the founder, who closes; build a repeatable outbound process.Source
• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source

Pick two states or regions where CareSwift already has users. Offer each regional EMS council or state association a free, non-sales education session on narrative quality (built from idea 12's material), a member-only pilot rate, and a short write-up for their newsletter. Follow up with attendees in small groups rather than single calls.

Associations already convene the chiefs and QA leads CareSwift wants, and a peer-endorsed session reaches dozens of agencies for the cost of one presentation.

• Groups do not allow vendor sessions

  Offer sponsorship of an existing education day instead.

• #12 A weekly "narrative fix" post from the EMT founder, using synthetic calls

• Past job postFounding EMS Sales Development Representative (posted May 26, 2026, closed June 24, 2026; still shown on the YC jobs page): prospect EMS agencies, ambulance services and fire departments; run cold call, email and LinkedIn outreach to agency chiefs and operations directors; book demos for the founder, who closes; build a repeatable outbound process.Source
• Y CombinatorYC company profile: Summer 2025 batch, team of 2, New York City; the CEO is a current EMT who worked four years in the NYC 911 ambulance system. The profile's demo link and the YC launch post both send visitors to careswift.com/demo. The launch post still describes an AI copilot that plugs into existing ePCR systems, with dictation and auto-filled fields, for agencies from small volunteer squads to large ones.Source

Keep the provider's in-progress answers on the device (encrypted, cleared on submit or after the seven-day draft limit) so a dropped connection pauses the draft instead of losing it, with a clear "reconnecting" state. Add a short FAQ answer on what happens offline. Check the change against the security model and BAA before release.

It removes a practical objection in demos and protects adoption, which is what agencies will measure.

• PHI stored on shared devices

  Encrypt, clear on submit and follow the agency's device rules.

• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source
• Competitor researchTwofold EMS chart and narrative generator: free for a week, then $19 for the first month; sold to individual medics as well as agencies; narratives are copied or exported into the ePCR; rated 4.8 from 3,079 reviews; a BAA at signup; says it works without full connectivity.See the research Source
• Your websiteSecurity, Data, and AI Practices page: HIPAA compliant for approved agency deployments; a BAA is signed before any PHI; a separate environment per agency; retention presets of 30, 90 or 365 days, with unfinished drafts deleted after seven days of inactivity; CareSwift support has no PHI access by default; a Vanta-hosted Trust Center. Two lines still carry internal "pending" notes with project milestone codes (on the default retention preset and on the Trust Center scope). No SOC 2 report, subprocessor list, hosting region or MFA detail is published.Source

Publish a /fire-departments page: how CareSwift fits a fire department's EMS documentation, the agency-approved questions for the call types fire-based crews run most, governance and BAA in plain words, and a demo button. Use it in outbound to fire chiefs and in association sessions.

A page that names the buyer's world converts better than a general one, and fire departments are a large segment of US EMS that the current site does not address.

• Thin page with no proof

  Add a fire department result as soon as one exists.

• #13 Publish starter question sets by call type, so agencies see their own standards in CareSwift before the demo

• Past job postFounding EMS Sales Development Representative (posted May 26, 2026, closed June 24, 2026; still shown on the YC jobs page): prospect EMS agencies, ambulance services and fire departments; run cold call, email and LinkedIn outreach to agency chiefs and operations directors; book demos for the founder, who closes; build a repeatable outbound process.Source
• Your websiteSitemap: 3 URLs (homepage, privacy policy, terms). /book-demo and /security are linked from every page but not listed. There is no blog, case study, pricing, FAQ or per-ePCR page.Source

Add a light review layer inside CareSwift: supervisors flag a finalized narrative with a reason from the agency's own rules, the provider sees the note on their next similar call, and the agency gets a report of the most common gaps by call type, feeding back into the clarifying questions. Keep corrections to the chart itself in the ePCR.

It gives QA leads a reason to champion CareSwift, raises the value of each seat and creates a loop where the questions improve from real gaps.

• Overlap with ePCR QA modules

  Focus on narrative gaps and feeding the questions, not chart correction.

• #5 Turn "100,000+ narratives" into one measured agency pilot result, published with the agency's permission

• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source
• Your websiteSecurity, Data, and AI Practices page: HIPAA compliant for approved agency deployments; a BAA is signed before any PHI; a separate environment per agency; retention presets of 30, 90 or 365 days, with unfinished drafts deleted after seven days of inactivity; CareSwift support has no PHI access by default; a Vanta-hosted Trust Center. Two lines still carry internal "pending" notes with project milestone codes (on the default retention preset and on the Trust Center scope). No SOC 2 report, subprocessor list, hosting region or MFA detail is published.Source

Pick one ePCR vendor whose customers overlap with CareSwift's pipeline and which lacks a built-in narrative feature. Propose a narrow integration: CareSwift hands the finished narrative into the narrative field and gets back a "chart locked" signal so agencies can measure completion. Start with a joint pilot at a shared customer.

Removing the copy step answers the most common workflow objection, and completion data makes CareSwift's results measurable end to end.

• Vendor builds its own narrative feature instead

  Keep agency standards and clarifying questions as the part they cannot copy quickly.

• #10 One page per ePCR, showing the tested copy-paste flow into each system

• Your websiteHomepage FAQ: supervisors can read finalized narratives and team analytics, but there are currently no approvals, comments, sendbacks or correction queue; the product is browser-based and needs an internet connection; CareSwift cannot confirm whether the ePCR chart was completed; in a deployment, using agency data, it can compare late charts, corrections, sendbacks and supervisor follow-up against an agreed baseline; formatting and copy-paste are tested with synthetic data in each ePCR, browser and device combination.Source
• Y CombinatorYC company profile: Summer 2025 batch, team of 2, New York City; the CEO is a current EMT who worked four years in the NYC 911 ambulance system. The profile's demo link and the YC launch post both send visitors to careswift.com/demo. The launch post still describes an AI copilot that plugs into existing ePCR systems, with dictation and auto-filled fields, for agencies from small volunteer squads to large ones.Source
• Competitor researchESO Auto-Generated Narrative (press release, June 25, 2025): launched in May 2025; more than 35,700 hours saved in the first month; more than 1,670 EMS agencies adopted it; included for existing ESO EHR customers; it builds the narrative from chart data, and a provider must review and approve it.See the research Source

With agency permission and only aggregated, de-identified counts (no narrative text), publish a yearly report: the most-missed details by call type, how time to finalization changes over the first months of use, and what agencies with the fewest sendbacks do differently. Launch it with a webinar for QA leads and send it to trade press.

Original data earns press, links and conference slots, and positions CareSwift as the authority on narrative quality rather than one more AI tool.

• Privacy concerns

  Aggregate counts only, agency consent, reviewed against the BAA.

• #5 Turn "100,000+ narratives" into one measured agency pilot result, published with the agency's permission

• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source
• Competitor researchESO Auto-Generated Narrative (press release, June 25, 2025): launched in May 2025; more than 35,700 hours saved in the first month; more than 1,670 EMS agencies adopted it; included for existing ESO EHR customers; it builds the narrative from chart data, and a provider must review and approve it.See the research Source
• Your websiteSecurity, Data, and AI Practices page: HIPAA compliant for approved agency deployments; a BAA is signed before any PHI; a separate environment per agency; retention presets of 30, 90 or 365 days, with unfinished drafts deleted after seven days of inactivity; CareSwift support has no PHI access by default; a Vanta-hosted Trust Center. Two lines still carry internal "pending" notes with project milestone codes (on the default retention preset and on the Trust Center scope). No SOC 2 report, subprocessor list, hosting region or MFA detail is published.Source

Offer a standard configuration (the starter question sets from idea 13, standard roles, the default retention preset) for agencies under a set number of providers, at a published flat annual price, signed with the standard BAA and set up through a guided onboarding call rather than a full deployment. Test it in one region first.

It opens many small agencies without consuming founder time, and some of them grow or join larger systems that later buy the full deployment.

• Support load from many small accounts

  Cap the number of standard-plan agencies in the test.

• #13 Publish starter question sets by call type, so agencies see their own standards in CareSwift before the demo

• Y CombinatorYC company profile: Summer 2025 batch, team of 2, New York City; the CEO is a current EMT who worked four years in the NYC 911 ambulance system. The profile's demo link and the YC launch post both send visitors to careswift.com/demo. The launch post still describes an AI copilot that plugs into existing ePCR systems, with dictation and auto-filled fields, for agencies from small volunteer squads to large ones.Source
• Competitor researchTwofold EMS chart and narrative generator: free for a week, then $19 for the first month; sold to individual medics as well as agencies; narratives are copied or exported into the ePCR; rated 4.8 from 3,079 reviews; a BAA at signup; says it works without full connectivity.See the research Source
• Your websiteHomepage (checked November 10, 2026): headline "Faster EMS narratives. Your agency's standards."; crews answer clarifying questions, then copy the reviewed narrative into the ePCR they already use, and CareSwift does not write back to or submit charts; "100,000+" EMS narratives generated by providers; the call to action is "Book a 20-minute demo"; pricing depends on deployment scope and is given after the demo, and individual providers are not charged; no customers, logos or testimonials are shown; it argues that personal AI tools or saved text don't give agencies consistent standards or governance.Source