MESUR

I started with the whole experience. The audit covered messaging, UX and structure, lead capture, content and credibility, and technical SEO, then ranked 23 findings by impact and effort. Ten were high priority.

That changed how I framed the work. MESUR already had the enterprise story. I made it clearer, more specific and much easier to see.

MESUR’s services are connected by nature. A site gets captured, the data is processed, and that becomes whatever the project actually needs: point clouds, drawings, BIM models, digital twins or topographic outputs. I brought the service story together around how the work actually happens: capture, process, deliver.

The consolidated Services page makes the full workflow legible while still giving technical teams the detail they need. The Retail / Multi-Site page pulls MESUR’s strongest enterprise use case out of the case-study archive and gives it somewhere to live properly.

One of the most useful things the client told me was how enterprise sales actually happen at MESUR. It is relationship-led B2B, so the site often takes over once somebody already knows the company exists and comes looking for evidence.

That made the retail work much more specific. Distributed retail teams were already using MESUR’s captures to avoid unnecessary travel, let design teams work remotely with site information, present projects internally and support work across multiple locations. The page needed to make that operating model concrete.

The proof was already in MESUR’s own work. Their case studies contained facts such as 17,000 sq m scanned, 500 scan stations, Revit workflows and BOMA 2020 compliance. I pulled those details forward and used them as the credibility layer instead of reaching for generic enterprise language.

I designed the conversion model around different levels of intent. Someone comparing a technical deliverable needs a different next step from someone considering a multi-site program, so I added a middle layer between reading and requesting a quote.

That layer gives buyers real next steps: explore the retail program, inspect proof, request a sample deliverable, discuss a multi-site rollout, or move into a consultation when there is enough intent. The overall path became much clearer: understand capability, review proof, explore the relevant program, then start the conversation.

The intake flow follows the same logic, collecting the project context MESUR needs to understand what kind of conversation comes next. Small things mattered too: visible form labels, proper consent language, bilingual QA, and separating technology partners from actual client proof.