Clevenue

Inspiration

The tech layoffs made it clear that companies were outgrowing their commercial potential, ultimately leading to overhiring and eventual layoffs. We found that this outgrowing came from bad planning, which was filled with bad data and assumptions. That's why we set out to make planning simpler and more effective, reducing the risk of getting it wrong.

What it does

Clevenue makes the process of building sales plans super easy, and ensures that teams are all working to the same data. It removes the need to build a model, instead creating its own model of future revenue, alongside active hiring recommendations. Users can then scenario test their plans to see the impact of changes to different revenue KPIs or hiring & marketing plans

How I built it

Clevenue started off as an hugely extensive spreadsheet which was then plugged into a nocode platform. We then rebuilt the back-end so which transformed our capabilities, which was where the multi-sandbox features were born, and then we replaced the nocode with out own dedicated front end.

Challenges I ran into

The nocode was supposed to support our initial pilots, however we found huge security issues in the platform, at multiple stages of the build. The first issues could be mitigated and meant building our own API to handle the engine, instead of using the nocode data hookups. This wasn't work lost as it would be utilised eventually with our own UI, however it slowed the rapid prototyping - Without it users could have spoofed other users and retrieved data. Then as we were a few weeks from launch we found that the similar vulnerability could be used to expose all users of the platform, which has another hard no for us. We aborted running the pilots and spent the time building the front end. This meant we missed peak planning season, however avoided ever putting customers at risk.

Accomplishments that I'm proud of

The platform is an exciting start to how headcount planning should be run in the future - What we've built around product and brand is really exciting

What I learned

Rapid prototyping is great, but when the problem that you're trying to solve has a high technical bar, there's no simple and easy solution you can build for quick validation

What's next for Clevenue

Growing our customer base, becoming self sustaining & profitable

Built With

• angular.js
• azure
• material