Quantum is two months old. I started it in November 2021 with $20K of my own money, no investors, and one rule that I wrote down before I wrote a single line of code: every person we pay is paid by a client who has already paid us.
That sounds obvious. In practice it is the hardest discipline in a young software company, because everything about the early days pushes you the other way. You want a team. You want to look like a real firm when you walk into a meeting. You want to say yes to the interesting project that needs four people you do not have yet.
Why the rule exists
A services business runs on one number: cash collected from work that is finished and accepted. Not pipeline, not proposals, not "we are close." I have watched good teams die of optimism, hiring for the deal that was about to close. The deal slips a quarter. Payroll does not.
So the rule is simple. Headcount follows revenue. Revenue follows delivered outcomes. Delivered outcomes follow clear scope. If I cannot trace a hire back to an invoice, the hire waits.
It has a second benefit that I did not expect. When you know the money is real, you can afford to be honest with a client. You can say the workflow does not need an app yet. You can say the scope they described is three projects, not one. You are not desperate, so you can be useful.
What "revenue first" changes about the work
It forces me to price outcomes, not hours of enthusiasm. Every engagement has to answer three questions before anyone starts:
- What result must exist at the end, and who will confirm it exists?
- What is the smallest version of that result we can show working?
- What does the client have to provide, and by when?
If a prospect cannot answer the first question with me, we are not ready to start, no matter how excited both sides are. That is not a sales tactic. It is the only way I know to keep a small company from drowning in half-finished work.
Saying no early
The most expensive projects are the ones you should have declined in the first meeting. This month I turned down two. One wanted a platform with no owner on their side who could accept it. The other wanted a fixed price for a scope that changed twice during the call.
Declining early is a service to the client too. They lose nothing except a vendor who would have disappointed them slowly. If you run a company and a builder tells you no in the first conversation, that is the person worth calling back with a smaller, sharper problem.
What this means if you are thinking of hiring us
You will get a small team that grows only when the work has earned it. You will get a scope that names the outcome, the evidence, and the person who accepts it. You will get straight answers about what is worth building, including "not yet."
The $20K is not a war chest. It is a runway that ends fast, and it is meant to. It keeps me focused on the only thing that matters in the first year: finish something a client is glad they paid for, then do it again.
What I have already gotten wrong
Two months is enough time to make mistakes. I underpriced the first engagement because I wanted the logo, and I am still paying for that in hours. I also let one scope conversation drift into a second and third meeting without writing anything down, and had to reconstruct what we agreed from memory. Both errors have the same fix: write the outcome, the price, and the acceptance in one page before the second meeting, and read it aloud at the start of the third.
Pay for people with money you have already collected, and you will never have to lie to a client to make payroll.