Site agent
One agent, one job, done well. A single-purpose agent embedded on your site — answers questions, qualifies leads, routes when it should. The cleanest way to put a real conversation on a landing page.
Custom AI agents with your brand voice, in your languages, trained on your knowledge. Built in weeks, owned by you. The same studio that designs the site writes the prompt.
Generic chatbot, the same script as the next ten thousand sites. Doesn't know the company, routes everyone to a form, brand voice set to SaaS default. The prompt and the data aren't really yours.
Six months of discovery before anything ships. Strategy decks before working software. Built by a team that won't be there to maintain it. Lock-in by design, dressed up as enterprise rigor.
System prompt with your brand voice, retrieval over your real documents, multilingual from day one. Shipped in weeks. Same hands from prompt to launch. Full ownership of prompt and data — no lock-in.
One agent, one job, done well. A single-purpose agent embedded on your site — answers questions, qualifies leads, routes when it should. The cleanest way to put a real conversation on a landing page.
Trained on what your company actually knows. Retrieval over your real documents — PDFs, internal pages, product specs. Answers from source, not from a generic LLM guess. The format most corporate clients land on.
One voice across web, WhatsApp and email. Same agent, multiple surfaces — the conversation that starts on your site continues on WhatsApp without losing context. For teams that already live where their clients write.
An agent that does the work, not just answers. Intake, triage, scheduling, structured handoff — automated end to end. For teams where the bottleneck is operational, not informational.
The real costs of keeping it running — hosting, model inference, monthly tuning. Declared up front, no surprises.
What does the agent need to solve. What it shouldn't touch. Sources of knowledge — documents, site, internal pages. System prompt v1 drafted by the end of the week.
Build, internal testing, retrieval setup if applicable. The agent starts holding conversations with us before it holds them with anyone else.
Real-case testing with the client. Tone calibration, edge cases, refusals. The agent learns what to say, and what to stop saying.
Deploy on site, handoff of prompts, logs and credentials. The client team learns to read conversations and where to ask for tuning.
Prompts get sharper with real use. Monthly or biweekly tuning, depending on tier. The agent gets better at sounding like the company over time.
The agent on this site. Built with the same prompt, the same voice and the same retrieval that we ship to clients. Live and learning. Talk to it →
Bilingual agent for trial bookings, schedule and pricing questions, complex requests routed to the team.
Visitor-facing agent for programming, ticketing and accessibility questions. Multilingual from day one.
Because no. They have to be trained, tamed. A custom agent knows your business, carries your voice and your way of communicating — you notice it fast.
We sign a DPA before kickoff and everything is stored in a secure place.
Yours, and we hand everything over at the end. If you later want to work with someone else, you take it with you and you've got a head start.
Depends on what for. Anthropic, OpenAI, open models — chosen by cost, latency, and how well it handles the language or the case. There's no best one; there's a best one for this.
It can happen, but it gets resolved — that's what training is for. Logs, refusal rules for sensitive topics, and human handoff when it can't answer. Monthly tuning at minimum, that's what the retainer is for.
Details up above.
The fastest way to know if this fits is to talk to the agent on this site. It was built with the same prompt and the same voice we ship to clients.
Next opening: Q3 2026 · 3 founding spots.