The business context
OAF Construction Corp. is a Calgary construction business working on basement developments, legal secondary suites, garage construction and tenant improvements. These are considered purchases: the homeowner or property owner needs to understand the service and describe the project before a useful conversation can begin.
OAF Construction is a client of Apex Radius. This account describes the project scope and does not claim a measured improvement in rankings, revenue or lead volume.
Connect information to the enquiry
The website work organizes the business around the services people are considering. A visitor should be able to find the relevant service, understand the kind of project it covers, and reach the appropriate enquiry path.
The information architecture connects:
- Service pages for the core construction work, giving each service enough space to explain the customer need and likely scope.
- Local and supporting content around Calgary projects, property questions and the planning journey.
- Contact and project enquiry paths that collect useful context for the next conversation.
- Internal links that connect related services and information instead of leaving each page as an isolated destination.
The purpose is practical: help a visitor move from a broad idea to a clearer description of the work they want to discuss.
Plan what happens after the click
An enquiry form is a handoff into the business. Its usefulness depends on what information it collects, where that information goes and who follows up.
OAF’s wider development workspace includes website forms, voice and intake work through Maya, and chatbot workflows. These parts bring enquiry context and response planning into the same operating picture. A workflow still needs agreed consent, routing, human review and fallback responsibilities before it is used with customers.
The lesson carries into other service businesses: plan the response alongside the page that generates the enquiry. The information a customer reads and the questions they are asked should support the same next step.
Keep the promise consistent
Construction enquiries bring questions about scope, timing, approvals and price. The website should explain the service without committing the business to a particular property’s feasibility or a quote before assessment.
That distinction shapes the content and the enquiry journey. General service information helps the visitor prepare; project-specific commitments belong in the assessment and written agreement. Clear language at both stages makes the handoff easier to understand.
What this work illustrates
The project brings content structure, website development and enquiry planning into one customer journey. It shows how the individual parts can be scoped together:
- Understand the services and the decisions visitors need to make.
- Give important services their own useful pages.
- Connect supporting information with a relevant next action.
- Collect enquiry context the business can use.
- Plan response, review and handoff responsibilities.
The public website can be inspected separately from the operating workflows. Current service availability and project terms are confirmed directly with OAF.