Skip to main content

NetSuite Buys OpenAir For $26 million

TechCrunch just reported that NetSuite Buys OpenAir For $26 million

This is interesting from a few angles. I've used both and I continue to use OpenAir for my timesheets having started almost (jeez!) 8 years ago. They have always struck me as a great company. They have a very straight forward policy: new upgrades every month.

They might be small, they might be large (they just announced Crystal Report integration this past month) - but they always deliver a set of updates every month.

And the price point is right - while I don't know what their current offering goes for, they have been able to keep my company on the same month to month cost for the entire time, less than $300 a year.

I've always wondered how they were doing as an overall business since they didn't really fall into the whole Web 2.0 stream but still had a huge number of industry relationships.

NetSuite, on the other hand, I really can't say. For an expensive solution (close to 30K for a small company implementation), the UI looked great but the end-run implementation was terrible. That could have just been our implementation experience but it left a bad taste in my mouth. One of those "so much possibility, so little delivery".

Everything I've seen about NetSuite however, does show that it is a real good force to compete with SalesForce and other tools - but they do approach the business somewhat differently than OpenAir.

When a client of mine was evaluating sales automation tools, in fact, we looked at Open Air as a possibility. While it didn't look as "sexy" as the others, it did offer really valuable features. I for one, love the online invoicing - I've been paperless on invoices since 2001.

I hope OpenAir stays the same great company I've always found but if this is what they wanted, good for them!

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...