How a build runs

The software development process, week by week

A healthy custom software project checks fit, turns the product direction into a scoped plan, delivers working increments, tests throughout and ends with a handover the receiving team can verify. Agree what the team will show at the first review and what will count as ready for release.

Book a thirty-minute call

Short answer

A software project runs from a first call through discovery, ships in weekly reviewable increments, and ends with documentation, tests, observability, and a complete handover.

Best for

  • Founders hiring a software agency for the first time
  • Teams comparing how different agencies actually work
  • Buyers who want checkpoints to hold a vendor to
  • Anyone unsure what happens between contract and launch

Not for

  • Teams with a mature in-house delivery process that already works
  • Buyers who want to disappear for three months and collect a finished product
  • Projects with nobody available for a weekly review
// 01

Compare the options

How a healthy process differs from agency theatre, phase by phase.

Phase A healthy build Warning signs
First call

Fit and scope questions, and a clear no if it is not a match.

A price quoted on the spot for an unscoped build.

Discovery

Requirements, architecture and milestones, with a plan to resolve important unknowns.

Skipped entirely, or a paid document nobody pressure-tests.

Contract

Fixed price for locked scope, weekly retainer if scope moves.

Hourly billing with no defined outcome.

Build rhythm

Working software you can click every week or two.

Status slides and burndown charts instead of software.

Quality

Tests, CI/CD, and monitoring grow with the code.

QA squeezed into the last two weeks before launch.

The end

The receiving team can operate and recover the system.

Knowledge stays with the vendor so you cannot leave.

// 02

Where Wavect lands on this

The first call checks whether we are a fit. Discovery then turns an agreed product direction into requirements, architecture, milestones and a build offer. Wavect’s published fee is EUR 3,500 fixed, excluding applicable VAT, and is credited in full against the build if you continue with Wavect. Any research or experiments require an agreed scope.

Agree how the project will be commissioned. Wavect offers fixed-price work against a signed scope and eligible weekly engagements under the published terms. Set a review cadence and agree how changes affect price and schedule. Tests, CI/CD and monitoring grow with the code. Use the QA checklist to plan release evidence.

What to ask for at the first review

Start with one complete user action in a test environment. For example, a buyer submits a request and the right operator receives it. Show the result, check what happens when submission fails and record what still depends on sample data or external access. Name the decision owner and the next increment. Agree release criteria for tests, accessibility, security and recovery appropriate to the project. The Scrum Guide calls its shared quality threshold the Definition of Done. Scrum Guide on increments and the Definition of Done.

For handover, ask the receiving team to run tests, deploy to a safe environment and verify recovery with accounts you control. Document any managed-service dependencies and check who can administer each account. Test replacement service credentials before revoking superseded access.

After launch, watch how long changes take to reach production and how often deployments require intervention. DORA’s current five-metric model covers throughput and instability, including failed deployment recovery time and deployment rework rate. Use trends for the same service to investigate delays and failures with the team. DORA software delivery metrics.

// 03

Cost, risk and timeline

Discovery EUR 3,500 fixedExcluding applicable VAT. Fully credited against the build if you continue with Wavect.
Build rhythm Weekly incrementsWorking software to review every week or two, from early in the build.
Full timeline Weeks to monthsThe PromptID and LivLive case studies each report six weeks for a specific scope. Estimate your project from the release scope, integration access and approval lead times.
// 04

Where this usually goes wrong

  • Signing a fixed price before anyone scoped the build, then fighting over every change.
  • Months of silence followed by a big-bang delivery that misses the mark.
  • Progress measured in tickets and slides instead of software you can click.
  • QA and documentation postponed to the end, then cut when the timeline slips.
  • No product owner on the client side, so decisions stall for weeks.
  • No defined end state, so the handover never happens and you cannot leave.
// 05

The checklist

What you should be able to verify in each phase of a build.

Tick items off as you go. Nothing is stored or sent.

// 06

What this looks like in our work

These two published cases illustrate six-week delivery timelines for specific scopes.

These are selected projects, not our full portfolio. We have shipped 100+ products since 2018.

// 07

When this fits, and when it does not

// 01

When Wavect is the right fit

  • You want checkpoints you can verify, not promises you have to trust.
  • Someone on your side can review working software every week or two.
  • You want to own the code, docs, and infrastructure at the end.
  • You want an honest no early instead of a messy yes late.
// 02

When we are not the fit

  • You want to hand off a spec and reappear at launch.
  • Nobody on your side can make product decisions week to week.
  • Procurement requires hourly billing and timesheets.
  • You measure progress in hours logged, not software shipped.

A process you can verify week by week is the difference between hiring a partner and funding a black box.

// 09

FAQs

Start by checking fit and defining the release scope. During the build, review working increments and verify quality continuously. At handover, the receiving team should be able to operate and recover the software from the code, documentation and accounts it controls.
It depends on the first release and the work needed to support it. Ask the team for a range tied to written assumptions about integrations, reviews and approvals. Revisit the estimate when those assumptions change. The six-week examples on this page describe specific projects.
Waterfall organizes work into sequential phases. Agile uses short cycles to review usable work and adjust priorities. Scrum is one way to organize those cycles. In either model, agree the checkpoints and acceptance criteria the team will use throughout the software development lifecycle.
They will change, and a healthy process plans for it. Small changes are typically absorbed within the current increment. Larger ones get an impact assessment, a priced change request, and an open reprioritization with you. The warning sign is a vendor where change is either a fight or a silent budget overrun.
Discovery is the intensive part, because your answers define the scope. After that, plan for a weekly review of working software and availability for decisions in between. What a build cannot survive is having no product owner on your side, because every open decision stalls the work.
Book a thirty-minute call