×CicadaWebsite proposal · November 2026
One
Kandu.
Four websites become one front door, designed to turn every visit into a next step.
Today
For professionals
One site, one brand, one place to start.
Scroll, or use the ↓ and ↑ keys to move between sections.
The short version
One site, built to convert every visit.
- What
Bring kandu.com, kandustroke.com, kanduhealth.com and neurolutions.com together as one fast, patient-first kandu.com, with a professionals section that works like its own site.
- Why
Kandu reaches more people than ever, with 1.24 million visitors so far in 2026. One clear front door turns more of them, from every channel, into qualified conversations.
- Worth
Every 0.1-point gain in visitor-to-DIQ conversion adds about 590 booked consults at 2026 traffic, roughly $100k of meetings that don't have to be bought with media.
- How
Built on 16 months of Kandu's own search and analytics data, with every page mapped to its new home.
Where things stand
Four websites. One company.
Since the merger, the Kandu story lives across four domains and three names. Each site was built for a different moment, and a survivor, a neurologist and a payer each have to work out which one is meant for them.
neurolutions.com
IpsiHandWhere people act
The IpsiHand site. Nearly all of today's traffic, qualify forms and bookings happen here.
213 indexed URLs
kandu.com
CorporateThe company story
Leadership, science and careers. Points to the other sites for IpsiHand and clinical services.
13 pages
kanduhealth.com
Pre-mergerProviders and payers
The original Kandu Health site, written for hospitals and payers.
15 pages
kandustroke.com
Navigation (PIN)Survivor support
Kandu's navigation program for survivors, with its own registration.
53 pages
domains, each with its own navigation and footer
brand names: Kandu, Kandu Health and Neurolutions
sets of privacy and legal pages to keep in sync
URLs in all, across the four sites and HubSpot
16 months of Search Console and GA4, plus 2026 Databox reporting
Every page is a front door.
People arrive from ads, from search, from a doctor's handout, from a link a friend sent. The new site is built so that every one of those entrances leads somewhere.
visitors in 2026 so far, across every channel
clicks from Google search in the last 16 months
of those search clicks came from phones
Small lifts, big numbers
About 86% of 2026 visitors arrive from paid media. At that scale, each 0.1-point lift in visitor-to-DIQ conversion means about 1,240 more DIQs and 590 more booked consults, roughly $100k of meetings at $169 each.
Databox, Jan 1 – Nov 4 2026
A huge audience already reading
Stroke education articles bring most of Kandu's search traffic, and today about 0.25% of article visits convert. A short "is this you?" module and a thumb-reach qualify button on every article can lift that. Doubling it adds about 500 conversions a year at current traffic.
Search Console + GA4, Jul 2025 – Nov 2026
Answer the questions people actually ask
The "Get IpsiHand" page converts 5.8% of visits, the strongest on the site. Searches like "ipsihand cost," "price" and "reviews" deserve pages built the same way. About 3,200 clicks came from searches for "neurolutions," so the name stays visible on kandu.com.
GA4 + Search Console
Designed for one thumb
Most visits happen on a phone, and many IpsiHand candidates have limited use of one hand. Every template is designed for one-handed use first, with the primary action always within reach.
Search Console device report
What we're designing toward
Five moves the best device sites make.
The new kandu.com
One domain. Two experiences.
Patients land on an IpsiHand-first site. Professionals switch to their own section with its own menu, one click away. Everything lives on kandu.com. Click the switch to see each side.
Where today's sites go
/ipsihand//find-a-screening//after-stroke/…/professionals/Product pages keep their current structure under /ipsihand/; articles keep their exact paths; clinician pages move to Professionals./about//careers//professionals/centers-of-excellence/Becomes the home of everything. Company pages move under About./recovery-support//resources/survivor-stories/PIN keeps its own section and its own registration./professionals/clinical-services//professionals/payers/Provider and payer content joins Professionals./news//events/Press, events and trade show pages move onto kandu.com. HubSpot stays the CRM.Why a section and not a subdomain? Visitors get the same separate experience either way. Keeping professionals on kandu.com means one site to secure, one analytics setup and one place for search history to build.
Do I qualify? · how it works
A qualify flow that keeps every visit on kandu.com.
The same routing decisions Kandu makes today, built into the site itself. Every path ends in a next step, and health details only ever travel between systems covered by a BAA.
Who it's for, insurance type, ZIP code, then contact details. One question per screen.
Form vendor with BAAInsurance rules and the territory ZIP list are loaded into the form. The decision happens there, so no patient data goes to a separate routing service.
No patient data storedBook a consult, check coverage, find a screening nearby or explore recovery support. Never a dead end.
Scheduling with BAASubmission and booking create or update the contact in HubSpot and Salesforce, with insurance and health answers stored as protected fields.
CRMs with BAASensitive-data properties for health answers. Email and SMS workflows only reach people who opted in, using the existing SMS consent checkbox.
BAA via HubSpot Sensitive Data TermsThe qualified lead, consult and screening outcome, synced through a BAA-covered connection.
BAA covers Sales, Service and Health CloudGA4 and ad platforms get a generic "lead submitted" or "consult booked" event, with consent. No insurance, ZIP or condition, and nothing in URLs.
Never receives health dataTry the flow
- Coverage up front. Medicare and VA go straight to booking. Medicare Advantage and commercial plans hear that coverage varies, and get a coverage check.
- Every path ends somewhere useful. Out of territory or not covered? A screening near them, Recovery support or a callback.
- Same live data. The territory ZIP list and insurance rules the team already maintains.
- Big targets. One question per screen, no dropdowns, easy one-handed.
Why one question per screen?
It's the default pattern for UK government services, chosen through lab research on high-traffic services because less confident users find it easier, it works well on phones, and it handles errors and branching questions better.
GOV.UK Design System, "Question pages"; GDS Design Notes, "One thing per page" (2015).
What the conversion data says
Published results are mostly single-company case studies. One reported conversions up more than 300% in the first week after switching a long form to multiple steps. That points the right way, but it isn't proof for Kandu.
Venture Harbour, "10 CRO Case Studies You Can Replicate."
So we test it
The qualify page sees roughly 100,000 visits a month. That's enough to A/B test one-question-per-screen against a shorter single page and get a clear answer within weeks of launch.
GA4: about 1.56M sessions over 16 months on the main qualify page.
Design principle
Bold for everyone. Built for stroke survivors.
In one large study of hospital stroke patients, 73% had visual problems, including 28% with visual field loss and 27% with visual inattention. And every IpsiHand candidate has limited use of an arm or hand.
So the energy in the design comes from scale, color and photography, never from tiny type, carousels or motion people can't stop.
Rowe FJ et al., PLOS ONE, 2019 (1,033 patients, three stroke units).
- One-handed by design. Big tap targets, no hover-only menus, no drag gestures, primary action within thumb reach.
- Readable. 18px minimum body text, and only the brand guide's approved color pairs, all of which meet WCAG AA contrast.
- Calm motion. Every video and animation has a pause button and respects reduced-motion settings.
- Plain language. One idea per screen, short sentences, no medical jargon on patient pages.
- Brand-true. Photography and illustration follow the October 2025 guide, including its rules on subjects, color and the Navigator symbol.
- Built to WCAG 2.2 AA, tested with screen readers, keyboard only, and on real phones.
Redirects and cutover
A migration plan built on real traffic.
Every URL that has earned a visit gets a mapped, tested destination. Search engines always take a few weeks to settle after a move, so we watch daily and keep a way back.
URLs mapped one by one, across all four sites and HubSpot
articles keep their exact paths, moved with a single rule
of URLs with a search click in 16 months have a named destination
top-priority URLs tested by hand, before and after launch
| Common approach | Our approach | |
|---|---|---|
| Starting list | The sitemap or a site crawl | 16 months of Search Console and GA4, plus every sitemap. That surfaced 99 URLs no sitemap lists, carrying 129,000 visits, including ad pages, short URLs and printed patient guides:/start-with-ipsihand/ih1/ih2/eeg-checklist/first-session-training-checklist/icd-10-codes |
| Matching | Nearest-looking URL | By purpose. PIN registration stays PIN registration; it never lands in the IpsiHand qualify flow. |
| Priority | Every row treated the same | Ranked by traffic and conversions. Ad pages, booking links in emails and texts, and printed patient guides come first. |
| Where it runs | Inside the CMS | At the edge, so redirects survive any future rebuild. One hop, tracking parameters kept (UTMs, click IDs, booking prefill). |
| The old domains | Allowed to lapse | Kept and redirecting permanently, with sensible fallbacks for any printed URL nobody remembers. |
| Launch day | Flip DNS and watch | Ad URLs updated, every form and booking redirect repointed, daily checks for 30 days, and old hosting kept as a rollback. |
Measurement, security and build
Fast by default. Locked down by design.
Measure what matters
- One analytics setup across all of kandu.com.
- Every conversion tied to its source, because qualify and booking stay on one domain.
- One funnel view joining media spend, DIQs, consults and screenings.
- A pixel and consent policy for health pages, agreed with legal before launch.
- SMS consent carried over exactly as approved.
Built to last five years
- WordPress with native blocks and custom fields. No page builders and no HubSpot CMS. The team edits in a system it already knows.
- The login isn't on the public internet. Admin sits behind single sign-on and two-factor authentication, with least-privilege roles and staging-only access for vendors.
- A performance budget, enforced: Google's Core Web Vitals "good" range on phones, checked on every release.
- Edge caching and redirects in front of the site, coordinated with Kandu IT, which keeps control of DNS.
Full component list in the appendix.
Timeline
Live in January.
Why Cicada
We already know how Kandu's funnel works.
Media
We run Kandu's national Meta campaign, LinkedIn and trade show pages, so we know where paid traffic lands and what it costs.
Qualify and booking
We built the DIQ routing and booking attribution, and we're carrying the SMS consent work through approval.
Proof
We're building the rep counter, automated the screening-event listings and are turning approved claims into patient-ready copy.
Data
This proposal runs on 16 months of Kandu's own Search Console, GA4 and Databox numbers, not a template.
Brand
Every screen follows the October 2025 brand guide: palette, type, photography, illustration and the Navigator symbol.
After launch
We maintain the site, so the team that built it is the team that answers when something needs to change.
Next steps
Let's build One Kandu.
This week
A 45-minute walkthrough with Kandu leadership, including the full redirect map.
Read-only access to start
Analytics viewer access, a content export, and one regulatory contact for printed URLs. Admin and DNS access only at cutover, with Kandu IT in the room.
Kickoff Nov 16
Baseline locked in week one, design approved by Dec 4, launch Jan 12.
Appendix A
Tech stack
What the new kandu.com runs on, what each piece does, and how it handles health data. BAA covered by a business associate agreement. No PHI never receives health details. Decide to confirm in discovery.
| Layer | Tool | Role and notes |
|---|---|---|
| Website | ||
| CMS | WordPress, native block editor No PHI | Custom block theme with custom fields (ACF Pro). No page builders (no Elementor, no Divi) and no HubSpot CMS. Editors build pages from approved components. |
| Hosting | Managed WordPress host Decide | Production plus a staging environment, daily backups, automatic security updates. Chosen with Kandu IT. Forms are vendor-hosted, so patient data never touches the web server. |
| SEO | Yoast SEO | Same plugin Neurolutions uses today, so titles, descriptions and sitemaps carry over cleanly. |
| Spanish | Multilingual plugin, /es/ pages Decide | Human-translated core patient pages (IpsiHand overview, qualify, coverage, safety, legal). Everything else built to translate well in the browser. |
| Edge, security and redirects | ||
| DNS, CDN, firewall | Cloudflare No PHI | Caching, web application firewall, bot protection. DNS stays under Kandu IT's control. |
| Redirects | Cloudflare bulk redirects | The full redirect map runs at the edge, so it survives any future rebuild. Old domains stay registered and redirecting. |
| Admin access | Single sign-on + two-factor | WordPress admin is not reachable from the public internet. Least-privilege roles, staging-only access for vendors, every login logged. |
| Qualify, booking and CRM | ||
| Qualify form | Jotform, HIPAA-enabled Gold or Enterprise plan BAA | Jotform signs a BAA on Gold and Enterprise plans. Embedded on kandu.com, one question per screen, separate SMS opt-in. Alternatives evaluated in discovery if a better fit signs a BAA. |
| Routing rules | Form logic + territory ZIP list No PHI | The territory list (not patient data) is loaded into the form, so the routing decision needs no separate service and stores nothing. |
| Scheduling | Cal.com BAA | Cal.com signs BAAs with covered entities. Booking embedded on kandu.com with prefill and tracking parameters carried through. |
| Marketing CRM | HubSpot with Sensitive Data BAA | Health answers stored in sensitive-data properties; the BAA comes through HubSpot's Sensitive Data Terms. Email and SMS workflows respect opt-in. |
| Patient pipeline | Salesforce BAA | Sales, Service and Health Cloud are covered services under Salesforce's Business Associate Addendum. |
| Integrations | BAA-covered connectors only Decide | Every hop that carries health answers (form to HubSpot, form to Salesforce, HubSpot to Salesforce) runs through a connection covered by a BAA, or carries no health data. |
| Measurement | ||
| Analytics | Google Analytics 4, one property No PHI | GA4 isn't covered by a BAA, so it only receives page views and generic conversion events. Cross-checked against CRM numbers. |
| Tags | Google Tag Manager, one container | Replaces the separate containers on each site today. |
| Consent and ad events | Consent platform + health-data-safe tag layer Decide | Consent banner and a server-side or proxy layer that strips health details before any event reaches Meta, Google or LinkedIn. Policy agreed with legal before launch. |
| Reporting | Databox | Existing dashboards repointed to the unified site and funnel. |
| Content modules | ||
| Rep counter | Nightly rep-total feed | Reads the nightly all-time rep total from Kandu's data warehouse. No patient data. |
| Locator | Kandu's Locator module | Embedded as the Find a screening page. |
| Careers | Greenhouse job board | Embedded on /careers/. |
| Video | Lightweight embeds | Videos load only when played, with captions and a pause control. |
| Quality | ||
| Accessibility | Automated checks + manual testing | WCAG 2.2 AA. Automated scans on every release, plus screen reader (VoiceOver, NVDA), keyboard-only and real-phone testing. |
| Performance | Core Web Vitals monitoring | Lab tests on every release and real-user field data after launch. Uptime monitoring with alerts. |
| Development | Git, staging, code review | All changes go through version control and staging before production. No editing code on the live site. |
Vendor BAA availability as published Nov 2026: Jotform (Gold and Enterprise plans), Cal.com HIPAA compliance page, HubSpot Sensitive Data Terms, Salesforce Business Associate Addendum covered services. Confirm current terms and plan levels during discovery.
Appendix B · Sources and notes
Search data: Google Search Console, neurolutions.com, web search, Jul 4 2025 – Nov 4 2026 (171,001 clicks; 27.0M impressions).
Site analytics: GA4, Neurolutions property, landing page report, Jul 4 2025 – Nov 4 2026 (2,411,205 sessions). Conversions = sessions × session key event rate.
Funnel and spend: Kandu Databox, 2025 and 2026 year-to-date marketing reports, through Nov 4 2026. DIQ count derived from spend ÷ cost per DIQ.
Site inventory: live XML sitemaps and navigation for all four domains, Nov 4 2026. Full redirect map provided separately (Kandu_Redirect_Map_v2.xlsx).
Brand: Kandu Brand Guidelines, October 2025. Photography, product images and illustrations from the guide.
Accessibility: Rowe FJ et al., "High incidence and prevalence of visual problems after acute stroke," PLOS ONE, 2019.
Form research: GOV.UK Design System, "Question pages"; GDS Design Notes, "One thing per page" (2015); Venture Harbour, "10 CRO Case Studies You Can Replicate."
Vendors: Jotform BAA terms; Cal.com HIPAA compliance page; HubSpot Sensitive Data; Salesforce Business Associate Addendum.