Contract development has a structural ceiling, and it sits on the third floor
“Isn’t this ultimately just converting labor costs into revenue?”
If you run a contract development business, you’ve probably felt this discomfort at least once.
On the surface, it looks like a well-built arrangement. The client has a budget, you have the people to build, requirements get aligned, and the deliverable gets handed over. It’s fair-trade-like, and both sides walk away satisfied.
But once you’ve run the business for a while, a feeling sets in: the income statement looks healthy, yet nothing seems to be “accumulating” inside the company. That’s the real substance of the discomfort I opened with.
Contract development isn’t my own main business, but putting together what I’ve heard from companies I’m involved with and from the operators around me, this discomfort seems fairly widely shared. This piece tries to lay it out as a structure. I’m not saying to quit contract development — I want to look at where the contract firms that survive for a long time hole up, and why that position is one you can survive in.
Hardware or software, the visible structure is basically the same, so I won’t distinguish between them here.
Contract development is actually a four-story building
“Contract development” gets said as one phrase, but inside it’s a continuous spectrum. Roughly, it breaks into four floors.
- Selling man-hours: price set by person-months. The client owns the requirements; you build to spec.
- Selling deliverables: the shape of the deliverable is fixed, but requirements get gathered fresh each time.
- Template plus customization: you take an existing in-house library and tweak it to the client’s request.
- Licensing / SaaS: you license your own product or service.
The higher the floor, the more reusable assets pile up. The lower the floor, the more everything gets rebuilt from zero each time.
There’s also a category of “companies that live off IP alone,” but that’s a different genre of strategy to begin with, so I’m not putting it on this ladder. It’s more accurate to say such companies start somewhere this spectrum never reaches.
And here’s the key point: nearly every contract firm that survives for a long time is holed up on the third floor, “template plus customization.” On the surface it looks like new development each time, but in substance it’s recombining internal libraries and implementing differences against past projects.
Conversely, contract firms that stay stuck on the first or second floor structurally fail to scale. The reason is blunt and simple.
Three reasons life on floors 1–2 is painful
① Gross margin is capped by the labor unit price
Revenue hits a ceiling at “person-month rate × headcount × duration.” If you want to double profit, the only way is to double headcount.
Frankly, this is fatal as a business. A company where profit is directly tied to headcount growth gets checkmated the moment labor costs spike or hiring gets hard.
② Management absorbs the full swing in utilization on its own
When a project stalls, only the labor cost remains. Fixed cost paired with revenue that behaves like a variable cost — the worst possible combination.
And it’s precisely during the busy periods that your best engineers tend to say “I want to work somewhere a bit calmer” and leave. Anyone with experience here knows the feeling.
③ Intellectual assets don’t accumulate
If you’re building different things to different requirements every time, no reusable library gets to grow. Even after ten years, the cumulative effect stays small.
Looked at in numbers, this is oddly brutal: it’s not rare for a company to reach the ten-year mark with nothing left but “people and cash.” A capital-equipment business ends up with a factory. A manufacturer ends up with molds and drawings. Contract work — if you’re not careful — ends up with nothing…
In other words, the lack of profitability isn’t an accident. It’s designed not to be profitable.
The trap where it disguises itself as “a blessing” from management’s vantage point
Here’s where it gets complicated — the real difficulty in saying “quit contract work” lies past this point.
From the vantage point of an executive juggling multiple businesses, contract development oddly looks like the model student. Product businesses are huge if they hit and a loss if they miss; new development is a multi-year investment; R&D has returns that are hard to see — against that backdrop, contract work gets placed in the stable slot of the portfolio, as “the business that generates roughly a few million dollars of gross profit every year.”
The explanation “contract work is what gives us the room to invest in new ventures” gets said in plenty of places, and in some years it’s factually correct. That’s exactly why it’s hard to stop.
But here’s the thing.
The “apparently stable gross profit” of contract work is, in essence, not stable at all.
Here’s why: projects are pipeline-dependent. If three large projects happen to overlap this year, the gross profit shows up on the surface. If those three finish next year and nothing new has been signed, it’s zero. Only the fixed costs remain. What looked like “roughly every year” was, in a lot of cases, just the waves happening to average out.
There’s another thing too: gross margin swings wildly project by project. A template-plus-customization project where 80% is reusable might carry a 40% margin; a full-scratch project with requirement changes every week — the so-called disaster project — might carry a 5% margin, or even a loss. Even calling it “$670,000 of contract work” in both cases, the amount that actually stays in the company can differ by a factor of ten depending on the mix.
Even so, executives tend to get handed a number like “contract work runs 30% gross margin,” based on last year’s results. That’s the magic of averaging.
And here’s where it turns cruel —
In a good year, contract work earns a certain amount of credit within the company. The margin looks predictable, and it looks like it’s funding the room to invest in new ventures.
But in a lean year — whatever the reason, the economy, the market’s budget cycle, anything — the evaluation axis flips in an instant. The drop in margin, the lost bids, the losses from disaster projects: all these questions get pointed at it at once.
The business that was called “a blessing” just recently suddenly turns into the one being held accountable.
This swing is probably another structural problem with contract development. Product businesses and R&D are positioned as “investment” from the start, so a bad year doesn’t easily flip the evaluation. Contract work, the moment it gets built in as a “stable revenue source,” has a bad patch translate immediately into a swing in how it’s judged.
Expectations are high, so a miss hurts. It’s the prospect-theory kind of thing.
There’s no complete answer to this dilemma, but there is an operational trick: only build contract work’s gross margin into the management plan at a conservative level — something like the lowest figure of the past 5 years. Treat anything above that as a “bonus.” This alone considerably lowers the risk of becoming the scapegoat.
So where do you make a home?
Given all this, let’s reframe the question. It’s not a binary of “quit contract work or keep it.”
Which position in the four-story building, when you hole up there, lets accumulation work in your favor and makes you less likely to be scapegoated — that’s the better question to ask.
As far as I can observe, the contract firms that survive for a long time share a few things in common.
First, they build up library and design assets in a specific domain. Not general-purpose contract work but domain-specialized. Medical, finance, manufacturing, embedded — anything works. The in-house assets for that domain grow fat, and they cover 80% of any new project. The remaining 20% gets implemented fresh each time. This is the core of template plus customization.
Second, they build a product they actually use themselves. A tool built to improve their own operations that also lands well in the client’s operations. Wherever dogfooding works, you get a clearly stronger competitive edge than a product built purely on outsourcing. It’s the gradient zone of “half product, half contract work.”
Third, they hold their price through quality assurance and relationship capital. They sell the same implementation a competitor would, but for more. The reason: the trust built up from a track record of past projects, and the capacity to respond when something goes wrong. Cost leadership is, in principle, impossible in contract work, so this is the only place differentiation can come from.
Put the other way: a portfolio where none of this accumulates — new every time, from zero every time, a different domain every time — is structurally painful. The more you do it, the less asset builds up, and only the swings in utilization bounce back onto management.
Using the third floor as a waypoint, not a terminus
Reading this far might sound like “hole up on the third floor,” but in fact the third floor works both as a terminus and as a waypoint. There’s a real path where you build assets on the template-plus-customization floor and then climb, on that foundation, to the fourth floor of “licensing / SaaS.”
For example, I know someone running a company in Saudi Arabia in a field close to Switch Science. We met in Italy, and he deliberately narrowed his focus to the domain of “cameras” and kept taking on contract work there. He paid no attention to general-purpose, miscellaneous projects and concentrated on camera-related hardware, image processing, and embedded systems.
A few years on, the in-house know-how in camera-related libraries, circuit design, and image processing had grown thick. Using those assets, he launched his own product and, carrying that with him, succeeded in raising funding — this is what he told me himself.
The route of “getting by on contract work while accumulating assets, then climbing to a higher floor on the assets you’ve accumulated” was something he designed on purpose. The initial decision to narrow the contract-work domain directly determined the later competitive advantage of his own product.
Another example: a company I advise, hacomono, has traced a similar structure. It originally started as a web-based contract development shop, but while working across multiple clients’ projects, it spotted “something that companies in a particular industry commonly wanted.” It threw its own SaaS product at that gap, the fit worked, and it has gone on to raise tens of millions of dollars cumulatively. It’s not yet public, so it’s too early to draw a conclusion, but as a structure, it’s a clean example of converting the “feel for the market” gained through contract work into SaaS.
What both share is that contract work was positioned not as “contract work for the sake of staying in contract work forever,” but as an asset-accumulation period for climbing to a higher floor. Holing up on the third floor is one strategy; using the third floor as a springboard to climb is another. The companies that can take the latter path tend to be the ones that narrowed their domain from the start.
Conversely, a contract firm that takes on anything without narrowing its domain can climb to the third floor, but the path from there to the floors above is hard to see. General-purpose libraries accumulate, but a deep feel for a specific domain does not.
Engineering enjoyment and management rationality are different things
This is probably the thing I most want to get across.
From an engineer’s point of view, contract work is fun. You touch different technology on every project, you see into different industries, your technical ability gets sharpened under the hard constraint of a deadline. This enjoyment is real.
I lean fairly heavily toward the engineer temperament myself, so there’s no doubt I like touching different technology on different projects each time.
But mistaking this enjoyment for “management rationality” is what makes it harder the longer you keep going.
Enjoyment as an engineer doesn’t guarantee enjoyment as a manager. These are different things. What’s enjoyable as a manager is — probably — watching something “accumulate” inside the company.
The discomfort I opened with — the sense that “isn’t this just converting labor costs into revenue?” — is probably just another way of saying this sense of “nothing accumulating.”
The good that’s reachable
I obviously don’t have the power to change the structure of the whole industry. But within the companies I’m involved with,
- lowering the share of man-hour sales and raising the share of template plus customization
- narrowing the domains taken on, and accumulating domain-specialized in-house assets
- once assets have grown substantial, seriously considering a move up to the floor above (own product / SaaS)
- building contract work’s gross margin into the management plan only at a conservative level
these are things I can implement as management decisions. I’m not saying to flip to SaaS all at once. It’s an operational matter of nudging your position on the spectrum up even half a step.
With a handful of management decisions and a few years of accumulation, a company’s structure changes slowly. Getting contract development some distance away from being a business that “just converts labor costs into revenue” probably takes about that much time.
This piece was drafted and directed by Yuichiro Kuzuryu, with the writing done by AI.
Originally published in Japanese at https://clazytech.com/2026/05/1606/. Translated with LLM assistance and reviewed before publication.