Straight answers before you start.

Standard websites start from $799 one-time setup, with an optional $79/month care plan. You can request a free website preview before you commit.

AI automation, AI agents and custom software are scoped and quoted after a free discovery call. The cost depends on what needs to be connected and built, so we don't publish fixed prices for them. The budget ranges on our contact form only help us suggest a sensible starting point.

We plan standard websites to launch within 1–2 weeks of design approval, depending on how quickly content and feedback come back.

Automation and custom software are scheduled during scoping. Your proposal lists milestones, and you review a working version at each stage.

Usually, yes. We connect tools through their official APIs, webhooks or automation platforms such as n8n: CRMs, calendars, accounting, e-commerce, email and more.

During discovery we check what each of your tools actually allows. If something can't be connected reliably, we tell you and suggest an alternative rather than building something fragile.

Yes. Once your project is paid in full, you own your website, your content and the custom code we write for you.

Third-party tools, hosting platforms, plugins and AI services remain with their providers under their own terms. We list them in your handover documentation.

Yes. You don't need to replace your systems. We recommend starting with one high-value workflow, such as following up new leads, booking appointments or processing a common document, connected to the tools you already use.

Once that is working and you trust it, we expand step by step. You can try a simplified example in our interactive automation demo.

You get a handover walkthrough and documentation of what was built, where it runs, and how to make common changes.

Ongoing support is optional and defined in your agreement. For websites, that's the care plan. For automation and software, we agree on monitoring, fixes and improvements that fit how much help you want.

Responsibilities are written into your agreement before work starts, so it is always clear who maintains what: hosting, updates, accounts, access and data.

We build with secure defaults: least-privilege access, secrets kept out of code, validated inputs, automated tests for important logic, and human approval before sensitive actions. See how we approach security.

We do not currently hold formal security certifications such as SOC 2 or ISO 27001, and we don't claim compliance on your behalf. If your project needs them, we'll say so up front.

We don't train AI models on your data. When a build uses an AI service, we name the provider in your proposal and connect through its business API.

Before we build, we check that provider's current data-use and retention terms with you, so you know whether anything you send could be stored or used for training.

We map it before we build: every system a piece of data passes through, what is sent to an AI service, and how long each system keeps it. That map is part of your handover documentation.

Where possible, automations run in accounts you own, such as your CRM, email and cloud storage, so you can see and revoke access. Each AI step receives only the fields it needs.

Only where you decide it should. Actions such as sending messages to customers, moving money or publishing content can be set to wait for a person's approval, and we recommend that for anything hard to undo.

Every automated step is logged with what ran, when and with what result, so you can review what the system did.

Tell us at the start. Some data, such as health records, payment card data or export-controlled technical information, carries legal requirements that shape how a system must be built and hosted.

We do not currently hold formal certifications such as SOC 2 or ISO 27001. We'll tell you what we can and cannot support, and we may recommend keeping certain data out of AI steps entirely.