Hello Owner, Looking forward your valuable feedback on submission #4053914. Thanks!

Couple of supplemental items:
- Our new website and brand are bending more toward a sustainable, airy feel, so designs that are dark or heavy will not fit. Please consider how to soften your color tone and feel.
- I want to make sure that when someone comes across the design, their eye has a "safe space" to land to start digesting it. We're trying to convey a lot of information, so the design needs to partner with the content to help the consumer absorb our message.
- Speaking of partner, one thing that I'd like to see everyone lean into more is the idea of Revere as a partner. We don't just want to do a project with them; we want to become their go-to partner for all their automation and control needs. This often looks like multi-site programs (same work, same company, different locations) and those have a unique approach (rather than just finding a new integrator every time). Something to consider.

I'd also remind that this design is primarily intended for us on a website page alongside other information, so the design needs to have some level of flexibility for different screens and the text has to be readable.

I apologize for the delayed feedback to all. As I've been working through internal feedback, I realized that the reason the designs don't quite flow how I'd like is because the message I gave you to use just doesn't make sense. It's a lot of jargon, but not a concise idea that can be graphically displayed. With that in mind, I think the bones of some good designs are here, so I've extended the project and I'm adding a little more detail that should help.

I've added 2 new images to the brief:
1. A breakdown of the general project cycle that we want to utilize with clients
2. A detailing of the primary services we deliver (the wheel) and key examples of those services (the floating outer pieces). When considering your designs, the concept would be that the services we provide help us support them through the overall project.

Most of your designs are already incorporating some elements that include details like this; let's update to include this here and keep in mind that we want the designs to be outcome-oriented. In other words, we're not trying to talk about technology as the end goal; we want them to see business outcomes as the end goal, whatever those may be for them: getting to market faster, producing more product, less downtime, etc.