Estimating guidance

Shape your business logic before estimating the work.

Custom development depends on the decisions an application must make, the data it exchanges and the system it joins.

This page sets out quote factors, not a fixed-price offer or a promised outcome.

MC / SERVICESCustom development pricing
MC / SERVICES

Why inspect software before estimating it?

Two applications with similar screens can involve very different rules, access needs and integrations.

For whom

Teams planning a business app, an internal tool or an extension to existing software.

In what situation

A new build, extension of a system or takeover requiring diagnosis.

MC / SERVICES

Three development situations

They guide discovery; the exact work belongs in the quote.

01 / Start

Initial build

Define useful journeys and rules for a first version.

Explore the service
02 / Change

Extension and integration

Add a capability or connect a tool to existing systems.

Explore the service
03 / Takeover

Takeover and reliability

Inspect an existing system before choosing fixes or changes.

Explore the service
MC / SERVICES

Read application layers and dependencies

The diagram separates interface, rules, data and dependencies to expose what needs examining before a proposal.

01

Business rules

Which cases, exceptions and decisions must be represented?

02

Interfaces and exchanges

Which screens and contracts connect people and systems?

03

Data and rights

Which data, permissions and obligations shape the work?

04

Operations

Which environments, checks and responsibilities are needed?

The diagram is educational; architecture, access and outputs are defined for each project.

MC / SERVICES

Six variables in an engineering estimate

Business rules, the existing codebase, data and interfaces drive the work behind the screens.

01

State of the codebase

Quality of code, documentation and existing dependencies.

02

Functional rules

Number of cases, variations and business decisions.

03

Roles and permissions

Access, journeys and boundaries to verify.

04

External interfaces

APIs, contracts, errors and availability of connected systems.

05

Migration and data

Sources, quality and transformation of relevant data.

06

Verification and transfer

Acceptance scenarios and any handover to agree.

MC / SERVICES

What a proposal should specify

The proposal sets out the agreed functions, exchanges, rights and responsibilities for the project.

TopicWork to defineDecision to agree
ScopingWork to defineJourneys, rules and assumptions to document.Decision to agreeApprove priorities.
DesignWork to defineArchitecture options and dependencies to examine.Decision to agreeChoose technical direction.
DeliveryWork to defineFunctions and integrations explicitly selected.Decision to agreeBound access and environments.
VerificationWork to definePossible scenarios, evidence and handover terms.Decision to agreeAgree acceptance criteria.

This table illustrates scoping questions; only an accepted quote fixes scope, rights and commitments.

MC / SERVICES

Possible handover elements

Rights, formats and handover terms are agreed in the quote or contract.

Subject to the quote / 01

Architecture note

Technical decisions and limits, if requested.

Subject to the quote / 02

Test record

Scenarios and observed results within the agreed scope.

Subject to the quote / 03

Transfer material

Information useful for takeover when included.

MC / SERVICES

Points outside assumed scope

Extra requests and external responsibilities need separate estimates.

  • No source-code ownership or access is implied by this page; the contract defines them.
  • No automatic OpenAPI dossier, runbook or transfer without explicit agreement.
  • No default hosting, licences or ongoing support.
MC / SERVICES

Development questions

Why no instant amount?

Rules, data and dependencies need scoping for a useful estimate.

Who owns the code rights?

Rights of use, delivery and ownership are stated in the applicable contract.

Can an existing application be taken over?

Yes, after assessing code, access and continuity constraints.

MC / SERVICES

Define what your application must do.

Explain the use cases, known rules and systems involved; we can identify the choices that matter to the estimate.

Describe your project