Velo
Helping a beloved SaaS product finally look like what it is.
The website finally does the selling.
A product people loved. A website that did not show it.
Velo had quietly become one of the most loved project management tools in the remote-first startup world. An NPS score of 67. Organic growth driven almost entirely by word of mouth. Eight thousand companies across forty countries using it every day to manage distributed teams, track projects, and keep async work moving forward.
The product was genuinely exceptional. The website was not. Built by the internal engineering team during the early days when shipping the product was all that mattered, it looked like every other SaaS tool on the internet. Dark background, generic floating UI screenshots, buzzword heavy headlines, and a pricing page that answered none of the questions a potential customer actually had.
The website was doing the sales team's job badly.
Every Velo sales demo started the same way. The first twenty minutes were spent explaining what Velo actually did because the website had not done that job. Prospects arrived on calls confused about who the product was for, unclear on how it differed from Asana or Monday, and uncertain whether the pricing made sense for their team size.
The website was supposed to pre-qualify and pre-sell. Instead it was creating friction and extending the sales cycle. For a company with a genuinely differentiated product and a passionate user base, that gap was costing them real revenue every single month. The problem was not the product. It was never the product. It was the first impression the product was making.
Answer the questions before they are asked.
We started by sitting in on three sales demos. Not to understand the product — we understood that quickly. To listen to the questions prospects asked before they understood it. Those questions became the architecture of the new website.
Every section on the new site answers something a real potential customer needs to know before they feel confident enough to request a demo. We rewrote every headline to speak directly to the pain of managing remote teams — not to the features of the software. We rebuilt the pricing page from scratch around the decisions a buyer actually makes rather than the tiers the company wanted to sell.
We replaced generic floating UI screenshots with real workflow scenarios showing exactly what Velo looks like when a distributed team is using it on a real project. The difference between a screenshot and a scenario is the difference between showing a product and showing a transformation.
The project management tool your remote team will actually use.
Velo keeps distributed teams aligned, async work moving, and projects shipped on time. Used by 8,000 companies in 40 countries.
The website finally does the selling.
Within sixty days of launching the new site Velo saw a 34% increase in demo requests. The sales team reported that prospects were arriving on calls already understanding the product, already sold on the differentiation, and asking better questions about implementation rather than basic functionality.
The sales cycle shortened by 22%. Trial to paid conversion improved by 18%. The website went from a liability to an asset. From something the team apologised for to something they sent prospects to with confidence. The product had always been exceptional. Now the website was too.