When a client's desired checkout experience conflicts with the constraints of their chosen e-commerce platform, the agency faces a three-way decision: accept the platform's defaults, switch platforms, or implement fragile custom workarounds. The LaMaurie situation illustrates why the middle path — hacking around platform limitations — is rarely the right answer.
Square is well-suited as a primary commerce platform when used within its intended design. However, it offers minimal flexibility for custom checkout interfaces. Clients who want to modify the checkout flow beyond Square's defaults will find that Square simply does not expose the necessary editing or customization capabilities.
"Square works great if you use it as your primary thing. But if you want to make it something different than the way Square works, Square is not very flexible. There's no editing capability or whatever."
— Mark Hope, 2026-01-22
A common temptation when hitting platform walls is to "duct tape" a solution together using custom PHP or similar server-side hacks. This approach carries significant long-term risk:
"We could probably figure out a way to duct tape something together using some PHP and stuff. But it's fraught with peril because the next version of PHP will break it."
— Mark Hope, 2026-01-22
When a client raises checkout customization requests that exceed platform capabilities, present the decision clearly as a binary choice — not a negotiation:
| Option | Implication |
|---|---|
| Stay on Square | Accept Square's default checkout interface as-is; no custom flow possible |
| Switch platforms | Full flexibility to build the desired checkout experience |
| Custom workaround | Not recommended; fragile, maintenance-heavy, and unsupported |
The key message to clients: you cannot be half in and half out. Committing to a platform means committing to its constraints.
"If they want to use Square, then quit bitching about the interface. If they don't want to use Square, then we can do pretty much anything. But you can't be half in and half out."
— Mark Hope, 2026-01-22
The LaMaurie situation was complicated by the presence of Kim, a technical contractor ("firefighter") who stepped in during the primary contact's maternity leave. Clients with IT backgrounds may:
When managing technically sophisticated client contacts, be prepared to explain why a solution that is technically possible is still the wrong choice — not just that it cannot be done.
When presenting the Square checkout situation to LaMaurie (or similar clients):