Skip to content
TRANSPARENCY BEFORE A NUMBER

What’s behind
a project estimate?

A starting point for a conversation about software value. The creator’s asking price is a separate choice.

An estimate with limits

Illustrative estimate from seller-provided data. Not an appraisal, verified market value, financial advice or a guaranteed sale price. Actual value may be zero or outside the range. The creator sets the asking price independently.

This release uses a deterministic scenario model, project-estimate-1. It is an original marketplace heuristic, not a Zillow model, independent appraisal, certified valuation or model trained on completed comparable sales. Its ranges are illustrative scenarios, not statistical confidence intervals. Input references are seller reports and are not automatically verified.

Which listing data is used?

The model uses bounded first-party source size, functional pages, implemented engines and stack size; industry and primary use case; development stage; actual revenue and normalized profit; ownership and IP transferability; implementation, security, scalability and handover evidence; reported operating costs; and coverage across all eight listing steps. The questionnaire supplies context and missing-data coverage. Prose dollar figures are not automatically parsed into earnings.

Typing more answers, checking declarations or increasing an asking price does not add a valuation premium. Missing financial figures remain unknown. Patents and trademarks are not assigned a fixed price per registration.

Early-stage software: discounted replacement cost

At least one functional page or engine is needed. Modeled hours = 24 + the larger of (6 × pages) and (18 × square root of source lines ÷ 1,000) + 28 × engines + 4 × stack entries. Pages are capped at 80, first-party source lines at 250,000, engines at 20 and stack entries at 8. LOC alone cannot generate a value.

Hours × an assumed $75/hour provides a replacement-cost cross-check. It is discounted for development stage, implementation and evidence readiness, use case, transferability and industry deployment risk. Three months of reported operating costs is reserved. These rates and factors are model assumptions, not observed transaction benchmarks; the creator can inspect each applied factor in the listing workflow.

Stage factors are 20% unknown, 30% prototype, 55% working MVP and 85% production. Readiness weights implementation 35%, security 25%, scalability 15% and handover 25%. Unknown evidence scores 35%, seller claims 55%, referenced evidence 80%, issues 20% and critical security issues 5%. Those are heuristic readiness inputs, not verified scores.

Use-case factors are 70% unknown, 95% business workflow, 80% consumer product, 70% internal tool and 90% developer infrastructure. Documented transfer rights with a reference and seller-confirmed transferability use 100%; incomplete transfer evidence uses 75%. Health or finance deployments without relevant review references use a 75% deployment factor. None of these states establishes compliance or title.

Income-producing projects: a flat-profit scenario

The income method needs 12 actual months of consistent revenue and positive normalized profit, both for the same period, with income reported as generating. Normalized profit should include all operating costs and a reasonable allowance for founder labor. The model does not annualize shorter periods, capitalize losses or infer revenue from an asking price.

It discounts three years of flat annual profit at an assumed 35% for recurring income or 45% otherwise, with no growth or terminal value. It then applies the transfer and industry deployment factors, plus an 85% security uncertainty factor (65% for known issues or 25% for critical issues). Replacement cost is not added to this income value; patents and trademarks are not separately added again to earnings.

Income history is not a promise of future earnings. References do not make financial reports audited. Conflicting financial inputs exclude the income method and produce a warning.

The range, missing facts and rights blockers

Range width starts at 60% for asset scenarios or 40% for income scenarios. It adds up to 15% for missing questionnaire coverage, 15% for missing structured inputs and 5% for incomplete transfer evidence, capped at 95%. The lower scenario is center × (1 − width), and the upper is center × (1 + 1.4 × width). Values are rounded to avoid false precision. A low or zero scenario is not a finding that a project has no possible value.

Data support is at most Moderate, and describes input coverage, not valuation accuracy. Sparse data produces Limited support. Disputed or restricted rights, non-transferable IP, or disputed patents/trademarks withhold a transferable-project estimate until clarified. This does not replace the separate marketplace publication review.

Patents, trademarks and privacy

Applications, grants, registrations, unregistered brands and disputed rights are distinguished. IP evidence and transfer rights can reduce uncertainty; a checkbox does not establish economic benefit, validity, enforceability, exclusivity or legal transferability. The model does not automatically award an IP premium. A qualified specialist should assess material IP separately where needed.

Financial inputs, evidence references and questionnaire answers stay private. Published listings show the computed estimate, range, method, version and general warnings. The server calculates its own estimate and ignores a client-supplied dollar result. Save changes to update the stored inputs; editing estimates does not change the creator’s ask.

Conceptual references

Cost, income and market approaches are established valuation concepts. The marketplace’s numerical assumptions are its own and are not endorsed by these sources.

Prepare your listing ↗
© 2026 ViberantLabs · Public working demo. Sample catalog clearly labeled.