Soko Healthcare — a recruiting website that is also the lead engine

Soko Healthcare places nurses directly onto the staff of nursing homes, assisted living communities, home health agencies and hospitals in South Florida, and it is founded and run by a registered nurse. The firm had a live site and real demand. It did not yet have the system that turns a facility from "found the site" into a signed agreement, or a nurse from "saw a job" into a placement.

The original site was a page builder export with a third-party form. A facility that started an inquiry and stopped halfway was gone. A completed inquiry arrived as an email with no alert, no score and no next step. The copy talked about temporary staffing when the model is direct hire only. Leads lived in a spreadsheet by hand.

Every facility conversation depended on the founder noticing an email. Nothing local could rank, because the site had no location or specialty pages and no structured data. And a recruiting business with one founder cannot afford a lead that waits a day.

The smallest system that moves money is intake, speed to lead and a system of record, in that order. Location pages, the blog and lead magnets come after the forms and the discovery-call routine are proven. We built in that order, and we kept the founder's own spreadsheet as the system of record rather than selling a CRM before the first placements.

A new home on Cloudflare Pages. The site moved off its original builder to a Git-deployed static build with security headers, a robots file that welcomes search and AI crawlers, llms.txt, and Organization, Person, Service, FAQ and breadcrumb structured data. Dev and production environments, CI checks on every pull request, and a domain cutover that left the firm's Google Workspace mail untouched.

Two-sided intake. A three-step facility form and a four-step nurse form that open with picklist questions and collect contact details on step two, where the lead is saved. A half-finished inquiry still gets a call. Nurses attach a résumé and up to three license or certification copies; the founder receives the application as a PDF with every upload, also filed in Drive. A save-for-later link emails the applicant back to where they stopped. Turnstile keeps the bots out, and the forms survive slow or failed uploads.

Speed to lead and scoring. Every lead is scored out of 15 on eight signals and landed as hot, warm or cool in the subject line, the spreadsheet and GA4. A facility inquiry texts and emails the founder and sends the facility a booking link inside a minute. Partial forms get a one-hour follow-up; anything untouched escalates after a day. A WhatsApp line sits on every page.

The spreadsheet as a system of record. Leads write straight into the founder's own facility and nurse tabs using her column names. Existing rows are matched by email, phone or facility name and only empty cells are filled, with a dated note. Identical resubmits are ignored; changed ones are merged. A "Tidy the workbook" menu normalized her existing data without guessing at anything ambiguous.

Found in search and AI search. A locations hub, county pages for Miami-Dade, Broward and Palm Beach, and 51 city pages, each built from sourced public data: licensed facilities by type and bed count, CMS staffing ratings and turnover, nurse pay percentiles, nurses licensed in the county, and the Florida staffing rules with citations. Thirty specialty pages for nurse niches. A market-data pipeline refreshes the figures quarterly and stamps every page with its as-of date. IndexNow submits the sitemap on every release.

The sales operating system. A seventeen-page sales hub for the firm's first business-development hire: the direct-hire model in plain English, a named selling method, stakeholder maps, a 10-day outreach plan with email templates, call scripts by role, objection handling, and the rule set for what can and cannot be said before terms are final.

Everything ships from the repository: feature branch, pull request to dev with a preview, release to main. Runbooks for Cloudflare, the forms integration and content editing live beside the code, and a Confluence space holds the build status, the decisions and the open items in one place. The firm owns its accounts and its data; OpsPal is never in front of a facility or a nurse.

The Cloudflare build is live on sokohealthcare.com, the forms are connected, and the location and specialty pages are indexed. What is not yet claimed on the site is deliberate: fees, guarantees and outcome numbers wait until the firm's terms are final and the first placements are in. The next evolution is measurement, which city and specialty pages earn impressions and inquiries, and the first published resources post.