I look at the funnel you already have — forms, landing pages, the path to signup — and test structural changes rather than button colours. The gains almost always come from removing a step, not from persuading harder.
Traffic is fine and conversion isn't. A funnel drops at a step nobody has examined closely. Or a series of A/B tests have run, all been declared wins, and the overall number hasn't moved.
Most conversion work fails because it optimises the wrong layer. Button colour tests are the easiest thing to run and almost never the reason people don't convert. The reason is usually earlier: unclear value, a missing piece of information, a form asking for something the visitor isn't ready to give, or a mismatch between what the ad promised and what the page delivers.
So I look at the whole path before changing anything on the page. Then test the biggest doubt first, with a hypothesis stated as a sentence rather than a variant name.
I'll also say when a test isn't worth running. At low volumes many tests can't reach significance, and running them anyway produces confident nonsense.
Three to four weeks for analysis and a test plan. Running and iterating suits an ongoing arrangement.
We don't have much traffic. Can we still do this?
Yes, but through qualitative work and reasoning rather than A/B testing. Low-volume sites are better served by fixing obvious breakage than by waiting on significance.
Do you implement the changes?
I can build and specify. Implementation in your stack usually sits with your team.