Loading something special...

Happy Lobster

Webflow Development, CMS Architecture, Design Systems, Technical Research, JavaScript

The Problem:

A multi-phase Webflow design and development engagement for a Chicago-based food truck business — beginning as a capped foundational sprint and growing organically into CMS buildout, third-party integrations, custom JavaScript solutions, technical research, and a full headless e-commerce proposal.

2025
Webflow Development, CMS Architecture, Design Systems, Technical Research, JavaScript

Phase 1: Prototyping

A well-architected, scalable Webflow foundation that enabled the internal team to build confidently, a component system that paid for itself across every subsequent phase, and a technical research process that reframed platform constraints into workable solutions. Each phase grew naturally from the previous one — proof that a clean foundational sprint is the best sales tool for future work.

Phase 1 — Foundational Sprint

A deliberately scoped 20-hour sprint focused on getting the fundamentals exactly right: a MAST-style component system, global styles covering typography, color, and spacing, core layout components including nav, sections, cards, and CTAs, and a CMS structure designed for future scalability. The homepage served as the reference implementation — a working example of how the system was meant to be used. Handoff documentation was treated as a first-class deliverable.

No items found.

Phase 2 — Additional Scope

Global scroll animations built once and applied across pages, a CMS-driven menu page with multi-reference wiring, Square deep linking to filtered category URLs, a 'Where We Roll' locations page built on the Truck Stops CMS collection with featured/non-featured logic and Google Maps links, and QOL fixes across the site. Mid-phase a persistent scroll bug was traced to fullpage.js — rather than continue patching, the library was replaced with a custom CSS scroll-snap and JavaScript solution: cleaner, lighter, and zero third-party dependency.

No items found.

Technical Research — SMS × Square Integration

Conducted a proper capability audit of Square's SMS and marketing APIs after the client requested a geofenced SMS alert system. Square doesn't support real-time GPS-based proximity alerts, but does support SMS opt-in and customer list segmentation by location. Recommended an intent-based location targeting model where customers self-select their neighborhood at signup via Square opt-in links surfaced directly in the Truck Stops CMS — fully supported, legally compliant, and operationally simple.

No items found.

Phase 3 — Headless E-Commerce Proposal

Scoped a full custom headless e-commerce build to replicate the client's Tock ordering experience as a native on-brand flow inside Webflow, routing through Square for payment, fulfillment, and reporting. Structured in four phases: Discovery and Technical Architecture, UI/UX Design, Webflow Development and Square Integration, and QA and Launch. Before the engagement moved forward, the client identified an internal solution — the project closed cleanly with the proposal on record as a benchmark.

No items found.
A storyboard depicting the user journey with a dental health app. It starts with a person waking up, followed by motivation to brush teeth, using an app that tracks and encourages good dental hygiene. The storyboard illustrates various app features such as progress tracking, rewards, and a smart mirror that analyzes brushing technique.

What I Learned

1

Capped foundational sprints are the best new client strategy

A 20-hour sprint with clear deliverables is a low-risk entry point for a new client. Executing it well — clean architecture, thorough documentation, disciplined scope — builds more trust than any proposal could. Every subsequent phase of the Happy Lobster engagement came directly from that first sprint landing well.
2

When a third-party library fights back, the migration cost is usually worth it

The decision to replace fullpage.js with a custom CSS scroll-snap solution took a few hours and eliminated an entire category of future bugs. The willingness to rebuild cleanly rather than keep patching is a discipline that pays compounding returns across a long engagement.
3

Technical research is client service, not a blocking task

Returning to Happy Lobster with 'here's what's actually possible, here's why it achieves the same goal, and here's how it fits what you already have' was more valuable than either a flat no or a silent workaround. Platform constraints don't have to mean feature compromises — they usually just mean rethinking the implementation path.
4

Not every proposal converts, and that's not a failure

The headless e-commerce proposal didn't close, but the process added real value: it forced technical clarity, gave the client a benchmark for evaluating other solutions, and maintained the relationship. A well-scoped proposal on record is a good outcome even when the project doesn't proceed.

Get in Touch

If you're impressed with my work, then let's make something special together

“The Website looks official and it’s Always evolving. I love it.”

-Vince Wimberly Jr.
Owner of Life Advance Fitness

Send me an email