Software is treated as the advantage. It is not. Any tool a firm can license, its competitor can license the same afternoon, at the same price, with the same features. What a competitor cannot license is the process wrapped around the tool: who reviews what, which errors get caught, where the output goes, and how the system learns from its mistakes. That is the CRE workflow advantage, and it explains why two firms running identical software routinely get opposite results.
Key Takeaways
A tool that anyone can buy cannot be a durable edge. The edge sits in the workflow designed around the tool.
Research on IT returns, from Brynjolfsson and Hitt (2000) to Bloom, Sadun and Van Reenen (2012), finds that the same technology produces sharply different gains depending on the organization using it.
Most failed software rollouts in CRE are process failures: the tool was added to an old workflow instead of the workflow being redesigned around it.
Four design choices separate firms that compound value from firms that only add cost: review routing, field ownership, downstream integration, and feedback.
The firm that redesigns the workflow captures the gain. The firm that bolts the tool on pays twice, once for the license and once for the workaround.
Why do two firms with the same software get different results?
Two firms with the same software get different results because software only changes the speed of a step. The workflow decides which steps exist, who owns them, and what happens to the output. A fast step inside a badly designed process still feeds a badly designed process. The tool sets a ceiling; the workflow decides how close a firm gets.
Consider two acquisition teams that license the same lease extraction product. The first team treats it as a faster typist: every extracted field is checked by an analyst, then re-keyed into the underwriting model. The second team decides in advance which fields matter most, routes only low-confidence or high-stakes fields to review, and maps output straight into the model. Same vendor, same accuracy, same contract. One team saved a little time. The other changed how it underwrites.
This is not a technology story. It is a design story. The tool is identical, so the difference in outcome must come from everything around it.
What does the research say about technology and process?
The research says technology returns depend on the organization that adopts it. Brynjolfsson and Hitt found that IT investments paid off most when paired with changes in work practices. Bloom, Sadun and Van Reenen found that firms with stronger management practices got more productivity from the same IT. The tool is necessary; the process determines the return.
Three bodies of evidence point the same direction:
Source | Finding | What it means for a CRE firm |
|---|---|---|
Paul David, "The Dynamo and the Computer" (1990) | Factories that bolted electric motors onto steam-era layouts saw little gain. Gains came after plants were redesigned around the new power source. | Adding AI to an unchanged process repeats the steam-era mistake. |
Brynjolfsson and Hitt, "Beyond Computation" (Journal of Economic Perspectives, 2000) | Organizational investments have a large influence on the value of IT investments. | The redesign is part of the investment, not an afterthought. |
Bloom, Sadun and Van Reenen, "Americans Do IT Better" (American Economic Review, 2012) | US multinationals got higher productivity from IT than comparable firms, and the authors trace the gap to people management practices. | Two firms with the same stack can diverge on management alone. |
Robert Solow summarized the puzzle in 1987: "You can see the computer age everywhere but in the productivity statistics." The decades of research that followed largely answered him. The productivity arrives, but only for the organizations that change how they work.
Where does the CRE workflow advantage come from?
The CRE workflow advantage comes from four design choices around any tool: how review is routed, who owns each data field, whether output flows into downstream systems without re-keying, and whether corrections feed back. Each is cheap to copy in principle and rare in practice, because each requires a firm to make decisions about its own operating model.
Design choice | Bolted-on workflow | Redesigned workflow |
|---|---|---|
Review routing | Every output reviewed the same way | Review effort concentrated on low-confidence and high-stakes items |
Field ownership | No one owns a field; errors belong to everyone | Each critical field has a named owner and a definition |
Downstream integration | Output exported, then re-keyed into the model | Output mapped directly into the model and the system of record |
Feedback | Corrections fixed in place and forgotten | Corrections logged, patterns reviewed, rules updated |
The first choice decides cost. A firm that reviews everything at the same depth gets the tool's speed and throws it away in review. Earlier pieces on this blog argued for designing around the exceptions rather than the straight-through path and for measuring the human review cost per document; both are workflow decisions, not software features.
The fourth choice decides compounding. A firm that logs and studies its corrections gets better every quarter. A firm that fixes errors in place makes the same corrections next year.
Worked example: what is the gap between two firms using the same tool?
The gap between two firms using the same tool can exceed the value of the tool itself. In the example below, both firms run identical extraction software on the same volume. The firm that routes review by risk spends less than a third of the review hours of the firm that checks every lease at full depth.
Assume each firm abstracts 500 leases a year with the same product. The inputs are assumptions chosen to show structure, not benchmarks.
Input | Firm A: bolted on | Firm B: redesigned |
|---|---|---|
Leases per year | 500 | 500 |
Leases given full review | 500 (all) | 75 (15 percent flagged as low confidence or high stakes) |
Minutes per full review | 45 | 45 |
Leases given spot check | 0 | 425 |
Minutes per spot check | n/a | 8 |
Re-keying into model, minutes per lease | 15 | 0 (mapped fields) |
Firm A: 500 leases times 45 minutes is 22,500 minutes of review, plus 500 times 15 minutes of re-keying, 7,500 minutes. Total 30,000 minutes, or 500 hours.
Firm B: 75 times 45 minutes is 3,375 minutes, plus 425 times 8 minutes, 3,400 minutes. Total 6,775 minutes, or about 113 hours.
The difference is about 387 hours a year from one process, on one tool, at one volume. The license fee is identical. Every input can be argued, but the structure holds: the cost is set by the workflow, and the tool only sets the floor. Firm B also produces a correction log and a data set that feeds the model directly, so its gap widens over time.
Why can a competitor not copy a workflow as easily as a tool?
A competitor cannot copy a workflow as easily as a tool because a workflow is not a product. It is a set of decisions tied to a firm's deal criteria, staffing, risk tolerance and history of mistakes. A competitor can see the result, but rebuilding it means making the same hard choices about its own operation, which most firms defer.
Michael Porter made the general point in "What Is Strategy?" (Harvard Business Review, 1996): advantage that rests on a system of activities that fit together is harder to imitate than any single activity. A tool is a single activity. A workflow is a system of activities.
This is also why the same software can widen gaps rather than close them. When a tool becomes common, the firms with a strong process pull further ahead, because they convert the tool into compounding gains while others convert it into another login. The point applies to packaged software built for the median firm: the product converges, so the difference shifts to process.
The quotable version: A tool can be bought on Tuesday. A workflow has to be decided, and most firms never decide.
Frequently Asked Questions
What is a CRE workflow advantage?
A CRE workflow advantage is the edge a firm gains from how it designs the process around its tools: review routing, field ownership, integration and feedback. It persists because competitors can buy the same software but cannot buy the decisions that shape how it is used.
Should a firm redesign its workflow before buying software?
A firm should define the target workflow before buying, then choose the tool that fits it. Buying first and designing later usually produces a bolted-on process, where the old steps survive and the new tool adds a layer instead of replacing one.
How can a firm tell if its software rollout is a process problem?
A rollout is likely a process problem when output is re-keyed downstream, every item gets the same review depth, or no one owns accuracy for critical fields. Those symptoms appear regardless of which vendor is in place, so switching tools rarely fixes them.
Does AI change the importance of workflow?
AI raises the importance of workflow. Faster, cheaper output means more volume flows through review, integration and feedback steps. If those steps are poorly designed, the extra volume amplifies their cost rather than removing it.
Conclusion
The CRE workflow advantage is the part of operations no vendor can sell. Every firm in a market will eventually have access to the same extraction, screening and analysis tools, so software alone stops separating anyone. What separates firms is whether they redesigned the work around the tool: routing review by risk, assigning ownership of data, removing re-keying, and learning from corrections. The evidence from electrification to modern IT points the same way. The technology arrives for everyone. The return arrives for the firms that change how they work.