We just shipped collaborator shares in OpenLedger. Everything works. And the first thing I did after the launch was go back to the reason I started building this in the first place.
That reason isn't payments. It isn't budgets. It's about who gets to say no.
What I saw
I've worked alongside some of the most brilliant engineers. People who could hold an entire system in their heads. People who could debug things the rest of us couldn't even describe.
And many of them couldn't push back on the most basic things.
An all-nighter for a feature nobody would use? Fine. A decision they knew was wrong? They'd say so quietly, once, and then build it anyway. I watched smart, capable adults go along with things they disagreed with because the cost of saying no felt too high.
Sometimes the stakes were low. Nobody dies because a quarterly sales report has the wrong column in it.
But the same kind of people build hospital systems. They build infrastructure. They build AI. And the habit of going along doesn't stay behind when the stakes go up.
What I tried
My first instinct was to fix it person by person.
I coached. I gave pep talks. I modeled pushback in meetings, hoping it would rub off. I told people, over and over, that they were allowed to say no, that their judgment mattered, that the company needed their honesty more than their compliance.
It didn't work.
Not because they weren't listening. Because people have to change themselves. You can't do it for them, no matter how much you care or how clearly you can see what's holding them back. I was trying to solve a structural problem with encouragement, and encouragement loses to paying rent every time.
The turn
So I stopped trying to change people and started looking at what surrounded them.
When one employer controls your income, your health insurance, your schedule, your IP and most of your social world, saying no isn't a personality trait. It's a risk calculation. And for most people, the math says keep your head down.
Dependence silences people. Not because they're weak, but because the system makes silence the rational choice.
Someone with one employer has all their eggs in one basket. Someone with several clients can afford to walk away from one. That's not a mindset shift. It's leverage. And leverage is something you can build.
The gap
Here's the catch. Going independent takes a skill set most technical people were never taught.
Some engineers are great at this already. They know what their time is worth, they scope tightly and they charge accordingly. I'm not talking about them.
I'm talking about the much larger group who can negotiate a salary because they have three competing offers, but freeze when it's time to scope a project, price it or hold a line with a client who keeps adding "just one more thing." Nobody taught them the language of money. Nobody taught them that a boundary is a business tool, not a confrontation.
That gap is where independence falls apart. You can have five clients and still be a dependent if you can't tell any of them no.
The tool
OpenLedger is my answer to that gap. It's a ledger that's actually open.
- Transparent scoping. Everyone sees what's being built and what it costs before work starts.
- Budgets that lock. Scope creep stops being a quiet favor and becomes a visible change.
- Payments tied to agreed work. Deliver what was agreed, get paid what was agreed.
- Collaborator shares. The people who contribute to a project have a clear, recorded stake in it.
The point is that the boundary lives in the system, not in your nerve. You don't have to win a hard conversation every week. The structure holds the line for you.
It's infrastructure for working as adults rather than as dependents.
And here's what surprised me: the first place it proved itself wasn't a software team. It was my family's clinical research business. Coordinating studies across Latin America means many hands, many budgets and a lot of room for things to get murky. OpenLedger is running there today, and it's our main use case right now.
It also solved a problem I didn't see coming: cash flow. A small family business isn't a bank, and clients sometimes pay late. Instead of fronting everyone's pay from reserves we don't have, we put the reality on the table: here's what came in, here's your percentage, paid as invoices clear.
It turns out people are remarkably forgiving when you're honest with them about the numbers. Adults can handle the truth. What they can't handle is being kept in the dark.
That tells me something. The problem was never really about engineers. It's about anyone whose work is real but whose terms are fuzzy. Clinical research just happened to be where I could test it first.
The stakes
I care about this more now than when I started, and the reason is AI.
The systems being built right now are powerful, fast and in some cases genuinely frightening. The people building them are going to face requests they know are wrong. Some already have.
Whether they can refuse depends less on their character than on their situation. An engineer who can lose one client and still pay rent can say no. An engineer whose entire life runs through one employer usually can't.
When skilled people have options, clients have to compete for them. And competition for talent creates pressure toward ethical behavior, because the best people can choose who they work for.
There's no silver bullet here. There are just individual battles: one person, one project, one moment where they either push back or don't. Infrastructure decides how those battles go. I want them to go our way.
Who it's for
OpenLedger is for genuine independent contractors: skilled people running their own practice, setting their own terms and, ideally, working with more than one client.
It is not a tool for companies to reclassify employees as contractors so they can skip benefits. That's the opposite of what I'm building. The goal is more power for the person doing the work, not less.
If you're a skilled technical person who's been thinking about going independent, or who already is but still feels like you can't say no, start small. Scope your next project in writing. Lock the budget. Tie payment to what you agreed to deliver. Notice how different the conversation feels when the terms are on the table instead of in your head.
And if you want a tool built for exactly that, OpenLedger is live. Come try it.