Bobby Huang

Writing and Systems Notes

I run Growthy, and I’m a partner at SDO CPA LLC, with 18 years of hands-on bookkeeping and accounting behind me. I was also Head of Growth at vidIQ and Mable, Growth Lead at Archive, and Growth Product Marketing Manager at BlueStacks. Almost everything I write comes out of the day job: the growth systems I build for my own companies and for other people’s, and what actually happens when you point AI at a real general ledger.

I’m Bobby Huang. If you came looking for my writing, this is the index. Two buckets, mostly: growth systems notes, and bookkeeping automation posts. Today most of it sits on LinkedIn, so follow me on LinkedIn if you want it as it goes up. Later it lives here. The topics stay the same either way, so here’s the map, and then the posts worth reading.

What I write about

Growth systems

I build the growth systems my companies run on, then I write about the parts that held up. Not strategy decks. The machinery: how a piece of content gets briefed, drafted, reviewed and shipped without a marketing department, what a small team can automate before it needs another hire, where a publishing pipeline cracks once you push it past a couple of posts a week.

These notes get written from inside the system while it’s still running. If something’s half-built, I say it’s half-built. That tends to be the useful part. The version of a growth system that survives a real week looks almost nothing like the version in the plan.

A lot of it is distribution. Founder-led content, what gets read versus what merely gets written, how an entity page and a LinkedIn feed end up feeding each other. I test all of it on my own brands first, which is why the examples are mine instead of somebody else’s case study.

I write up the calls I got wrong too. I own the companies, so I eat those.

Books and automation

The other half is bookkeeping. Eighteen years of it, and I’m still in real client books at SDO CPA. That’s the vantage point for everything I write about automation. I know what the work costs by the hour because I’ve done the hour.

So the posts stay specific. What breaks when a model categorizes transactions it has no context for. Why reconciliation is the genuinely hard part while categorization gets all the demo airtime. Which prompts a bookkeeper can use on a Monday morning, and which ones produce confident nonsense that takes longer to unwind than doing it by hand.

A third thread runs through both halves: running a firm on AI instead of bolting AI onto a firm. Which parts of a monthly close I’d hand to a model today, and which parts I wouldn’t hand over for another two years. Then the harder question of what a reviewer has to check when the first pass wasn’t done by a person. That thread is the one people argue with me about most.

Growthy is where a lot of this eventually turns into product. The writing is the working-out.

Where it lives now

LinkedIn, for now. Five posts, in the order I’d hand them to someone who wants a fast read on how I think and what I actually work on. They aren’t a series and they don’t build on each other. Each one is whatever I was in the middle of that week.

  • Optimistically random: what automated categorization looks like when the model has no context for the transaction it’s filing. Start here if you want the short version of why the accuracy number on the box isn’t the number that matters.
  • Clicking categorize 500 times a day: the problem all of this automation points at, and why the tedium is the tell rather than the complaint.
  • The $3,847.92 Stripe deposit: why reconciliation, not categorization, is where automated bookkeeping gets its real test.
  • Claude Cowork and the month-end close: an honest read on where a general AI agent is genuinely good and where it stops, which is one folder at a time rather than 30 client books each carrying its own audit trail.
  • Reconciliation is a matching game: the case for clearing the easy matches fast so your attention lands on the one line that is actually wrong. Written while the thing was still being built.

That’s the current body of work.

What’s coming here

The blog lands on this URL. Same two subjects, longer form, and the LinkedIn posts move over as they earn a permanent home. No date on it yet, and I’d rather ship it late than announce it early.

Until then LinkedIn is where I post and where I answer messages. If you want who’s writing this before you read any of it, start there. If a post raises something you want to push back on, message me on LinkedIn.