## Ammended SOW Content

### Maintenance deliverables

- General server maintenance and monitoring
- Address all support issues
- Work with IT to resolve pen test results
- Increased maintenance activities to support v3 platform
- Production, dev and testing/demo environment management and cost
- Development focus on v3 infrastructure security based on latest pen test result

With the continued development of v3 we will need to maintain and have support around the new servers and infrastructure. This runs parallel with the current cost of maintenance and support on the live v2 version. Keeping the v3 system up will allow us to continue working on the development deliverables stated below. Both systems will need to be maintained and updates need to be made in two places. This includes servers, integrations, and security.

#### Cost

- Aug: $5,000
- Sep-Dec: $10,000 (x4)
- TOTAL: $45,000

### Development deliverables

- Finish v3 platform feature development
- Interior layout admin tool
- Cover layout admin tool
- Spark authentication integration
- Testing and quality assurance cycles for v3 platform
- Bug fixing
- Making enhancements by addressing stakeholder feedback
- Content updates
- Design adjustments
- Feature adjustments
- Deployment preparation development
- Production infrastructure readiness
- Parallel v2/v3 deployment strategy

If development is delayed until January of 2024 we will lose the current momentum and have to restart with a new team. This will push out the time to release by a minimum of 3 months. Continuing this work until the end of the year provides time to incorporate feedback to continue improving the product to increase confidence and prepare to take the product live.

#### Cost (invoices deferred until Jan 2024)

- Aug: $36,000
- Sep-Dec: $18,000 (x4)
- TOTAL: $112,500

## 2024 Planning

Commitment to work together on 2024 planning to ensure we can support:

- January deployment
- Post deployment support
- V3 platform maintenance
- V2 platform maintenance until we turn off the v2 platform
- New product enhancements and features enabled by v3 platform

-----

## Response

We would like to explore how we could make option 1.b. work for both of us:

*"You continue with the current development work but delay development-related invoices until January 2024."*

Keeping development momentum is ideal for us to get the platform production-ready. Option 1.a would be risky because delaying dev invoices does make it hard for us to maintain resources and deliver at the rate we've been working up until now. Moving deployment out until Jan 2024 allows us to focus the rest of the year on finishing development and refining the platform at a lower rate of development requiring less resources.

We'd propose Aug-Dec focus on:

- Finishing platform development
- Testing and bug fixing
- Addressing your feedback to refine the platform
- Development to prep parallel platform deployment in January
- Continue v2 maintenance + pen testing updates

#### Consideration for a revised SOW

Current SOW:
- Previous cost per month
- Maintenance: $5,000
- Development: $36,000
- This was set to run up in September, so what would still be outstanding from the $415,000 total in that SOW was:
- Maintenance: $5,000 (invoiced in August)
- Development: $40,050 (deferred until 2024)

New SOW:

## August
- Maintenance: $5,000
- Development: $40,050 (deferred)

## September, October, November, December
- Maintenance: $10,000 (x4)
- Development: $18,000 (x4) (deferred)

## Total
- Maintenance: $45,000
- Development: $112,500 (deferred)

## Notes
- After August We would propose lowering that monthly development cost (invoices deferred until January) to $18,0000 per month Sep-Dec
- Is there any room in your maintenance budget to up what could be billed on that side? If we could bill $10,000 per month instead of $5,000 it would help us retain some resources to ensure a succesful Sep-Dec along with the extra maintenance of the v3 infra and servers so we can continue to host the v3 demo site.
- We could then engage in planning for 2024 and determine what an SOW could look like to support Jan deployment + maintenance + future projects.

-----

## SOW

### Current contract

Costs Per Month
- Maintenance: $5,000
- Development: $36,000

Timeline:
- Oct-2022 thru Aug-2023

Outstanding owed (after july 26 invoices paid):
- Maintenance: $5,000
- Development: $40,050

### Notes for new contract

Continue work as outlined in option 1.b.

- August-December Focus:
- Finishing platform development
- Testing and bug fixing
- Address Ingram Feedback to refine the platform
- Development to prep parallel platform deployment in January

- Cost:
- Up maintenance budget to $10,000/mo = $50,000 total paid in 2023
- enables us to keep some developers on the team
- Lower development cost to $18,000 = $90,000 total - invoices delayed until 2024

- Work on defining 2024 SOW 2023 Q4
- January deployment
- Post-deployment support
- New project opportunites

## Notes

- SOW total of $415,000
- maintenance: $55,000
- dev: $360000
- Ingram has paid $369,950.00 since 10/3
- this includes outstanding invoices to 7/26
- maintenance: $50,000
- dev: $319,950
- Ingram owes us $40,050 to meet 2023 SOW

## Ingram email

Hi Team Odyssy,

We wanted to follow up from our meeting earlier this week with a recap of the options we have for moving forward in light of the budgetary issues we discussed. Here’s a quick summary of our options as we see them today:

1. We continue with development:
a. You continue with the current development work but delay development-related invoices until January 2024. We would continue to pay maintenance-related invoices through the remainder of the year and would pay the current open invoices we discussed through July 26, 2023. The timing of the rollout to production would remain the same with no changes – September 2023 for new users while current users would continue on the current version of the tool through the remainder of 2023.

b. You continue with the current development work but delay development-related invoices until January 2024. We would continue to pay maintenance-related invoices through the remainder of the year and would pay the current open invoices we discussed through July 26, 2023. While development would continue, the roll to production would not happen until 2024, after the development-related invoices for 2023 are paid in January 2024.

2. We cease new development entirely and go straight into maintenance mode.
We would pay the current open invoices through July 26, 2023 but only receive and pay maintenance invoices through the remainder of 2023. Development on the V3 tool would pause until January 2024 and the only work completed by the Odyssy team for the remainder of the year would be related to maintenance of the tool. We would then fold the remaining development work into a new 2024 SOW, at which time development would resume.

In any of these scenarios, we would need to consider what a revised SOW might look like to outline the path forward. Also, work related to the pen testing would be considered a maintenance cost that would fall under the description of maintenance invoices above. This work would continue until any open issues are resolved to Ingram IT’s satisfaction.

Please let us know what further discussions are needed and how you would like to move forward.

## Reference

[2023 sow](https://drive.google.com/drive/folders/18dyHJwPnYqq-Lu0JA0lpY19ztb4EFSTU)