QuickBooks SDK Integrations, Cloud Hosting, and the Customer Relationship

QuickBooks SDK Integrations, Cloud Hosting, and the Customer Relationship

Intuit QuickBooks desktop editions are the most popular small business accounting software products on the market, boasting somewhere in the neighborhood of 3.5M users.  In contrast to the QuickBooks Online Edition, which has approximately 300,000, desktop QuickBooks still reigns supreme with small business.

While QuickBooks satisfies most of the general business functionality required from a general accounting product, it doesn’t address much else.  For this reason, numerous software developers have created the software products – the extensions, integrations, widgets, and tools – that make QuickBooks more useful to the business.

The sheer popularity of the QuickBooks product line has supported the creation of a very large and diverse community of developers who make things that work with QuickBooks.  However, as with any attempt to bring like-minded people together, the QuickBooks developer “community” is not all-inclusive, and there are lots of ISVs (independent software developers) out there who aren’t communicating with Intuit frequently, and who aren’t necessarily exposing their solutions through the Intuit marketplace and other Intuit-branded venues.  In many cases, these are developers who have line-of-business solutions that represent the operational priority for their business clients, and where the integration to QuickBooks financial is somewhat of an after-thought.  In many cases, these solutions rely on QuickBooks only for general back-office account functions, where the GL, AR and AP are all that really matter.  The “tough stuff” is done in the line-of-business application.

Most of these types of solutions, as well as many with more complicated functionality or data integration requirements,   utilize a method of communicating with QuickBooks developed using the QuickBooks SDK, or software development kit.  This SDK was originally introduced as a means to replace the clumsy IIF import facility, an early way to get data into QuickBooks from other systems.  The SDK is really a tool kit designed to facilitate desktop application integrations, which is why so many developers use this method.  Particularly when an application is intended to be used on the desktop in conjunction with QuickBooks, it makes sense for developers to use an integration method that will allow them to produce the rich experience and seamless re-use of data that the desktop environment allows.  The SDK requires that the QuickBooks program be present, and QuickBooks controls access to the data file rather than allowing the 3rd party application to have direct data access.

The new method for integrating with a QuickBooks application is by using the IPP (Intuit Partner Platform) method, which is essentially an API (application programming interface) which simplifies the creation of data streams to and from the QuickBooks database.  This method of integration is intended to be serviced by the Intuit Sync Manager (included with QuickBooks), where your data first syncs to Intuit servers, and then connected apps sync from that source.  In this case, Intuit acts as the intermediary, hosting the synchronized data and controlling the sync with the QuickBooks database.  While this may be much easier in terms of offering stricter standards for QuickBooks data integration, it is not a method which addresses the needs of those solutions requiring an integrated experience involving QuickBooks programs and data, or which have more complex data integration requirements than may be served through the IPP.

Because the QuickBooks SDK has been around for many years, it allowed for very stable QuickBooks-integrated solutions to be developed.  In comparison, the IPP is pretty new and has taken Intuit a few tries to get working.  For this reason, there is a limited catalogue of solutions available in the Intuit App Center, which is where IPP solutions are promoted.  Moving forward, Intuit has stated that the focus will remain on the IPP, with the SDK no longer being a preferred (or supported) method.

The method of integrating with QuickBooks desktop editions matters, especially if you’re looking to bring your business applications to the cloud.  Application hosting services is the way to “cloud-enable” desktop solutions, yet not all hosting providers recognize or understand the differences in how applications might integrate with QuickBooks, and what that means to the technical and user environments.  Not all applications are created equal, and not all QuickBooks integrations are, either.  Some integrations sound simple enough to implement, yet have hidden requirements that make deployment with a host or outsourced infrastructure provider an interesting endeavor to say the least.

Developers using SDK integrations with QuickBooks should make certain that they have thoroughly discussed their solution requirements prior to deploying their applications with any host, particularly with a client-selected provider.  Companies experienced in hosting QuickBooks are not necessarily adept at understanding the nuances of SDK-developed integrations, and may minimize the technical requirement to the point of leaving your company and your customer with a bad feeling about hosting.  In worst-case scenarios, the software developer loses their customer altogether due to a poor experience with the solution in a hosted environment.


Cooper Mann Consulting
 is working to help developers and commercial ISVs with QuickBooks-connected solutions get their products to the cloud, and in a way that they can influence and help control the all-important customer experience.  Rather than being just one of a few hundred hosted products customers can select from the provider menu of offerings, we believe your solution should be delivered with your values, your message, and your unique service approach.   Doing so allows you to keep your arms firmly wrapped around your customers and users, working closely with them as you develop your solutions towards a true SaaS or cloud application model, and easing the transition from desktop to web application delivery and subscription service.

Intuit believes they own the relationship to all QuickBooks customers, and they’re right to the extent that the user relies on QuickBooks for some business functionality.  Hosting service providers think they own the customer relationship because they have significant influence over the products accessed from their servers.

Operational support solutions go deeper into the business than any high-level accounting product, and the method of deploying the solution (locally installed or hosted) is an IT issue and nothing more.  As a developer or provider of essential solutions which address specific vertical industry or line-of-business needs, and as the company who understands the business of your customer and supplies those solutions that help them perform, don’t you really think you should own that customer relationship?  We do.

Make Sense?

J

Want to know more about how Intuit is changing their approach to QuickBooks integration?  Read Charlie Russell’s rant: Is Intuit Abandoning QuickBooks SDK Developers?

Read more about QuickBooks cloud hosting: Cloud Hold-Out No More: QuickBooks Desktop Editions in the Cloud

Read more about cloud development: Lessons Learned (or Not): Development and the Cloud

Read more about legacy application modernization, and why IT and back-office outsourcing makes sense for a lot of reasons 

Knowing Your Options: Hosting QuickBooks for Shared and Remote Access

Intuit’s QuickBooks financial applications, the desktop editions in particular, are the most popular small business accounting solutions on the market.  The QuickBooks Online Edition, Intuit’s cloud-based contender, is not quite as accepted among accountants and advisors for a variety of reasons.  Being in the cloud isn’t necessarily one of those reasons, if you consider the growing demand for access to multi-user cloud-hosted QuickBooks desktop editions.  Mostly it comes down to functionality and how the application operates.  QBO just isn’t like good old desktop QuickBooks and isn’t the preferred solution for many financial professionals or their clients.  Yet these users still want and need remote access and mobility.  This is where hosting comes in.

QuickBooks hosting and creating the ability to access QuickBooks applications and data remotely is something that a lot of businesses can benefit from.  Whether it’s to outsource the management and maintenance of servers and systems to a 3rd party, or to create the ability for remote workers or contractors to collaborate with real-time applications and data, there may be a need for a hosted application approach.  Business owners and IT managers need to give consideration to the level of service and support they and their users will need before selecting their provider.  Knowing what the provider will handle and what the subscribers are responsible for might make all the difference in determining the right approach.

In-House DIY Hosting

Local networks and PCs allow users in the same location to share resources, like printers and data storage locations.  Typically, desktop computers have application software installed on them, and use the network to access shared data.  When users work outside of the network, getting access to applications and data might not be so easy.  Even extending the network via VPN access doesn’t solve the problem when the desktop applications are not designed to access data over remote connections (desktop applications like QuickBooks).  It used to be that the only reasonable way to allow remote users to access and run QuickBooks as if they were inside the LAN was to set up remote desktop or application servers (terminal servers).  MyQuickCloud is a product that addresses this need very gracefully, providing in-house personnel with the tools necessary to establish a secure cloud for QuickBooks access directly from existing on-premises systems.

Co-location and Outsourced Infrastructure (IaaS)

Instead of setting up remote access solutions in the office, many IT departments find that co-location with a 3rd party addresses a number of issues.  Leasing equipment, operating system and virtualization tools may be more cost-efficient than purchasing them directly, and the security and redundancy in most hosting facilities far exceeds what most businesses are able to afford to implement by themselves.  Co-location provides managed service for infrastructure elements, but doesn’t necessarily address business needs in terms of user security or application and data management.  These elements are traditionally left up to the subscriber; installing and configuring software applications, establishing user and application permissions, and managing updates and software upgrades.  For this reason, co-location may be a good option for a business with internal IT staff, but not necessarily for businesses seeking “full service” application hosting.

Application Service Providers (ASP) and Managed Application Hosting

Application hosting service providers handle software installation and management, user and security administration, and ongoing technical support as part of the subscription service.  Customers need only to provide their software licenses, name users and upload data in order to use the service.  The service provider does the software installation and configuration, sets up the users and establishes permissions, and connects users and applications to managed data storage.  This model allows businesses to enjoy many of the benefits of a cloud-based or SaaS solution model while also allowing them to continue to use software solutions they are already invested in, in terms of both software licensing and process development.  On the other hand, these models can be extremely restrictive in terms of the applications or integrations they will support, and can be quite costly as the number of users or applications hosted increase.

Whether you roll your own (DIY hosting) or work with a full service QuickBooks host, accessing business applications and data from anywhere is an option every business can take advantage of.

Make sense?

J

Read about the race to find the secret sauce of hosted application services for small businesses

Changing How We See Software: QuickBooks 2013 interface frustrates power users

Changing How We See Software:

QuickBooks 2013 interface frustrates power users

You’re an accounting, bookkeeping or business professional and have been working with QuickBooks desktop software for years.  Your processes and methods for using QuickBooks to manage client accounting have been developed over time, and have been refined to the point where you are able to maximize your efforts and efficiently handle all your customer requirements.   Sure, there have been changes in the software over the years, and many of them have proven to be helpful.  But sometimes you have to wonder what they were thinking when they changed the interface for 2013.

Initially I thought it was the grumbling of a few people who simply resist change, some admittedly so.  But then the grumbling got louder, and started to come from folks I would expect to hear only “happy rainbows and sunshine” from when it comes to QuickBooks.  The new interface, they say, “sucks”.

So what’s the issue?  What did Intuit do with QuickBooks 2013 desktop editions that has inflamed so many devoted users?  One ProAdvisor puts it this way: “Basically no real enhancements at all, just the interface and relocation of options”.  In short, QuickBooks desktop editions now look a bit more like QuickBooks Online Edition, and “there’s extra stuff in the navigation – Intuit stuff“.

I understand Intuit’s motivations for making the desktop and online editions appearance more similar.  After all, the benefit of the QuickBooks product line is that you can start with an entry-level edition and move up the product line to more features and functionality without converting to and learning entirely new software.  Since the online edition of QuickBooks is positioned as the entry-level product for some businesses, it makes sense to continue that same look for the user as they upgrade to richer desktop editions.  Unfortunately for many accounting and bookkeeping professionals, this means giving up on some of the usability you’ve come to expect (like being able to fit all the necessary information on the screen, and having easy-to-read menus, or not seeing a lot of unusable space on the screen, or even being able to suppress Intuit in-product offers).

Many companies have successfully increased their revenue potential by adding offers for services via links in the software interface, which is much more acceptable now that people have adopted web technologies and are familiar with the “hyperlink” concept.  Building additional value (and revenue streams) in the solution makes sense from a business perspective, which is why you see so many software companies moving in this direction.  Software solutions and services can interconnect seamlessly and transparently via the web, so we should all expect to see software makers engage their customers in as many ways and with as many products and services as possible.  For Intuit, this means being positioned to take advantage of, initially, their partner network of interconnected solutions and, later, their own direct offerings in each area.

Software developers like Intuit DO listen to their users and market influencers, as they value your continued patronage.  They have come to learn, however, that devoted (or invested) users will accept change eventually – even more so when there is a chance to use the change to generate business opportunity.  QuickBooks accountants and trainers rely on change in order to keep their clients coming back for more.

The real target is the new user – the business not already adopted into the product – and it is primarily for this new user that the interface changes were made and in-product advertisements targeted to.

In the case of Intuit’s interface selection for QuickBooks 2013 desktop editions, it might seem like there’s “no enhancement, just the interface change”.  I would suggest, however, that the interface change IS the enhancement Intuit elected to deliver – enhancement of the acceptance of the online edition and connected services.

Make Sense?

J

Check out buildingup.biz and see what we’re up to these days