Battlecard (YC W20) helps teams organize and collaborate on their playbook. Playbooks tend to be a sprawling mess of Google Docs. Battlecard enforces good documentation practices with its opinionated interface, and encourages training to be done on the platform with interactive roleplay activities.
Why join us?
We have seen 50% week on week growth and have cracked over $50K in ARR just 1 month after launching.
Founders have been working together for over 4 years and have a strong vision of where to take this product.
We are funded by FCVC, Soma Capital, and GSV Ventures alongside YCombinator.
Engineering at Battlecard
Currently, our engineering team is just the founders. While both Rikhav and Mathew are technical Mathew is focused on sales and customer success, as well as design, and Rikhav is focused on the product implementation.
We use Vue Router but a grand majority of our code lives in React! We use Laravel for the backend which is mostly just bridging the Frontend and the Database. We are soon to build a Desktop App and Live Call Listener.
The original feature that started this product was a way to simulate sales calls for training. This had a lot of difficult technical challenges on how to structure these calls, but also challenges with designing the User Interface to build your own simulated sales call.
You would build a listener to live sales calls, using Twilio, that then fed that audio into the Chrome Speech Recognition API to provide live, call assistance on the Battlecard platform.
You would build a way to use the entire Desktop app via just keyboard shortcuts so that using Battlecard on a day by day basis felt effortless.
Working at Battlecard
We are focused on building good products from the get-go: we spend a decent time whiteboarding what the implementation should look like to ensure we don't need to refactor the code too many times in the future.
We are very fast moving, often building features for a customer the next day. We are able to ship quickly by building frameworks that predict what the common, user requests are going to operate on, and ensure those requests are operating on something built for quick, non-hacky iterations.
Interested in this company?
Skip straight to final-round interviews by applying through Triplebyte.