Fairytale Dreamers: a Deaf-led travel agency
and the website built like cabinetry.

A Deaf-led family travel agency in Maryland needed a website that earned trust before the first call. We built it under one roof — public site, agent CRM, lead pipeline, branded email — on commodity hosting, no monthly SaaS bill, no React build farm. Two of the tools live on this page below. Sign your kid's height in, pick a park, see what they can ride.

Who they are

Fairytale Dreamers Travel is a small, Deaf-led travel agency that books Walt Disney World, Disneyland, Disney Cruise Line, and runDisney weekends — primarily for Deaf and hearing families who want a planner who actually signs, runs the races, and has been on the boat. Free to the client; the agency is paid by Disney through the standard agent commission model.

The lead agent, Fallon, was born Deaf into a Deaf family and chaired an ASL interpreting program for ten years before going full-time on travel. The bench around her includes a Disney University alumna, a runDisney lifer who has stopped counting half marathons, and a coach in Colorado who is 16 medals into a "50 by 50" goal. The team's pitch is the kind of small-business pitch that has to be earned in a single page on the internet, and earned again every time someone fills out the contact form.

What we built

One stack, top to bottom, deployed to GoDaddy cPanel with a single bash command. The whole thing is static HTML, vanilla JS, hand-rolled CSS, and a Google Apps Script — chosen on purpose. No monthly bill that creeps. No upstream vendor who can break a release window the day before a peak booking weekend.

fairytaledreamerstravel.com Home · live park-hours strip pulls from ThemeParks.wiki API

• Public site 11 marketing pages, 9 blog posts, a 2027-cruise landing, a runDisney microsite, and 9 free interactive planning tools — two of which we lifted into this case study below. Hand-coded HTML/CSS/JS, no framework tax.
• Agent CRM A full back-office dashboard at /agent/: leads board, bookings tracker, campaign queue, saved lists, KPI strip, email template editor. 8,500 lines of vanilla JS. Sheet-as-database via Google Apps Script. Same login the agency uses today.
• Email pipeline Form submission → Apps Script → Microsoft Power Automate → real Exchange mailbox at contact@fairytaledreamerstravel.com. Customer-facing emails go out with proper SPF, DKIM, and DMARC. Zero Gmail "via" footers.
• Deploy + DNS One bash script with snapshot rollback. GoDaddy cPanel, AutoSSL, the right TXT records. The agency owner can read the runbook and not need us. That's the deliverable, not a vendor lock-in.

Try two of the tools.

Both of these run on the FDT site today. They are exactly the same code, restyled to live on this page. Self-contained — no API calls, no logins, your inputs save to your own browser's localStorage so they're there next visit. We ship a lot of small tools like this. They cost almost nothing to build and they're how a small business demonstrates competence on the internet without saying the word "competence."

Why this fits 1891's pitch

The page you are on right now — 1891's main demonstration — argues for systems built end-to-end, in Frederick, under one roof, that work for the body that walks in the room. Cameras instead of microphones. Hardware, firmware, gameplay, and set design from the same shop.

FDT is the same argument in software. Hand-coded site, hand-coded back office, hand-coded email pipeline, deployed to commodity hosting with a single script. No SaaS rent. No framework that needs a rebuild every six months. No vendor who can change the deal mid-flight. When a customer fills out the contact form on a Friday night, the email goes through real Exchange and lands in Fallon's inbox at 9:42 PM with proper authentication. When the agency wants to send a quarterly campaign, the queue is in their own sheet.

One small choice that matters: Google Sheets is a premium connector in Power Automate. To wire it directly costs $15 per user per month, in perpetuity. So we don't. The Apps Script writes a small JSON-bearing email to a hidden mailbox, an inbox rule moves it to a folder no human ever reads, and Power Automate's free Outlook trigger picks it up, parses it, and dispatches two clean branded emails — one to the agent, one to the customer. The user sees a thank-you screen. Three seconds later, two emails land. No license is in the loop.

That kind of routing decision is what we mean by "software built like cabinetry." You measure the wall before you cut the boards. You don't pay for a feature you don't need, and you don't ship a stack that costs the client more to keep open than the agency makes in a slow month.

Google Sheets is a Premium connector in Power Automate. To keep everything free, we trigger off an email instead. — Anthony Mowl, on the day FDT's email pipeline went live

The Deaf-led angle — quietly

The lineage matters, but it does not lead. FDT's homepage says "Disney vacations made for every family." Then, lower: "a Deaf-led, signing travel team." The order is on purpose. The promise is universal. The fact that the people behind it are part of the community they serve is the why, not the headline.

That's exactly the line 1891 walks too. The work has to stand on its own merits in front of every kind of guest. The fact that the team has been in this conversation for generations is what makes the work feel right when you finally hear about it — not the reason to click in.

What changed for the client

Pre-1891, FDT was running their lead pipeline through a hand-managed spreadsheet, a Gmail account, and a free no-code form builder that quietly added its own footer to every confirmation email. Booking customers were emailing the personal Gmail addresses of agents who happened to be on duty that week. There was no shared system.

After: every contact form on the site lands in one canonical Sheet, with a routed advisor copy, a properly branded customer confirmation, and a CRM dashboard where five agents can see leads, take ownership, leave notes, mark won/lost, and pull list segments for campaigns. Multi-user Google OAuth is teed up for whenever they want it. The whole thing is theirs — including the source code — and they own the domain, the email tenant, and the deploy keys.

Maybe the most important deliverable, though, was the runbook. GO-LIVE-GUIDE.md is plain-language. It says what shipped, what was deferred, and what would take an hour to upgrade if they ever want to. It's the kind of document you write when you actually expect the client to read it — and you don't want them to need you forever.