NICOLAS DESRANLEAU.

Nicolas Desranleau | Websites & Strategy

I build websites. I put out fires. I wear a lot of hats.

I'm Nicolas. I design websites, build them, and set up the systems that keep a whole network of them running, in-house, start to finish.

  • 75+Venue websites
    I look after
  • 86Domains
    managed
  • 3 mo.To launch a venue site,
    down from 5 to 7
  • +43%Corporate site enquiries,
    with half the pages

Selected work / 01

About / 02

A leader who
still builds.

I lead web at scale: turning complexity into clarity, and strategy into results you can measure. I build teams, improve systems, and get the details right.

Learn more about me

NICOLAS
DESRANLEAU.

© 2026 Nicolas DesranleauPrivacy PolicySt. Petersburg, Florida
NICOLAS DESRANLEAU.
All work

01 / Operations

Building a
web operation.

From zero to a scalable, in-house web operation for a network of 75+ venue websites.

Web operationsStrategyDelivery
Homepage design
Homepage design for GPT Sportsplex in Gulfport, Mississippi, an outdoor sports complex
GPT Sportsplex. Homepage design, launched 2026.

Homepage design, built in-house on one standard.

The challenge

Scale without compromise.

A growing network of venue websites meant more sites, more stakeholders and higher expectations, without the resources to scale the team.

The approach

Build for scale.

I designed and implemented the systems, processes and infrastructure to manage 75+ websites across 86 domains, with one standard for every launch.

  • In-house delivery
  • One written standard
  • Hosting and security owned
  • Faster build times
75+Venue websites
86Domains
~3 mo.Build timeline

The work / 01

How it moved in-house

Four decisions,
in order.

The case, the stack, the standard, and where AI earns its place. Every launch since has followed the same steps.

  1. Made the case

    Showed leadership that building in-house would be faster and cost the venues less. It was, and it did.

  2. Built a venue-specific stack

    One WordPress and Elementor foundation made for sports and recreation venues, so no site starts from zero.

  3. Set the standard

    Intake, scoping, QA and ticketing, written down. A small team runs a large network because the steps are the same every time.

  4. AI in the planning

    Every site starts as a sitemap drafted with AI from the company's own documents, so the plan fits what that venue is for. In QA, AI checks alt text, heading order and schema before a person signs off. Planning and QA, not the builds.

A venue site took 5 to 7 months. Now it takes about 3.

The impact / 02

A stronger,
more scalable
foundation.

The in-house model gave the business more control, faster delivery and a web function it earns from instead of pays for.

  • 75+ venue websites supported across 86 domains
  • Build time down from 5 to 7 months to about 3
  • One security standard across the network
  • A profit center where there was a cost center

"Most of my job is making the next site faster. The rest is making this one good."

Operating principle

Next project

02 /Corporate website redesign

View case study

Let's connect

Big-picture thinking.
Hands-on execution.

Get in touch

NICOLAS
DESRANLEAU.

© 2026 Nicolas DesranleauPrivacy PolicySt. Petersburg, Florida
NICOLAS DESRANLEAU.
All work

02 / Transformation

The corporate
site, rebuilt.

One owner, one agency, five groups to sign off. I owned the audit, the navigation, the content and launch day. An agency built it.

StrategyNavigation and UXContentDelivery
Services page
The Financial Feasibility Study page on the new corporate site
The corporate site. A services page, launched April 2026.
Contact page
The contact page on the new corporate site
The corporate site. Contact page, launched April 2026.
Homepage
The Sports Facilities Companies corporate homepage, launched April 2026
The corporate site. Homepage, launched April 2026.

Swipe for the other pages. Screenshots of the live site at launch.

The challenge

A site that grew a page at a time.

116 pages, by different hands, over years. Services no longer sold, the same offer explained twice, and few calls to action where a visitor needed one.

The approach

Start from who's looking.

Audit every page, rebuild the top level around three kinds of visitor, write the content, and take each round to five groups in order.

  • Full page audit: keep, merge or cut
  • Three doors in, one per kind of visitor
  • Every redirect mapped before launch
  • Five groups signed off, one owner

The impact

  • +43%Form submissions
  • 11658Pages
  • 5Groups signed off

What was in the way / 01

A page at a time,
by different hands.

You could read the whole site and still not be sure what the company did.

  1. Services the company no longer sold

  2. The same offer explained twice

    Once by service, once again by type of client.

  3. Broken UX in places, and a UI that looked its age

  4. Few calls to action

    Rarely where a visitor needed one.

Navigation and UX / 02

Process

Built around
who's looking.

The old site was organised around what the company does, so it explained the same offer twice and left the visitor to work out which version was theirs.

I started from the other end: who lands on this site, and what do they already know when they arrive? Three kinds of visitor, three questions. So the top level got three doors, and each one opens onto a page written for the person who chose it.

Door 1 / Industries

"How do you work with people like me?"

Who
Decision makers choosing by the world they work in: a city, a college, a developer.
Where it leads
One page per industry, before they read a word about services.
134Industry pages, merged

Door 2 / Facilities

"What does it take to plan, build and run one of these?"

Who
Visitors with a facility type in mind.
Where it leads
The page for that kind of facility: development, management and operations.
1Page per facility type

Door 3 / Services

"I need a feasibility study. Where is it?"

Who
Visitors who already know what they need.
Where it leads
Straight to the service, grouped under Advisory, Development and Management.
2411Service pages, merged

Each thing is explained once, on the page built for it. The old "Clients" section, 21 pages that re-explained the services by type of buyer and drew almost nobody, went entirely. A visitor who knows what they need goes straight to it; one who doesn't gets a page that speaks to their world first, with a call to action where they'd want one.

How it ran / 03

One owner,
one agency,
five groups.

The agency built it. I owned the plan, the content and the calls, and kept every group aligned until the CEO set a launch date.

More than one round per group. A change asked for in round three never undid something agreed in round one.

  1. Content team

    The words, page by page.

  2. Design team

    Assets, brand, copy review.

  3. Sales team

    Does the site sell what they sell?

  4. The partners

    Review and sign-off.

  5. The CEO

    Final approval and a launch date.

What I did / 04

01

Cut what no longer earned its place

Problem
116 pages, grown by different hands. Services no longer sold. Pages that said what another page already said.
Decision
The agency's SEO audit scored every URL on visits, backlinks and keywords. I made the keep, merge or cut call on each one. A page almost nobody visited, with years of links pointing at it, stayed.
Impact
116 to 58. Half the pages, each with one job.
02

Mapped every redirect before launch

Problem
Half the URLs were about to change, and years of rankings and links sat on the old ones.
Decision
Every URL that moved got a destination before launch: merged, retired, renamed or moved.
Impact
Every old address still lands somewhere useful, and the links it had earned came with it.
03

Wrote the content, ran the rounds

Problem
Five groups, five ideas of what the site should say, and an agency that needed one answer.
Decision
I wrote the new content, steered the design rounds with the agency, then took each round to every group, in order.
Impact
One version of the site, which every group had seen before the CEO did.
04

Moved the blog, tidied the backend

Problem
862 posts, and a backend that had grown the same way the site had.
Decision
Every post moved under one /blog/ address, each one redirected. Files organised by type.
Impact
The next person needs no guide.
05

Measured it after launch

Problem
A site everyone signed off on is not the same as a site that works.
Decision
Kept HubSpot on the forms, so enquiries compare like for like. Added Microsoft Clarity after launch to see how visitors use the pages.
Impact
The results below, and a way to keep checking them.
Old URLNew URLAction
/industries/government-services//industries/economic-development/Merged
/industries/private-developers//industries/real-estate-development/Merged
/clients/financial-institutions/forecast//sf_services/advisory/financial-forecasting-pro-forma/Retired
/sf_services/venue-planning//sf_services/development/sports-facility-architect-selection/Renamed
/what-is-facility-optimization//sf_services/management/sports-facility-optimization/Moved
/11-benefits-of-a-community-recreation-center//blog/11-benefits-of-a-community-recreation-center/Moved
Part of the redirect map. One row per old URL, one destination each. 862 blog posts moved under /blog/ the same way.

Before and after / 05

Same company,
same address.

Old and new. The homepage, then a services page with its call to action where a visitor needs it.

The homepage

Before
Old site · Homepage
The old corporate homepage, before the redesign
Before. A rotating slider, the message changing every few seconds.
After
New site · Homepage
The new corporate homepage, launched April 2026
After. Three doors in the navigation, one message.

A services page

Before
Old site · Feasibility study
A services page on the old corporate site
Before. The first call to action sat about 1,400 pixels down.
After
New site · Feasibility study
The same service on the new corporate site, with its call to action
After. The same service, with the call to action where a visitor needs it.

What changed / 06

Enquiries are what the navigation and the calls to action were built to move. A relaunch changes a lot at once, so no single change gets the credit. The number moved all the same.

Visit the live site
+43%Form submissions, year on year
11658Pages, half the old site
5Groups signed off before launch

What I'd keep doing / 07

  1. Audit before anything is designed

    Nobody argues about the design of a page that no longer exists.

  2. Start from who's looking, not what you sell

    Ask who arrives and what they already know. The doors draw themselves.

  3. Map the redirects early

    Launch day was a checklist, not a scramble.

  4. Put sales in the review loop

    A corporate site sells what the sales team sells. Without them, it is guessing.

  5. One owner, start to finish

    Delegating the build is fine. Delegating the ownership is not.

  6. Leave the backend better than you found it

    Nobody sees it on launch day. Everyone depends on it after.

Related work