Frequently asked

Look for repeated manual work: copying enquiries between tools, chasing booking details, unclear team handoffs or missed follow-ups. We review your current workflow and identify whether a small improvement or a connected system is the better fit.

Yes. Website strategy, design and development remain part of our offer. A standalone website can be the right solution, and we can discuss connected features later if your business needs them.

We begin by mapping your client journey and team workflow. We agree the scope, design the experience, build the solution and test the agreed journeys before launch. Handover, staff onboarding and support responsibilities are defined in the proposal.

Timing depends on the features, integrations, content readiness and review process. Your proposal sets out the stages and expected schedule. We do not apply a single delivery promise to every website or system.

It can answer routine questions using approved business information, collect enquiry details and guide people towards a booking or staff handoff. The agreed scope defines its limits. Sensitive questions, exceptions and decisions that need judgment are passed to a person.

We assess the tools you already use and the connections they allow. Automated WhatsApp messaging requires an approved API connection and account setup; a click-to-chat link alone cannot read or reply to messages. Integration requirements, approvals and any provider fees are explained before you commit.

Yes, role-based access can be included so people see and manage the information needed for their responsibilities. We agree the permission rules with you and test them as part of the project. Access controls reduce risk but do not make any system risk-free.

Pricing depends on the agreed features, complexity, integrations, onboarding and support. Your proposal separates project work from recurring items such as hosting, AI usage, messaging providers and maintenance where applicable. We do not assume that every project needs the same subscription or support plan.

Not necessarily. We first review what works and where the gaps are. The solution may improve your current website, connect supported tools or replace one troublesome workflow. Any data transfer or changeover work is scoped separately.

We plan testing and handover around the agreed workflows, including the tasks your team needs to perform. Staff onboarding and launch support can be included in the scope. Your team reviews the solution before it becomes part of daily operations.

Ownership, account access, data handling, licensing and handover are documented in your agreement. We clarify how your business can access and export its data, along with any third-party terms. Ownership is not a promise of zero security risk or independence from every provider.

Support is agreed before launch. It may include maintenance, issue handling, monitoring and prioritized improvements. Response expectations, ongoing fees and the difference between fixes and new features are set out clearly in the support scope.

Select ‘Start with strategy’ and tell us what is slowing your business down in the project brief. You can use the goals field to explain enquiry handling, bookings, team coordination or follow-up needs. We will review your priorities and discuss an appropriate starting point.