Stratego
Site and engine room for a fractional-CFO practice: its own publishing panel, podcast episodes kept out of the code, and a weekly article that drafts itself and waits for approval.
The problem
A fractional-CFO practice is hired for its judgment, and that judgment has to be visible before the first call. Which means publishing often. But the partners bill by the hour, and writing is the first thing that falls off the week.
What we built
The site, and the engine room behind it.
Their own panel. Articles and podcast episodes are written and ordered from there. They no longer live in the code: changing a line of copy stopped being a deploy.
A draft every week. The system writes the article and leaves it waiting. Nobody publishes anything without reading it first.
A knowledge base. You feed it their own documents — PDF, Word — and that is the material it writes from. That is why the result sounds like them and not like a template.
How it works underneath
The site, the clock that triggers the weekly draft, and the service that exposes the panel are three separate pieces. If one goes down, the others keep running.
The panel can also be driven by talking to Claude, without opening a browser: publishing, fixing or reviewing a draft is done by asking.
Forms land straight in the CRM the firm already used. There is no second inbox someone has to remember to check.