01
Initial consultation
We discuss the business, current situation, project goals, timing and what success should look like in practical terms.
Discovery is where we identify what customers need, how your operation works and which technology will create genuine value. It prevents a polished website from solving the wrong problem.
The depth of each area depends on project scope, but every decision connects back to the customer journey and the way the business needs to operate.
We discuss the business, current situation, project goals, timing and what success should look like in practical terms.
We examine services, audiences, internal responsibilities, operational constraints and the problems the project must solve.
We map how people discover, compare, enquire, book, pay, receive confirmation and return.
We assess relevant market patterns, common expectations and opportunities to communicate more clearly—without copying competitors.
We define site hierarchy, priority pages, content needs, calls to action and the information required at each decision point.
We consider WordPress architecture, hosting, forms, integrations, data flow, accessibility, SEO and future maintainability.
We plan service selection, availability, customer details, staff notifications, confirmation, cancellation and rescheduling where required.
We identify when payment is taken, what the customer sees, how success or failure is handled and how refunds or records are managed.
We look for repetitive hand-offs that can be made more reliable through CRM, notifications, task creation and connected tools.
The questionnaire gives us the essential context before deeper discussion, making consultation time more focused and productive.
You do not need to know which plugins or integrations to use. The most useful input is a clear description of what happens today, where customers struggle and what your team repeatedly handles manually.
Discovery turns broad ideas into documented decisions that can guide scope, design and development.
Goals, audiences, services, constraints and priority outcomes.
The key paths visitors and staff need the system to support.
A logical page hierarchy with clear content responsibilities.
Forms, bookings, payments, CRM and automation requirements.
Recommended platform, integrations and architecture.
Deliverables, assumptions, timing and investment for approval.
Yes, although its depth varies. Even a smaller website needs enough discovery to confirm goals, content, responsibilities and technical needs.
It depends on scope, stakeholder availability and the complexity of the workflows. The expected timeframe is explained before the process begins.
No. Describe the business problem and current process. We translate that information into a suitable technical plan.
Yes, where relevant. The purpose is to understand customer expectations and differentiation opportunities—not to reproduce another company’s design.
We assess the effect on scope, cost, timing and quality. Small refinements may fit the plan; material additions are documented as a change.
Where the project is suitable and sufficiently defined, discovery leads to a written proposal. If there is a significant mismatch, we will explain it honestly.
Share your goals, workflows and challenges. We’ll identify what the website genuinely needs to do.