These posts are not written in one sitting. They come from years of captured fragments: thousands of phone notes, voice memos recorded on dog walks, a thought caught right after a client call, and the odd shower idea, finally drafted into the long version. This one is a thank-you to the people who read them.
- The raw material is collected constantly and assembled later, not brainstormed from a blank page.
- The blog has reached more than 50,000 readers across 80-plus countries.
- The free tools have been run more than 2,500 times, with the result shown before any email is asked.
- Operators and writers I respect, including Aishwarya Iyer of Brightland and the Scaling Apps newsletter, have pointed their own audiences here.
This one is different from the usual post. No framework, no teardown. I want to pull the curtain back on how these get written, and say thank you to the people reading them. The honest answer to "how do you write so much" is that I do not, exactly. I collect constantly and assemble later.
Most of what ends up here started as a fragment I caught months earlier and forgot about. A note typed with one thumb in a parking lot, a voice memo from a dog walk, a line scribbled right after a client call while it was still sharp. The writing part is mostly connecting fragments that were already there, then doing the work to make them useful to someone else.
So this post is two things at once. It is the behind-the-scenes version of the process, for anyone who has asked how it works. And it is a real thank-you, because a blog with no readers is just a journal, and this one has turned into something a lot better than that.
Over fifteen years of
notes, finally used.
I have been taking notes on this stuff for a long time. Over more than fifteen years, through building the Shopify Partner Program from the inside, running brands at WIN Brands Group, and selling getuptime.co to Tiny, I kept a running pile of observations: things that worked, things that quietly did not, patterns I noticed across dozens of brands and apps that nobody seemed to be writing down plainly.
For years that pile just sat there. Tens of thousands of notes, most of them never reread. The blog started as a way to actually use them. To take the scattered, half-formed operator instinct I had been accumulating and turn it into something a real person could read and apply, instead of letting it die in an app I never opened.
Here is the thing fifteen years of notes actually taught me: the problems repeat. The brand stuck at $5M, the app bleeding trials, the enterprise team that cannot move fast enough to matter. I have watched the same patterns play out dozens of times, just wearing different costumes. That repetition is the quiet advantage I bring to clients. They get the discoveries I already made and the mistakes I already paid for, which means they skip the expensive version of the lesson and go straight to the outcome. The blog is the public, generalized version of that. The private version, the one tuned to your exact numbers, is the work I do with a small number of operators at a time.
The other reason is simpler. I like writing things that I wish had existed when I was in the seat. When I was running a brand and trying to figure out the real shape of a problem, the available content was either a vendor pitch in disguise or a thin summary by someone who had never done it. The bar I hold to is that every post should be something only a practitioner could write. If you want the long version of that argument, it is in how I built this blog audience from zero.
Capture constantly,
assemble later.
Here is the part people ask about most. There is no single writing session where a post appears. There is a capture habit running in the background all the time, and then a separate assembly step where the fragments get pulled together and shaped. The two are deliberately kept apart.
Capture is messy and constant. The best ideas almost never arrive at a desk. They show up on a walk, mid-conversation, or in the shower, which is exactly when you cannot write properly. So the job in the moment is just to catch the thing before it evaporates, in whatever crude form. Cleaning it up comes later.
| Source | What it captures | Why it works |
|---|---|---|
Phone notes | Thousands of one-line observations typed on the spot over the years | Zero friction. The thought gets saved before it is lost, even if it is rough |
Dog-walk voice memos | Longer thoughts talked out loud while walking, no screen involved | Speaking is faster than typing and the argument comes out more naturally |
Post-call notes | A few lines written right after a client or advisor call | The real, specific question an operator is wrestling with, while it is fresh |
Shower thoughts | The angle or the framing that finally makes a messy idea click | The brain connects things when it is not trying. Catch it the second you are dry |
Assembly is where it becomes a post. I will look at a cluster of related fragments, a few phone notes, a voice memo, the thing a client kept asking about, and realize they are all circling the same idea. That is the moment a post exists. The draft is mostly arranging those pieces into an argument, filling the gaps, checking any numbers, and cutting everything that is not pulling its weight.
"The writing is not the hard part. The capture is. A good post is usually three forgotten fragments that finally found each other."
The voice-memo step is the one I would recommend to anyone. Talking an idea out on a walk gets you past the stiff, careful version you would type and into how you would actually explain it to a friend in the industry. A lot of what people tell me reads like a real person on this site comes straight from the fact that the first draft of the thinking was spoken, not typed.
Working through a messy operating problem and want someone who has actually run it to think it through with you? The form takes two minutes.
People, in eighty
countries, reading.
I want to put the actual numbers here, because they are the reason this post exists at all. These come from the site's own analytics, not a vanity estimate, and they still surprise me. A pile of notes I almost never reread has turned into something that reaches people I will never meet, in places I have never been.
| Measure | Where it stands | What it means to me |
|---|---|---|
50,000+ readers | More than fifty thousand unique people have read the site | Each one chose to spend attention here. That is not nothing, and I do not treat it as nothing |
80+ countries | Readers in more than eighty countries around the world | Commerce problems rhyme everywhere. The specifics differ, the operator instinct travels |
2,500+ tool runs | The free calculators and the Store Audit have been run thousands of times | People are not just reading, they are plugging in their own numbers and acting on them |
The countries number is the one that gets me. I write from a fairly specific vantage point, the Shopify ecosystem seen from the employee, partner, and merchant seats. To find the same operating questions landing for a founder on the other side of the world is a reminder that the work is more universal than it feels day to day.
Some of the places this has reached still surprise me. Alongside the United States, Canada, the United Kingdom, India, and Australia, the writing has found readers in Nepal, Benin, French Polynesia, Andorra, Barbados, Montenegro, Honduras, Cambodia, and Uruguay. Commerce turns out to be a language operators speak everywhere, and watching the posts get passed across borders and languages is the part of this I did not see coming.
Thank you to every one of those readers. Wherever you are reading this from, the fact that it traveled there at all is the whole reward.
The feedback that
keeps me going.
The part that actually keeps the writing going is not the traffic graph. It is the messages. People taking the time to say a post helped them see a decision more clearly, or sharing it with their own audience, which is the highest compliment there is. A few have meant a lot, so I want to share them here.
Two writers I respect pointed their readers to this work in their own newsletters, which is a different kind of signal than a like. Aishwarya Iyer founded Brightland, which makes the best olive oil in my kitchen, so I was a customer and a fan long before any of this. Seeing her recommend my writing to her own audience was humbling. She referenced the growth-stage piece in her essay on early-stage brand building:
"If you want a really sharp breakdown of what actually changes at each revenue stage, this piece by Taylor Sicard is worth bookmarking."
She was linking to the post on DTC growth inflection points, which maps what actually breaks at each revenue stage. And in the Scaling Apps newsletter, the app M&A breakdown got a generous write-up for founders thinking about exits:
"If you're thinking about exits, acquisitions, or just want to understand how the market is moving, Taylor Sicard published a thorough breakdown worth your time."
That one pointed at the 2026 Shopify app M&A market breakdown. When operators in the trenches treat a post as worth handing to their own people, that is the outcome I am actually writing for.
The comments on LinkedIn and X have been the other steady source of fuel. I would rather not paraphrase them, so here they are: the people, and what they said, grouped by where they showed up.
From LinkedIn
"Just wanted to let you know that I've read quite a few of your articles lately. Some of the best written and thought through content on the Shopify ecosystem. Thanks for sharing them."
Justas Galaburda · Co-Founder, Essential Apps · Oberlo Co-Founder"Taylor you are dropping insane amounts of value on the timeline for free lately."
Nick Selman · VP of Growth, Shoplift"I've been binge-reading your blog a ton lately. It's been super helpful for my company's strategy. I'm sure this article is bound to be another banger."
Tobe Osakwe · Founder, Regios"Love this list, you've inspired me to make one for marketing workflows."
Drew Sanocki · DTC growth advisor"Crazy that you give this content out for free. Thanks."
Zac Cherin · VP & Partner, Simplistic · Co-Founder, Hiro Analytics"Nice work man."
Daniel Patricio · Co-founder, Abra · ex-Shopify PM"Interesting, never thought about it this way. Thank you for expanding my mind."
Suraj Reddy · Engineering, Beacon"A great read. My favorite quote: 'The worst strategy is to keep competing in the same market with lower prices and new features that don't change the fundamental value proposition.'"
Ruben Bristian · Co-Founder, Krown Themes"That opening line is the whole shabang: 'A fractional advisor is the most cost-effective way to put senior expertise on a problem you could never afford to hire for full-time.'"
Michael Bair · CX Executive · Fractional advisor"Operational complexity grows much faster than revenue. The systems, communication, and support processes that work at $1M can quickly become bottlenecks at $5M+. Scaling successfully often means rebuilding the business behind the scenes before the next growth phase."
Mishal Zahra · E-commerce specialist"Retiring the playbook that just worked is the hardest operational discipline there is. The binding constraint shifts first. The infrastructure that served the old stage becomes the thing silently capping the next one."
Ibrahim Shishir · Klaviyo email flows for Shopify brands"Another good read. The order discipline is the part most founders fight, having been through this myself. Two brands with the same CM3 can have very different real margins once you account for buy box ownership and unauthorized 3P seller capture. The P&L won't show it until you read the channel ledger separately."
Justin Taliaferro · Founder, JETT"💙 💙"
Eli Weiss · VP Advocacy, YotpoFrom X
"Taylor, this is awesome writing, loving this streak that you are on. Solidly insightful. Why is this not a podcast btw? Would be even more impactful when it's conversations with existing players that lend rich context to your insights."
Arvind Krishnan · @arvindax"'The $1M milestone requires a first cohort of repeat buyers. A handful of actual customers who came back without being paid to.' Amazing playbook that I wish I'd read earlier."
gxara · @gmxara"These tools cut through the noise and get to real impact. Appreciate the share."
Cirox · @CiroxEth"Read the post on growing a Shopify app to $1M last night and shared it with the team. Great read."
Elliot Kovac · @elliotkovac28"Thank you for this. You open to consulting?"
Cody Gibbs · @codygibbs"Thank you for sharing the sauce."
Owen Martinetti · @OwenMartinetti"Appreciate this, need more of this in the space."
Patrick Bollenbach · @patrickbo11e"You ruined my morning doom-scrolling routine. Now I will have to read this."
SPS · @spsbuilds"Tools like this one are incredibly useful to make sure you are on the right path. Oh, and it's free."
Emmett Naughton · @EmmettNaughton"Bookmarking this for my next app build."
Ella · @Ella_ML_"Taylor knows what he is talking about. Check out his guide, people."
Andrew Le · @andrewle"The goat got a glow-up. Looks great."
Zack Elias · @zaackelias"Listen up, people."
Thomas · @kimurathomasI read every one. They are the reason the next post always gets written, and a big part of why I wanted to put this page together at all.
Built to give an
answer, not a gate.
Somewhere along the way the writing turned into tools. The same operator instinct that goes into a post, the real benchmarks and the math that actually matters, became a set of free calculators. The rule on all of them is the same: you see your result before anything asks for your email. More than 2,500 runs later, here are the ones I am happiest with.
For DTC operators, the one I point people to first is the Shopify Store Audit. Paste your store URL and it scores the things that quietly cost you money. After that, the DTC growth scorecard tells you which stage your brand is actually in, and the profitability calculator and max allowable CAC tool settle the two arguments I see brands have most often. The returns cost calculator tends to surprise people the most.
For app founders, the Shopify app valuation tool is the one that gets shared, especially by anyone thinking about an exit. The churn cost and CAC payback calculators are the ones I would run first if I were building an app today. They are all in the full tools collection, grouped by whether you run a brand or build an app.
Because the benchmarks inside them come from operating and advising real brands and apps, not from generic industry averages, and that is exactly the kind of thing that should not sit behind a form. If a calculator helps you make a better call on your CAC or your returns or your asking price, that is the point. The work speaks for itself, and a few of the people who run them end up wanting to talk through the harder version.
Keep the questions
coming.
The plan is to keep doing exactly this, just more of it. There is still a deep backlog of notes and voice memos waiting to become posts, and the best new topics keep coming from readers. When the same question shows up across a few different conversations, that is usually the next thing worth writing in full.
A few of you have asked why this is not a podcast yet. Arvind, I hear you. It might be, eventually, especially the version where these ideas become conversations with operators who lived them. For now the writing is where the thinking gets done, and the voice memos on the dog walks are about as close to a recording booth as I have gotten.
So if there is something you keep running into and cannot find a straight answer to, tell me. Drop it in the box below, reply to the newsletter, or email hello@taylorsicard.com. A real operator question is the strongest brief I can get. If you want to make sure the posts reach you, the blog and the Commerce Dispatch newsletter are the most reliable way, and the broader map of how I think about all of it is in the 2026 Shopify ecosystem value map.
Mostly, though, thank you. For reading, for sharing, for running the tools, and for the notes that tell me this is landing. It is the reason the pile of fragments became something worth assembling. I am just getting started.
A few things
people ask.
Mostly from captured fragments collected over years: thousands of notes in my phone, voice memos recorded on dog walks, a thought jotted down right after a client call, and the occasional shower idea. A post is usually several of those fragments finally connecting, not a single sit-down brainstorm. The capture habit runs constantly in the background, and assembly happens later.
Yes, and the best ones often come from readers. If there is a question you keep running into as a DTC operator or app founder, email hello@taylorsicard.com or reply to the newsletter. A recurring question from a real operator is the strongest signal that a topic is worth a full post, and several pieces on this site started exactly that way.
Yes. Every calculator and the Store Audit are free, and you see your result before any email is requested. They have been run more than 2,500 times. The numbers behind them come from operating and advising brands and apps, not from generic benchmarks, which is the whole reason they are worth running. Start with the tools collection.
Subscribe to the Commerce Dispatch newsletter on the site, or follow along on LinkedIn and X where I share each post with a standalone take. The newsletter is the most reliable way to get the writing without depending on an algorithm to surface it, and it is free.
Reading along? Let us talk.
If a post has made you think differently about your brand or your app, the next step is a conversation about your specific version of it. I work with a small number of operators at a time.
Start a conversation More about Taylor →