Founded by engineers.
Even our recruiters are engineers.

20 years, self-funded, no investors, and no pressure to inflate anything. We put senior engineers into the work for companies that have to defend what they ship, and a human engineer stands behind every output.

2005

Founded

Perform started with performance engineering and QA for companies whose systems could not be allowed to fall over.

2015

Staffing launched

Staffing launched because clients kept asking for the engineers who wrote the report. Vetting was already the craft, so the recruiters were engineers from the first hire.

12

Countries

Engineers in 12 countries, most of them nearshore, reviewing and handing off the same day as the teams they sit with.

2024

Rebranded as Perform

The name changed to Perform because testing had stopped being the whole job. The standard behind it did not change.

Our story

The idea from day one was narrow: engineers who could prove the thing worked, screened by engineers who had done the job.

20 years later it is still self-funded. No investors means nothing here is inflated to make a raise look good, and nobody is asked to sell work we cannot deliver. The work moved from testing to delivery to staffing, and staffing is now how most of our AI work starts. The standard is the one Amit set in 2005. A human engineer stands behind every output, and when something should not ship we say so.

Start with a conversation

Perform engineers working with a client team

Meet our experts

The people who scope your work have done the work. Our recruiters are engineers, so the technical screen is run by someone who could pass it.

Small enough to care, senior enough to matter

20 years of growth on relationships, good work and referrals, with no cold outreach. Every conversation is with a person. We would rather lose a deal than perform certainty we do not have.

We work for companies where a bad release is a reportable event.

They have to ship AI as confidently as everything else they build. We put governed technology into production for them, through engineers accountable to the client, the auditor, and each other.

Amit Patel

Founder & CEO

Lawrence Nuanez

VP of Customer Success & Growth

Ben Humphries

Chief Revenue Officer

Aby Yohannan

VP of Client Delivery

Dino Cajic

VP of Artificial Intelligence

John Spencer

VP of Growth Strategy

The company record

2005Founded by engineers. Self-funded ever since, with no investors

1,000+Engineering projects shipped

12Countries our engineers work from, most of them nearshore

5 to 7 yearsHow long a client relationship usually runs

18 yearsOur longest client relationship, still running

The hard part of AI has moved.

The hard part of AI moved. Building the model is no longer where projects stall. Getting one past legal, risk and validation is, and keeping it governed once it runs.

Adoption is a trust problem. We build for the reviewer from day one, because a system the reviewer cannot pass is a system that does not exist.

AI does not replace your developers. It replaces the roles you cannot hire for.

One thing in production beats four pilots waiting on review.

Who we are wrong for

No engineering function to embed with

Our engineers join a team and work to its standards. With no team to join, there is nothing for them to plug into and the model does not work.

Shopping for the cheapest hands

We sit in the middle of the market and we say so on the first call. If rate is the deciding factor, someone else will win and should.

An AI ask with no workflow behind it

If nobody performs the task today, there is nothing to measure the AI against and no way to tell whether it worked.

Why we say this out loud

Finding this out in month three costs both of us more than finding it out on the first call.

Customer stories

Camis · Reservation platform

The first season that opened without a waiting room

A camp reservation platform buckled above 100 concurrent users, and a year of demand arrived in about an hour. The waiting room had managed the symptom for three seasons.

Under 100 to 1,000Concurrent users

Over 15s to under 3sPage response time

Read the story

CommScope · SAP performance testing

The year performance testing moved in-house

Tests were being requested so late in the lifecycle that nothing they found could be acted on. Leadership wanted the capability on their own team. We built it there.

72 test casesConverted to Tricentis NeoLoad

Their own teamRunning it after handoff

Read the story

I built Perform in 2005 to be the partner I wished I had. Engineers who can prove the thing works, screened by engineers who have done the job.