Fixed gross price
The advantage is that budgets and boundaries are clear, provided that needs are estimated. Any additional scope requires a change assessment and is not suitable for highly exploratory projects.
Home / Project decision guidance / Fixed gross price and monthly collaboration
PROJECT DECISION GUIDEFixed Price vs. Monthly Development
The method of cooperation is not simply price selection, but rather an arrangement whereby needs are uncertain, project management capacity and risks are borne.
Answer the question.
Fixed gross price and monthly collaboration
The projects that are stable in scope and with clear acceptance criteria are suitable for fixed gross prices; projects that have clear objectives but require gradual validation are suitable for phased delivery; and monthly team collaboration is usually more flexible when products evolve and clients have product owners and priority management capabilities.
DECISION FACTORS
Key elements to be checked for decision-making
First, the boundaries of restraint and responsibility are identified, then the technical routes and modalities of cooperation are compared.
Phased delivery
Decisions on diagnosis, prototype, MVP and formal construction can reduce one-off inputs and technical uncertainties.
Teamwork on a monthly basis
Demand can be sequenced dynamically according to role and input cycle payments, but clients need to provide ongoing product decision-making, acceptance and priority management.
Acceptance
Fixed ranges should be accepted and accepted by functional and non-functional criteria; teamwork should focus on iterative outputs, quality indicators, technical debt and operational effectiveness.
Change mechanism
Any model should clearly identify, assess, confirm and document the process of change and avoid the continuous extension of borders through oral communication.
Withdrawal and surrender
Contracts should identify the source code, account numbers, files, data, unfinished matters and knowledge transfer to ensure that cooperation is in an orderly manner.
Preparation of recommendations prior to communication or assessment
Stable demand bordersQuantification of acceptance criteriaIs there a customer who is responsible for the product?Technical risk validatedBudget release by stageWho is responsible for making the change?How transparent is team input?How to complete the transfer by concluding cooperation
Suggested path to implementation
Complex projects are often clustered: first, a fixed range of diagnostics or a PoC, then a phased core system, which moves into a stable iterative structure and is then converted to a monthly team or annual mobility.
DECISION WORKSHEET
Change fixed gross price from monthly collaboration to enforceable decision-making
The following worksheets help enterprises to organize vague advice into vendor-based, internal-approval and project-receivable inputs.
Fixed gross price
The advantage is that budgets and boundaries are clear, provided that needs are estimated. Any additional scope requires a change assessment and is not suitable for highly exploratory projects.
If the factor remains uncertain, a diagnostic or small-scale validation should be arranged and it is not appropriate to include the non-variable fixed total price range directly.
Phased delivery
Decisions on diagnosis, prototype, MVP and formal construction can reduce one-off inputs and technical uncertainties.
If the factor remains uncertain, a diagnostic or small-scale validation should be arranged and it is not appropriate to include the non-variable fixed total price range directly.
Teamwork on a monthly basis
Demand can be sequenced dynamically according to role and input cycle payments, but clients need to provide ongoing product decision-making, acceptance and priority management.
If the factor remains uncertain, a diagnostic or small-scale validation should be arranged and it is not appropriate to include the non-variable fixed total price range directly.
What should a comparable summary of assessments contain?
At a minimum, the stability of the demand boundary, whether the acceptance criteria are quantifiable, whether the customer has a product owner, whether the technical risk has been validated, and whether it is demonstrated the current volume of business, average processing time, major anomalies, existing systems, data privileges, third-party dependence and access windows. The same version of information is provided to different suppliers, with the requirement that the assumptions, exclusions, customer cooperation matters, deliverables and acceptance evidence be separately specified, so as to avoid comparing only the total price of one missing border.
For example, the enterprise expects that the project will save 160 hours of labour per month, but this figure should be broken down into the number of tasks, single time savings, adoption rates and manual review ratios. If only 40 per cent of users use the first period, or if the new process increases the review process, the actual benefits will be significantly lower than the apparent estimate.
Four types of evidence recommended for questioning during vendor communication
The first is scope evidence: consistency of demand versions, business processes, prototypes, interfaces and exclusions; the second is engineering evidence: whether similar technologies have accessible structures, code management, testing, deployment and trouble management methods; the third is personnel evidence: whether actual participants, input stages, responsibilities and replacement mechanisms are clear; and the fourth is delivery evidence: how source codes, data, account numbers, documents, training, quality assurance and transport are handed over. It is normal for suppliers to be unable to provide customer confidentiality at the bidding stage, but should be able to explain their own methods and the evidence that can be developed under this project.
It is recommended that scope clarity, critical reliance, team capacity, acceptance enforceability and long-term takeover be rated separately and that the basis for each score be recorded. If a programme is cheaper, the interface, migration, testing or online responsibility is excluded, then it should be converted to the same delivery calibre before comparison.
The principle of judgement
This page provides a decision-making framework that does not constitute a fixed offer or performance commitment.
FAQ
FAQs
The most common issues before cooperation are clearly stated in advance.
Is the fixed total safest for the customer?+
Only when the scope is clear. Demand is unclear and the total price is fixed, often leading to high-risk retention, scope disputes or quality compression.
How can a monthly team avoid inefficiency?+
Roles of personnel, iterative goals, task records, demonstration reviews, code quality and delivery indicators should be defined and continuously sequenced by the client product owner.
Can we change the pattern of cooperation halfway through the country?+
The scope and terms of collaboration could be reassessed after the completion of the milestones and new costing, delivery and liability boundaries could be clarified through supplementary agreements.
DECISION FAQ
Check out all 265 questions.Common issues related to current projects
Software development and outsourcing of projects
Is the software outsourced to select fixed gross prices or to work together on a monthly basis?
Fixed total prices are easier to control when demand is stable, borders are clear and the outcome can be defined in advance. Demand changes, and if technology routes are explored or businesses can participate in product management, they are more flexible in person or on a continuous basis.
View full answerSoftware development and outsourcing of projectsWhat should be the choice of software outsourcing and self-building teams?
Software outsourcing is usually more effective if the business requires a long-term continuum and the enterprise has a product and technology management capability. If the target is clearly defined, quick start is required or there is a temporary lack of dedicated capacity, many enterprises retain the product and technology owners, leaving the phase of R & D or dedicated construction to the outside team.
View full answerSoftware development and outsourcing of projectsWhat should Shanghai Software Outsourcing choose?
It is important to see whether the supplier can translate business issues into scope, risk and acceptance criteria, rather than company size and sales rhetoric. While local communication in Shanghai facilitates complex process interviews and online collaboration, code quality, project management and ongoing maintenance are still subject to proof. It is recommended that the other party be asked to explain the structure, delivery, unusual handling and takeover of similar projects.
View full answerSoftware development and outsourcing of projectsHow long does a custom software project usually take to develop?
The cycle depends on the degree of scope determination, interface and data preparation, decision-making efficiency and access requirements, not only on the number of people developed. Small internal tools may be completed in weeks, and cross-system enterprise platforms often need to be implemented in phases over a month.
View full answerRELATED
Submission of project evaluationKeep your knowledge of the services
Relevant
Software Project Outsourcing
View project design, phasing and collaborative scope of the R & D team
For more information.RelevantGuidelines on cooperation and delivery
Knowledge of contracts, milestones, acceptances and knowledge transfer
For more information.RelevantSubmission of preliminary project assessment
Assessing the modalities of cooperation in the context of maturity of demand
For more information.