What should you clarify before requesting proposals?
Spending a day or two preparing before speaking to companies makes their proposals comparable. Give everyone the same information so differences reflect their approach, rather than just their price.
Pre-proposal checklist
- Problem: one paragraph describing what is going wrong today, for whom and at what cost.
- Users: the roles that will use the product and approximate numbers in each role are known.
- Systems: the ERP, accounting software and spreadsheets that need to connect are listed.
- Success measure: what should change after launch is written in measurable terms.
- Constraints: fixed dates, KVKK and security requirements, and where data will be stored are known.
- Budget range: the upper limit and budget period have been discussed internally.
- Decision process: the decision-maker and the person responsible for day-to-day project coordination have been identified.
Put this information in a one-page project brief and send the same text to every company. You can use our project brief tool. Sharing a budget range makes it easier for companies to propose a realistic scope within it.
How do you prepare a software project requirements list?
A requirements list should describe users, actions and acceptance criteria before screen names. Give each item a priority and a decision owner. Mark an unknown integration as an open question rather than a confirmed requirement.
Hypothetical example: The following list prepared by a distributor for its first release makes proposals comparable in scope. The numbers are test conditions, not client results or prices.
| Requirement | Acceptance criterion | Priority and owner |
|---|---|---|
| Dealers see their own prices | When two different dealer accounts open the same product, each sees only its assigned price. | First release · Sales management |
| Orders are transferred to the ERP | Sending the same business transaction ID twice creates only one order; if the ERP is unavailable, the user sees a pending status. | First release · IT and operations |
| Show an account summary | Show the total with the data timestamp; accounting compares the ERP result against agreed sample records. | First release · Accounting |
| Download an app from the store | Use a mobile-friendly website until a need for barcode scanning or offline operations is demonstrated. | Later phase · Product owner |
Also include source data and transfer direction, existing access, records to migrate, the support owner, budget limit and fixed dates. You can start preparation with the project brief tool and, during a discussion about custom software development, turn the list into a scope and assumptions document.
Freelancer, agency, studio, integrator or in-house team?
A “software company” is not a single type of organisation. The right choice depends on project size and how lasting a capability software will be for your business.
| Option | When is it suitable? | What should you watch for? |
|---|---|---|
| Freelance developer | Small, clearly scoped work requiring one area of expertise | Dependency on one person; who will handle design, testing and continuity |
| Digital agency | Work focused on websites, campaigns and promotion | Engineering depth for projects with complex business rules and integrations |
| Product and software studio | Products and operations platforms requiring strategy, design and engineering together | Capacity; who will actually be assigned to the project |
| Large integrator | ERP implementations and multi-country, multi-vendor programmes | Differences between the sales team you meet and the team delivering the project |
| In-house team | Situations where software is a core capability that will evolve for years | Recruitment time; building the first release with outside support and hiring later is also an option |
Sometimes the right answer is to use an existing product rather than choose a development company. Off-the-shelf software often meets accounting, payroll or standard CRM needs faster and with less risk. Custom development becomes worthwhile when your workflows do not fit existing products.
8 technical checks for proposal meetings
For each proposal, record answers, supporting documents and unresolved decisions beside these questions. This list helps compare technical scope and working methods; it is not a legal contract template.
1. Which task will the first release complete, and what is excluded?
Why does it matter? The same screen names can cover different business rules. Ask about user roles, start and end points, exceptions and exclusions together. Uncertainty: If a proposal says “order module included” but does not separately define approval, cancellation and ERP transfer, proposals are not yet comparable.
2. Which scenarios determine acceptance, and who approves delivery?
Why does it matter? A screen opening does not mean the work is complete. Define test data, expected results, failure scenarios and the business decision-maker. Uncertainty: If “we will give a demo” does not explain what happens with incorrect permissions, outages or duplicate transactions, acceptance criteria are incomplete.
3. When will the code repository, accounts and documentation be handed over?
Why does it matter? Owning source code is not the same as being able to deploy a working release. Ask separately about repository access, cloud and domain accounts, setup documentation and third-party licences. Uncertainty: If “everything belongs to you” comes without account owners, access dates or licence restrictions, the handover terms are unclear.
4. Who will provide integration access, and who will investigate errors?
Why does it matter? The ERP API licence, test account, field mapping and provider support may belong to different parties. Ask for an owner and readiness condition for every dependency. Uncertainty: If “ERP connection included” does not explain the plan when access cannot be obtained or who receives fault reports, the schedule and price rest on assumptions.
5. How will the accuracy of migrated data be verified?
Why does it matter? Equal record counts are not enough. Ask about checks on amounts, relationships, dates and duplicates, a trial migration, and the data owner who will approve it. Uncertainty: If “we will import the Excel file” comes without an error list, a correction owner and preservation of the old source, migration scope is incomplete.
6. How will bug fixes be distinguished from new development?
Why does it matter? A failure of accepted behaviour and a new rule requested later are different kinds of work. Ask which acceptance criterion will be used to assess the request and how the change's time and cost impact will be approved. Uncertainty: Treating every correction as extra work, or including every new request without limits, signals a potential scope dispute.
7. Who will monitor production and restore backups?
Why does it matter? Maintenance may include receiving alerts, responding, backing up and restoring. Ask about support hours, the responsible person, backup location and a restore rehearsal. Uncertainty: “Backups are being taken” does not explain which point in time you can restore to or how later records will be handled; do not assume recovery without disruption.
8. How can another team take over the working release?
Why does it matter? Handover requires architecture, versions, setup and deployment steps, dependencies, access owners and known issues. Request a handover check in which the new team can install the system in a test environment. Uncertainty: A code archive alone, services tied to personal accounts or undocumented manual actions make handover harder.
Example use: Two proposals may both include “ERP integration”, while one covers only order transfer and the other also covers transfer-error monitoring and duplicate checks. Do not compare only the total price before clarifying the unresolved items. The sample proposals in the cost guide can help complete your comparison; add to the project brief the users, systems and questions awaiting decisions. Apply the same questions to Codariva through our delivery and maintenance scope; project terms are clarified in the written scope.
Alongside these checks, ask who will be assigned to the project and in which roles. Distinguish live client projects, products and fictional concepts in the work shown; treat only authorised, verifiable examples as evidence.
How should proposals be compared?
Before putting proposals side by side, check whether they price the same work. The total price becomes meaningful only once scope and assumptions are aligned.
| Category | What should you look for? |
|---|---|
| Scope | Which user journeys and modules are in the first release; are the same screens being counted? |
| Assumptions | Are integration, data quality and the contribution expected from you documented? |
| Exclusions | Is what will not be done explicitly listed? |
| Team | Are roles, experience levels and time allocated per person clear? |
| Schedule | Is there a fixed date or a range, and does the proposal explain what will narrow the range? |
| Acceptance criterion | Who decides that a task is finished, and on the basis of which test? |
| Pricing model | Fixed price, staged fixed price or time and materials: what happens when scope changes? |
| Delivery and support | Are code, documentation, warranty period and post-launch support included in the price? |
Hypothetical example: a distributor receives three proposals for a portal where dealers can place orders. A has the lowest price and shortest schedule, but excludes ERP integration on the assumption of a “ready-made API supplied by the client”. B has the highest price; it starts with two weeks of discovery, includes integration and provides a range for the first release. C is fixed-price with apparently broad scope, but has no exclusions list and delivers code only at the end.
The comparison reveals that A and B do not price the same work: A leaves ERP connectivity, the most uncertain item, to you. C's fixed price hides a scope that will be renegotiated with every change. The best next step is to ask all three companies for revised proposals based on the same assumptions, so the result is comparable rather than merely appearing cheapest. We explain when fixed-price and time-and-materials models are appropriate in our guide to custom software costs. Dealer Ordering Platform product concept shows what such a portal could look like using a fictional company.
Contracts and code ownership: what should be in writing?
A contract determines what happens when things go wrong, not just when they go well. These technical points should not remain ambiguous:
- Intellectual property and source code. Assignment of the economic rights to project-specific code, designs and documents; usage licences for tools and libraries the company already owned.
- Account ownership. Code repositories, domain, cloud and third-party service accounts are opened in your company's name; the development company is only granted access.
- Acceptance. The criteria and number of days for testing and accepting each delivery.
- Warranty and support. How long defects will be fixed without charge after launch; support scope, hours and response times (SLA).
- Data and security. The safeguards the company will apply if it accesses personal data, and where the data will be processed.
- Exit plan. Return of access, transfer of documents and knowledge, and associated costs if the relationship ends.
Rights assignments, third-party licences and the contract's governing law should be considered together. Have the required rights and transfer conditions clearly defined in the contract, and ask your legal adviser to review the wording.
Limiting risk and signs that rule out a proposal
Whichever company you choose, you do not have to make one large commitment at the outset. Especially when working with a team with few references, you can limit risk by:
- Starting with a short, fixed-price discovery phase and requesting outputs usable by another team too
- Running a narrowly scoped pilot before the first release
- Seeing working software every week and linking payments to accepted work
- Obtaining repository access from day one
- Including an exit clause with a reasonable notice period
Any of these three signs is sufficient to rule out a proposal: a firm deadline and price given before seeing your systems and users, refusal to identify the project team, or refusal to show the code. Fixed pricing is not itself a problem; it is appropriate when scope is genuinely clear. The problem is uncertainty hidden within the price.
At codariva, we recommend starting a new product with a fixed-price discovery sprint; source code is kept in your repositories from day one. Our delivery terms and working approach are on our custom software development service page. You can ask us every question in this guide too.