What to do when the Products are poor?


I work at a small(ish) web agency and we’ve been fortunate enough to hit upon many of the big paradigm shifts while they were still in the custom built phase. (responsive websites, using WordPress as full blown CMS, Headless websites).

But now we have a new “problem”. A client is using A/B testing on their site. A/B-testing is clearly in the Product phase, but all the products come with big drawbacks. After learning about Wardley Mapping I feel kind of bad for selling a custom built solution to them.

Does anyone else recognise this challenge? In my opinion it makes sense for them to pay us to custom build a product that will be inferior in some respects (fewer features) but superior in others (no 3rd party code injection, no freezing of the render stack due to said code injection).

1 Like

Great question, I guess my immediate reaction would be that the virtue of A/B testing to help the client establish the customer experience helps them determine if off the shelf products might be a viable option in the future but in the interim it would be ok to go with custom built if nothing meets the client need.

Thank you for your thoughts, they helped me see the issue better.

This morning on my way to work (it’s when I usually get my best ideas) I suddenly realized something about my problem. The issue wasn’t that there are products out there and that I should feel bad for us building a custom made one.

What was needed was a more precise definition of the user need. There are some needs that are met by the existing products but there are others that aren’t.

Our custom made product fixes thee needs that the available products can’t adress. Mainly that it runs server side, second need is the fact that it doesn’t inject 3rd party JavaScript on the site.

1 Like

There are other server side / edge side A/B testing frameworks

I guess that challenge is how does you solution differ to theses, or could it complement one?

Mapping them might give you some answers!