Before you start a project

A few sentences are enough to start. Tell us what you want to build or improve, who it is for and which tools you use. We’ll work through the details with you before preparing a proposal.

The cost depends on what we build, the systems it connects to, expected usage and the support you need. We agree the scope and provide a proposal before development begins.

Timing depends on the scope, integrations and testing needed. We agree a schedule once those requirements are clear. If you have a launch date in mind, include it in your enquiry so we can assess what is feasible.

We check whether your tools can connect and what access they allow. Then we explain what can be automated and any limits before you commit to a build.

Yes. We build bots for customer enquiries, sales and support. We can also connect WhatsApp to customer records, online stores, booking systems and internal tools, subject to what those systems support. We agree when the bot should hand a conversation to your team.

Yes. Logo design, graphic design, copywriting, hosting, bulk SMS, bulk email and private email servers can be separate projects or part of a larger build. We agree the deliverables and any ongoing service or sending costs in the proposal.

We agree which routine tasks can run automatically and which decisions need a person. Your team can handle approvals, exceptions and conversations that need judgement or care.

AI can give incorrect answers. We limit what it can do, test realistic scenarios and define when a person needs to check its work or take over. Those checks are part of the project scope.

Chat content and technical metadata may be stored to operate, secure, and improve the service, and messages are processed by an AI provider. Do not submit passwords, payment details, or sensitive personal information. Read our Privacy notice for details.

Your proposal sets out the handover and any ongoing support or monitoring. We plan this around how your team will use and manage the product.