-
★
★
★
★
★
“Working with him never feels transactional. It feels like building something together.”
-
★
★
★
★
★
“Of course, I'll always know who to tap if I need a WordPress guru!”
-
★
★
★
★
★
“Entertaining and engaging talk – more directed to WordPress developers and consultants – was hoping for a little more about how people using WordPress as a platform can make money.”
-
★
★
★
★
★
“This is absolute gem of a presentation by Chris Ross which proves yet again that you can still earn a decent wage by providing VALUE to people for free.”
- Where do these testimonials come from?
Clients I have delivered for, WordPress.org users reviewing plugins I publish, LinkedIn recommendations, and post-engagement email. Each card links back to the original source where one exists publicly — the WordPress.org review page, the LinkedIn recommendation, or the case study the quote was pulled from. Nothing here is paraphrased or reconstructed.
- Are these edited or curated for praise?
No editing — typos and all. The selection is for variety: different services, different team sizes, different countries, different decades. Some testimonials are short because the writer kept them short. The page is not a wall of five-star superlatives, and it is not meant to be.
- How do I verify the people are real?
Public-source testimonials link back to the verifiable original — the WordPress.org plugin page, the LinkedIn recommendation, the platform that hosted the review. Email-source quotes are attributed by initial, role, and region by default, with full name and engagement context only where the client gave written consent to attribution. If a card looks anonymous, that is the consent boundary, not a sign that the quote is invented.
- Can I leave a testimonial if I have worked with you?
Yes, please. Email or LinkedIn message works for a direct quote; if the engagement included one of my free plugins, a review on the WordPress.org plugin page is the most useful place because it helps other potential users too. Either route reaches this archive on the next refresh.
