J. Rieger & Co:
Landing Page
A mismatched nav link, a paper sell sheet, and a phased roadmap that let the page ship without waiting on a new store. (2026)
The problem
The site's navigation had a "Corporate Gifting" link. It just didn't lead anywhere close to corporate gifting. Clicking it opened a third-party form in a new tab — one built for private event bookings, asking for event date, guest count, start and end time. A gifting inquiry has none of those things.
Meanwhile, a real corporate gift guide already existed: a printed sell sheet with actual SKUs, tiered pricing, and personalization terms, built for sales conversations that were happening anyway. It routed interested parties to a plain email address. Two systems, built for two different moments, with nothing connecting them.
Challenge
Before I proposed anything, I live-crawled the site and the third-party destination myself rather than trusting a client description of the problem. Confirming the nav-to-form mismatch firsthand meant I walked into the discovery meeting with a diagnosis, not a guess.
Goals
Give corporate gifting its own on-site home. Something that could hold the sell sheet's real offerings, set expectations before anyone hit a form, and give the brand's existing fulfillment paths room to keep working while the harder decisions got sorted out separately.
Methods
I built a content-agnostic wireframe before any real content existed — six sections (Hero, Occasions, Offerings, Customization, Process, CTA), an architecture that could flex to whatever the discovery meeting surfaced. Alongside it, I put together a meeting prep one-pager laying out the current-state diagnosis, a proposed architecture, and open questions, so the conversation started from a point of view instead of a blank page.
Insight
Mid-process, the actual sell sheet surfaced. The placeholder tiers gave way to the real SKU categories: Spirits, Personalization, and Mercantile. Real numbers followed — a 12-bottle engraving minimum, tiered per-bottle pricing, 7 to 10 day turnaround, 4-week notice for larger orders.
Ideation & Prototyping
The hero needed to set the tone immediately. I designed it as two near-equal-length all-caps lines, centered, reading "SOMETHING THEY'LL / ACTUALLY REMEMBER" — the actual H1 on the live page. SEO title and description followed the site's established live pattern rather than inventing a new format, keeping the new page consistent with everything around it.
Key Decisions
The real decision wasn't which fulfillment channel should win. It was recognizing that question didn't need answering yet. I reframed the project from a single-channel choice into a phased roadmap, clarified over Slack ahead of the in-person meeting so everyone arrived aligned:
- Ship the landing page linking to the existing Tripleseat form
- Investigate changes to the third-party form itself
- Build a new Shopify store for Corporate Gifting
- Integrate the landing page CTA to Shopify once it's ready
That sequencing meant the page didn't have to wait on the harder downstream decisions — a form rebuild, a Shopify build — to go live. It could ship now and evolve later.
Final Design
The wireframe, built in Illustrator, served as the source of truth for the Wix build. It's live now, giving corporate gifting the on-site presence it never had.
URL: jriegerco.com/corporate-gifting
Takeaways
The page closes a loop that had been open since the sell sheet was first printed: someone curious about corporate gifting now finds a page built for exactly that, instead of an event-booking form or a cold email address. It's also a forward hook — this page is positioned to become the first real foothold for the brand's larger Square-to-Shopify migration, a phased roadmap with a clear next step rather than a one-off fix.
The strongest version of this project wasn't "I built a landing page." It was research-driven: a fragmented current state, live discovery, a sell-sheet pivot mid-process, and a phased roadmap decision that let the page ship without waiting on the harder problems behind it. Building the wireframe content-agnostic from the start is what made the mid-process pivot painless instead of a rebuild.