Skip to main content

A Customer Calls It as He Sees It

By
An email from one of our customers this morning reminded me that sometimes it’s best to just get out of the way and let them do the talking.  Following is unedited text from John Weatherby, Director of Product Line Management, at LAB-AIDS (and an umpire in his spare time), on why he recommends Tizra to his colleagues...
                Reliability of TIZRA – we have experienced very little downtime during the course of our relationship and that is critical, especially to teachers that rely on access during class time
                Cross platform Capabilities – This is key in my mind as the diversity of the products teachers and students are using to access TIZRA is an issue. To develop something in-house that would work across all platforms would be fairly complicated
                Technical Support – You guys have done a great job supporting us and troubleshooting problems when they come up. This is something most publishers worry about: will someone be there to help through the process
                Cost – The financial investment to develop a multi-platform product would be huge at this point, then you still have to worry about whether it will work
Competition – We did our due diligence and could not identify another company that was doing the kinds of things TIZRA is doing. Couple that with the very positive feedback I received when I solicited feedback from your customers and in many ways it becomes a no-brainer.
Thanks, John!  You can't buy better marketing than that.
Labels:

Comments

Post a Comment

Popular posts from this blog

Technical Podcasts

By Francisco Assis Rosa
If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...
2 comments
Read more

Using XML to Create a Better Online Reading Experience for the American Payroll Association

By
Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...
Post a Comment
Read more

The importance of continuous integration

By Francisco Assis Rosa
Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...
Post a Comment
Read more