Business

A 56-post collection

Built to last

Many projects don’t seem to prioritise longevity very much these days.

Think how many buildings built over a hundred years ago are still standing, still cherished, and have great uses.

How often do we build buildings today to those standards? It seems, not often enough.

I don’t know why. I’m not a qualified architect. But I suspect it comes down not to designers or materials, but budgets and policies and priorities.

What if it came down to pride? Not being told or due to requirements, but because you want to?

It used to be impossible to build cheaper or take shortcuts. Now it seems to be the default.

But the default doesn’t have to be the only way. And pride doesn’t have to cost more.

Decisions are made by one person

It's bugged me for a long time — the process of decision making.

Sometimes I think I'm quite bad at making decisions and I take too long to make them.

That's absolutely true at times.

But when in a team, there is sometimes a sense that decisions are made by a group. You get together as a team and collaborate to make a decision.

If the team is healthy, you collaborate and you listen and you give each other time to share thoughts. Great ideas and suggestions can come from anywhere.

But decisions… those can be harder.

In reality, most teams are not purely democratic, so decisions are rarely ultimately made by the team as a whole. They are made by a person on the team.

Often, all too often, in a team, things fall down because it isn't clear who the person to ultimately make the decision is.

Sometimes it's because the person who makes the decision isn't qualified or doesn't have the right information.

Sometimes it’s to do with the health of the team — the psychological safety of putting your neck on the line. Toxic cultures can make decision-making a more political or emotional challenge than necessary.

But from what I've seen, often it's because the person who needs to make the decision isn't aware that they are the ones who need to make the decision in the first place. There is ambiguity and misunderstanding within the team.

In startups and small businesses, often one of the few advantages over bigger companies is speed — you can move more quickly than a thousand-person behemoth because you can strip away the politics and bureaucracy and risk aversion that larger organisations tend to accrete.

You don't have a lot else: you have less money, fewer people, and less time. Which is why speed is not just advantageous but necessary.

While there's a lot of information and tooling around building and designing things faster, there's relatively little about making decisions faster and more effectively, even in a small team.

It could be the difference between life and death. Sometimes a decision doesn't just wait for hours. It waits for days, weeks, months, if not years.

Figuring out how to change this is a constant endeavour of mine. And I believe primarily it starts with making sure it's clear who makes the decision. 

Inevitable criticism

It's worth bearing in mind that very rarely does anybody get criticised for not making a decision.

It's very easy to criticise a wrong decision being made, because you can usually see it play out on a given time horizon.

A decision not being made though: in most companies this can be invisible.

The very absence of something makes it hard to pin down. You rarely see the negative impacts of indecision directly. But you ultimately pay the price.

Which is why a culture where decision-making is

Use the goddamn product

Being customer obsessed is easy to say, but extremely hard to consistently do.

Whether you run a five star hotel or a SaaS business, the best way to understand how to make your product or service better is to experience it as a customer would.

Yes, it's crucial to gather customer feedback, to actively seek their feedback, and to execute on improvements based on what they tell you.

And as a software business you can instrument your app with metrics and tracking so you have every datapoint you could ever dream of.

But I'm convinced that customer feedback and metrics can only take you so far. No matter how direct and open your customers are with you, they likely will never tell you everything that could make your offering better.

And, the act of responding to customer feedback inherently means building something and waiting for feedback to improve.

You can make your offering better without a single piece of user feedback by doing something simple: use your service yourself.

For a software business, you should sign up for your own product. And you should use it on a regular basis.

And I don't mean "use" it in the sense of testing. Of course you want to make sure a few common workflows always work. I mean really use it like a user would — to carry out an objective, under realistic conditions.

In EcoSend, we've fixed hundreds of things that users have never (and I suspect would never have) told us about. Does that mean those issues don't matter? I believe they do — they all add up to an experience, whether vocalised or not. They're not show-stopping issues, and they're not necessarily bugs. They're quirks, things that could be more obvious, flows where we can save the user a click, or guardrails that help the user avoid a mistake.

I love making these kinds of improvements — they often go unnoticed, but they add up to an experience that feels more robust and reassuring, and at times delightful.

It's this approach that leads to good software. No matter how much AI is used in software creation, the process of using your own product cannot be outsourced.

The best software will always come from countless iterations based on feedback and refinement. When you are a user, you can run so many more of these cycles without users ever needing to tell you.

Tobi Lütke of Shopify on AI, slop, and responsibility

I really enjoyed this discussion with Tobi Lütke, the founder of Shopify.

I’ve always admired him for leading and building Shopify into the business it is today — one that is both financially successful, strives to build truly great products, and champions entrepreneurship itself.

Tobi shares the ups and downs of how they’ve been using AI as a company of thousands. They appear to have developed an incredibly valuable “team agent” that assists their team members in their daily tasks, and continuously evolves based on feedback.

This talk introduced me to the concept of “slop grenades” — huge and thoughtlessly verbose documents generated by fellow team members that get dumped on your desk to wade through.

Perhaps most interesting to me was Tobi’s remarkably simple answer to whether AI would ever take his job as CEO of Shopify: “no”. Tobi argues that AI cannot lead because it cannot take responsibility for its actions. Only humans can do that, and that’s a huge part of what makes any leader.

This talk seems to have been picked up by a lot of tech community thanks to its discussion around AI, but it’s well worth a watch regardless to get an insight into the brain of someone running a highly successful and large software business in its prime.

First vs only

Earlier this year Elon Musk became "the world's first trillionaire".*

That wording made me pause.

The use of the word "first" inherently implies that there will be more.

More trillionaires?

I would rather write "the world’s only trillionaire".

"Only" does not imply momentum.

"Only" implies uniqueness. Isolation. Loneliness.

It takes the edge off the statement.

"First" suggests we might want more trillionaires.

We don't.

* In desperately sad news, Musk's trillionaire status has fluctuated, and shortly after the IPO he lost it.

Revisiting the agile manifesto in the age of AI

If you’re an engineer I can already hear you letting out a sigh.

As long as I’ve been in the world of building software I’ve heard the term “agile” and I’ve never really dug into it too much.

It’s always had connotations of “work” and project management and, to be honest, Jira.

Yuck!

It was only recently when someone shoved the core principles of the Agile Manifesto under my nose that I thought to take a closer look.

If you haven’t come across the Agile Manifesto before, you can find it on a website that appears to be unchanged since the 90s. It’s gloriously old school.

But the words are as relevant as ever. If anything they feel more relevant and important.

For convenience, here are the principles, with a little interpretation of my own.

Satisfy the customer

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Satisfy the customer. Satisfy the customer.

If nothing else, this is the most important principle of all. If this was the only principle, and every single organisation and individual adopted it, I think software would be perceived in a much more positive light by people. And I think we would perhaps have a lot less, but better, software.

Embrace change

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Changing your mind when new information emerges is a good thing.

Working software in weeks

Deliver working software frequently, from a  couple of weeks to a couple of months, with a preference to the shorter timescale.

I'd argue this should now be hours, or days, in the age of AI.

Don't ignore the business

Business people and developers must work together daily throughout the project.

By "business" people I'd include customer service, marketing, sales, and leadership.

Trust motivated people

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Speak to each other

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Technically Google Meet and Zoom are face to face. But nothing beats being in person.

Actual working software is the priority

Working software is the primary measure of progress.

Yes you can get a fancy dashboard to measure user numbers, activity, and more. In fact, I am inclined to believe analytics can be very helpful! But don't lose sight of the top priority: working software.

In an age of tokenmaxxing, and having witnessed previous phases of optimising for "lines of code written", this feels like a rather important goal to keep in mind.

Sustainable development is sustainable

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

You can only move fast and break things

Focus means saying no

Ask anyone who's been in business for a while how they got successful, and they'll almost always highlight the importance of focus.

In the famous Apple video called "Intention" that opened one of Tim Cook's first keynotes as CEO — there was the unforgettable line:

There are a thousand no's for every yes.

And as Jony Ive has said many times: people think focus is about saying yes to one thing. In reality, it's about saying no to (sacrificing) many fantastically good ideas. All so you can focus on the one thing that really matters most.

That all sounds rather obvious, perhaps.

But of course, that is all a lot easier to accomplish if you're incredibly sure of what you should focus on.

The challenge, I have often found, is choosing what to focus on.

What is actually most important? And can those other ideas, asks, and requests really be a "no" right now?

Surely there is a balance?

The more you can gain conviction on what is truly important — what truly deserves your time and attention — the more confidently and therefore successfully you can focus.

And with that focus — only with that focus — can greatness be achieved.

Your product is a conversation with the market

Des Traynor and John Collison on Stripe's Cheeky Pint podcast

A while back I watched this talk from two legends of the software world: Des Traynor of Intercom and John Collison of Stripe.

I love these discussions and this series I find to be a relaxing, fun environment. How could you not enjoy watching a couple of smart people sharing a Guinness or two, discussing topics you've always wanted to ask them about?

A few quotes that really stuck with me:

A product is a conversation with the market.
Your launch is your opening bit, and then you have to basically adapt and react to what gets thrown back at you, which might drag you in different directions. And then you need to have, again, the confidence to prune certain things.
People massively underestimate what it means to have a truly happy customer base.
Word of mouth doesn’t have a UTM code.
Don’t afford yourself too much freedom on pricing. You will end up crippling yourself in a quagmire of complexity.

The whole discussion is worth a watch or a listen.

And it's worth noting that since this aired, the company Des co-founded, Intercom (and Fin) sold to Salesforce for $3.6 billion.

Why individuals have an incredible advantage over teams when building software

If you want to go fast, go alone. If you want to go far, go together.

I’ve written about building software (primarily web-based software for small businesses) many times in the past.

It’s pretty much the only thing I’ve ever done.

There has been more change in the last two years than the last twenty combined.

Thanks to AI, the processes and methods and tools have changed unimaginably, and continue to do so.

But what amazes me is that many people — and many businesses — have barely changed at all.

Both in small teams and large ones, I still hear timeframes quoted in months for building features that could be crafted in days.

It’s easy to think everyone is on the cutting edge if you’re someone who enjoys checking the latest releases of each model, seeing what the Hacker News community have to say about every new AI developer tool, or have spent any time building things with AI recently.

But most of the world isn’t yet doing that.

Most people work in teams and many work in teams at bigger businesses. From what I’ve seen, the structures in place at most larger businesses are largely incompatible with — or at least are limiting — how they can truly embrace AI to build software.

The current (old) way

The old way of building software often meant doing something along the lines of the following:

  1. Talk to users.
  2. Digest their feedback and figure out what to build.
  3. Design a prototype (often a wireframe).
  4. Hand over a written document and a wireframe to developers to build out.
  5. Do some more design to polish up what the developers have built.
  6. Get the thing deployed and live on a server somewhere.
  7. Go back to your users and see how they like it.
  8. Depending on what the users say, go back to step 2 and repeat.

Every step of that journey could take hours if not days… if not weeks.

In an early-stage startup, that is time you don’t have. One of the most critical processes to speed up is that loop of feedback > build > ship.

But when the steps in between can take hours or days. Communicating and translating ideas into actual built products is extremely hard. Yes it may take a week to deploy a new database but have we accounted for the days of discussion between product and engineering to make sure its clear why we need that database and what it should do and what it’s strengths and weaknesses are and how much it’ll cost?

The advantage of the individual

I think individuals have a tremendous advantage right now because they don’t need buy-in and they don’t need to agree with anyone but themselves.

You could also see that as a disadvantage. Sometimes you need to be told no. But more often than not, you need the market to tell you that, not the developer.

I'm

John takes over from Tim

Today is the day John Ternus takes over from Tim Cook as CEO of Apple.

I thought it was interesting to read Apple’s own biography of Tim now he’s Executive Chair of the Board of Directors — it’s a brief summary of the last 15 years at Apple.

I was pleased to see a few highlights that really go against the grain of the general business narrative in 2026:

Under his leadership, the company reduced its carbon footprint by more than 60 percent below 2015 levels during a period in which revenue nearly doubled.

As well as

He pushed for continued innovation in the accessibility space, believing that Apple products should be made for everyone.

And

He made central to his leadership the notion that Apple should be a place where everyone can feel they belong and where everyone is treated with dignity and respect.

I truly believe Apple’s success has been because of these core beliefs and values, not despite them.

It’s an extremely tough act to follow, but I’m excited to see John Ternus take the lead at Apple.

I’ve never tired of following Apple, from the thrilling and awe-inspiring tenure of Steve Jobs, to the calm yet explosive growth under Tim Cook.

Next week, Apple will hold their first event led by John Ternus as CEO, where they’re set to unveil their first ever foldable iPhone.

What will set it apart? Why would anyone want it? What will make it truly Apple?

It’s the dawn of a new Apple, and all will be revealed soon. I can’t wait!

Dirty business

In February of this year, Channel 4 released Dirty Business an incredibly well produced, and hard-to-watch dramatised series about the dire state of "public" water in England. It's based on true life, real data, and heartbreaking real events .

Since the 1980s, water has been privatised in England, meaning instead of it being in the government's control, it is now under the control of for-profit organisations like Thames Water, Southern Water, and South West Water, who have, for the most part, left their infrastructure to fall apart, while ensuring "customers" (everyone who lives here) pay ever more for the privilege.

A huge focus of the program is the heartbreaking impact that pollution and spills have had on local habitats and environments, leading to countless issues for wildlife, and human illnesses and deaths. Of course, these have all been challenged and questioned by the heavily lawyer-ed up water companies themselves.

The show is beautifully shot, incredibly well written, and brilliantly acted. It deserves all the attention it can get. The issues surfaced deserve to be as big of a story as the British Post Office scandal that has been through a similar cover-up and subsequent exposé conveyed through brilliant storytelling and creative efforts.

If you are running short on things to get you angry, then give this a watch. I share it here because I hope that more visibility and awareness will ultimately drive change.

Playing to win

You can’t just boot the ball from the goalie and hope it’ll land in the back of the net on the other side of the pitch.

But that’s what sales efforts can sometimes feel like. And of course that almost never works.

When watching the World Cup final on Sunday I was rather impressed with how Spain played against Argentina.

I’m not the biggest football obsessive, but I enjoyed the match and I have to admit I enjoyed watching a lot of the World Cup.

There’s something that has grown on me over time about seeing 11 people (and many more behind the scenes) come together to achieve something that none on their own could.

Seeing a team play with hunger, patience, and fluidity can give you a lot to think about in the world of business.

After all while any team, on or off the pitch, may have superstars, they can rarely achieve their potential without working together in a unified passionate way.

What the heck does this have to do with sales? Perhaps not much, but a little thought came to my mind.

When you’re trying to sell a service or an offering, it can feel tempting to do what a junior footballer might do: get the ball and hoof it at the goal and hope it goes in.

This is what I see most people do when they’re just starting in sales. They go for the sale almost immediately — before they’ve made any rapport, and before they’ve even established if the other person is at all interested or even the right person to make a buying decision.

Don’t do this.

If it works, it’s because you got lucky. You may win a sales once or twice but it’s not a robust process that will enable you to win in the long run.

Instead you want to take your time. Build momentum, build control, be patient. Don’t rush, and don’t make unforced errors.

If I’ve learned anything from watching the World Cup, to win you must do more than score lucky goals. You must work together as a team, and have patience.

In football, in sales, in business, and in life, you rarely want to just score a goal. You want to win the championship.

20 years of GoSquared

On Tuesday of this week, GoSquared turned 20. Yes, we've been in business for twenty years.

I thought it was the perfect excuse to resurrect the Lost and Founder podcast to reflect on our journey to this point.

In this long-overdue episode, I share 8 lessons from building GoSquared: on team, leadership, and focus. And I dropped in a few inspiring quotes for good measure.

On team

  1. Never underestimate what a small group of focused, aligned, motivated people can do. 
  2. Celebrate the small wins. Have fun along the way.
  3. Most meetings don’t need to happen.
  4. Knowing yourself is a superpower.

On business and leadership

  1. Simplicity is a war.
  2. If you think you’re repeating yourself too much, repeat some more.
  3. Focus is impossibly hard, but without it you’re doomed.
  4. Just do it.

To see more about our 20th birthday, you might also want to check out:

Thanks, and after this reflection, here's to the future!

Listen here:

Or watch it on YouTube:

When should you separate “growth” and “product” in a startup?

In the summer we removed any concept of a “growth” and “product” department at EcoSend.

I should say “department” is a loose term. We aren’t a big team (less than 10 people) so the terms mostly applied to meetings, and areas in our tools like Slack for chat and Linear for project management.

The distinction between the two was starting to cause more issues than it was solving.

The problem with separation

I found myself asking questions daily:

  • Is this a growth thing?
  • Is this a product thing?

Those questions can be helpful in a larger team.

But at our size, the primary thing I care about is: What will this do for the business? How will this make things better for our customers?

And often the answers to those questions don’t naturally fall into one bucket or the other.

What’s a product thing if it’s not about growth, for a team of our size?

How do you classify and prioritise a product feature that’s designed to help us grow? Like a viral loop or a public facing design change?

With the two concepts labelled separately, a lot of the most valuable work fell through the cracks.

Almost everything one could label “Product Led Growth” (PLG) was in the middle. And it rarely got done!

We needed to change, and thankfully as a small team, changes like this don’t have to be a big deal.

The results so far

We removed the distinction over the summer and it went far more smoothly than I expected.

What we’ve shipped since this change: 

These are the real results.

But I’m just as excited about the underlying changes, behind the scenes.

As a team we are now prioritising as one. One list, with a focus on impact.

We are uncovering problems that used to get passed around — yes even in a small team — and actually discussing them and finding a solution.

When coming up with ideas or reporting a problem, there was an overhead on every addition to Linear: where do I put this?

Now it’s all in one place. The prioritisation and decision is separate, and weighed up against everything, not an isolated set of priorities in one part of the business.

Some of this likely sounds obvious.

Or maybe you’re reading this thinking “hah! There’s no way that will scale!”

You’d be right to have either of those opinions.

Yes it’s quite obvious for us, but obvious solutions can stare me in the face for months before I try them. And often the change is not as bad as my worst fears.

I don’t believe this would scale to a team even with 10 people. But as I’ve noted in the past, referencing the wonderful Joel Gasgoine of Buffer: there’s an optimum level of process for any company. And too much,

34 lessons

I’m turning thirty four years old. I had been meaning to write a post on my birthday for at least four years, so it’s long overdue that I get my typing fingers out and commit myself to writing this.

Let me be abundantly clear: these are not lessons I have fully learnt. But they are lessons that I hope will prove as useful to you as they have to me.

What started as a ”30 lessons at 30” post has turned into “34 lessons at 34”.

Which is a wonderful tee up for lesson one…

1. Start today

The best time to plant a tree was thirty (four) years ago. The second best time to plant a tree is now.* Get started and stop thinking you're too late.

2. Get a coach

Find someone who can support you, listen to you, never judge you, and help you be the best version of yourself. I have worked with a coach on and off for the last four years. In that time I have become clearer than ever about what I want from life, I have co-founded a new endeavour, proposed to my partner, become fitter and healthier than ever before, and I feel more comfortable than ever in my own skin. For me, coaching has given me the space I didn't realise I needed to explore and articulate my thoughts. You can solve so many of your challenges if you give yourself the space and ask the right questions.

3. Wake up earlier

Wake up early — you can be a morning person if you fix your evenings. I believe I am naturally a night owl, but I love an early morning when I can do it. Earlier dinner, earlier bed-time, reducing screen time, and a consistent routine seem to be the path to earlier mornings for me.

4. You can run a marathon

You can run a marathon, but you need to put some trainers on first. Master putting your kit on and the rest will get easier. I still don't really think of myself as "a runner", but I find immense satisfaction from running.

5. Write a diary

It’s therapeutic and develops like a second brain. I can look back on any day in the last year and recall the tiniest details I noted down. Magic. Much like coaching, it enables me to clarify my thoughts and spot patterns in how I approach situations.

6. Take a break

Take a break – don’t quit. One day may be all you need to check in with yourself and get yourself back on track.

7. Overnight success is easy

Overnight success is easy once you’ve spent years (or decades) practicing, building, failing, and learning.

8. Build habits

Build habits a day at a time. This applies to both good and bad habits. Acknowledge what triggers both, and try to avoid living on autopilot with all of

It just works

There’s a saying, much popularised by Apple, that distinguishes certain products:

"It just works."

It seems like a very low bar on the surface, doesn’t it?

Surely every product works, to some extent.

“It just works” only becomes a selling point when you consider how much hassle most products are to use.

Remember the last time you bought anything significant — was it entirely effortless? Was it a pleasure? Was it obvious at every step what you needed to do to start getting value from it?

I think this concept applies to services and experiences as well as products. I've written before about the experience of using my gym for the first time. And there are plenty of restaurants and hotels I've been to that fall short of the mark when judging them by the "it just works" assessment.

I don’t believe these are exhaustive, but here are a few principles that come to mind for building a product or service that just works:

  1. “It just works” means a lack of cruft and complexity.
  2. "It just works" means the product is reliable and consistently so over its lifetime.
  3. “It just works” means the maker has an opinion.
  4. “It just works” cuts to the chase, and gets the user to their desired outcome as quickly as possible.
  5. “It just works” eschews end-user choice for simplicity and obviousness.
  6. “It just works” means prioritising the primary function of the product above all else, even if that is at the expense of other meaningful uses.

These are easy to write, but very hard to achieve in a team building a real product.

It begs the question, then, why do so many products and services not “just work”?

I believe most products on the market exhibit some combination of the following:

  • A lack of care. The designers and makers just don’t care enough about the end user.
  • There is a misunderstanding of the core purpose of the product.
  • Feature creep. In a drive to make the product more attractive to more people, extra features are added in.
  • Short-term financial incentives drive cost-cutting and profit over product quality.

There are too many products that fall short of the "it just works" goal. Fortunately, that leaves tremendous opportunity for makers willing to go the extra mile.

A few products I’ve used recently that just work:

  • Granola — we’ve all been on a Zoom call that has had some form of AI note taker unexpectedly join. We’ve all experienced how useless a transcription can be. And we’ve all tried taking notes from a meeting only to find we either weren’t paying attention or missed a critical piece of information. Granola is the first note taker I’ve found that truly “just works”. You install it on your Mac, there are no awkward bots, and the results I've seen have been exactly what I wanted. It just works!
  • The Journal app — one of

Two Clothes Hooks

It has flown by, but one of my highlights in January was attending the Better Business Summit in Manchester.

Inspired by the Better Business Summit

It’s an annual gathering of inspiring people running businesses small and large, all finding ways to do business in a better way. There were conversations on all the topics you might imagine — paying staff fairly, making products with sustainability in mind, and questioning what each of us can do to both sell and shop more thoughtfully.

Rather than relay the whole thing here, go check out the post I wrote on the EcoSend Blog about the Better Business Summit.

Patagonia, clothing, and going back in time

One of the images that has stuck in my mind since the Summit was from the impossible-to-pronounce Patagonia movie about how our habits around buying clothing have changed over the last few hundred years.

There was a time, some years after we evolved from Neanderthals, but some years before today, where we had clothes, but significantly fewer.

There was a time where each of us had just two clothes hooks.

One hook was for our everyday clothes — the ones we wore to work the land and around the house for six days of the week.

The other clothes hook was for our special clothes — the fancier of the two options that would be worn to church on a Sunday — that we kept clean and pristine.

Some years later, supposedly the French aristocracy invented something called “fashion” and it’s all gotten a bit out of hand since then.

In today’s world of fast fashion, things have changed somewhat. Even compared to 1980 (quite recent in the scheme of things), as a percentage of household spending, spend on clothing has halved, while the number of items purchased has more than doubled.

What can I do about it?

It prompted me to ask, not just for my clothes, but for all aspects of my life: do I need as much stuff?

What do I need? What do I want? And what can I give to a better home?

Last weekend I found it therapeutic to clear out over 30 items of clothing, sending them all to the local charity collection.

I now have much more space in my wardrobe. I can see more easily what I have. And I appreciate the clothes I kept.

And I still need a LOT more than just two clothes hooks.

Other things

Reflecting on 2024

As is often the case, the Christmas period was a busy one, full of delightful moments with loved ones. I wanted to write a little about 2024 in 2024 but, predictably, I ran out of time.

We are just teetering on the edge of ”Happy New Year!” being a stale greeting, so it’s now-or-never for me to share a look back at 2024 and jot thoughts down about the year ahead.

Highlights of 2024

2024 has been a momentous year for me, with some life-defining moments I will never forget.

Engagement

I don’t think my partner would forgive me if I didn’t put this at the top of my list.

In January I took a trip to Rome and proposed. In fact, it was on this very day last year.

It felt like a dream, and was a moment I had envisioned for a long time. Somehow I managed to keep it secret, even though my partner fiancée is a rather impressive detective!

There's not a detail about the weekend I would change. It underscored my love for the person I am choosing to spend my life with, and for Italy!

Running and exercise

Accountability

Both 2023 and 2024 have been big years for my exercise regime. Early in 2023 I began working Daily Body Coach, run by a friend of mine. The experience has driven me to achieve things I never thought possible. I've transformed my attitude to fitness, to eating, to routines, and have been blown away by the results.

While DBC was not specifically about running, it clearly had an impact here. I have written about running before, and while I didn't run a marathon in 2024 it was still a personal-record-breaking year for me.

Half marathon

I took part in the Royal Parks Half marathon and completed it in my fastest time yet. I wrote a piece shortly after this about why I run.

The Hardest Mile

I also completed an event called The Hardest Mile. It's hard to describe this as anything other than ridiculous. The challenge is to get around a running track four times in an hour. Does that sound hard? No. Not until you add in the small detail of how you get around each lap:

  1. Burpees
  2. Lunges
  3. Bear crawl
  4. Run

It was brutal! Once it was over, and I made my way home on a rail replacement bus service, I reflected. When I was at school, or even just a few years ago, I would never have even contemplated doing something like this.

Parkrun

Parkrun has also been a mainstay of my weekly routine. Almost every Saturday, I get down to my local park and run 5km.

If you've never heard of Parkrun, I can't recommend it enough. It's a free, community event where you can walk, jog, or run 5km around your local park. You can volunteer or spectate as people make their way around,

The joy of creation

Lately I have been conflicted in where I spend my time.

I love creating things. But I also love building a team, leading, marketing, and selling.

There have been patches of time where I have done very little creation, and in those periods I realise I quickly become demoralised.

I find joy in creation.

For as long as I can remember, I have been in awe of the idea that anyone can grab a computer, connect it to the internet, and build something. And that someone else on the other side of the world can then utilise and benefit from that thing.

Anyone can create something of value, and you don't need to ask anyone else for permission.

Creating vs publishing

I don't just like creating, I like publishing.

Don't get me wrong, publishing can induce immense fear.

But I get a kick out of directly creating something and then putting it live.

Getting feedback is addictive — whether it's seeing usage, receiving comments, or simply knowing "it's out there".

I sense that the act of creating is never complete, but publishing (or shipping) is a marker to say: I've completed the first step.

"Publishing" can mean anything here — deploying to production, putting a blog post live, hitting send on a Tweet or Thread, or even just writing an idea down and sharing it with your team.

The critical benefit of "publishing" is that you not only get to call your work "done" for now, you get to receive at least a little feedback: did anyone care?

Speed vs perfection

There's a study I read a while back in the book Art and Fear that summarises the dichotomy of aiming for perfection:

The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality.

His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pound of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot – albeit a perfect one – to get an “A”.

Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the “quantity” group was busily churning out piles of work – and learning from their mistakes – the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.

Ever since I read this, it changed my views on perfection.

"Quick and scrappy" is often viewed as "not the proper way". The proper way is to do X and Y and

Olympic precision, and advice from Sam Altman — weekly roundup

Last week I shared a post summarising what I had learned in the week.

I found it helpful for myself, and hopefully it may be at least mildly interesting for others too.

Here’s a few things I found interesting this week.

An incredibly densely packed set of wisdom from Sam Altman. I found this very motivating to read:

7 frameworks Sam Altman wishes someone told him earlier

I found this via Joel Hansen of Napkin Notes.

  • Getting an idea off the ground: “Optimism, obsession, self-belief, raw horsepower and personal connections are how things get started.”
  • Thinking long term: “Cohesive teams, the right combination of calmness and urgency, and unreasonable commitment are how things get finished. Long-term orientation is in short supply; try not to worry about what people think in the short term, which will get easier over time.”
  • Hiring: “Spend more time recruiting. Take risks on high-potential people with a fastrate of improvement. Look for evidence of getting stuff done in addition to intelligence.”
  • Coworkers: “Working with great people is one of the best parts of life.”
  • Making bets: “Concentrate your resources on a small number of high-conviction bets; this is easy to say but evidently hard to do. You can delete more stuff than you think.”
  • Wasting time: “Fight b*llshit and bureaucracy every time you see it and get other people to fight it too. Do not let the org chart get in the way of people working productively together.”
  • Time: “Fast iteration can make up for a lot; it's usually ok to be wrong if you iterate quickly. Plans should be measured in decades, execution should be measured in weeks.”

Other things this week

  • The first week of the Olympics in Paris has been incredible. Beautiful venues, Paris at its best.
  • I’m blown away by how little separates Olympic athletes between a gold medal and no medal. The men’s 100m final separated gold from silver by just 0.005 of a second.
  • We wrapped up July at EcoSend and it was a busy month.
  • I figured out how to add the Lost and Founder to YouTube. A while ago I started sharing my deepest darkest thoughts as a founder. I haven’t published in a while but I’m hoping to change that. I’ve just started posting old episodes to YouTube to give them a new lease of life. Stay tuned to YouTube for more.
  • I’m excited for something new for GoSquared next week. Stay tuned!

A quote for the week ahead

"The ultimate form of preparation is not planning for a specific scenario, but a mindset that can handle uncertainty." — James Clear

P.S. If you’re receiving this via email, you might notice it’s not sent from EcoSend. I’ll be changing that soon!

A few things I learned this week

A handful of things I learned in the last week:

  • Carpetright was taken (back) over by its original founder, Lord Philip Harris who grew up in Peckham near where I live. He started with a market stall in Peckham, and built it up over time to become the most successful carpet retailer in the U.K. The story of the takeover and Lord Harris’s empire is outlined in The Times. It’s also available to Apple News+ subscribers.
  • By switching to using a compostable toilet you can save 27,000 litres of fresh clean drinking water per year.
  • I was on the “Can marketing save the world?” Podcast talking about EcoSend and responsible email marketing.
  • Nestle built a supermarket on a barge to sell confectionary to communities along the Amazon river. Years on, these local communities have experienced greater rates of obesity as locals began to prefer processed foods over their native diet. I learned this while reading the truly life-changing book: Ultraprocessed.
  • The Olympic opening ceremony for the Paris 2024 games happened on Friday. Despite many dismissive reports of the ceremony, I thought it was full of incredible moments. The Eiffel Tower looked stunning, and I have no idea how they have achieved the floating balloon for the Olympic cauldron!

A quote for the week ahead

"If you want to kill any idea in the world, get a committee working on it."

— Charles Kettering (an American inventor and the holder of 186 patents)

What sells? Climate or ROI?

Climate vs ROI

What sells? 🌍 Climate, or 💰 ROI?

In the world of sustainability, what *actually* sells?

Is it a friendly, climate-focused tagline?

Or is it cold, hard business return-on-investment?

As someone who’s been leading with a sustainability focused message for over a year, just asking that question makes me feel a little uncomfortable.

When selling a product in a crowded market, you always need to stand out from the rest of the industry. And it’s hard to dislike a more sustainable alternative.

Standing out from the industry tends to mean leading with a proposition that is different. If everyone else leads with a pitch around ROI, then how do you lead with a pitch on ROI and still maintain differentiation?

I recently had an inspiring conversation with Tim Schumacher who put the question to me: do people buy based on environmental benefits or business benefits?

What gets you in the door might not be what gets you bought.

From what we’ve seen at EcoSend, leading with a pitch around climate is a fantastic way to drive awareness and attention, and it expresses our values in building the most environmentally conscious email marketing platform in the world.

However, leading with an environmental pitch doesn’t always drive business.

In fact it’s a challenge I’ve heard many times from other founders in the climate space — people love the idea of changing the world for the better, but when push comes to shove the business decision almost always wins out.

That business decision might be:

  • Switching will take time, so we’ll stick with our current tool.
  • We will go with the most trusted brand, to avoid unnecessary risk.
  • There’s a specific feature we need that your product doesn’t have.
  • We can get this cheaper elsewhere.

Fortunately with many environmental focused products and propositions the trade-off of climate vs ROI doesn’t necessarily need to exist.

Often what is better for the environment is also the more effective, more impactful decision for the business.

The challenge is finding the right balance between communicating your climate focus while driving awareness of business impact.

It’s something we’re going to experiment with more at EcoSend — by focusing on sustainability, we’re building a highly optimised, efficient platform where your emails are much more likely to get delivered, opened, read, and actioned.

Can we ultimately drive more people to a climate conscious solution by leading with a business focused pitch?

We’ll find out.

An interview on the Misfit Founders podcast

The incredibly generous and supportive Biro Florin recently invited me on his show Misfit Founders.

The show was filmed in his beautiful house in Brighton, UK, and we chatted about building a SaaS business, and a whole lot more.

It's the first time I've spoken at length about our work on EcoSend and how GoSquared fits into a bigger picture more than ever.

It's a very long show (the best part of two hours!) so if you have the time, I hope you enjoy it.

Thank you Biro, for inviting me on, and helping to set my life goals for a podcasting setup like yours!

Where do you find inspiration to write?

Every so often, I feel at a loss when trying to figure out what to write about.

I frequently feel uninspired and lacking in ideas, so I will go weeks, possibly months without writing.

But there’s a great source of material I haven’t turned to enough: questions.

Whenever I speak at an event, or meet another founder, or really, anyone, I’m usually thrown a question of some sort.

I’ve started to note these questions down, as they’re the perfect starting point for topics to write about.

I’ve found that writing answers to questions I’ve been asked has three valuable advantages:

1. Writing addresses my frustration

If I had more time, I’d have written a shorter letter. — Blaise Pascal

When I’m asked a question, typically I must think on my feet.

Occasionally, that works OK. But sometimes, about 2 minutes after I’ve answered the question, I’ll realise I had something better to say on the topic.

There’s no rewind, or “edit” button for live conversation.

It can be incredibly frustrating!

By retrospectively writing an answer to questions I’m asked, I can address my frustration by giving a better answer.

2. Writing helps form better answers

I find writing to be a fantastic way to clarify my thoughts.

It forces me to consider something on a deeper level. The act of writing can crystallise a topic for me.

It’s correlated to the way I like to learn: if I must teach someone about something, it will absolutely force me to learn more about that thing.

I’ve often found that teaching others is the best way to teach myself, but it always feels like cheating!

3. Writing multiplies my impact

I’d like to think another benefit of turning these questions into written articles shared here, is that I can be more helpful to you, the reader of this blog.

When I have a chat with a friend, or when I am fortunate enough to speak at an event, I often think “gosh I wish that was recorded, the conversation could have been very helpful for more people.”

A wonderful thing about writing is it tends to last a lot longer than audio or video. It’s easier to find via search, and can more easily be edited to bring it up to date.

Some questions I have written answers to

Some questions I need to write answers to

  • Why are you building an email marketing tool, when it’s one of the most crowded markets you could possibly enter?
  • What’s driving you after so many years to keep doing GoSquared?
  • How have your values influenced your decisions and lifestyle recently?
  • What advice do you have for someone starting out on their own startup journey?

Do you have a question for me? Please

Measurement, goals, and instinct

“Not everything that can be counted counts. Not everything that counts can be counted.” — Albert Einstein

A friend shared a fantastic podcast episode with me today: Brian Chesky of Airbnb on Steven Bartlett’s show, “Diary of a CEO.”

Brian shares his journey building Airbnb and covers many of the low points and personal challenges of being a founder, grappling with balancing work and friendships, and a lot more. I highly recommend giving the episode a listen.

Something Brian also talked about creativity, instinct, and measuring success.

He highlighted that Airbnb is one of the few companies in the Fortune 500 with a designer and creative talent in the boardroom.

The world of business has come to praise measurement and financials more than creativity. Yet, the world is changing faster than ever, requiring ever more creative thinking to adapt and change.

I’ve always struggled with balancing instinct, creative ideas, and doing bold but immeasurable work against the “proper” way to do things: small, measurable experiments, data-driven decision-making, and focusing on ROI.

It reminded me of a quote I read a while ago from David Ogilvy:

“I notice increasing reluctance on the part of marketing executives to use judgment; they are coming to rely too much on research, and they use it as a drunkard uses a lamp post for support, rather than for illumination.”

Why put craft into anything if you can’t prove it makes a difference?

Why go the extra mile to make things “just right” if no one seems to care?

Brian’s suggestion is to not try to measure it.

As soon as someone passionate about their craft has to justify making their work as good as it can possibly be, they should probably move on.

Craft and creativity must be baked into your company’s culture. As a leader, you are the one that sets and reinforces that culture in every action you take.

The whole conversation inspired me. Speak up for what you believe in a little more.