WyeWorks

I’m the director of the Research Cores program at Northwestern University.

We have a custom web application called NUcore that we developed to manage the program here. It's a large, fairly complex application that is actually used by four different universities. Our previous developers had already been working with WyeWorks, but they decided that they weren’t going to support the app anymore, so they transferred all of the development to WyeWorks.

WyeWorks has taken over the development and support of our web application. The app is a transaction processing platform written in Ruby on Rails and running over several different database systems at different locations. For example, we use Oracle here, but some of the other universities that use the software use other database applications.

We have a lead developer, two other developers, and a project manager from WyeWorks.

Our previous developers had already been working with WyeWorks, so we came to them through our prior developers.

We’ve spent about $200,000.

We started working with them in December 2024, and our engagement is ongoing.

The transition was pretty seamless because they were already involved in the project. WyeWorks’ primary metric is the speed with which they develop features and the quality of the code they write, which is reflected in the application's performance. They’re very efficient and code faster than our previous developers. We’ve had no issues whatsoever with the code they’ve written.

They’re always on time. They can be a little bit over budget, but nothing unreasonable. We use Jira for project management and Microsoft Teams, Zoom, and email for communication.

We’re really impressed with their efficiency. They grasp concepts very quickly and build solutions much faster than we’ve experienced in the past. Moreover, they don’t rush and develop bad code; they write very good code efficiently.

Not really. We’ve been very impressed.

Be very clear with them about what you need. They’re capable of delivering almost anything.

I’m an engineering leader at Cisco Meraki. We provide cloud-managed IT solutions that simplify networking, enhance security, and optimize digital experiences for businesses, making IT management easier and more efficient.

We needed help upgrading our monolithic Ruby on Rails application to the latest versions.

WyeWorks manages the end-to-end Ruby on Rails upgrade process for us. This involves a roughly 5 million-line, 16-year-old monolithic codebase that has been running on very old LTS versions of Rails. Getting to the latest versions of both Ruby and Rails is a large, complex, and error-prone effort, and WyeWorks handles the entire project for us.

We work with 6–10 teammates from WyeWorks.

We found them through a referral and conferences. We chose them over other options because they had high ratings, their pricing fit our budget, they were a great culture fit, and they offered good value for the cost.

We started working with them in July 2022, and our engagement is ongoing.

Thanks to WyeWorks, we’re running our Rails application on more modern versions of Ruby and Rails. We’ve also achieved security compliance and unlocked new capabilities such as DB replicas and OTEL. Moreover, the Ruby upgrade (with YJIT) has made Rails response time between 20%–50% faster while saving around 30% on CPU.

WyeWorks is excellent at project management. They often deliver on time or ahead of schedule. As for communication, we use virtual meetings, emails, and messaging apps.

WyeWorks is reliable, knowledgeable, has a team player mindset, and is flexible.

No, they’re doing great. They’re very flexible and responsive.

I'm the director of technical operations of a SaaS software startup specializing in hiring software. I oversee work across all of our engineering and product groups.

We started working with WyeWorks in March 2024, and our engagement is ongoing.

WyeWorks' team is integrated with our developers and works directly with our engineering managers. All teammates join our meetings on Zoom. WyeWorks' developers have been treated as part of our team, and their performance is on par with our internal team's. We had some communication issues at first to get the team set up and build norms to get them into our everyday workflow. But once we got there, the team has been fantastic. WyeWorks is on top of communication and has been easy to work with.

I love that WyeWorks' teammates are long-term employees. Every teammate we work with has worked with WyeWorks for at least a year, most of them for two years. The team has a wide range of developers, which is really important for me because I need to work closely with a team I can trust. Another strength of WyeWorks is their communication in general. Anytime I have a problem, I reach out to the team and quickly receive a response.

The current state of the global market makes it hard for Latin American companies to compete with service providers from Ukraine or India regarding prices. Although this isn't a direct issue of WyeWorks, their prices can't compete with those of other cheaper companies. However, once we compare their work, WyeWorks' price is competitive because they offer good work value.

I suggest hiring WyeWorks and being as transparent as possible. The team is willing to work with you and wants to help you succeed. WyeWorks offers a partnership, which is what I look for when working with a nearshore company. I like to work with a team that will integrate with our team and not just someone looking for our money.

I’m the director of engineering at HMBradley. I’ve been with the company for three and a half years and started as a regular frontend software engineer.

Around the spring of 2022, we had to migrate our underlying banking core to a new one. The CTO and company leadership decided to have Elixir as the new language. We were entirely written in Go, so we didn’t have any Elixir developers at the time. In summary, we were changing out the engine of the airplane while learning how to read the manual.

WyeWorks provided software engineers to write code. We treated them like any other engineer; we just gave them the work and general outline. They integrated well with the internal team. We partnered with full-time engineers on various projects, and they worked remotely from Uruguay and Argentina.

We always had three developers at the same time, but in total, we worked with six developers. As one rotated off the project, another one would come as a replacement.

Our CEO was very involved in the Ruby on Rails community. WyeWorks’ co-founder was on the Ruby on Rails core team, so he found them through his network.

We spent over $250,000.

We took them on in July 2022, and the partnership ended in November 2023.

WyeWorks wrote code and delivered features independently. We gave them sensitive work, and they took on an entire flow unsupervised. Moreover, the engineers had to learn about the inner workings of the US banking system, which was probably more challenging because they weren’t from the US. However, they consistently shipped features from the data they landed.

All engineering projects can go a little over time, but there wasn’t anything that WyeWorks couldn’t work on. The only project that went over was the one I was working on, and it went over because we didn’t know what we were doing. We rebuilt the feature three times because we didn’t have a good conception of the requirements.

Julian (Software Developer) was super smart and very patient. We really enjoyed working with him; he was with us for nearly six months.

They were great at keeping their cool in a chaotic environment. WyeWorks joined us at a turbulent time in our history. We were doing a big core migration and switching a language, which alienated a lot of our existing staff. We had 4–5 engineers leave within a month, so the morale was rocky.

Our particular architectural style wasn’t a common practice in software engineering; it was a solid pattern, so it was easy to understand. However, it required a bit of ramp-up time and training. Our only feedback was that we had to train the new developer all over again whenever an engineer left.

If you don’t want to invest much time in training, get a minimum commitment for how long an engineer is around. However, it can be a double-edged sword. Many of our full-time developers get to a point of exhaustion because the architecture is a pattern, and they want to work on something different and try new things.

I work at a technology consulting firm as a senior organizational growth associate. We work with other companies to help them craft their digital products, which include strategy, design, and development. In my role, I’m involved in our staffing and recruiting efforts.

We didn’t have the resources we needed, so we required an additional engineer to keep one of our projects going and ensure we didn’t pause it to avoid missing our delivery goal.

We currently work with one of WyeWorks’ engineers — Andrés (Software Developer) — to augment our team. He works remotely for us to support one of our projects.

Besides Andrés, I’ve communicated with the head of their business.

We’ve been partners with WyeWorks for quite some time, so I wasn’t part of the discovery process.

We’ve spent around $10,000–$25,000. However, I’m not entirely sure.

We started working with WyeWorks on this project in March 2023, and our engagement is ongoing. However, it’ll wrap up in May 2023.

The main reason we continue going to WyeWorks to get support is that we’re always very pleased with their work. Andrés has demonstrated excellent skills in React and Node.js, and he’s been hitting all of our goals.

WyeWorks is one of the easiest partners I’ve been able to work with. They’re very accommodating, quick, and responsive, so our engagement has been very smooth. Additionally, they’ve helped us work on a reasonable rate that works for all parties, which I really love. As for collaboration tools, our development team uses Slack and Zoom to communicate. Additionally, they use Miro to collaborate.

WyeWorks is a very professional team. They’re very responsive, and I’ve had a great customer experience collaborating with the head of their business. We have a smooth and strong working relationship, and he has been very accommodating and understanding.

I haven’t been working with WyeWorks enough time to identify areas of improvement. I’ll probably have constructive feedback for them if I continue working with them for more months.

Be specific about what you’re looking for from the engineer you’re looking for to join your team — it’s very important to be specific about your needs. Additionally, if you’re looking to work with WyeWorks for a long-term partnership, I encourage you to be very responsive. They’re incredibly responsive and friendly, so it’s important to reciprocate that responsiveness.