Questions we hear most

A small, developer-led studio. We keep a limited client roster so the engineers who build your product also support it afterwards.

It depends entirely on scope. We will give you a concrete estimate after a short discovery call, not before.

We are remote-first and based near Bournemouth in the UK, working with clients across the country.

Scoped permissions, evaluation before rollout, a rollback path, and a named owner. Agents that take real actions start with human approval on send until the process has earned trust.

Yes. Agents are grounded in your documents, APIs, and internal tools, with scoped access rather than broad, unaudited permissions.

Running costs vary with usage and the model chosen; we scope this with you up front and flag it as part of the estimate, alongside the build cost.

We build on well-known hosted model providers, Claude, OpenAI's GPT models, and Google's Gemini, plus automation platforms like n8n, Make, or Zapier for connecting your existing tools. See our models and tools guide for how we choose between them, and how we handle your data.

It reads and writes directly against your actual calendar or booking system, not a separate copy, so a slot that's just been taken by someone else is reflected immediately. Cancellations and reschedules update the same calendar, and anything the automation isn't confident about, a conflicting request, an unusual time, a VIP or repeat customer, gets routed to a person rather than booked automatically.

Yes. Reminder wording, channel (SMS, email, WhatsApp), and timing are all things we agree with you up front, and we build in a straightforward way for a customer to opt out or reply with a question, which gets routed to a person rather than ignored.

It's built to say so and hand over to a person, rather than guessing. Answers are grounded in the documents and pages you give it access to; if a question falls outside that material, or the assistant isn't confident, it says it doesn't know and routes the question on, instead of inventing a plausible-sounding answer.

It's connected to the documents and pages you point it at, so updating the source material is usually enough: there's no separate copy to maintain by hand. For anything that changes often, we agree a simple process for flagging updates so the assistant doesn't keep answering from an outdated version.

Common starting points are lead qualification, enquiry triage, invoice chasing, and appointment reminders: repetitive tasks with clear rules and a predictable shape.

Usually yes. We connect to the systems you already run (inbox, CRM, invoicing, ticketing) rather than asking you to switch tools.

Yes. Describe the workflow that takes up the most time and we will tell you honestly whether automation is the right fix, and how small a first slice could be.

Core screens and anything a customer has already loaded are built to keep working offline, with changes syncing once a connection comes back. We design around patchy connectivity rather than assuming a constant one, since that's the reality for a lot of mobile use.

Yes, it reads and writes against your real calendar or booking system rather than keeping a separate copy, so a slot taken on the app is immediately reflected everywhere else, and vice versa.

Usually yes. We scope migration from whatever system currently holds membership or subscription data as part of the project, rather than asking members to re-register from scratch.

Through established, secure payment providers: we don't store card details ourselves, and the integration is kept current as those providers update their requirements, the same approach we use for ecommerce on the website side.

By scoping it around one real, specific pain point rather than a generic do-everything app, and testing early with the staff who'll actually use it day to day. A tool that solves one thing well tends to get adopted; one trying to do everything usually doesn't.

Yes, that's usually the point: connecting to your existing CRM, stock system, or scheduling tool so staff aren't re-entering the same information in two places.

Yes, the app reads from the same product and stock data as your website rather than a separate copy, so a price change or a sold-out item updates everywhere at once.

Yes, where that's genuinely useful to the customer: order status updates and opt-in offers are both straightforward to add, scoped to what you actually want to send rather than defaulting to everything.

Your first month is paid when you sign up, which secures your build slot and is refundable until we start building. Nothing else is due until your site goes live: then it's monthly from your go-live date.

No. Your first payment is your first month, not a fee.

12 months: your signup month plus 11 months after launch. After that it's month to month, and you can cancel with 30 days' notice.

No problem, we'll chase you. If we're still waiting 30 days after you sign up, monthly billing starts, but we'll never launch your site with placeholder text.

Yes, you pay the remaining months of your first 12, then you're free to go.

Yes. Every plan includes CMS access, so you can update text, images, and blog posts without waiting on us.

Yes, at any billing cycle. Most teams start on Bronze or Silver and move up once they want more page sections, a blog, or an online shop.

No. Every plan lets you build and edit as many pages as you like yourself in the CMS. The number we quote per plan (5 on Bronze, 10 on Silver, 15 on Gold) is how many pages we build for you at launch: after that, add more whenever you want. Need a page section we haven't built yet? Extra sections from our library start from £20 each, and fully custom sections are £100 each.

Your domain and content are always yours: your domain is registered in your name, even if we look after it for you. The design and code are licensed to you while you're on a plan.

Yes. After your first 12 months you can buy your site for £250 and move it wherever you like.

Bronze includes 1 hour of changes a month, Silver 2 hours and Gold 3 hours. Unused hours roll over for up to 3 months. Extra hours are £50/hour. Critical updates and security fixes are always included and never count against your hours.

The price you see is the price you pay: no VAT added on top.

We work in focused slices and report in plain language: what was done, what's next, and anything that needs a decision. You're not buying an opaque "hours bank": you're buying visible capacity with a clear monthly summary of where the time went.

Yes, with reasonable notice. We align tier changes to billing periods rather than switching mid-month, and make sure handover notes stay current so nothing gets lost in the transition.

Large net-new products, major redesigns without a scoped phase, or work that needs a dedicated team beyond the agreed capacity. We'll say so early and propose a sensible split, a phase, a spike, or a separate quoted project, rather than quietly stretching a retainer to cover it.

Usually yes, especially Next.js, TypeScript, Strapi, and common cloud setups: the same stack we build on ourselves. If something is legacy or unusual, we'll be honest about the risk and the sensible first step.

Organic SEO typically takes up to six months to show its full effect, because search engines need time to crawl, trust and rank new work. That is why monthly SEO has a 6-month minimum, and Pro has 12 months: it is when you can really start to see the effect. Early movement is often visible sooner, and your monthly report shows it as it happens.