How Flowcode delivers quality to 65 million people, saving 1000+ debugging hours w/ Jam
“Some of the biggest brands in the world are using Flowcode. We need to make sure the product is as smooth and easy to use as possible. Jam helps us do that faster.”
Flowcode is trusted by 77% of the Fortune 1000 to connect with their massive offline audiences.
From the launch of SKKN (Kim Kardashian’s $1BN cosmetics company), to NBA All-Star games and live CNBC broadcasts; Flowcode helps businesses easily capture audience info from what happens outside the internet.
Millions of people interact with Flowcode QR codes every day. They all need to have a great experience. Flowcode customers count on it! And they deliver. Flowcode’s DTC tool suite has a conversion rate of 34% — that’s a big deal, most offline campaigns convert at a benchmark below 1%.
With these results and sheer volume, quality and reliability on either side of the product experience are non-negotiable.
Recently, we caught up with Sumer Rathinam (Product Manager), Andrew Hawk (Growth PM), and Max Block (Technical Account Manager) at Flowcode to learn how Jam helps their team ship faster while maintaining exceptional quality.
The challenge
Getting the technical context developers need to fix bugs fast
Flowcode has achieved remarkable product velocity and quality with a lean team. But reporting bugs was a tedious and time-consuming task for developers, their PMs, and customer success.
"People used to just take screenshots, which would turn into a bunch of back and forth in Slack threads. There was a lot of context lost between what was actually happening and being able to reproduce and get to the root cause" — Sumer Rathinam, Product Manager, Flowcode
The engineering, product, and success teams needed a way to simplify bug reporting, reduce back-and-forth communication, and get all the context needed to fix issues quickly
The solution
One-click bug reports with automatic debug data
With Jam's browser extension, anyone at Flowcode can report bugs in seconds - complete with network requests, console logs, and reproduction steps.
“Every Jam comes with a dev console - so devs can quickly identify which network call is specifically associated with the error that shows up in the user sessions; and map that on a timeline to exactly when the error occurred, and which network request failed in real-time.”
— Max Block, Technical Account Manager, Flowcode
Jam’s simplicity made it an easy choice for the Flowcode team:
- Automatic technical context: console logs, network calls, and environment details automatically added to every screen recording or screenshot
- Bug replay: capture hard-to-reproduce issues up to 2 minutes after they happened
- Faster Linear tickets: instead of writing up a ticket, Flowcode uses Jam’s Linear integration to assign Jams as tickets in 1 click.
- Built-in investigation: engineers don't need to create spike tickets to investigate issues because Jam automatically captures what the broken calls are.
Now with Jam, all of that is basically streamlined into a video that has all the developer information in one of our linear tickets, and you cut out all the back and forth.
— Sumer Rathinam, Product Manager, Flowcode
The outcome
3x more bugs fixed + 1000 hours saved to build what’s next
Since implementing Jam, the EPD org at Flowcode can capture and fix 3x more bugs, faster.
If I have 20 minutes a day to find bugs, before Jam I would maybe find one or two. Now with Jam I can find five, six bugs in that 20 minute time period. So, that’s 3x on bug finding velocity.
— Andrew Hawk, Growth PM, Flowcode
The team has captured over 1,400 bugs using Jam, saving significant time across engineering and customer success.
Since using Jam, we've saved over a thousand hours of time for our developers to be able to actually go in and fix bugs faster and then spend more time developing core features.
— Sumer Rathinam, Product Manager, Flowcode
With Jam, Flowcode has been able to remove duplicative work throughout the whole software development lifecycle. From staging QA to wider bug bashes with customer success, Jam is the fastest way to collect bug information.
For example, Jam came in really handy during development of Flowcode’s new AI generator:
We did a bug bash last week with the team and they recorded any bugs with Jam. You don't need to hop on a call to discuss the bugs. You can let everyone be heads down and not disturb their workflow.
— Andrew Hawk, Growth PM, Flowcode
This increased efficiency means Flowcode can maintain their high quality bar and keep shipping new features even faster.
Building the future with Jam
With increased bug-catching speed and thousands of hours saved, Jam has become an essential part of Flowcode's development process. With Jam, Flowcode can ship more new features their users want while maintaining the exceptional quality their enterprise customers expect.
Quality matters because our product touches millions of people every day in the real world. The more people that can have a positive experience from using Flowcode, both from the consumer side and from the business side, is really what we're in the middle of - creating that magical experience that allows both people to have value.
— Sumer Rathinam, Product Manager, Flowcode