“We’re not getting enough leads.”

No. A machine drafts the reply and a person sends it. The agent writes from your own prices, availability and past replies, so you’re editing rather than starting from nothing, and nothing leaves until someone in your business has read it. Correcting a draft takes less time than writing one, and each correction tells us what to tighten in the instructions the agent follows. If you later decide something simple can go out on its own, such as a booking confirmation, that’s your call, agreed in writing, and you can reverse it.

Not if it works and your team actually uses it. We can connect the agent to it through an MCP server - a connector that lets the AI read and update your CRM - and build the reply, chase and tracking around what you already have. The same kind of connector can reach your inbox, calendar and website forms, which is the start of a business brain: one memory of how your business works that staff and AI both read. If your CRM is really a spreadsheet with ambitions, we’ll say so and build you a proper pipeline instead.

On the free review call we name one thing we could ship in two weeks and roughly what it’s worth to you. We start with whichever leak is costing you most, because that’s what pays for the rest. If you go ahead, the proposal has a fixed price, a fixed scope and a fixed timeline. While we build, you get a written update every week and a demo every two weeks, so there’s never a month where you wonder what we’re doing. We’d rather show you a working system than a slide about one.

It depends on what you need, so there’s no price list. After the review call we quote a fixed price for a fixed scope, with the value written beside it: leads answered, hours saved, work won. If the numbers don’t justify the build, we’ll tell you. The review itself is a 20 to 30 minute call, and you get a plain-English summary by email within one working day: three fixes, in order, with a rough value on each. One question on that call is what happens to a lead in its first hour, so it’s worth timing yours before we speak.

In your accounts, not ours. We build on Cloudflare, the network your site is served from, which keeps hosting bills near zero, and at handover you get the code repository and every login. Notes, the activity log and the history of every enquiry sit in the same system, so nothing important lives in someone’s personal inbox. Game and Flames’ system also runs a nightly backup and tests that it restores. If we ever part ways, everything stays exactly where it is, because it was never ours to take.