# Draft reply to Adam's questions (2026-08-20, evening)

> Context: Adam raised 8 points, incl. the deadline jab and "operational in 4 weeks for
> Cannes outreach, 10-50 locations scraped." He flies to Europe Saturday, back Sept 7,
> working while away. Rian's goal: total honesty, no overpromising, fine with losing
> the WP evolution work. No em dashes.

---

Hi Adam,

Great questions, and I'll go straight through them. But first, since you were direct
with me, I'll be direct back on the deadline point: you're right. I haven't given you
much reason to trust my delivery lately. The last project cost me an embarrassing
amount of time and money, and honestly the money mattered less than failing to deliver
on the promise. So I'm not going to argue my way back to credibility here. Instead,
I've structured my offer at the bottom so you never have to take my word for anything
for more than a week at a time.

Your questions:

AI content vs human content: totally agree, and I think we're saying the same thing.
AI is for the plumbing (scraping, the pricing database, comparisons, the map). The
editorial voice stays human. One distinction worth making for you and Mark: a pricing
database isn't "AI content" in the sense Google penalizes. It's original structured
data, like a flight comparison site. Done right, it becomes the strongest SEO asset on
the site: thousands of genuinely useful pages no competitor has. The thing to avoid is
mass-generated articles, and that's a content policy, not a platform choice.

Same look across the competition family: this actually strengthens the custom app
plan. If DFA is built custom, we develop its design as the IBC family look from day
one (same medal system, same structure, familiar layout for producers entering NYISC
or BISC plus DFA). Then when we circle back to Melbourne in October, the conversation
isn't "re-theme WordPress," it's "Melbourne becomes the second site on the new
platform," and the design work gets done once instead of per-site.

"So no more WordPress?": eventually, probably, but not as a rip-and-replace. My
recommendation is to build DFP and DFA custom now, leave every existing WordPress site
exactly as it is, and migrate only once the new platform has proven itself, one site
at a time (Melbourne in October is the natural first candidate). If your writers like
the WordPress editor, it can even stay on behind the scenes as the article-writing
tool feeding the new front end. No big-bang migration.

DFP as a one-off layout: understood, and that's fine. A custom app doesn't need to
match the professor sites, and ecommerce plus content is exactly the shape it's best at.

Platform, and who maintains it if I'm in Tahiti: fair concern, so honest answer first.
Replit is legitimately good, and for pure speed to a first version it may be the best
thing going. What I build instead is a standard, boring, open stack (the same
technologies half the industry uses), with the code in a repository you own. It runs
on my infrastructure today but could move to any cloud host in an afternoon.
Documentation for handoff is one of my primary focuses, and I mean handoff to other
developers and to AI tools alike, because that's how maintenance actually works now.
If I disappear to Tahiti, any competent developer (frankly, including Hamish) could
pick it up. The real difference between the two paths isn't week one, it's year two:
Replit optimizes for getting started fast inside their hosted ecosystem, an owned
stack optimizes for the long life of a platform you keep building on. If DFP were a
one-off experiment, I'd tell you Replit is the rational choice. My pitch only makes
sense because of where you say this is going: DFA inside the IBC family, then the
competition sites, and maybe the professors after that.

Hamish's quote: I can't compete with $1K and a weekend, and I won't pretend to. If his
scope covers the scraper, database, and design, his quote is simply better than mine,
and he comes trusted through your EO network, which counts for a lot. What I'm
charging more for is a different bet: the platform thinking above, and me still being
here every season after launch.

The 4-week deadline and Cannes: here's my honest read. DFP operational with 10+
locations scraped by mid-September is achievable. 50 locations is possible, but I
won't promise that today. And given my track record with you, you shouldn't accept
either statement on faith. So, two options:

1. Go all in with Hamish and Replit. I keep supporting the WordPress sites, with the
   shared understanding that they wind down over time and we stop building new
   features onto them. If the Replit path stalls, I'm happy to revisit later, no drama.

2. Run both. Greenlight my $1,500 proof of concept before you fly Saturday, and let
   Hamish do his thing in parallel. By Friday the 28th you get a link to a working
   slice of the real thing (real scraped prices, a few airports, the compare view, a
   medal badge) plus a short video walkthrough you can watch from Europe, no call
   needed. Compare the two, abandon one, and honestly it's 50/50 it'll be mine. Seeing
   both before deciding costs you about $2,500 total, and your deadline is protected
   either way because you lose zero calendar time. If mine wins, we grab 30 minutes
   whenever you have it, I quote the remaining build to operational, and you'll be
   deciding based on something you've already watched working rather than on my word.

Your trip isn't a problem for either option. Everything I'd send before Sept 7 is a
link and a video you can review whenever you like, and email works fine for the
decisions.

The choice is genuinely yours, and there are absolutely no hard feelings if it's
option 1.

Rian