Work / Community and public sector / Fredericksburg Symphony Orchestra
From Base44 to WordPress: how a Virginia orchestra turned an AI-built prototype into a live site in just over two weeks
The Fredericksburg Symphony Orchestra had a new site prototyped in Base44, an AI app builder, but the prototype wasn’t ready to launch as the orchestra’s public site. We rebuilt it in native WordPress, with a real page for every section and content staff can edit, in time for the new season. From August 1 to October 17, the site had two-thirds more visitors than the old site had on the same dates in 2025.
Case file
Measured
4,185
visitors from August 1 to October 17, two-thirds more than the same dates in 2025
Industry
Symphony orchestra
Where
Fredericksburg, Virginia
Built
WordPress, from a Base44 prototype
Launched
End of July 2026
Kickoff
Launch
78 days measured
The orchestra’s Google Search Console and Google Analytics, August 1 to October 17, 2026 against the same dates in 2025.
01 At a glance
The new site against the old one, on the same dates a year apart.
August 1 to October 17, 2026 (78 days) on the new site, against the same dates in 2025 on the old site:
| Result | 2025, old site | 2026, new site | Change |
|---|---|---|---|
| Visitors to the site | 2,507 | 4,185 | Two-thirds more |
| Clicks from Google search | 1,490 | 1,992 | A third more |
| Clicks to pages other than the home page | 609 | 860 | Up 41% |
| Clicks to the Join the Orchestra page | 36 | 166 | 130 more |
Opening night of the new season, September 19, was the busiest search day in the 16 months of data Google keeps: 158 clicks in one day.
02 Where they started
The prototype looked the part.
In July 2026 the orchestra was ready to replace its 2021 website. Its founder and music director, Dr. Kevin P. Bartram, already had the new one prototyped in Base44: a cinematic, dark-theater design with musician bios, a season schedule, backstage videos and sign-up forms for volunteers, advertisers and teachers.
The prototype looked the part. Underneath were three problems a launch would expose, and a deadline.
What a launch would expose
- Pages search engines would miss. Whole sections opened only from dropdown menus, with no page of their own to link to.
- Content locked in code. The season, the testimonials and 13 musician bios lived in code files, not in a content editor.
- A backend they couldn’t take with them. As of July 2026, the builder could export the code, but the database, user logins and server functions ran on its platform.
- A printed deadline. The new season brochure was going to print with the site’s address on it.
03 What we did
We mapped the prototype first, then rebuilt it in WordPress.
Mapped the whole prototype before building
Through the builder’s own connector we read the app end to end: about 60 pages, 65 components and 9 server functions, plus content tucked into code and videos hosted elsewhere. The migration pulled from the source, not from copy and paste.
Kept the look, rebuilt the structure
The same cinematic design and typefaces, rebuilt natively in WordPress.
Gave every section a real page
Clickable top-level navigation replaced the dropdown-only menus.
Turned code into content staff can edit
Musicians, concerts, board members and testimonials became structured content. Thirteen one-off musician pages became one profile template.
One place for sign-ups
Volunteer, advertising and teacher forms all feed one tracked list.
One ticket link for the whole site
Every Buy Tickets button goes through a single address that points to the orchestra’s ticketing storefront, so a new season is a one-line change.
A private room for musicians
A password-protected portal holds the roster and the musicians’ handbook.
Giving that’s easy to find
Pages for membership, concert sponsorship, gifts from an IRA, gifts of stock and legacy gifts.
A launch with no downtime
The new site replaced the old one on the same hosting, with no domain changes and a two-minute rollback ready.
Since launch we’ve kept building. In September we added the Maestro’s Listening Guide, a preview Dr. Bartram writes before each of the season’s five major concerts. The first guide brought in 165 visits in its first 30 days.
04 The new site
The same cinematic design, rebuilt natively in WordPress.
Home page
A prototype in Base44
Before · July 2026

fredericksburgsymphony.org · the live homepage
One profile template

Thirteen one-off musician pages became one profile template.
Screenshots of the live site at 1200 by 800, November 5, 2026.
05 Results
Weekly clicks from Google, a year apart.

Both years rise and fall with the concert calendar. The quietest weeks rose too: in its slowest weeks, the new site drew about as many search clicks as the old one did in a typical week. Over the same dates it served 13,301 page views, up from 9,639.
Every traffic figure on this page comes from the orchestra’s Google Search Console and Google Analytics, comparing the same calendar dates a year apart so both periods cover the start of a concert season. Published with client permission.
06 Timeline
Just over two weeks from kickoff to a live site.
Jul 15, 2026
Kickoff
Jul 17
Prototype mapped
Every page, component and server function.
Jul 27
New site built
In review with the orchestra.
End of July
Live
On the same hosting, with no downtime.
Aug 1
New season announced
Sep 15
The Maestro’s Listening Guide launches
Sep 19
Opening night
Your turn
Built your site with an AI app builder?
Base44, Lovable and tools like them make it fast to get a site that looks right. Turning it into a professional WordPress site your team can edit and search engines can read is the part we do. Tell us what you’ve built and when it needs to go live, and we’ll tell you what it takes.