Six things are fixed and live on your site and booking page as of today. We also read every comment your audience has ever left you β all 1,034 of them β and they have been telling you the same thing for months.
We read all 1,034 comments across your 39 most-commented videos. These are the three most liked comments in the entire history of your account:
That's 86 likes on one single objection β more than triple any other comment you've ever received. And it keeps coming:
Food is the number one topic in your comments β 25 separate mentions, ahead of everything else including the elopement vote.
This isn't people saying you're too expensive. Nobody once said the price was too high on its own. They're saying $350 sounds like a dinner price, and they can't tell that dinner isn't part of it. That's a wording problem, not a pricing problem β and right now it's the first thing a stranger thinks when they see your best-performing video.
Four out of every ten comments on your own account are you answering questions. Price, guest counts, how to book, whether food is included, how the marriage licence works β you have typed these answers hundreds of times.
The words people actually use, counted across every comment: "please" (68), "details" (47), "how much" (37), "info" (37). They are asking for information that should already be on the page.
Your booking page tells customers this, right before they pay:
That one sentence is why nothing adds up. Here's July:
| Where we looked | July total | Of the real number |
|---|---|---|
| Your own tracker | $13,166.91 | 100% |
| Setmore | $6,673 | 51% |
| Stripe | $2,164.05 | 16% |
About $11,000 of July never touched your card processor.
Here's the part worth knowing: the 2.9% isn't coming out of your pocket. Your checkout adds it on top β a $600 booking charges the customer $618. So sending people to Zelle doesn't save you the fee. It saves them the fee, and costs you the deposit, the records, and Afterpay.
These sit one above the other in the box customers tick to agree:
Both can't be true, and as written it wouldn't hold up if someone pushed back.
The old policy was strict because it had to be β you were collecting nothing, so the only thing stopping a no-show was a stern sentence. Now that a real deposit is in place, you can afford to be generous.
In July you posted a video asking people to vote β 1οΈβ£ Same-Day Elopement or 2οΈβ£ Micro-Wedding. It became the best thing you've ever posted: 49,100 views, 1,263 shares, 379 comments.
We read all of them.
Elopement wins on raw count, 59% to 41%. But that's not the whole story.
"1" is the easy thing to type. The comments that got the most agreement were almost all micro-wedding, and they arrived with details:
The strongest read: offer both. Elopement is what most people click. Micro-wedding is what the serious ones describe.
People told you how many guests they wanted to bring:
| Guests asked for | How many asked |
|---|---|
| 2 Β· 4 Β· 5 | 4 |
| 6 | 3 |
| 8 Β· 9 | 2 |
| 10 | 4 |
| 12 Β· 14 | 2 |
| 20 | 4 |
| 40 | 1 |
Across every comment, as many people asked for 20 guests as asked for 10. Your packages are aimed at the 2β10 crowd. There's a 12β20 crowd of about the same size knocking on the door.
What is costing you is that the limit isn't written down anywhere. So every person hoping for 15 or 20 has to message you to find out, and you answer each one by hand. Put "up to 10 guests" plainly on the page and that whole group either self-selects out or asks about something smaller β either way, without a DM.
Price was the single most asked-about thing. You answered every one of these personally, in DMs β 145 replies. That's the work the website should be doing for you. Both packages exist in Setmore and are bookable today. Neither appears anywhere on your site.
Twenty comments asked about something other than a proposal β and anniversaries came up more than anything else, followed by birthdays, vow renewals and a baby shower.
These land on weekdays, which is exactly the inventory sitting empty. Your site is written almost entirely around proposals, so people have to ask whether they're allowed to book for anything else.
A handful of people asked, including from Houston and Chicago. Not a business yet β but worth a line on the site either way, so the answer isn't always a DM.
Women want to hint to their partner without spoiling the surprise. Right now they have no way to do it. A simple "send this to someone" page β a hint they can forward that doesn't look like they sent it β would be shared constantly by exactly the people who most want to be proposed to.
You don't have a logo yet β the site currently just sets your name in whatever font the page happened to use. Everything else in the brand is waiting on this one choice: the site, the booking page, signage, the sign-off on your emails.
Eight directions are laid out side by side here:
skyline-brand.pages.dev
All eight are shown at the same size, so you're
comparing the letterforms rather than the presentation. The drawn heart mark is on the
same site at /mark.
| # | Typeface | Character |
|---|---|---|
| 01 | Fraunces, title case | The incumbent β warm, literary |
| 02 | Bodoni Moda, tight caps | High fashion, sharp contrast |
| 03 | Jost, wide caps | Modern, architectural |
| 04 | Inter, tight mixed case | Clean, understated |
| 05 | Newsreader, mixed case | Editorial, quiet |
| 06 | EB Garamond, small caps | Classical, generous spacing |
| 07 | Marcellus, stacked | Two lines β reads as a monogram |
| 08 | JetBrains Mono | The wildcard, and a real risk |