Call us about courier software 1 541 326 4200   Monday - Friday, 8 AM - 5 PM Pacific Time

Requesting Custom Software Development Services

Step 1: Prepare your request

To successfully evaluate your project, we need several details. Your request should include the following information. Please be as specific and detailed as possible.

  • Your name
  • Email address
  • Phone number
  • Name of your organization
  • Complete address
  • Website URL
  • Your business sector (e.g., healthcare, manufacturing, government, etc.)
  • If you are already an OnTime customer, provide your OnTime Company ID.
  • Provide an overview of project to be developed:
    • What is the main purpose of the project?
      (e.g., streamlining data between systems, automating processes, improving reporting capabilities.)
    • What are the key objectives you want to achieve?
      (e.g., reduce manual work, improve data accuracy, enable new features.)
    • What software systems are you currently using that need to be connected?
      (Please provide the names of the software or platforms.)
    • Do these systems have any known ways to connect with other software?
      (e.g., API, file exports, or specific integrations they already support.)
    • What type of data needs to be shared between the systems?
      (e.g., customer information, sales data, inventory levels.)
    • How often does this data need to be updated or synchronized?
      (e.g., real-time, hourly, daily.)
    • How much data will be shared or processed during use of the project?
      (e.g., number of records per day, size of files, number of transactions.)
    • How many users or departments will rely on this project?
    • Are there any specific security requirements for handling the data?
      (e.g., data encryption, user access controls, compliance with regulations like GDPR.)
    • Is any of the data sensitive or confidential?
      (e.g., personal information, financial data.)
    • When do you need the project to be completed?
      (Please provide any deadlines or timeframes you have in mind.)
    • Are there any key dates or milestones we should be aware of?
      (e.g., product launch, end of the fiscal year.)
    • Do you have a budget range for this project?
      (Providing a range helps us tailor the solution to your financial expectations.)
    • Are there any financial constraints or priorities we should know about?
    • Do you have any documentation or resources about your current systems?
      (e.g., user manuals, system diagrams, or any relevant files.)
    • Is there a team member or contact person who can provide more technical details if needed?
    • Will you need ongoing support after the project is completed?
      (e.g., for troubleshooting, updates, or system monitoring.)
    • Do you have any existing support agreements or contracts that we should consider?
    • How will you measure the success of the project?
      (e.g., reduced processing time, fewer errors, increased productivity.)
    • Are there specific features or results that are particularly important to you?
    • How would you like to receive updates on the project?
      (e.g., regular meetings, email summaries, project management tools.)
    • Who will be the main point of contact for this project?
      (Please provide their name, role, and contact information.)
    • Are there any future expansions or additional integrations you are considering?
      (Knowing this can help us design a solution that is scalable and adaptable.)
    • Do you foresee any changes in your systems or processes that could affect the project?
  • As possible, provide the technical details required for the project:
    • Existing Systems: Details about the current systems, platforms, and technologies that will be integrated.
    • Operating Systems: Versions and types of operating systems in use.
    • Data Volume: Expected data size, frequency of data exchange, and peak loads.
    • Data Mapping: Required data transformations, mappings between different systems, and any necessary data cleaning.
    • APIs: Specifications for existing APIs, including authentication methods, rate limits, and available endpoints.
    • Web Services: Details on SOAP or RESTful services, WSDL files, and service documentation.
    • Middleware: Any middleware or integration platforms already in place (e.g., enterprise service bus, message brokers).
    • Third-Party Services: Information on external services or applications that need to be integrated.
    • User Authentication: Mechanisms for user authentication (e.g., OAuth, SSO, LDAP).
    • API Security: Details on API key management, token expiration, and security protocols.
    • Performance Requirements: Minimum acceptable performance metrics, such as response times, throughput, and latency.
    • Testing Environments: Information on staging or sandbox environments, including configurations and data sets.
    • Validation Criteria: Acceptance criteria for integration success, including specific use cases or scenarios.
    • Monitoring & Logging: Requirements for system monitoring, logging, and alerting mechanisms.
    • Technical Documentation: Availability of current documentation and requirements for new documentation.
    • Support Structure: Information on support teams, SLAs, and escalation procedures.
    • Training: Requirements for training on new systems or integrations.
    • Regulatory Requirements: Industry-specific regulations that need to be adhered to during integration.
    • Audit Trails: Requirements for maintaining audit trails, logging, and reporting for compliance.
  • Attach or link any documentation or specifications related to the planning of this project.
  • Are there any other details or requirements you would like to share with us?

Step 2: Email your request

Send your completed request to: development@vesigo.com

A member of our team will contact you regarding your request.

When we were doing 300 stops a day and I was using QuickBooks for billing I would spend about 50 to 60 hours a month on billing. Now we’re doing over 450 stops a day but thanks to OnTime (which integrates with Quickbooks) last month I did all the billing in about 20 hours. I cannot express how happy that makes me.

Zach Woody | Dash Delivery, Inc.