Fixed price, fixed date

Fixed price, fixed date means we commit to three things in writing before the first sprint: what we will deliver, what it will cost, and when it will be in your hands. All four of our programs, from Sprint Zero to ReCore, run this way. The price is a number, not a range that widens as the work proceeds, and the date is a calendar date with a named acceptance test behind it.

It works because we do the scoping properly first. Before we quote, we run discovery, write the scope as a list of testable outcomes, and mark the items that are explicitly out. Anything that arrives later goes through a change request with its own price and its own effect on the date. We carry the delivery risk on the agreed scope; you carry the risk of changing your mind.

It is not a cap on a time and materials engagement, and it is not a promise that requirements can float. Fixed price without scope lock is just a discount the vendor plans to claw back through disputes. The discipline lives in the scope document, not in the invoice.

• Founder / CEO: you can put a single number and a single date in front of investors or a board without a contingency column.
• CFO: the engagement is a capital line with a known ceiling, which makes approval and cash planning straightforward.
• CTO / Head of Engineering: scope is written as acceptance criteria, so your team knows exactly what to test at handover.
• Product manager: the change-request process forces prioritisation decisions into the open instead of burying them in a growing backlog.

Fixed price, fixed date exists because the most common failure in software procurement is a project that costs twice the estimate and arrives a year late, with nobody able to say when it went wrong. Putting price and date in the contract moves that risk from the buyer to the builder, who is better placed to manage it. The trade-off is flexibility: a fixed engagement punishes changing requirements, so it suits work you can scope in advance and suits exploratory research less well. That is why we pair it with a short discovery step, so the scope we fix is one we both believe in.

• A SaaS company commissioning an in-app copilot as a six-week Launch 6 build with a fixed launch date tied to a customer conference.
• An NBFC funding a KYC document-intelligence system from a capital budget that requires a firm price before approval.
• A hospital network buying a multilingual voice agent for its front desk, where the go-live date is set by a new ward opening.
• A university replacing a legacy ERP module by module, each phase quoted and dated separately under one framework agreement.
• A D2C retailer commissioning a WhatsApp personalisation engine that must be live before a festive-season sale.

ConceptA commercial model rather than a skill, but delivering it well depends on scoping discipline and honest estimation. It underpins every Eazyware program listed on the programs page; ongoing support after delivery moves to a monthly Care Plan instead.

Eazyware service that covers it: Fixed-price programs. Starting prices are on the pricing page.