A custom desktop software quote checklist should define who uses the application, where it runs, how data moves and how installation will be accepted. Give suppliers the same workflow, sample files and test conditions so you can compare included work, exclusions and assumptions.
Map users, workstations and the core workflow
Describe one complete job: who starts it, what they enter or import, which checks apply, who approves it and what output ends the task. Include corrections and failed steps, not just successful screens.
List workstation quantities, simultaneous users, shared terminals, locations, peripherals and any existing application being replaced. Distinguish everyday users from people allowed to install or administer the software. If records must be shared across devices, compare desktop and web-based business systems before fixing the architecture.
Specify operating systems and data handling
Name target operating-system versions and processor architectures, not just “desktop.” Ask which combinations the proposal includes for testing and support.
Choose separate workstation databases or a shared source of records. Separate databases need a transfer or synchronization plan; a shared server needs an agreed response to lost connectivity. If synchronization is required, define how conflicting edits are resolved.
State expected record volumes, attachment sizes, retention needs, backup responsibility and recovery requirements. Ask for a restore demonstration on a separate installation: creating a backup file alone does not prove that records can be recovered.
Define imports, exports, reporting and access
Attach anonymized files that preserve real structures and edge cases. For replacement projects, also review the spreadsheet-to-system migration brief.
| Requirement | Specify in the brief | Verification step |
|---|---|---|
| Imports | File formats, columns, encoding, date rules, duplicate handling and invalid-row behavior | Import agreed samples and reconcile saved, rejected and duplicate records. |
| Exports | Formats, columns, filters and permission rules | Open exported files in the intended receiving tool and compare identifiers and totals. |
| Reports | Calculation rules, filters, rounding and print layout | Compare results with an approved calculation using the same records. |
| Role access | Who may view, create, edit, delete, export and administer | Test both allowed and denied actions under each role. |
Separate in-app permissions from operating-system file access. Ask how local database files, exported files and backups are protected; hiding a button does not establish that access is blocked.
Ask what installation and documentation include
The Desktop Software Development starter scope lists an installer package and user documentation. Ask what those deliverables cover on your target devices.
Request confirmation of prerequisites, administrator rights, offline installation, signing requirements and third-party licenses. Agree how updates preserve data, how failed upgrades are reversed and whether uninstalling removes records.
Request a clean-machine installation test using the agreed permission level. Ask for a user guide covering daily tasks and import errors, plus administrator instructions for configuration, backup and recovery. Identify who will maintain those instructions after changes.
Check scope against files and acceptance criteria
Before approving the quote, require a scope matrix marking each requirement as included, excluded or optional, with assumptions and a verification method.
- Run the agreed workflow using your sample files on the named operating systems.
- Reconcile imported records, report totals and exports against approved expected results.
- Record who signs off, how defects are handled and how scope changes become separately approved work.
Separate application development, historical-data cleanup, one-time migration, training and post-launch maintenance in the proposal. Confirm source-code handover, build instructions and responsibility for future operating-system updates rather than assuming launch support covers them.
FAQ
Does local storage mean the application works offline?
Not necessarily. Ask which workflows depend on login services, external APIs, licensing checks or shared data. Test the agreed offline workflows with the network disconnected, including what happens when connectivity returns.
Does one installer cover every operating system?
Do not assume so. Ask for a deliverable and test matrix naming each operating system, processor architecture, installer format and upgrade path included in the quote. Confirm responsibility for preparing and testing each package.
Before requesting a quote: Share target operating systems, workstation and concurrent-user quantities, installation locations, workflow notes, anonymized files, role rules, backup needs and existing code or database details. Bring this brief to Manboo Studio to discuss requirements, and ask for written inclusions, exclusions and acceptance tests.