We've been around since 2005. We are profitable and self-funded. We don't have to please anybody but our customers.
There's nothing wrong with being small. "Small" means "fast". Something big companies are incapable of.
Before founding Jitbit in 2005 Alex worked as head of IT in several organizations, managing help desk teams and automating techsupport. Lead developer, designer, MCSD, MCDBA, MCP, MC<you-name-it>. Loves snowboarding, mountain-biking, bass-guitars and blogging. But above all - coding.
...and we really do mean "officer". Art served in the Israeli army, special forces. When he says "this is our new design", we say "SIR, YES SIR!"Yeah, yeah, I know... An "Al Farakh" co-founder and an Israeli soldier working together, please save your jokes, we heard them all ;)
Vlad is our head of customer success and he's the reason our customers love us. Period.
He's there 24/7, literally. Well, except when he's paragliding, which he's a huge fan of.
Robbie writes all the awesome stuff you see in our blog, builds our website and makes it Google-friendly. An Aussie living and working in the US, full-stack digital strategist that we're lucky to have working with us.
Helen Gerson in Chicago (IL), Serge Schel in Seattle (WA) and other even more awesome folks work for us in London (UK), Chicago and Tel-Aviv (Israel).
As a profitable company we have only one boss - the customer. We don't have to survive from one funding round to another, we concentrate on building a sustainable business around a cool product instead.
We are very open about our success and failure, both within the team and with our customers.
"Where are you based"? Everywhere, from Hong Kong to Seattle. We know a heck of a lot about supporting customers in different time zones, which helps us build an awesome customer service tool.
I've recently bumped into several conversations about outsourcing customer support, mostly among bootstrapped software founders who are (obviously) overwhelmed with work.
How should a support agent deal with unresponsive users - who create tickets and then don't respond? ITIL tells us an incident should only be closed by the user who created it. Otherwise the ticket should be put "on hold". But in reality... There's only so much you can do: