Development cycle analysis is mostly useful. Review collected by and hosted on G2.com.
Product is still not mature enough and it has a lot of quirks. Review collected by and hosted on G2.com.
It has plenty of tools that allow me to better understand my team performance, without going deep into many insights that could confuse me.
Before Typo, I had to crush data which took me a long time and deviated me from my management role. With Typo, there are only a few clicks and voilà, I have all the information I need from each of my Engineers, how the teams are behaving, what to do to fix/resolve slumps we might have, bugs within code and level up the team to be at our highest level possible.
Features like benchmarks within each insight help me visually to better understand where we are, Code Health also helps us understand much better the issues ( Bugs ) we have, the ones that aren't based on the best practices, and the ones we got wrong. Slack's integration allows me to watch when a PR or merge has been done without getting into Typo to find out about it. Review collected by and hosted on G2.com.
If you are a preseed/bootstrapped startup Typo's pricing ain't for you. Review collected by and hosted on G2.com.
We migrated and onboarded to Typo in no time, replacing our previous, more expensive tools without missing a beat. The developer surveys generate truly actionable insights—helping us pinpoint exactly what to fix next. I’m also a big fan of the AI-powered comments on pull requests, which streamline our code reviews. Beyond the product itself, the Typo team is exceptionally responsive on Slack, happily handling bespoke requests—like building a custom cycle-time calculation on their backend to fit our exact workflow. All in all, Typo has delivered huge efficiency gains and real ROI for our engineering team. Review collected by and hosted on G2.com.
Honestly, nothing — Typo has exceeded our expectations at every turn, and we have no regrets switching over. Review collected by and hosted on G2.com.
Best thing is it captures the code health on each PR and specially the Cognitive Complexity in code which we often ignore. It helps in simplifying the code and always helps in finding obvious errors. Review collected by and hosted on G2.com.
I don't see any downsides of using Typo but definitely some improvements needs to be there. Review collected by and hosted on G2.com.
Typo is simple to use and the barrier to entry is very low. With explanations of what metrics mean embedded inside the platform, even junior engineers with no prior experience of KPI's or DORA metrics can learn to about them very quickly. Reports are clear, setup, and onboarding is easy.
Customer support is excellent with our Account Manager very quick to respond and go the extra mile for us at times when needed. Review collected by and hosted on G2.com.
No native DataDog integration at present. Workarounds are available (webhook send from DataDog to a typo endpoint) but require more effort than would be needed with a proper integration in place. Review collected by and hosted on G2.com.
Team progress and status can be easly tracked in a glance Review collected by and hosted on G2.com.
nothing as such in particular which goes into dislike Review collected by and hosted on G2.com.
Value for money product. Very responsive team. Allows for custom reporting. Enables developers to self-manage a lot more of their own work performance instead of being told by someone else. It allows them to course correct. Whilst many vendors in this segment and often organization may be tempted to DIY dashboard, the value offering from Typo enables teams to focus on building what matter more than building & maintaining a metrics dashboard. The industry benchmarks are useful assess performance across the sector (even if just a guideline). Review collected by and hosted on G2.com.
No DIY custom reports, needed Typo to create it. Review collected by and hosted on G2.com.
I like how it identifies a block of code as complex block. Review collected by and hosted on G2.com.
There can be less comments in the PR to not create much noise. Review collected by and hosted on G2.com.
Provides a range of ways to monitor productivity and provide reviews on PRs Review collected by and hosted on G2.com.
Pricing is not good. It shouldn't charge per github seat. It should instead charge per user added to Typo Review collected by and hosted on G2.com.
In my role - the best part of Typo is it's easy to understand expression of Git Metrics. They are good enough that I'm able to directly use them with my leadership, and they're able to get a week-to-week pulse of how the engineering team is performing. Similarly, I review these metrics in a little more detail to help coach up some engineers, teams, and leaders.
For my team - they use it as team leads and individual contributors to get an understanding of how they work has been flowing. Admittedly, we could be doing better here, but Typo gives us all the data we need.
Rolling this out was pretty easy - mostly was three steps: (1) hooking up Github, (2) Configuring Typo to match our workflow, and (3) Meeting with their customer success team to go over any questions I had. I've had a few interactions with that team, and have been impressed with the speed of service and how knowledgable the team is. Review collected by and hosted on G2.com.
I haven't really found much that I dislike - there are some philosophical limitations that might catch some off-guard, like:
1. Metric calculation cannot be instantaneous on configuration change, as there is often a lot of history to recompute
2. Pure Git and Jira metrics are not going to measure team success directly. It's a great, necessary, tool to have under your belt - but you're never going to know if your having good "outcomes" from a tool like this
3. I've had relatively minor bugs that I've reported (but as with any great team, these were solved quickly) Review collected by and hosted on G2.com.
Pricing provided by Typo.
