Work
Client notes, in their words.
Short accounts of the work — not a case-study factory.
“I have hired a lot of shops that talk more than they ship. These people argued with me about scope, then they actually closed it. When something broke after we went live, they were still on the thread. That is rarer than it should be.”

Slavo
Director, Penrod
“We did not need another vendor deck. We needed someone who would sit in the code and not disappear after the first demo. They did the unglamorous parts — the data, the edge cases — and we could run it without them in the room.”

Anton Storozhuk
CEO, Metrica Software Inc
“Plenty of teams will bolt a model onto a screen and call it done. I wanted the thing wired into how we already work. They asked better questions than I expected, cut two ideas that would have been noise, and shipped the one we still use.”

Steve Komplot
CEO, Real Intelligence
“What I cared about was whether they could keep up without creating a mess for the next team. Communication was plain. The work was reviewed. I did not have to chase status. That is the bar, and they cleared it.”

Arcène Goossens
Director, Salesforce
“We brought them in on a piece that was already mid-flight. They did not insist on a restart. They read what we had, told us what was going to hurt later, and fixed that first. I would hire them again for that reason alone.”

Anthony
Director, Vicasso
“I am picky about code review. They did not get precious about it. PRs were small, notes were specific, and they did not hide the ugly decisions. For a technical lead, that is the whole job.”

Guillermo Larranaga
Technical Lead, Neocol
“We have seen partners who look senior on the call and junior in the repo. This was not that. They took ownership, they wrote things down, and they did not need a meeting to move a ticket. That is why I would send them more work.”

Craig Isakson
Technical Director, Perficient
