Latest / Built Not Born with Dr. A / How I run social media for five brands without a team.
Transcript
- 0:00Five brands. Five audiences. And no social media team.
- 0:03ParaReady. Florida Civics Prep. Built To Pass. PrincipalReady. And me, Dr. A. Every one of those has a different person on the other end. A paraprofessional studying at night.
- 0:14A Florida college student who needs to graduate. A district HR leader. A future principal. Different problems, different language, different platforms.
- 0:23If I tried to wing it every morning, I'd be cooked by Wednesday. So I don't wing it.
- 0:29Here's what actually runs behind the scenes.
- 0:31First, every brand gets its own content document, every week. Not one big generic plan.
- 0:37One for ParaReady, one for Florida Civics Prep, one for Built To Pass, one for PrincipalReady, one for my personal brand.
- 0:45They get built ahead of time, so when the week starts, I'm not staring at a blank screen asking what to post.
- 0:51Second, every day of the week has a job. There's a rhythm. Some days teach something. Some days prove it works. Some days send people to a free way in.
- 1:01I'm not inventing the purpose of a post every time. The calendar already decided it.
- 1:06Third, the posting itself runs through a scheduler.
- 1:09Blotato handles the scheduling for every brand, so the work of posting is mostly done once, in a batch, and not scattered across my whole week.
- 1:18And the content itself leans on the rest of what I've built. The scripts come out of my brand voice. The videos come from my voice clone and my avatar, with captions added at the end.
- 1:30So a lot of the production that used to need a team, a studio, and an editor, now runs through a pipeline I set up once and keep improving.
- 1:39That's the part people want to hear about. Here's the part they usually skip.
- 1:44It breaks.
- 1:44A system like this gets posts out the door. It does not tell you whether anyone cared.
- 1:50For weeks I was running this thing and flying blind on the numbers, because the analytics connection wasn't set up the way I needed it.
- 1:58I had a machine that posted consistently, and I didn't have a clear read on what was working. Those are two completely different problems, and I confused them for a while.
- 2:09Consistency is not the same as traction. You can build a beautiful system and still be talking into an empty room. And I've had to be honest about that.
- 2:18So here's what I'd tell you if you're a solo founder or a small team thinking about doing this.
- 2:24Build the system first. Decide what each day is for. Batch the work. Let tools handle the posting. That part is real, and it gives you your time back.
- 2:34But then protect time for the part a system can't do. Looking at what actually happened. Reading the comments. Deciding what to stop doing.
- 2:43Nobody can automate that for you, and if you skip it, you've just built a very efficient way to be ignored.
- 2:49So here's my question for you. If you had to cut your time on one repetitive task in half this week, what would you automate first?
- 2:58I'm Dr. A. Built. Not. Born.