Get Revenue-Driving Features into Production. Sooner.

Non-technical SaaS founders: You're wrangling a firehose of new feature ideas, customer feedback, analytics data, and bug reports. Everything from grand new initiatives to sales copy changes. You're doing your best to turn this into something manageable for your product and engineering teams.

You probably don't yet have a VP of Engineering or Product. You can't (yet) justify hiring them, but that doesn't mean you can't build a low-friction pipeline that takes product ideas from inception through execution to delivery, evaluation, and iteration.

Seriously, this can make or break your company. The faster and more reliably you can get the right ideas into production, the sooner you can validate those ideas and iterate on them. The more quickly you can iterate on your ideas, the better you can delight your customers, boost your NPS, go upmarket, and do all those other things you know you need to be doing.

Ask yourself these questions:

  • When faced with the mountains of potential things you could commit engineering resources to, do you have an objective way to evaluate the most pressing items?
  • When you have decided to commit engineering resources to a problem, do you have a clear, unambiguous format for communicating requirements, so that your engineers are more likely to build the right thing the first time?
  • If you got a status update this morning from your engineering team, was it useful to you at all?
  • Can you show your current or potential investors a coherent product roadmap and a demonstrated ability to deliver on it?

Right now--RIGHT NOW--you can start smoothing out this process. Your team is more than capable. With the right leadership (that's you!) and the right process (that's me!), they will build the right things.

Get help delivered to your inbox

5 actionable lessons will teach you to create a coherent product roadmap and execute like your business depends on it.

"Ben's work is already worth the investment and will continue to pay dividends far into the future."

Our product team had reached a size where the classic early startup "hustle" (i.e. a couple people huddled around a computer writing as much code as possible) was becoming less practical and effective.

Ben has completely revamped the way that our team plans, scopes, and builds product features. Because he's done so in a way that jives so well with the way our team likes to work, the new habits and processes he's implemented have stuck.

He didn't simply take a boilerplate process and apply it. He was careful to listen to our team's specific requirements, preferences, idiosyncrasies, and appetite for change and turn that into bite-sized, custom optimizations that made the most sense for us. Ben's work is already worth the investment and will continue to pay dividends far into the future.

James Francis

James Francis
CEO of Screencastify
10 million weekly users
Read the Case Study

Recent Articles

How to do a Research Spike

What do you do when you don't have enough information to confidently commit to a feature? Research spikes deliver value to your product in the form of reduced uncertainty.

Read it →

How Do You Build a Team?

High performing teams have a strong sense of team identity. They are a resilient, self-correcting system, but this culture must be intentionally created and cultivated early on.

Read it →

Be an Expert, not a Dictator

I was leading a retrospective with a client team today, and one of the developers suggested a change to a process that I'd put into place; a process that I've used successfully with other teams for years.

Read it →

You'll Never Get it Right the First Time

When you really understand and accept this, it's incredibly liberating. Move early and make sure you have tight feedback loops to evaluate how you're doing and make improvements.

Read it →

Get in touch

Questions? I'd love to hear from you! Drop me a line at [email protected]