what it is
Find the thing that makes the money. Build the system that does more of it.
That is the whole job, and it is why this is a consultancy and not a software product. Every business has one thing that turns into revenue: the repeat customer, the referral, the quote that goes out the same day, the schedule that stays full. Most of an owner's week goes to everything around that thing. The work here is finding it, then building the system that lets more of it happen, so that the shop down the street is competing with you and not the other way round.
The system is usually an AI operating system. Not a product. Your own workspace, with an agent working inside it. Most AI arrives as one more tab: a chat window off to the side, disconnected from where the work actually happens, useful for about a week. An operating system is the other shape. 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 it handles depends on what your day is made of. Intake that arrives one way and gets retyped somewhere else. A quote that takes an hour because the numbers live in four places. A schedule only one person knows how to change. Notes that never make it into the record. Those are the jobs, and they are different in every business, which is why this is built rather than bought.
what stays true in every build
- it drafts, you send.
- Nothing reaches a customer, a patient, or a payer without a person approving it. That is a property of how the thing is wired, not a setting somebody has to remember to leave switched on.
- it says when it does not know.
- An agent that guesses is worse than no agent, because you have to check everything anyway. These are built to answer from what they actually have and to stop when they run out. 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. If your team can write a message, they can use it.
- 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. There is no platform in the middle that stops working when we stop working together.
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.
08:10
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. Nobody retyped anything.
11:30
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.
14:45
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. It sits there until a person reads it and presses send. If it is wrong, it is wrong in a draft.
17:00
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. That is the behavior that makes the other three worth having.
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. Two pages of hand-written HTML, no framework, no analytics, and no script in the browser beyond the one that remembers which palette you chose. Behind it, two routes: a question box that answers from the site's own published text and refuses anything else, and a trade box that writes for the visitor's own business. Both stream the answer as it is written, and the answer pages run no script.
- 26 KB for the front page, fonts self-hosted and subset, no third-party request on any page load
- the ask and for routes are the only code that runs; the pages are served as static files
- answers are grounded on the site text and capped, so it cannot invent a price or a client
- no key configured means the box offers a mail link instead of an error
- unit tests over both handlers and the Pages wiring, run on every push
- the wordmark and favicon are true outlines, so they render the same with or without the font
- zero hosting cost on the free plan; a fraction of a cent in model spend per question
- questions are logged, visitors are not
read the sourcecloudflare pagespages functions
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.
- Cloudflare Workers and D1 for the data, Twilio for the messages
- 95 unit tests across 16 files, including a 25-way race on a single claim
- 70 conformance tests across 26 files, run alongside the unit suite
- 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
- a check that fails the build if a secret is ever written into a workflow file
- destructive database work needs an explicit flag and a typed confirmation at eight of eight checks
- type checking and both suites run before a deploy is allowed to start
cloudflare workersd1twilio
the standard
Rigor you can audit, craft you can feel.
That line is on the front 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.
- deploys are gated.
- Nothing ships because a script ran. Anything destructive asks a person, in words, and waits.
- the source reads like prose.
- Somebody else has to be able to pick this up, including you, including in two years, including after we have stopped working together. Comments say why, not what.
- 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 faster than every site it competes with for the same reason.