It depends on how big the site is and how fast content and feedback come back to us, so we give you a date on the kickoff call rather than a number on a pricing page. However long it runs, we work in short slices and you see a running build at the end of each one — so if something looks wrong, you find out early enough to change it.

Only from your content graph — the pages, docs and data you've explicitly connected. It quotes the source and the last-updated date on every answer. When the graph can't support an answer, it says so and offers a handoff instead of guessing.

Each branch gets an automated adversarial pass before it can merge: prompt injection, context leakage, auth bypass, schema drift. Findings block the deploy and land in your console with a reproduction. Quarterly, our security researchers do it by hand as well.

You do. The design, the words, the images and the domain are yours and stay yours, and your content is yours to export whenever you ask for it. The code underneath is ours — we build on our own stack and we deploy and run every site we make, so there is no repository to maintain and no server for you to keep alive.

Usually. We read from most headless CMSes, Notion, Contentful, Sanity and plain Markdown repositories. If your content lives somewhere stranger, we'll tell you in the scoping call whether it's a connector or a migration.

Support is included for the window in your package — 30 days on Whistle, 90 on Orchestra — covering fixes, small changes and retraining the assistant as your content shifts. After that the site carries on running on our infrastructure and nothing changes for your visitors. Most clients come back for a fixed-price update when they need one; a few put us on a small monthly retainer, but nothing obliges you to.