--- title: "Billing, migrations and my first team" url: "https://toddpaulbrownjr.com/writing/billing-migrations-and-my-first-team/" author: "Todd Paul Brown Jr." description: "** Hired into Bluehost billing to absorb two acquired hosts, I learned fast, led training and escalations, and walked out knowing WordPress well enough to…" kind: "article" updated: "2026-09-26T02:50:25+00:00" --- # Billing, migrations and my first team I was hired into Bluehost's billing department to help with something that turned out to be a lot more technical than anyone expected. The company had just acquired JustHost and HostMonster, and somebody needed to figure out how to migrate those customers into Bluehost's systems without breaking their accounts or their billing. That somebody ended up being me. The migration work made what should have been a straightforward billing job into something else entirely. I wasn't just processing payments—I was learning how three different hosting platforms handled billing, domains, and WordPress sites, then figuring out how to correct the processing errors that came up when we tried to make them talk to each other. I learned their systems fast enough that I could fix the errors myself, and that got noticed. Within a reasonably short time, I was promoted to team lead. ## What the team lead job actually was The role had three parts. First, I was responsible for training and education across the team, with a specialty in bypassing system errors for special exceptions—the cases where the normal process didn't work and you needed to understand the system well enough to route around it safely. Second, I handled escalation calls. That included specialized training for resolving payment disputes, and direct coaching on customer relationship management and de-escalating conflict. Those escalation calls were my earliest recorded people-leadership work: learning how to give someone an outcome they could live with when the thing they wanted wasn't possible, and how to do it without the conversation getting worse. Third, I was responsible for SEO and website knowledge across a department of 60-plus specialists. I created and maintained internal documentation about products, features, and processes, and I assisted with sales enablement training to upsell existing customers on SEO services and website performance enhancements. That last piece—the SEO and website enablement work—wasn't in the original job description. It came out of the migration. When you're fixing billing errors for hosting customers, you end up hands-on with WordPress, web hosting, domain registration, and DNS settings. I wasn't just looking at billing info; I was troubleshooting why a site wasn't loading after a migration, or why a domain transfer had stalled, or what happened when someone's SSL certificate didn't carry over correctly. All of that gave me a WordPress and hosting foundation I didn't have when I started. That foundation became the bridge into SEO. ## The morale initiative Somewhere in the middle of all this, the parent company cut a lot of employee perks and benefits. It happened fast, and it hit morale hard across the department. I put together a team morale initiative to try to improve employee retention. The initiative had buy-in from the department head, and it was largely seen as a positive across the team. I don't have a retention number to point to—none was recorded—but the response told me it mattered. Looking back, that initiative was the first time I took on a project that wasn't about fixing a system or training someone on a process. It was about recognizing that a team is held together by more than documentation and escalation scripts, and that sometimes the most useful thing you can do is acknowledge that something changed and people are dealing with it. ## What I carried forward The Bluehost job shows up in almost everything I've built since, even though I didn't see it at the time. Learning a system fast enough to fix its errors became the template for how I approach any new platform or codebase. The job is to understand the process well enough that you can make it run without someone having to remember the workaround every time. Training and documentation were part of the role from the start. I trained a team, and I wrote internal docs for a 60-plus person department. That's the same muscle I use now when I'm writing documentation for LEGION or building onboarding materials for Sadyr—the goal is always to get the knowledge out of one person's head and into a system that survives their absence. The conflict de-escalation and payment-dispute work taught me how to hold a conversation when the stakes are high and the other person is already frustrated. I use that skill constantly, though usually now the conflict is between what a client wants and what the system can actually do, rather than between a customer and their credit card statement. And the bridge from billing to SEO—the one that came out of a migration nobody planned for—taught me that the most interesting work often shows up in the gaps between what a job is supposed to be and what it actually needs. You just have to be willing to learn the parts that weren't in the job description. I left Bluehost knowing WordPress and hosting well enough to move into SEO. That move set the rest of the career path in motion: SEO led to marketing operations, operations led to systems work, and systems work led to building those systems with AI agents instead of hiring teams to maintain them. But the foundation—learning systems fast, training people, writing things down, and staying calm when the process breaks—all of that started in a billing department during a migration that turned a straightforward job into something nobody expected.