CUSTOM SOFTWARE PROJECT BRIEF Control Shift | https://www.controlshift.ae Use this brief to compare suppliers on the same scope. Do not include passwords, live employee records, identity documents or customer data in an initial enquiry. 1. Business outcome Which task needs to improve? Who does it today? What does a successful result look like? 2. Current workflow List the steps, approvals, spreadsheets and existing software involved. Describe one normal transaction and one exception, such as a cancellation or failed sync. 3. People and locations List user roles, approximate user counts, branches and legal entities. Which records are shared? Which records must remain restricted? 4. First release List essential capabilities and what can wait. Identify the pilot team. Would configuring or extending an existing product meet the need? 5. Integrations and migration Name the systems to connect, API access available, data owners and migration sources. Provide field headings or anonymised examples only after agreeing a secure exchange. 6. Operating requirements Specify language, hosting, access, audit, availability and reporting requirements. Ask the relevant internal reviewers to confirm requirements before approval. 7. Acceptance Write observable pass/fail checks for the workflow, permissions and exceptions. Name the person accepting the release and how migrated records will be reconciled. 8. Proposal comparison Request separate costs for discovery, build, migration, licences, hosting and support. Record exclusions, dependencies, change-request terms and payment milestones. 9. Handover Confirm repository and account ownership, deployment instructions, backup recovery, training, support responsibilities and the process for leaving the supplier. 10. Budget and timing State the budget range and any fixed business deadline. Identify dependencies that could delay delivery. Agree the schedule after discovery; this brief is not a quote. Discuss the scope: https://www.controlshift.ae/get-quotation