
Your team is doing the work of half its size. I write about why. Co-founder @doxflowy. The fix is in my bio link.
Profitable
Joined March 2015
- Tweets4.7K
- Following855
- Followers1.7K
- Likes572
Pinned Tweet
I started my first business when I was in my early twenties.
Since then, I've built and sold products, hired people who turned out to be amazing, hired people who turned out to be terrible (My fault. I take the blame). And watched processes I built with my own hands slowly fall apart.
The falling apart part is what I want to talk about.
There's this thing that happens in every company. I call it Process Drift.
It looks like this. You set up a 3-step process for onboarding a new client. Works great. Six months later, someone adds a step because of an edge case.
Then someone else adds a workaround because step 2 broke for a specific client. A year later, your 3-step process is 9 steps, and nobody remembers why half of them exist.
Such is life.
Nobody planned it. Nobody approved it. It just... drifted.
Here's where it gets expensive.
I've been auditing teams for the past year. Tracking where hours really go. Not where people think they go. The real place hours go to die.
The average team I look at is losing 20+ hours a week (oftentimes more, depending on headcount) to drift.
That's not a rounding error. That's a full salary.
Your $85k/year ops lead spending 11 hours a week reformatting documents and chasing signatures?
That's $22k a year in misallocated talent. It's painful. It happens all the time.
Your best person who can't take a sick day because the whole system lives in their head? That's not dedication. That's a single point of failure wearing a loyalty costume.
As a founder, as a team lead, as a C-level leader. That's on you.
You may be thinking "my team is different."
No.
It's not.
Really.
It's not.
It's just that you haven't measured it yet.
I write about Process Drift here.
What I'm finding across real companies, what's working to fix it, and what isn't.
This isn't theory I thought up in my office. I'm not yet clever enough for that.
This isn't "10 tips to optimize your workflow." Meh.
I'm just sharing what I'm seeing on the ground. In the trenches.
If you run a team and things feel harder than they should. If you're a solo founder and the grind is soul-sucking.
Look at your processes. Not your people. Not your contractors.
I put together a blueprint for how to reclaim 10+ hours a week. It takes about a week to implement if you take it slowly. A day if you're motivated.
It's in my bio.
77
Daniel Ndukwu retweeted
The tech job market is in its best shape in years. But almost none of the growth is coming from software jobs.
There are 281,000+ open roles at tech companies, up 17% from a year ago and 73% from the March 2023 low.
But open PM, eng, and design roles grew just 2%. Design (−28%) and UX research (−45%) actually shrank.
So where’s the growth coming from? Hardware engineering openings doubled. Business ops added ~4,200 openings. Supply chain is up 63%. Many of the fastest-growing jobs are physical: data center technicians, installers, field service engineers.
The AI boom is creating jobs, but mostly in building and running the physical infrastructure (chips, data centers, hardware), not building software.
Times, they are a-changin’.
Full report: lennysnewsletter.com/p/state…
STATE OF THE TECH JOB MARKET IN 2026
Twice a year, I dig into trends in hiring and job openings. This is the fifth report I've done, and the most surprising yet:
1. PMs are winning in the AI era
2. Engineering demand has stalled
3. Design openings are at a record low
4. Every role now requires AI skills
5. Tech jobs are concentrating in the Bay Area
6. Remote roles are at a record low
7. The tech job market is growing fast, but mostly outside of software (gasp!)
Full report here: lennysnewsletter.com/p/state…
Daniel Ndukwu retweeted
I started UsefulPDF to make signing easy. I built DoxFlowy to give people control.
Get @DoxFlowy
Daniel Ndukwu retweeted
When I and @daniel_ndukwu started building UsefulPDF, our goal was simple: solve a problem. We weren’t trying to create a groundbreaking new product; we wanted to rethink how existing solutions worked and remove the bottlenecks around them.
Today, @DoxFlowy serves businesses across the globe, helping teams save time, increase productivity, and generate more revenue.
One lesson we’ve learned along the way is that time is everything in business, and in life. The more time you have, the more freedom you have. And with that freedom, you can focus on what truly matters: growth, innovation, and creating value.
That’s exactly what DoxFlowy does, gives businesses their time back by eliminating the hassle of creating and managing repetitive documentation.
Every service business I've worked with has the same hidden expense.
It's not software, marketing, or even payroll. Though payroll is where it hides.
It's the time between "yes" and "done."
A client says yes. Then your team spends hours turning that yes into deliverables. Contracts. Onboarding docs. Intake forms. Service agreements. Follow-ups. Signatures. Filing.
The time spent doing all of that is where the deal goes to die. Every hour spent on admin work is an hour where the client can regret their decision or talk to a competitor.
This gap is still present when you’ve signed the client. It’s what makes them think you’re not reliable. It’s what makes it harder to get the renewal.
Most founders have never mapped that gap. They know it exists. They can feel it. But they've never sat down and counted the hours.
When they do, the number is usually 3x to 5x what they expected.
I built a system for shrinking that gap. It starts with identifying exactly where the hours go and ends with workflows that handle the repetitive parts automatically.
Link in bio.
2
36
We get compared to DocuSign on almost every sales call.
Every. Single. One.
"How are you different from DocuSign?" "Is this like DocuSign?" "We looked at DocuSign but it was too expensive." "Our team already uses DocuSign."
For a while, that comparison made me defensive. I'd scramble to list features, explain our pricing, justify why we exist in the same universe as a company worth billions.
Honestly, it was exhausting. Then, I stopped doing that.
Now when someone asks, I say: "DocuSign is great at signatures. We're not trying to be DocuSign. We handle what happens before and after the signature. The document creation, the data collection, the approvals, the filing. The signature is one step in a 12-step process. We handle all 12."
We stopped competing on the feature they're known for and started competing on the problem they don't solve.
The core is that you need to define your own lane. You can’t compete directly with billion-dollar brands, and you don’t need to.
Define your own category or you'll spend your whole life defending your right to exist in someone else's.
Not everything should be automated. I sell automation tools, and I'm telling you this.
Some processes need human judgment. Some need flexibility that a workflow can't handle. Some are so infrequent that the setup time costs more than the manual work.
Here's my quick filter for what to leave alone:
If the task requires a decision that changes based on context every time, don't automate it. You'll spend more time building exception handling than you save.
If the task happens fewer than 4 times a month, probably not worth it. The math doesn't work unless each instance takes over an hour.
If the task is the part of the job your team enjoys doing, leave it. Automating someone's favorite responsibility is a fast way to kill morale.
Automation is a tool. Not a religion. The goal isn't to automate everything. It never has been and never should be.
The goal is to automate the right things so your team can spend their energy on the work that needs a human. The work that needs judgement.
The companies that get automation right are the ones that know when to stop.
1
1
42
Underrated ops advice: the process your team follows day after day is your real process. The one in the wiki is a suggestion.
23
"We already have a system for that."
I hear this on probably 40% of my sales calls. And honestly? Most of the time, they do have a system. It works.
Nobody's complaining.
Life’s good.
So I ask: "Can you show me?"
Then I watch.
The system is usually a combination of a Word template, email, maybe a PDF converter, a shared drive folder named something like "Contracts 2024 FINAL," and a spreadsheet tracking who signed what.
It works. I'm not going to pretend it doesn't.
But it takes 25 – 45 minutes per contract. It breaks when the person who built it goes on vacation. And twice a year, someone sends a contract with the wrong client name because they forgot to update the template after the last one.
Errors are a feature of this kind of system.
"Working" and "working well" are different conversations. Most businesses operate somewhere in between and never realize there's a gap because the current way is the only way they've ever done it.
I don't sell to people who are happy with their system. I sell to people who watch me show them their own process and go, "Yeah, that's kind of ridiculous when you see it laid out like that."
That moment of recognition? That's where the deal lives.
Find that moment in your business and things will change.
38
My cofounder handles The tech side. I handle product and growth.
Sounds clean. It wasn't always.
For the first year, I had my hands in everything. Reviewing every template.
Approving every outreach email. Checking every workflow before it went live. I told myself I was maintaining quality.
I was creating a bottleneck with my name on it.
Everything had to go through me. Which meant everything moved at the speed of my calendar. Which, if you've met a founder's calendar, is not fast.
The turning point was embarrassingly simple. My cofounder shipped a product update while I was traveling.
He didn't ask.
Didn't wait for my review.
Just built it and shipped it.
Looking back, he didn't need to. He's my cofounder.
I digress.
Moving on.
It was better than what I would have approved.
That stung a little. But it also freed me.
I realized I wasn't protecting quality. I was protecting my sense of relevance. Two very different things.
Now my rule is simple: if someone can do it at 70% of what I'd do (80% after a bit of hand-holding), they should do it. Because 70% done now beats 100% stuck in my inbox for a week.
Just a bit of food for thought.
1
38
How to guarantee your operations break at 15 employees:
- Never write down how anything works because you're iterating
- Let everyone invent their own process because you're innovating
- and assume what worked at 5 will work forever because you have magic fairy dust.
22
Your team isn't slow. Your processes are.
Let me land.
I know that's a hard sentence to sit with. Because you hired these people. You trained them. You trust them. Rightly so.
And they're still missing deadlines, double-handling deliverables, and spending half their day on admin that doesn't generate revenue.
This is not a people problem.
It's a systems problem wearing a people mask.
I've sat with dozens of founders who were ready to fire their ops person, only to realize the ops person was doing exactly what the process told them to do. The process was just bad. More than half the time, it was the founder who built the process.
When you fix the process, the same team starts looking like a completely different one. The same people, given a better system, produce a different output.
I built a system that helps you find and fix the processes that are quietly strangling your team's capacity. It starts with a simple audit and ends with workflows that run without you having to babysit them.
Link in bio.
23
Something weird is happening in the small business tool market.
Every SaaS company is trying to become an all-in-one platform.
CRM wants to be your email tool. Your email tool wants to be your CRM.
Your project management tool wants to be your document tool. Your document tool wants to be your project management tool.
Everyone is building everything.
I know part of it is because of subscription fatigue. Another part of it is designed to capture more revenue from the same base.
And it kind of sucks for the customer. Because now you've got 6 mediocre tools crammed into one interface instead of 2 great ones that talk to each other.
On a side note, I saw a tool for real estate agents. It’s value prop is that it replaces 15 different tools. It made me shake my head because I knew they’d be mediocre at all of it.
Moving on.
I watch founders evaluate these platforms. They pick the all-in-one because it feels simpler. One login, one bill, one vendor.
Then six months later, they're using 3 of the 12 features, paying for all 12, and the 3 they use don't work as well as the standalone tools they replaced.
The all-in-one pitch is seductive. But the best operators I've talked to do something different. They pick 2 or 3 tools that are best-in-class at the thing they need, and connect them.
Fewer features. Better execution. Lower total cost.
The tool that does one thing extremely well will always outperform the tool that does twelve things adequately.
1
53
We underpriced DoxFlowy for the first year.
I knew we were underpriced. My cofounder knew. Our users definitely knew because a few of them told us, which is wild when you think about it. Customers volunteering that you should charge more.
In hindsight, it’s a good place to be in.
We didn't raise prices because we were scared of churn. Classic founder fear. "If we charge more, people will leave."
Eventually, we raised prices. Here's what happened:
Some people left. A small number. It was fewer than I expected.
The people who stayed complained less, used the product more, and asked for fewer discounts. Revenue went up. Support load went down.
You know, the things that we knew would happen but were too afraid to test out.
And the new customers who came in at the higher price? Different caliber entirely. I hate to say it, but they were all around more enjoyable to have as customers.
Underpricing does more than just cost you revenue. It attracts the wrong customer profile. The bargain hunters, the tire kickers, the ones who need the most hand-holding but pay the least.
Price is a filter. And for a long time, our filter was set way too low.
On a side note, we eventually brought prices back down because we're in a much stronger position. Now, we have the bandwidth to deal with some of the less desirable customers.
Think of it like how Mailchimp started out as only a paid platform, then eventually introduced a free tier. They sold for a few billion.
30
If you want to find where your company leaks time, do this exercise tomorrow morning. It takes 15 minutes.
Pick your most common client deliverable. The one your team does the most. For most service businesses, it's a proposal, a contract, or an onboarding packet.
Now list every step between "client says yes" and "deliverable is complete." Every single one. Include the waiting, the follow-ups, and the "check if they signed it yet" emails.
Most people think it's 4 or 5 steps. They’re probably wrong. It's usually 12 to 18.
Next to each step, write how long it takes and who does it. Be honest. That’s the only way this will be useful. Include the time it sits in someone's inbox waiting to be noticed. That counts.
Now circle every step that's identical every time regardless of the client. Same email. Same document. Same follow-up. Same filing.
Those circled steps? That's your automation shortlist. Always keep in mind that not everything needs to be automated. This is coming from the founder of an automation company.
But if a step is identical every time and a human is doing it manually, you're paying for a decision that's already been made.
It takes 15 minutes. You'll find 3 to 5 hours of weekly waste you didn't know existed.
31
A company that grows by adding people has a business. A company that grows by removing friction has an asset.
5
Three different founders told me the same thing this month.
"We need to hire someone to handle onboarding and admin."
In all three cases, I asked them to walk me through their onboarding process. All three had the same issue. The process itself was fine. The execution was manual to the bone.
Founder A: new client comes in, someone creates a welcome packet, a service agreement, and an intake form. Sends them in three separate emails. Follows up individually on each one.
Founder B: same thing, but with a project kickoff doc added. Four documents, four emails, four follow-up threads.
Founder C: Four documents as well. You can see where this is going.
None of them needed another person. They needed the documents to populate and send themselves based on the client info they already had (or could reasonably get).
One form. Client fills it out. Everything generates, routes for signature, and files itself.
All three went from "I need to hire" to "I need to automate" within about 20 minutes of mapping it out.
The instinct to hire when you're overwhelmed is strong. Often, it's the wrong instinct. Of course, it’s not always the wrong instinct. But it is more often than people want to admit.
1
28
The most dangerous hire at a growing company is the one who memorizes a broken process and calls it expertise.
10
There's a version of your company that runs on half the admin hours.
Same clients, same quality, same compliance and half the busywork. Shocking, I know.
Yes, that sounds like a pitch. Stick with me for a second.
Most service businesses I work with are spending 30-40% of their team's time on document prep, approvals, follow-ups, and filing. Not because anyone chose to. It just accumulated. One process at a time. One workaround at a time.
That 30-40% doesn't show up on any report. It's buried in everyone's day. An hour here. Thirty minutes there. A whole afternoon lost to chasing a signature. IYKYK
When I sit down with a founder and map where the hours go, the reaction is always the same. They knew it was bad. They didn't know it was that bad.
You don't need a transformation. Not really. You don't need a consultant. Not really. You need to see where the time is actually going and fix the three or four processes that are eating the most of it. Yes, really.
I built a system for doing exactly that. It walks you through identifying the leaks, prioritizing what to fix, and setting up workflows that handle the repetitive parts for you.
Link in bio.
1
22







