The One-Liner

The week a casual conversation became a real proposal and I stopped thinking of him as a contact and started thinking of him as a client.

What Happened

Wednesday, April 23 — Getting Serious About the Prospect

WhatsApp with the prospect. He wants a UI/UX specialist. He mentioned the codebase metrics again — hundreds of thousands of lines of code and a massive product catalog. The scale of this operation is genuinely big. This isn't a small ecom shop with a Shopify template. It's a real business with a real traffic problem and a real revenue gap.

I made a deliberate positioning call in how I responded. I'm not presenting myself as a second developer or a technical resource to plug into John's workflow. I'm positioning as a growth partner — someone who cares about the number that matters (revenue from existing traffic) and works backwards from that. The distinction matters. Developers get compared to other developers on rates and technical capability. Growth partners get evaluated on whether they can move the needle on outcomes.

He seemed to track the difference. We kept talking.

Thursday, April 24 — The Intro Ask

I asked the prospect for an introduction to his developer. Framed it carefully — not as me coming in to review John's work or compete with him, but as wanting to meet and potentially work together to speed things up. Two people who both want the same outcome for the same client.

It's a low-risk ask for the prospect. Best case, his dev and I find a way to combine efforts and things move faster. Worst case, the intro goes nowhere and nothing changes. I made that framing explicit. He said he'd make the connection.

This kind of patient positioning is something I've been getting better at. The instinct used to be to push for the decision — yes or no, in or out. The more useful instinct is to create conditions where yes becomes natural. That means meeting the people they trust, understanding the system they're already inside, and finding where you fit without forcing it.

Sunday, April 27 — Proposal Built

Built the proposal. The first version was broad — here's what's wrong, here's how I could help. This version is specific: here's what I know about your checkout, here are the numbers, here's what I think the highest-leverage first move is.

The data is stark. The GA4 data told a clear story: strong traffic, very few purchases, and a checkout drop-off rate that’s well above industry average. The traffic is there. The intent is probably there, at least in part. Something is breaking between the product page and the completed order.

Proposal in hand. Meeting the prospect Sunday evening. Good context for a relaxed conversation — not a formal pitch, more of a check-in with something concrete to show.

Monday, April 28 — VPN on VPS

Set up WireGuard on the VPS. Clean privacy layer while I'm travelling — routes traffic through the VPS in Singapore. Took about an hour to configure properly but it's been on the to-do list for a while. Good to have it done.

Also did auto-backup and CLAUDE.md updates — maintenance work, not glamorous, but the kind of thing that matters when something breaks at the wrong moment.

Tuesday, April 29 — Meeting Strategy

Prepared the detailed meeting strategy for the conversation. The specific ask I'm planning: propose calling 15 to 20 abandoned checkout customers directly — real people who added to cart and didn't buy — and interviewing them about what stopped them.

This isn't a technical fix. It's a research move. Before you rebuild a checkout flow or redesign a product page, you want to know what the actual friction is from the person who experienced it. Most businesses never do this. They look at analytics and guess. Talking to 15 people who abandoned checkout will tell you more than any heatmap.

The pitch is simple: let me call them, I'll compile the findings, and then we have a fact base to make decisions from rather than assumptions. Low cost to the prospect, high signal for both of us, and it creates a natural next step into whatever the actual fix looks like.

This is also how I want to work more generally. Not pitching solutions before I understand the problem. Not guessing at the brief. Get into the data, talk to the humans, then build.

Also This Week — Blog Post Shipped

Published "Claude Design Just Made UI/UX Designers Obsolete" on lachlancb.me. Full treatment — custom cover image, CTA card, two data visual infographics. The piece I'd been thinking about since the Claude Design drop last week. Got it written, built the assets, and pushed it live.

Happy with how it came out. The take isn't clickbait — or at least it's not only clickbait. The argument is real and I tried to make it with specifics rather than vibes.

What I Built

  • the proposal — specific, data-backed, focused on the high checkout drop-off rate
  • Meeting strategy for Sunday church sit-down with the prospect — abandoned cart customer research plan
  • Blog post: "Claude Design Just Made UI/UX Designers Obsolete" — cover image, CTA card, 2 infographics, published to lachlancb.me
  • WireGuard VPN configured on VPS — privacy layer for travel
  • Auto-backup and CLAUDE.md maintenance

The Honest Take

This is the most interested I've felt in a prospect since I started this agency. Not because the deal is done — it isn't, not even close — but because the problem is genuinely interesting. A site doing strong daily traffic with a very high checkout drop-off rate is a mystery worth solving. The data is real, the gap is real, and if I can close even a fraction of it, the impact is significant.

The other thing I've been sitting with: I positioned myself as a growth partner early and I've been consistent about it. That consistency matters. He’s seen me show up three or four times now — site audit, WhatsApp follow-ups, offer to meet his dev, proper proposal. None of it was pushy. All of it was relevant. That's the difference between a sales process and a trust-building process. They overlap, but the orientation is different.

The abandoned cart research idea is the move I'm most confident about. It de-risks the engagement for the prospect — he's not committing to a rebuild or a retainer, he's just letting me make some calls. And it positions me as someone who does the work before making the recommendation, which is who I actually want to be.

Good week. Something real is forming here.

Next Week

Run the church meeting with the prospect, get a clear yes or no on the abandoned cart research calls, and start the outreach if he's in.

Have a good one. Peace. Lachy