The front page is short on purpose. This one is for the reader who wants to know what an AI operating system actually is before writing to a stranger about one.
what it is
Find the thing that makes the money. Build the system that does more of it.
The system is usually an AI operating system. Not a product. Your own workspace, with an agent working inside it. It lives in a Slack workspace set up for your business, with your people, your channels, and your vocabulary in it. You write to it the way you would write to a capable new hire who has already read everything you have. It reads the thread, does the work, and puts the result back where you and your staff can see it.
what stays true in every build
it drafts, you send.
Nothing reaches a customer, a patient, or a payer without a person approving it.
it says when it does not know.
An agent that guesses is worse than no agent, because you have to check everything anyway. The ask box at the bottom of this page is the same rule in miniature: it answers from this site or it tells you it cannot.
it works where you already work.
No new application for your staff to learn, no second place to check.
it is yours the whole time.
Every license and every account is in your company name from day one, billed to you by the vendors at their price.
a day with it
A small clinic, as an example of the shape. None of this is a promise about your business; it is what the pieces look like when they are assembled.
the overnight pile. Referrals, portal messages, and voicemail transcripts arrived overnight in four different places. They are already sorted into one channel, each one summarized in a line, flagged where something is missing.
the question. A staff member asks, in the channel, what the prior authorization policy is for a given payer. The answer comes back with the paragraph it came from and the date that document was last changed, so she can see for herself rather than take its word.
the draft. A letter that used to take twenty minutes comes back in thirty seconds, in the practice’s own language, with the patient details filled in. If it is wrong, it is wrong in a draft.
the thing it would not do. Asked for something the record does not support, it says so and stops instead of producing a confident paragraph.
built here
Client engagements are confidential, so what is shown here is work built in the open, where you can read every line rather than take a claim on faith. Both run on the same stack the client systems run on.
franzfloyd.com
live · the site you are reading
A site that had to argue for restraint by being restrained. Four pages of hand-written HTML, no framework, no analytics. The only script in the browser turns the cards on the front page into a wheel; no other page runs one. Behind it, four routes: a question box that answers from the site’s own published text and refuses anything else, a trade box that writes for the visitor’s own business and keeps the good answers in a library, a page that lists them, and the short form that carries a lead straight to the owner.
under 59 KB for the front page, its stylesheet and its one script, fonts self-hosted and subset, no third-party request on any page load
the ask, for, hello, and trades routes are the only code that runs; every other page is a static file
answers are grounded on the site text and capped, so it cannot invent a price or a client
unit tests over every handler and the Pages wiring, run on every push
questions are logged, visitors are not
read the sourcecloudflare pagespages functionscounts as of oct 2026
motorcade
built and tested · awaiting cutover
A dispatch system that takes work in over SMS and hands it out, written for a pilot on the same serverless stack. The interesting part is not the messaging, it is what happens when two people claim the same job in the same instant, and what the system refuses to do when it is not fully configured.
95 unit tests across 16 files, including a 25-way race on a single claim
the model gateway is empty until it is configured, and the code fails closed rather than guessing
continuous integration cannot deploy; that gate is a test of its own
cloudflare workersd1twiliocounts as of oct 2026
the standard
Rigor you can audit, craft you can feel.
That line is on the about page, under the two grandfathers it came from. Here is what it means in practice, and both systems above are the evidence rather than the claim.
tests come first.
Not as a finishing touch. The hard cases get written down as tests before the code that handles them, which is why a 25-way race on one record is a line in a suite rather than a phone call at midnight.
it fails closed.
A system that is missing a credential should refuse to act, not act on a guess. Both systems above stop and say so, and each has a test proving it stops.
small is a feature.
Every dependency is a thing that can break, get abandoned, or start charging. The front page of this site has none at all, and it is fast for the same reason.
the other work
01
owner’s-side strategy.
The thinking an owner needs before the architects, agencies, and vendors start billing: concept master plans, proposal scoring, phasing tied to revenue. Fixed fees, itemized hours, numbers you can audit.
02
healthcare ai.
Twenty years in cardiac electrophysiology, device clinics, and physician relationships, now applied to AI that has to survive clinicians, compliance, and reality. Translation between the algorithm and the exam room is the job.
ask
answers come from this site only. the question is kept for 180 days; you are not.