A lot of startup pain is self-inflicted. Not the "market is hard" kind. The "we decided to reinvent payroll because vendors are for cowards" kind.
I've sat through enough co-working space conversations about disruption to know the pattern. Someone pitches an idea, gets funded, then spends six months rebuilding payroll because "vendors are for cowards." The product dies while they're still debugging their custom payment pipeline.
In 2019, I worked at a company where the product was genuinely interesting. The team was sharp. Then the CTO decided we needed a custom payroll system. Gusto existed. ADP existed. But those weren't "ours."
Disrupt the thing that makes you money. Leave payroll alone.
Payroll: Pay People. On Time. Every Time.
Payroll has one job: pay humans correctly and on time. That's it. It's not a branding opportunity. It's not a "platform." It's not a chance to show off your love of event-driven architecture.
If payroll fails, your culture evaporates.
People will tolerate a lot of startup chaos. Weird priorities. Shifting roadmaps. A CEO who thinks "transparency" means posting vague threats in Slack. But they will not tolerate "my rent check bounced because your cron job failed."
I watched one startup wire payroll manually for three months. By month two, their senior engineer quit mid-sprint. By month three, half the team was interviewing elsewhere. Manual wires sound scrappy until your best people realize you can't handle the basics.
Use Gusto. Use ADP. Pick one. Pay the invoice. Move on.
Regulatory Compliance: The State Does Not Care About Your Vision
I sat in a meeting where a CEO told a California labor board investigator that contractor classifications were "just semantics." The investigator pulled out a three-ring binder and asked if the CEO wanted to debate semantics or write a check.
The acronyms don't care about your vision either:
- HIPAA if you touch health data
- GDPR if you have EU users
- PCI if you store credit cards (and you probably shouldn't)
I've watched auditors sit through pitch-deck energy explanations of "our compliance philosophy" and respond with "show me your access logs." They don't care about your burn rate. They want documentation, not vibes.
If compliance isn't your product, buy the boring solution and follow the boring checklist.
Accounting: Don't Invent Alternative Math
Accounting exists so outsiders can trust your numbers. Investors. Acquirers. Banks. The IRS. People who don't want to learn your special snowflake revenue model.
The fastest way to kill an investor conversation is pass-through revenue presented as growth.
If you do $1M in revenue but $900k immediately goes to a partner, you didn't build a rocket ship. You built a pipe.
Pipes are useful. Just don't sell a pipe like it's a rocket.
Infrastructure: Your Custom Platform Is a Knowledge Silo With a Bill
In 2021, I watched a team spend fourteen months building a custom Kubernetes setup. By the end, three people understood it. Two of them quit within six months.
It "worked," in the sense that it consumed money monthly and generated fear daily. Every deploy was a small religious event. Vacations were myths.
Use defaults:
- Pick AWS, GCP, or Azure (just pick one)
- Standard IAM
- Standard monitoring
- Standard backups
- Managed databases unless you have a real reason not to
You want a stable foundation, not an internal platform that requires a priesthood.
I'm writing this on a custom Python blog running on a hand-built Linode cluster, so do as I say not as I do. The difference is I'm not running payroll on it.
Customer Service: Don't Replace Humans With a Maze
LLMs are great for support assist work:
- Drafting replies
- Summarizing tickets
- Routing issues
- Pulling context from docs and past threads with vector search
But "remove humans entirely" usually means you relocated work to the customer. People notice. They get mad. They leave.
A SaaS company I consulted for in 2023 replaced their support team with a chatbot. Churn went from 4% to 9% in five months. The product didn't change. The experience did. Nobody wants to argue with a bot after software deletes their data.
The Rule
If it's not how you make money, don't disrupt it.
Outsource the boring stuff to boring vendors who wake up every day excited to do payroll, compliance, and accounting correctly. Let your team spend its limited attention on the thing customers pay for.
Otherwise you'll be the startup that disrupted payroll into a lawsuit while your actual product sits unfinished because everyone was debugging the custom payment cron job.
This is one of those patterns where building stable systems that don't rely on motivation matters more than disruption theater. When you're recovering from catastrophic failure, you want boring infrastructure that just works—not custom platforms that require heroics to keep running.
-Sethers