Build LogConversion
#06
2026-08-045 min read

Thirteen sessions, zero enquiries: the funnel I thought I had

A GA4 segment built in thirty seconds revealed the Upwork funnel: one desktop visitor returning thirteen times, seven minutes on /work/, no contact made. The site had no front door, no closing till, and a contact note written as a quality signal that read as a rejection.

Read post
Build LogAnalytics
#07
2026-08-024 min read

One visitor, seven minutes, no exit: the data that wrote the brief

A GA4 segment query ran before any design work started on /work/, the homepage, or the contact page. What it found wasn't a vague underperformance signal — it named a specific gap. Every build that followed was a direct response.

Read post
Build LogConversion
#08
2026-07-305 min read

The thirteen-session visitor who reshaped three pages

GA4 turned up essentially one Upwork-referral visitor with more than thirteen returning sessions. Seven minutes on /work/, no action taken. The sample size was one. The behaviour was deliberate enough to act on anyway. Three site changes followed in a single sprint.

Read post
Build LogConversion
#09
2026-07-275 min read

Seven minutes on /work/ and no hire button: the problem wasn't the copy

GA4 showed a single desktop visitor returning thirteen-plus times, spending seven minutes straight on /work/ with no way to act. The instinct was to rewrite the copy. The data was pointing at something structural — the page had no till.

Read post
Build LogLearning
#10
2026-07-245 min read

The backlog called it a content gap. It was navigation.

Completing an eight-chapter course on the learning hub felt like progress. Then I looked at what had actually moved the needle — track sections, prerequisite chips, and a JSON-LD breadcrumb. The backlog had been mis-filing the bottleneck for months.

Read post