Discovery & Consulting
The brief, the operations, and the integrations in writing, before anything is designed or built. And for a platform you already run, a clear view of what to keep, what to consolidate, and what to connect.
Most WordPress projects go wrong before anything is designed.
Discovery prevents that. Before design starts, we put the brief in writing: what the organisation does, who the platform serves, which operations it needs to support, which tools it must connect to, and what success looks like. Everything that follows is shaped by what we learn here.
Consulting applies the same thinking to a platform you already run. We review how the platform, the processes around it, and the tools it connects to fit together, then recommend what to consolidate onto WordPress, what to integrate, and what to leave as it is. Consolidate where it makes sense. Integrate where it does not.
Who this is for
- Organisations planning a new platform or a rebuild
- Teams whose brief is still taking shape
- Organisations running several disconnected tools
- Platforms that have grown without a plan
The brief is vague, the scope is misunderstood, or the client and the team have different pictures of what is being built. By the time that becomes visible, there is work to redo and expectations to reset.
A brief everyone has signed off. No interpretation gaps. No surprises mid-project. Design, build, and launch all follow the same written picture of what is being built.
What discovery and consulting cover.
- 01
Introductory call
Understanding the project, the organisation, and the brief.
- 02
Discovery questionnaire
The detail we need before designing anything.
- 03
Operations and integrations review
The processes and tools the platform needs to support.
- 04
Scope agreement
Deliverables, timeline, and investment confirmed in writing.
- 05
Platform and tool review
For an existing platform: what it runs today, where the data lives, and which standalone tools could move onto WordPress.
- 06
Recommendations and next steps
Written recommendations on what to consolidate, what to integrate, and what to do first.
Discovery is the first of six phases in every WPFlat project.
See how a project runsDiscovery is where every project starts.
Six phases. Each one exists because skipping it produces a worse result.
- 01
Discovery
The brief, the operations, and the integrations in writing.
- 02
Design
Designed and approved before development begins.
- 03
Build
Built from the approved design on staging.
- 04
Review
Written sign-off before anything goes live.
- 05
Launch
A managed technical event, not a button click.
- 06
After Launch
The same team stays as your technical partner.
Every project is different, and the process adapts to the scope.
See our full processFrequently asked questions
Can discovery run on its own?
Yes. Discovery can be the first phase of a project with us, or a standalone engagement for organisations that want a clear, written brief before they commit to a build.
We already have a brief. Do we still need discovery?
Usually a shorter one. We review your brief with you, fill the gaps on operations and integrations, and confirm the scope in writing so both sides work from the same picture.
Do you only advise on platforms you built?
No. We review any WordPress platform, and platforms on other systems that are considering a move to WordPress.
What do we have at the end?
A brief everyone has signed off, with deliverables, timeline, and investment confirmed in writing. For consulting work, written recommendations and a clear order of next steps.
Tell us what you need WordPress to do.
A new website, a redesign, a client portal, a booking system, or a move from another platform. Tell us what you need and we will tell you how WordPress can carry it.
What happens next
- 01Introductory callUnderstanding the project, the organisation, and the brief.
- 02Discovery questionnaireThe detail we need before designing anything.
- 03Scope agreementDeliverables, timeline, and investment confirmed in writing.