Estimation and ROI - Pinpoint Estimates Are Mostly Lies

About this article

As the fourth installment of the “Solution Architecture” category in the series “Architecture Crash Course for the Generative-AI Era,” this article explains estimation and ROI.

Architects who speak only in tech are half-fledged; speaking in numbers is full-fledged. This article handles FP method / story points / TCO / ROI / NPV/IRR, initial cost vs operational cost, phased-investment decisions, and AI-era estimation-accuracy improvement - the numerical tools needed to bridge tech and management.

Other articles in this category

Why estimation and ROI are needed

Get on the management-decision platform

Decisions on budget, personnel, and period are all done by numbers. “Technically correct” alone doesn’t get approved - investment-effect numbers are needed.

Priorities become clear

When multiple project candidates exist, starting with the highest ROI is rational. Without numbers, it becomes emotional.

Post-completion evaluation possible

To judge “success or failure” after project completion, comparing original assumptions with actuals is needed. Without ROI set, can’t verify.

Cost components

Project costs are thought of as initial + operational. Judging by initial alone causes the pattern of operational-cost deficits.

Cost class	Content
Initial (CapEx = Capital Expenditure, investment for asset purchase)	Design, dev, hardware, licensing
Operational (OpEx = Operating Expenditure, operating expenses)	Cloud fees, maintenance, license renewal
Personnel	Internal-staff effort
Training	Education for users / operators
Opportunity cost	Loss from postponing other projects
Risk cost	Loss expectation on failure

The modern way is estimating with 3-5 year TCO (Total Cost of Ownership), including operational cost invisible from initial alone.

Effect components

Effects split into quantitative effects and qualitative effects. Quantitative effects can be quantified; qualitative effects are hard to quantify but high in importance.

Effect class	Content
Cost reduction	Operational time reduction, personnel-cost reduction
Revenue increase	New customers, average customer value increase
Risk reduction	Avoiding incidents / violations
Operational quality	Mistake reduction, customer satisfaction
Speed	Faster decisions
Strategic value	Data utilization, DX foundation

Operational time reduction is counted as effect in nearly all projects, the most-used effect. Calculate via hourly-wage conversion.

ROI calculation formula

Simple ROI calculation is below. Complex metrics exist, but simple formulas pass for explaining to management.

flowchart LR
    INV["Investment<br/>e.g.: JPY 5M"]
    EFF["3-year effect<br/>e.g.: JPY 15M"]
    GAIN["Profit<br/>= effect - investment<br/>= JPY 10M"]
    ROI["ROI = profit/investment x 100<br/>= 10/5 x 100<br/>= 200%"]
    JUDGE{200% >= 100%?}
    OK["Approval line passed<br/>(double return after recovery)"]
    NG["Approval NG<br/>review requirements"]
    INV --> GAIN
    EFF --> GAIN
    GAIN --> ROI
    ROI --> JUDGE
    JUDGE -->|Yes| OK
    JUDGE -->|No| NG
    classDef inv fill:#fef3c7,stroke:#d97706;
    classDef calc fill:#dbeafe,stroke:#2563eb;
    classDef good fill:#dcfce7,stroke:#16a34a;
    classDef bad fill:#fee2e2,stroke:#dc2626;
    class INV,EFF inv;
    class GAIN,ROI,JUDGE calc;
    class OK good;
    class NG bad;

The general approval line is 3-year ROI 100%+. 200% means double-return after recovery.

NPV (Net Present Value)

ROI accounting for time value. The thinking that “JPY 1M now and JPY 1M 3 years later have different values” - converting future cash flows to discounted present value.

NPV = sum(per-year cash flow / (1+discount rate)^n) - initial investment

At 5% discount:
JPY 1M 3 years later ~= JPY 0.86M now

Large-scale / long-term projects use NPV. The discount rate is decided per company, usually 5-10%.

Payback Period

The metric showing in how many years investment is recovered. More intuitive than NPV, easy to land with management.

Payback period	Evaluation
Within 1 year	Extremely advantageous
2-3 years	Standard approval range
4-5 years	Cautious consideration
5+ years	Strategic value needed

The general guideline is recovery within 3 years - exceeding requires additional explanation.

Estimation methods

Major effort-estimation methods are below. Not 1 method - combine multiple and compare results to raise accuracy.

Method	Content
Analogous estimation	Comparison with similar projects
Function point method	Calculate by feature count
COCOMO	Calculate by line count and complexity
Bottom-up	Stack work items
3-point estimation	Optimistic / pessimistic / most-likely
Planning Poker	Agile, relative estimation

For agile projects, Planning Poker + Velocity is practical. Estimate by relative complexity, not absolute values.

Estimation buffer

On the premise that estimates always shift, stack buffers (margins). Per novelty / uncertainty, see 20-50% buffer.

Uncertainty	Buffer
Existing tech / similar projects	+10-20%
New tech / inexperienced	+30-50%
Has research element	+50-100%
PoC stage	Unable to calculate, flexible operations

“Pinpoint estimate” is impossible - initial estimates becoming 1.5x isn’t rare. Not budgeting buffer is a typical estimation failure.

Concrete ROI calculation example

Calculate ROI using internal application-workflow digitization as an example. Concrete numerical calculations are an architect’s basic skill.

[Investment]
- Initial dev cost: JPY 5M
- Annual ops cost: JPY 1M x 3 years = JPY 3M
- Total investment: JPY 8M

[Effect] (3 years)
- 500 hours/month x JPY 3000/hour x 12 months x 3 years = JPY 54M
- Operational mistake reduction: JPY 0.5M/year x 3 years = JPY 1.5M
- Total effect: JPY 55.5M

[ROI]
(55.5 - 8) / 8 x 100 = 594%
Payback: about 6 months

Showing in numbers makes management decisions instant. Vague “operational efficiency” doesn’t get approved.

Handling qualitative effects

How to handle effects hard to quantify is the difficult part of ROI calculation. Forcibly quantifying or treating as qualitative effects in parallel - judgment needed.

Qualitative effect	Handling
Employee satisfaction	Quantify via attrition reduction
Brand value	PR effect, ad-cost conversion
Security strengthening	Avoid penalty on violation
Strategic advantage	Competitor comparison, market share
Data foundation	Future AI-utilization value

Forcibly quantifying all qualitative effects loses persuasion, so the realistic answer is the 2-part composition of “quantifiable effects + list of qualitative effects.”

TCO (Total Cost of Ownership)

Cost over the entire lifecycle is called Total Cost of Ownership. Not just initial purchase price - compare in totals including operations, maintenance, retirement, opportunity cost.

TCO components	Content
Initial cost	Hardware, software, dev
Operational cost	Personnel, electricity, network
Maintenance cost	License renewal, patches
Update cost	Periodic replacement
Retirement cost	Data migration, disposal

Preventing “penny-wise, pound-foolish” is TCO analysis. Cheap initial cost with high operational cost is more expensive long-term.

Decision criterion 1: project nature

Depth of ROI analysis varies with project nature. Strategic investments emphasize qualitative aspects too, sometimes uncuttable by simple ROI.

Project	ROI emphasis
Operational efficiency	Very high (cost-reduction effect emphasized)
New business	Mid (uncertainty of revenue increase)
Infrastructure reform	Mid (TCO emphasized)
Security response	Low (risk reduction primary)
Regulatory compliance	Calculation unneeded (no choice not to do)

Decision criterion 2: org culture

How to produce ROI varies with management’s decision style. Number-loving management wants detailed calculations; vision-emphasis emphasizes qualitative.

Culture	Recommended
Number-emphasis	NPV, IRR (Internal Rate of Return), Payback triad
Balanced	ROI + qualitative effects
Vision-emphasis	Strategic value forefront, ROI supplementary

How to choose by case

Operational-efficiency projects (internal applications, RPA, etc.)

Operational efficiency like RPA (Robotic Process Automation) evaluated with simple ROI + time-reduction monetary conversion + 3-year TCO. “X hours/month reduction x hourly wage x 12 months x 3 years” is direct quantification, Payback in front. Buffer +20% enough, 2-track estimation of analogous + bottom-up.

New business / B2C services

NPV + Payback + qualitative-effects list. Sales prediction is 3-point estimation of optimistic/pessimistic/most-likely, initial approval in PoC budget frame → main investment after seeing results. With high uncertainty, +50% buffer; also set early-withdrawal judgment criteria.

Infrastructure reform / cloud migration

5-year TCO comparison + 6R analysis + risk-reduction effects. Total comparison of on-prem maintenance vs cloud migration, including electricity, ops personnel, hardware updates. Also list qualitative effects of security strengthening / disaster response in parallel.

Regulatory compliance / security strengthening

Risk amount on violation + response cost comparison + loss if not done. ROI calculation unneeded (no choice not to do), put “avoid up to JPY X billion in personal-info-leak losses” forefront. Judge by regulation-fulfillment level over TCO.

Common misconceptions

High ROI gets always approved

Falls due to comparison with other projects / budget constraints. Alignment with management agenda matters.

Lower initial cost is better

Reverses in operational cost. Should evaluate by TCO.

Estimate accurately

Accurate estimation is impossible. Showing in range (min-max) is honest.

All effects can be quantified

Some effects can’t. Forcing quantification loses trust.

When initial estimate of JPY 30M and 6-month dev period was presented, it was rejected as “too pinpoint, suspicious”; next presented as “JPY 30-45M, 50% buffer for uncertainty in range” - easily approved at JPY 45M frame - cases reported. Estimates feigning accuracy lose trust; estimates showing range gain trust. There are also cases of settling at JPY 42M and being evaluated as “expected landing.” A suggestive episode that aiming to “miss correctly with range” rather than aiming to hit pinpoint makes projects more peaceful.

Estimation-accuracy / ROI numerical gates

Note: Industry baseline values as of April 2026. Will become outdated as technology and the talent market shift, so requires periodic updates.

The iron rule for estimates is stacking buffer on the premise they shift. Below are industry-standard guidelines.

Item	Recommended	Reason
Buffer (existing tech / similar projects)	+10-20%	Standard uncertainty
Buffer (new tech / inexperienced)	+30-50%	Learning-cost expectation
Buffer (has research element)	+50-100%	PoC-first premise
Payback Period	Within 3 years	General approval line
3-year ROI	100%+	Recovery+profit minimum
TCO evaluation period	3-5 years	Include operational cost
Qualitative-effect handling	Parallel listing	Forced quantification drops trust
Estimation method	Multiple combined	Dual-track of analogous + bottom-up
NPV discount rate	5-10%	Per company standard
Cloud-ops-cost / revenue ratio	5-15%	Varies by industry

Pinpoint estimates are lies - missing correctly with range is honest. Presenting “JPY 30-45M, 50% buffer,” landing at JPY 42M gets evaluated as “expected.”

For estimates, “miss correctly with range.” Feigning accuracy loses trust.

Estimation / ROI pitfalls and forbidden moves

Typical accident patterns in estimation. All pay the cost of burying projects.

Forbidden move	Why it’s bad
Present pinpoint estimate	Bufferless always shifts, the standard local-government case of initial JPY 300M becoming JPY 1.2B
Judge by initial cost only	Reverses in ops, evaluate via TCO (3-5 years)
Submit estimate with just 1 method	Improve accuracy via dual-track of analogous + bottom-up
Forcibly quantify all qualitative effects	Loses trust, parallel listing is honest
Aim for approval with known ROI alone	New business requires NPV + scenario analysis
Start new-tech projects without buffer	Estimates always become 1.5x, +30-50% buffer required
Calculate ROI for regulatory-compliance projects	No choice not to do, compare with risk amounts
Don’t count AI-utilization effects	Operational-time-reduction 30% etc. directly affect ROI
Don’t change estimates once decided	Modern is continuous re-calculation, refine via PoC-first
Calculate man-month rates at old market price	Drastically changing in AI era, re-calculate with latest

The 2013 Healthcare.gov launch failure (initial $94M estimate ballooning to $2B added, 1-year medical-policy stagnation) and Japan local-government core-reform projects (initial JPY 300M / 18 months becoming JPY 1.2B / 48 months, redo of council approval) - typical cases of the cost of pinpoint estimates.

Estimates designed on premise of shifting. Missing correctly with range is more honest than hitting pinpoint.

AI-era perspective

When AI-driven dev (vibe coding) and AI usage are the premise, calculate estimation and ROI on the premise that AI drastically changes them. AI may make dev period 1/10 and cost 1/5, with areas where conventional estimation formulas don’t apply emerging.

Favored in the AI era	Disfavored in the AI era
AI-premised short estimates	Conventional man-month estimates
Continuous re-calculation	Sticking to once-decided budget
Fast PoC → judgment	Large-scale waterfall
Also count AI-utilization effects	Just evaluate vs conventional

The era when AI-utilization operational-efficiency effects can also be counted in ROI - for example, “AI-agent introduction reduces operational time by 30%” is directly quantified. Both the side using AI and the side being used by AI greatly change estimates.

In the AI era, calculate estimates on the premise of writing with AI. Man-month basis is outdated.

What to decide - what is your project’s answer?

For each of the following, try to articulate your project’s answer in 1-2 sentences. Starting work with these vague always invites later questions like “why did we decide this again?”

• Cost composition (CapEx, OpEx, personnel)
• Effect quantification (time reduction, revenue increase)
• ROI calculation method (simple ROI, NPV, Payback)
• Estimation method (bottom-up, analogous, etc.)
• Buffer rate (margin per uncertainty)
• TCO period (3 years, 5 years, 7 years)
• Qualitative-effect handling (parallel listing or quantification)

Author’s note - cases of “estimation breakdown” causing project cancellation

Cases of estimation laxness burying projects are continuously told as standard talking points in the SI industry.

The 2013 Obamacare Healthcare.gov launch failure is a symbolic case caused by divergence between estimation and implementation capability. The US government’s medical-insurance-exchange site, with initial estimate of about $94M, scheduled October 2013 launch, but estimation of complex existing-system integration was sloppy, with system stoppage at thousands of concurrent connections on launch day. By 2014, estimated $2B added to recover. An incident slapping home that “estimation optimism stopped a nation’s medical policy for 1 year.”

Another, Japan local-government core-system reform projects are often reported - initial JPY 300M / 18 months estimate, with requirement-change accumulation finally reaching JPY 1.2B / 48 months, with procurement revisions and council-approval redo losing additional 1 year. The result of ordering “pinpoint estimate” without stacking buffer - entered the negative spiral of every change collapsing budget / deadline / council approval.

Both show the cost of not designing estimates on the premise of shifting. A case group teaching the practical truth that aiming to miss correctly with range rather than aiming to hit pinpoint results in more peaceful project landings.

How to make the final call

The core of estimation and ROI is the thinking of putting tech proposals on the management-decision platform. Even technically-correct proposals don’t get budget approved without speaking in numbers. Compare with 3-5 year TCO, not just initial cost; show investment-effect with ROI / Payback / NPV; quantify by hourly-wage conversion of operational time reduction - this is the technique moving management. The honest proposal is stacking buffer (existing tech +20% / new tech +50% / research element +100%) on the premise that estimates always shift - “pinpoint estimate” is the typical failure. For qualitative effects, don’t forcibly quantify - the realistic answer is the 2-part composition of “quantifiable effects + qualitative-effects list.”

Another decisive axis is recognizing AI drastically changes the estimation premise. Areas where dev period becomes 1/10 and cost 1/5 exist - conventional man-month-based estimates don’t apply. AI-utilization operational-efficiency effects (agent introduction reducing operational time 30% etc.) can now be counted directly in ROI. PoC-first, fast judgment, and continuous re-calculation become the standard for AI-era estimation operations.

Selection priorities

1. Compare via TCO (3-5 years) - include operational cost invisible from initial alone
2. ROI calculation simple formula + Payback - what lands with management is simple metrics
3. Always stack buffer - 20-100% per uncertainty, pinpoint is failure
4. Update estimation premise via AI - man-month basis is outdated, re-calculate via PoC-first

“Speak in numbers, win approval.” TCO + ROI + buffer, re-calculate on AI premise.

Summary

This article covered estimation and ROI, including TCO, 3-point estimation, buffers, ROI, Payback, NPV, qualitative effects, and AI-era premise upheaval.

Compare via TCO, hit with Payback, honest with buffer, re-calculate on AI premise. That is the practical answer for estimation / ROI in 2026.

Next time we’ll cover “PoC design.” Plan to dig into Go/No-Go criteria, period setting, and effect-verification practice, plus numerical gates preventing “PoCs that never end.”

Back to series TOC -> ‘Architecture Crash Course for the Generative-AI Era’: How to Read This Book

I hope you’ll read the next article as well.