Overview

What is Rough?

Rough lets SaaS customers extend a product themselves — building lightweight features on top of it, without code changes from the vendor.

The short version

Rough is a way for the people who use your software to add small features to it themselves — directly inside your product, without waiting on engineering. As the vendor, you decide where Rough lives, what it can touch, and what kinds of features your customers can build.

Internal teams use it the same way. Sales, Customer Success and Product can plug feature gaps without filing tickets. The features they build run inside your product, alongside everything else.

The problem we're trying to solve

Every B2B SaaS product has the same problem at scale: a long tail of requests that are individually small, collectively enormous, and almost never important enough to make the roadmap. A weird CSV export. A tiny workflow tweak. A custom view nobody else asked for. Multiply that by every customer, every CSM call, every sales conversation, and most product teams end up either stuck in the long tail or ignoring it entirely.

Both options cost real money. Stuck in the tail means the roadmap stalls. Ignoring it means deals slip and customers churn.

Rough is built around the idea that the people closest to those requests — customers, sales reps, support engineers — can solve a lot of them themselves, given the right surface to work in.

Who Rough is for

Rough is built for B2B SaaS companies that need to move fast. Specifically, leaders who are either trying to stay at the cutting edge of what's possible, or trying to get out of some form of stagnation. If you have a product with real users, a long tail of requests, and not enough engineers to chase all of them, Rough is for you.

The teams that get the most value from Rough are usually:

• Product teams who want to absorb edge cases without derailing the roadmap.
• Engineering teams who want a controlled extension surface they don't have to build from scratch.
• Sales teams who keep losing deals to "can it do X?" questions.
• Customer Success teams who want to resolve customer requests without engineering involvement.
• End users who know exactly what they want their software to do, and just want to get on with it.

How it fits in

You embed a Rough surface into your product wherever you want — a panel, a sidebar, a section on a page, an empty corner of a dashboard. Your users open it, describe the feature they want, and Rough builds and renders it inside that surface. You stay in control of where surfaces live, what data they can read, and what they're allowed to do.

For an interactive walkthrough, visit the live demo.

Where to go next

• Features — what a Rough Feature actually is, what it can do, and what it can't.
• How RAF works — the pattern underneath everything Rough does.
• Security — how features stay sandboxed and how data flows.