Start with the work that reduces uncertainty

Starting points for custom software, project takeover and integration work.

Final quotes depend on the workflow, existing code, integrations and delivery risk. These starting points help decide what should happen first.

Consultant and business owner comparing clear service options and a quote

Three practical starting points

Choose based on what is known, what is risky and what decision needs to be made next, rather than on a preset package size.

01

Technical review

Codebase, infrastructure and risk review with a written next-step brief.

  • 60–90 minute discovery
  • Risk and dependency map
  • Recommended first milestone
02

Custom development milestone

A bounded business-system feature, API, backend workflow, rescue milestone or integration.

  • Written scope and acceptance evidence
  • Tested delivery
  • Deployment notes
03

Ongoing maintenance

Scheduled support for an existing business system.

  • Prioritised maintenance queue
  • Monthly health review
  • Release support

Small work is prepaid or starts with a 50% deposit. Larger work is billed by accepted milestone.

Start with the right question

Start with enough information to make a responsible decision.

For an unfamiliar workflow or codebase, a technical review is usually the fastest way to define a realistic scope and quote.

Discuss your project