90 entries on engineering, growth, design, and what we've learned building products.
We were spending twenty hours a month putting together reports that clients skimmed for thirty seconds. Automating the process forced us to rethink what the reports were actually for.
We committed to posting three times a week on LinkedIn for six months and tracked every inbound contact that mentioned it. The results were not what we expected.
We used to save case studies for the proposal. Moving them to the first call changed the entire trajectory of those conversations.
We spent three years sending proposals in the same template and one typographic change shifted how seriously they were received.
I spent a week inside WordPress.org support forums studying how real users describe problems with plugins, and it changed how I think about documentation.
We walked away from the biggest single contract we had ever been offered, and the months that followed made it obvious we had made the right choice.
Turning something we had always done ad hoc into a fixed-scope, fixed-price product took four attempts and is still not perfect, but it changed how we sell.
After a year of experimenting, we have settled on a small set of tools that genuinely save time, and a much longer list we abandoned.
Building a scheduling tool sounded straightforward until real users started using it in ways we never imagined during development.
Every instinct in conversion optimisation says add more. We tested removing more, and the data disagreed with our instincts.
We published consistently for years with almost no traction, and then a single post reached 40,000 people in a week. Here is what I think actually happened.
Cookies are going, ad platforms are tightening, and the clients who built their own data assets are the ones who are not panicking.
Showing 13–24 of 90 entries
