For Sales

Rough for Sales teams

The conversation that keeps happening

Late in the process. The buyer is sold on the product. There's one specific thing they need. A custom view. An integration tweak. A workflow nobody else asks for. You don't have it. They go quiet.

You can ask product. You can ask engineering. You can promise something and hope. None of those work fast enough, and "we'll add it to the roadmap" stopped being persuasive a long time ago.

Build the thing

Build the thing. In the demo, on the call, while the buyer is watching. Or in a follow-up that goes out the same day. Rough lets you describe a feature in plain language and get a working version of it inside the customer's instance of the product.

You're not promising a roadmap item. You're showing the working software. That changes the shape of the conversation.

How to use it in a deal cycle

Discovery. When a buyer mentions something the product doesn't do, write it down — but don't park it. Most of the time, it's something you can build.
Demo. If the request is small, build it live. The effect is disproportionate to the effort.
Follow-up. For requests you don't want to build on the spot, send a working version of it the next day. Customers who've received working software in a follow-up don't go cold the way they go cold after a normal demo.
Procurement. "We can build this for you" beats "we'll consider it for the roadmap" every time.

What you're actually selling

With Rough in the picture, you're selling the product as it exists today plus the surface area for the customer to make it fit. That's a different sale, and it's usually a stronger one. It doesn't depend on perfectly anticipating what the buyer will need a quarter from now.

What not to oversell