Retaining Productivity while Empowering the Remote and Mobile Workforce

Retaining Productivity while Empowering the Remote and Mobile Workforce

anywhere-anydevicehttp://wp.me/p2hGOJ-J7

A lot of the marketing and discussion around why businesses should use the cloud for IT service is focusing on creating anytime, anywhere access to business data and improving overall IT performance.  By deploying applications to remote desktops and hosted systems, business owners are recognizing the benefits of outsourcing IT service management to professionals who can spend their time actually managing IT.  Focus is able to remain on the business operation and not the technology supporting it; the main office and remote locations are able to work with the same systems and information, and users are able to access information while at home or on the road. Bringing workers together with the same applications and data means new levels of productivity can be achieved regardless of where the work gets done.

Yet the perceived value of “working in the cloud” and the reality remain somewhat disconnected for many mobile business users. The confusion and frustration many users experience with connected, online working models has quite a lot to do with the realization that they don’t simply need remote access or virtual office solutions to bring them together.  Users want solutions that help them get their work done even when they aren’t working on a traditional computer.  When a computer is available, that’s great.  But users want to be able to work from their tablets and smartphones, too.  Have you ever tried to login to a remote desktop from your phone, or to see a full screen of data when the keyboard takes up more than half of the view?  It may technically function, but there’s no way to get anything useful done with that little teeny weeny screen, and that’s a problem.

It is this new multi-mode working environment which is testing the boundaries of usability for software developers and service providers alike.  No longer may the assumption be that users will perform their job functions using a desktop or laptop computer, just as it is no longer assumed that a mobile phone will be used just for phone calls.  Users want (and sometimes need) to be able to get their work done using their smartphones, iPads, Kindles, or other types of tablet, pad or surface computers.  Applications designed to run on full size screens and desktop computers often don’t work well for users accessing them with other types of devices, even when the device is connecting to a remote desktop service.

Mobile device users are starting to face these usability barriers somewhat less frequently when visiting various websites.  If you look at many reasonably modern business websites, you’ll find there is a “mobile” counterpart.  The mobile website is often somewhat less functional than the full website, providing only essential information for the mobile viewer rather than the expanded content and functionality available on the full site.  Yet the mobile site delivers a more pleasant and usable resource for the mobile device user, encouraging the user to visit the site more often.

Application software development can be approached in a similar manner, where essential functionality is presented for mobile users in a format usable by mobile devices, and where the full functionality and rich feature set might be available only in the full application interface.  Even where legacy applications are concerned – those firmly tied to the desktop and network – there are likely options for extending some manner of functionality and access to remote and mobile devices, perhaps by using 3rd party integrated or connected solutions.

Many commercial software developers are successfully viewing this “web and mobile enabled” approach as a means to capture Software-as-a-Service buyers by providing some web-based and mobile functionality with attachments back to the data and applications residing on the LAN or hosting platform.  This hybrid approach may actually present better and more options for businesses, as it embraces the concepts of mobility and device independence while at the same time retaining the features, functionality and productivity-enhancing working mode that only desktop applications have to-date fully proven… and the businesses can keep their own data to take with them and not be relegated to list-only extractions if they wish to change solutions.

This idea is not really new – the idea of providing users with the specific functionality they need (and not more) to accomplish their tasks and get their jobs done.  The concept of Service Oriented Architecture has always spoken to this philosophy, advocating that the right approach to software is the one which orients the application, functionality and view specifically and directly towards the user and their role.

The new twist on SOA is that the orientation of the application should be based not only on roles and functionality.  Modern business applications must also address device and modality, not assuming a particular form factor or platform of access, and having an understanding of the particular mode in which the solution exists or is experienced by the user.  Mobile users want a useful experience on their  mobile devices, and remote and  local desktop users want the features, functionality and performance of desktop applications.

Website designers have figured out that visitors may access the website using any variety of computing devices, including smartphones, tablets, laptops and desktops.  Understanding that each device has a different capability in terms of displaying and interacting with content, site developers have begun to include mobile site designs as a standard offering with business website services.  Users accessing the site with smartphones and tablets are able to effectively navigate and view information on the site because it’s been formatted to fit the screen, and navigation and other action options are accessible from smart menus that are sized and placed for touch screen access.  This approach is now finding its way in many business applications now that the applications are also “living” on the web.

The growing number of web and SaaS products on the market clearly demonstrate that mobility is a big consideration in modern application design.  Unfortunately, productivity losses due to sluggish interfaces or complicated operating processes often offset the benefits of the solution, even though it may be both desktop and mobile “friendly”. Software companies rolling out new SaaS models to their existing desktop product user bases are finding that the desirability of the subscription model web-based solution may be somewhat less than expected.  This may be attributed to the fact that users have become not simply accustomed to how they can make the desktop software work for them – they’ve become reliant upon that ability.  Initial experiences with transitioning from desktop applications to SaaS has left many businesses with frustrations founded in overall productivity loss.  I’ve even heard the term “productivity-sucking”, which I don’t think describes either a feature or a benefit.

There must be a balance found, where productivity is enhanced for both desktop and mobile users and where critical functionality is not sacrificed in order to facilitate a mobile capability.  The goal is to empower the remote and mobile user to be as productive as the non-mobile user, and to do it without forcing changes which may impede rather than improve productivity of the overall organization.

Make Sense?

J

Read more about:

QuickBooks online, or QuickBooks Online? Use Software on the web without using Web-based software

Bringing Order to Inefficient Business Processes: Give people easy to use tools that make sense, and they’ll use them.

Revenue Recognition and closing the reporting GAAP

Revenue Recognition and closing the reporting GAAP

chartOne company earns what the other company spends.  This is business, and it seems like it would be pretty straightforward, accounting for the money coming in and the money going out.  But it is really not that simple when it comes to business finances and accounting for revenue.  With investor pressure to improve share prices and market pressures forcing greater competition, businesses have always sought out ways to make the performance look as good as possible – on paper even if not in reality.  It is this requirement to make the business look better than it may actually be that drives “innovation” in financial reporting, and encourages some companies to use whatever rules are available to mislead investors or paint a rosy picture for stakeholders.  When the balance is lost and financial reporting standards become so oblique as to allow regular and gross misrepresentation, it is time to change the standards.

There are numerous instances of fraud and scandal reported from the finance departments of big businesses, but instances of improper or misleading revenue recognition can happen in even the smallest of companies, and not necessarily on purpose.  It is important to understand that properly and accurately reporting business revenue and earnings isn’t done just for investor satisfaction, it is an essential part of describing business performance that any owner or manager must be able to rely on.

Generally Accepted Accounting Principles (GAAP) provide investors and business owners with some consistency in the financial statements they use to analyze company performance, but only minimally.  This is partly due to the fact that GAAP is based not only on some standards established by policy boards (the authoritative standards) but also on “generally accepted” standards, which are often not really standards at all but simply past practice that was found to be accepted.  Especially in the global economy where fewer businesses operate solely within traditional territorial boundaries – and where accepted reporting methods vary widely – having a single financial reporting standard has become more important than ever.

Make it so, Number One.

Now there are new rules from FASB (Financial Accounting Standards Board) and IASB (International Accounting Standards Board) which provide clear and detailed guidance for how businesses recognize revenues.  These rules are based on a consistently applied set of principles, no matter what sort of business is involved and regardless of where the business is located.

A focus of the new rules of revenue recognition centers on customer contracts, delving into the details of how earnings from those agreements should be recorded. Consider that many businesses combine multiple products and services into a single agreement, even though there may be several deliverables or milestones included.  This method of booking customer contracts allowed companies to report revenues they were not yet due as part of a total agreement, often resulting with inflated earnings reports.   Stakeholders would perceive that the company had reached one earning threshold, but the reality was something quite different and performance expectations were unmet.

“FASB and the International Accounting Standards Board (IASB) issued converged guidance on recognizing revenue in contracts with customers. The new guidance is a major achievement in the Boards’ joint efforts to improve this important area of financial reporting.”  http://www.fasb.org/jsp/FASB/Page/BridgePage&cid=1351027207987

The new rules force an additional level of discussion, including a full set of disclosure requirements that will provide more information about contracts with customers.  Businesses must identify each promised deliverable and attached revenue or earning component, which helps to better understand how the revenue may be earned (and recognized) as the business performs on the various obligations to the customer.

Just take a look at some big ERP companies and the lawsuits generated from problems and failures in delivery – problems that might have been more clearly identified to investors and stakeholders if the tie between product sales and services to be performed were more clearly described.  In many cases, these situations exemplify the revenue recognition reporting problem, where large customer contracts and license sales were fully booked and recognized even though implementation services milestones attached to those license sales remained undelivered.

“2010 – JDA Software (i2) – Dillard’s, Inc.:  Dillard’s had alleged i2 failed to meet obligations regarding two software-license agreements for which the department-store operator had paid $8 million.” http://www.zdnet.com/blog/projectfailures/erp-train-wrecks-failures-and-lawsuits/12055

For private companies, reporting periods beginning after December 15, 2017 must follow the new guidance.  It may seem like a long period of time – from the decision to apply the new rules to the effective date – but the number of businesses the new rules will impact is large.  The FASB made a decision to delay the effective date because of the broad scope of organizations affected and “the potentially significant effect that a change in revenue recognition has on other financial statement line items.”

Business owners and their accounting professionals need to make sure that financial systems and processes are up to the task and can track and produce the detailed reporting these new rules require. For investors and analysts, the new reporting rules and detailed information they generate will go a long way towards minimizing the impact of innovative revenue reporting practices, and will hopefully bring a new level of believability and usefulness to business financial reports.

Make Sense?

J

Following the Rules: Users and Licensing for Hosted QuickBooks

Following the Rules: Users and Licensing for Hosted QuickBooks

I have said many times before that the licensing for QuickBooks desktop editions appears to be a bit complicated, and a lot of that may have to do with the fact that so many people use QuickBooks in so many different ways.  With a solution like QuickBooks (or Microsoft Office or other really popular and widely used software products) there is a tendency for folks to want the flexibility of accessing their software regardless of what computer they are using.  Also, especially in businesses, there is the habit of installing software on a computer and then allowing anyone sitting at the computer to use the software.  In some cases these approaches are okay with the software vendors, but in most cases they’re not.  Yet too often, the small business owner doesn’t find out what the actual rules of using the product are until they try to deploy the software with a hosting service provider (because nobody ever actually reads the EULA, do they?).  If the provider has any credibility at all, they will enforce the licensing rules of the software, but that doesn’t always sit well with the customer.

picture-hostedQBThis situation rears its ugly head quite frequently in the QuickBooks hosting world.  Perhaps it is because there are a lot of possible working models involving QuickBooks users, or maybe it’s simply a matter of people not seeing the value of paying for what they want to accomplish.  Either way, service providers find themselves being challenged every day in trying to explain to a customer why they need to have more than one license for QuickBooks and more than one service account if they want more than one person to access the hosted solution.

Different people at different times: The Concurrent User approach

One of the arguments people make for not having licenses for all of their users is that they don’t actually need everyone in the system at the same time.  The belief is that there should be licenses enough only for the number of concurrent, or simultaneous, users that will access the system, yet each individual human being/user should have a login to the system with the software available (for convenience, of course).  A QuickBooks 3-user license, they believe, should be able to be used by any number of business users as long as no more than 3 of them are in QuickBooks at any given time.

While the customer may be making a reasonable argument, it all falls down when you consider the license agreement for QuickBooks.  Each user of the product is supposed to have a specific license.  A business with a 3-user license (or 3 single-user licenses) for QuickBooks has the rights to allow 3 people (unique human beings) to use the software, not any combination of people as long as they number no more than 3 at a time.   There is to be no sharing of licenses, and there is no “concurrent” licensing model: each person/user/human being is supposed to have their own license for the product no matter how often they access it.

Look but don’t touch: The Read-Only User approach

Another of the arguments people make for not licensing all of their users is that there is somehow a belief that if you don’t actually enter information, then you aren’t really using the software.  This often comes up in situations where an accounting professional works with their client, or when business owners want to occasionally see what’s going on in the company.  The approach centers on the concept of what a “user” is and suggests that users are the people entering or changing the data, and people only viewing that information aren’t really “users” at all.  When the bookkeeper opens QuickBooks and enters an invoice, the bookkeeper is recognized to be a user.  But when the business owner opens QuickBooks to view the financial statement or see the bank account balance, isn’t the business owner also a user?  Yup, they sure are. Any person that actually opens the program on the computer is a user, regardless of what they do when the program is open.  Just looking around at the data still requires that the program be open, and opening the program requires a license.

Two Fer: But the other hosting company lets me…

Just because you can do something doesn’t mean that you should.  So, just because a different hosting provider might let you get away with things that aren’t right (but perhaps are convenient or cost saving in the short-term) doesn’t mean you should expect a different host to allow the same thing.  If your current host says things like “as long as you don’t tell us…”, you should be concerned.  This often comes up in a hosting scenario where there is an outside accounting or outsourced back-office professional working with a hosted client business.  The outsourcer will want to access the client books, so they will want to have a login and access to QuickBooks software on the host system.

The trouble starts when the outsource professional doesn’t want to have to pay for their own service or licensing, yet they want to be able to login to the system and run QB just like the client does.  Falling sometimes under that attempt to leverage a concurrent user approach (see above), these outsourcers just aren’t realizing that the benefits of accessing their client information and working in real-time with that data is often valuable enough to support the cost of a hosted account and license.  Instead, they want their access to be free of charge and not be bound by silly rules of licensing, often because their client won’t want to pay for the accountant service in addition to their own.

This is when the “if you don’t tell us” stuff comes in – where the service provider may suggest to the accountant or outsourcer that they can simply login as the client and nobody would be the wiser.  I’ll fess up and say I have even entertained this idea with clients a few times but always shy away from discussing it in-depth.  While it is basically true that the service provider doesn’t generally know which exact human being is sitting at the other end of that remote desktop connection, that doesn’t mean that it is okay to leverage it into an abuse of services or licensing.

Two or more people sharing a single login just isn’t good ju ju, and it’s usually against a whole bunch of licensing rules and rights of use.  The funny thing is that many customers who initially leverage their service in this manner end up finding it was a really bad idea.  I saw a scenario a few years ago where a business allowed their outside auditors to share the logins of regular employees in the finance department.  When an employee tried to login to their remote desktop, they opened the session the auditor had open – exposing the employee to a lot of data that was not theirs to see but which the auditor user in QB had access to.  The company called it a security breach and it was on their part – and it was allowed to happen because they shared their remote desktops with the auditors rather than giving the auditors their own accounts with their own security profiles.  What seemed like a good, cheap approach on one day rapidly turned into a big issue the next, and the service provider had no power to prevent it from happening.

The moral of this story is simply that following the rules is the right thing to do and most reputable hosting service providers will try, even if they don’t end up doing it really well.  There are always going to be those who figure that the risks don’t measure up to the potential rewards, so they will do what they choose to do.  I’m always left wondering about those guys; if they have no problems breaking these rules, I wonder what other rules (or confidences) they are willing to break.  Hmmm.

Make sense?

J

 

Avoid the Aftertaste| QuickBooks Desktop Hosting Comes in Many Flavors

Avoid the Aftertaste| QuickBooks Desktop Hosting Comes in Many Flavors

There is a lot of activity and interest around the hosting of desktop applications in the cloud, and it is no wonder that a great deal of the effort centers on the use of Intuit QuickBooks desktop editions.  QuickBooks is among the most popular software products used by small businesses, so it makes sense that service providers and hosting companies are taking advantage of that market share to reach prospective hosting customers.  After all, a hosting platform may be kind of neat, but it is not all that valuable unless there are applications and data living on it.

For the average small business, the applications of choice include Microsoft Office and QuickBooks.  Yes, there is an online edition of the QuickBooks product (called QuickBooks Online, of course).  However, the market share Intuit earned for QuickBooks wasn’t accomplished with an online application, it was done with the desktop applications which still own market share today.  Hosting service providers recognize this truth, and are taking steps to bring those QuickBooks desktop solutions into the cloud.  Now we have the ability to get QuickBooks Desktop editions online – which is not the name of a service but a description of what it offers – available from a variety of authorized hosting providers (and from many unauthorized ones).

I’ve said before that there is a fine art to hosting QuickBooks desktop for lots of users.  There are a great many different considerations and possible use cases, and not all providers will be able to meet every requirement.  There are also lots of different technology models and methodologies which may be applied to the hosting model, and each has some benefit or barrier depending on the specific need of the client.  Hosting companies may throw around terms like “cloud server” or “published application” or “remote desktop”, but at the end of the day, the systems are still Windows computers running QuickBooks software.  How those systems are wrapped up, how you connect to them, and how you operate with them often becomes the real difference in the service experience.

The specific technology a hosting provider applies to the service does not necessarily describe exactly how the service works.  Just because a provider may use Citrix doesn’t mean they have more capability to provide quality service than a provider using other technologies, or a host using VMWare is not necessarily creating better cloud servers than a host using Hyper-V or Parallels or some other virtualization strategy.  The technology may impact how the infrastructure is operated and can impress upon the customer experience, but the real differences in delivery often come down to the provider’s understanding of the software product, the customer need, and their ability to meet the need directly.

Does the experience of connecting to and using the service work for the users, and are people able to get their jobs done quickly using the service without a lot of support or frustration?  (**Please note that hosting services aren’t a solution for bad software and poor working processes.  If the software or processes aren’t workable now, they’re likely not going to become magically more workable if hosted).  Does the hosting service address issues like making the right data available to only the users who need it, and giving access to applications only when a user is permitted to use them?  What about “external” users like contractors or client businesses… does the host offer a way for them to also participate in the solution?

It’s important to consider all of the aspects of how the service will be used, and by whom and under what circumstances, to ensure that the delivery offered is the solution needed. The point of all this is to encourage users to concern themselves a little less with exactly what technology the host is using to deliver QuickBooks applications, and to evaluate the actual solution.  It won’t typically matter to an end-user what specific technology is being used to provide them with service as long as the service works well for them.

While some people do adopt a fondness for a particular “flavor” of technology or approach, the reality is that a quality user experience coupled with a useful and reliable system means much more to the business.  And knowing that there are future options for growing, expanding or simply changing the service is essential.  It’s not so much the flavor of technology users should be concerned with when shopping for QuickBooks hosting services, it’s avoiding that icky aftertaste that comes with selecting a QuickBooks hosting approach that just doesn’t meet the business need.

Make sense?

J

Accounting for Point of Sale

Accounting for Point of Sale

There are a lot of solutions available to help retail businesses get business done.  From touch screen technology to mobile credit card and payment processing, retailers have many choices when it comes to selecting the right technology for the establishment.  But even the best point of sale system can lack the critical element that makes it truly valuable for the business.  This critical element is integration to a trusted accounting and finance solution.  While the POS system may include a level of basic accounting functionality, the reality is that a dedicated financial application will perform better in the long run.

Just as specialized line of business applications are used to handle operational functions, the financial application should be considered to be the “line of business” solution for the accounting and finance department (even if it is a department of one). This system not only services essential processes like receivables management, bill payments and bank account reconciliation, it serves as the basis for payroll, financial, tax, performance and other reporting. Further, the financial systems are often the first and primary source of analytical data, illuminating KPIs and cash flows and ultimately the business value.

The point of sale application generally handles the selling of and payment processing for goods and services sold by the business.  Whether it is composed of registers and terminals connected to a host system, PCs running POS software, or mobile phones and tablets running mobile payment processing apps like Square or GoPayment, point of sale addresses the retailers need to capture and record sales and payment information, sometimes customer information, and often inventory information.

The data from the POS solution must make it to accounting in some manner, yet point of sale applications are too-often approached as a standalone business requirement, somehow disconnected from other aspects of the business including the back-office.  Sales and items may be recorded in the POS system, yet only summary sales data ends up being re-keyed into the accounting system.  Centralized inventory management is all but nonexistent in these cases, and gross sales total are often recorded rather than individual transactions and receipts being transmitted to the accounting system.  The process of re-keying information from the POS to accounting systems is not only an efficiency-killer, it is also introduces a great potential for errors.  When the business elects to conserve on data entry and post only summary information to the accounting system, valuable detailed sales and transaction data may be lost.

The right approach to bringing point of sale together with accounting is to automate the process of integrating POS data with accounting on a regular basis – with AUTOMATION being the key.  Rather than establishing a process that requires manual entry of information from either system, a data integration solution is the best approach, with an import/export solution running second. The point is the elimination of manual re-entry of information.

There are numerous tools available that can take formatted POS data and import it into products like QuickBooks, for example, where it can be properly accounted for.  While QuickBooks Point of Sale integrates with QuickBooks desktop products, other POS solutions can also connect with QuickBooks if the right integration tool is selected, and there are quite a few available.  Check with the POS vendor and ask about a direct integration with QuickBooks desktop or whatever financial system you use. If there isn’t a packaged integration solution available, then check out products like Transaction Pro Importer, which can automate a variety of data import processes and ease the burdens moving external data into QuickBooks.pointofsale

The other factor in getting point of sale data to accounting is actually getting it there… transporting the data from the POS location to where the accounting system lives.  In many situations it is not desirable to keep the accounting system on the same computers as the point of sale systems, and in some cases it isn’t even possible.  But there is generally a way to get the information in a form that makes it possible to transmit it in some manner.  Among the most popular approaches to solving the “getting the POS data from here to there” problem is to use a data sync solution like Dropbox.

If the point of sale data can be exported or output to a file on a PC hard drive, then it may be able to be stored in a Dropbox folder on that PC.  At the home office where the accounting system resides, the operator would access the sync’d files from the local PC Dropbox folder and import the data to QuickBooks.   For QuickBooks Point of Sale there is an option to create a “mailbag” of sorts from the POS data of a remote store, which QuickBooks POS at the home office would pick up from the Dropbox folder and push to the QuickBooks financial application.

For businesses using POS systems like Micros or POSitouch and others, there is likely a service or application that will produce the POS data for import to QuickBooks or other financial system, pulling POS data files placed in the Dropbox folders by the POS app or performing the function as a web service or SaaS integration.

While I am a big fan of application hosting services and running QuickBooks desktop editions in the cloud, I’m also a realist and recognize that many POS solutions either can’t or shouldn’t be hosted.  There are situations where a hosted point-of-sale makes a lot of sense, and then there are cases where no bandwidth or proprietary hardware-based solutions make hosting not even an option. That doesn’t mean that the financial systems shouldn’t be hosted, though, and there are numerous ways to get the sync’d POS exports to the hosted QuickBooks environment, for example.

The key for retailers is to make sure there is a solid process for getting detailed and accurate POS information into the accounting system on a regular basis.  Manual entry is never the best answer.  With all of the technology and tools available, manually re-entering sales information is a waste of time and is likely to produce errors.  The better answer is to use an approach that automates the regular collection of point-of-sale data from all sources, delivering the data in a regular and consistent manner to accounting, and providing the basis for end-to-end automation supporting the integration of the point of sale system data with the rest of the business accounting.

jmbunnyfeetMake Sense?

J

Where do we go from here? The SMB SaaS Migration

Where do we go from here?  The SMB SaaS Migration

Forests are a great renewable resource.  You may cut them down, but you can replant and grow new ones to cut down again later.  I suppose it’s sort of like that for software vendors who provide small business solutions.  While many small businesses fail and close every year, lots and lots of them start up and continue operating each year.  Since there’s a steady stream of new prospective customers coming up each year, maybe it is OK when some of them outgrow the product and leave (leaf?).

On the other hand, maybe it makes sense to understand where those customers who do grow up and flourish will go… to which products or solutions they will migrate, and how the company might actually retain a relationship with them through that process and beyond.  Some businesses will mature successfully, and will outgrow their small business solutions and leave their vendors, but it doesn’t necessarily have to be that way for all.  For some key software vendors, a fair question to ask themselves is where their customers will go from here… where “here” is the solution the customer is using now.

When this question is applied to the small business accounting market, it ends up centering on the QuickBooks product line.  Intuit is currently encouraging all QuickBooks customers to look at the QuickBooks Online solution, the fully SaaS-based offering which is different from the desktop editions.  The QuickBooks desktop editions, on the other hand, service small businesses very well.  The functionality improves and increases as users move up the product line from the Pro version through Premier and to Enterprise edition.  This line of solutions has done a great job of serving the needs of both small and larger businesses – all within the same product set.  But now Intuit wants users to experience the benefits of subscription-based service and an online working model.  Those are great benefits, but there’s a question that is left open for the asking.  Where are QuickBooks customers supposed to go from there, assuming that at least some of them might grow beyond the capability of the online product?  It’s a fair question, and here’s why I think so.

fall_from_cloudOnce a business has adopted a certain working model and the mentality that goes along with it, it is difficult to come in and tell them they have to change to a new model and find a way to adjust.  Change doesn’t come that easily for many individuals much less an entire organization, so this is a big deal and potentially very impactful to all aspects of the operation.  Yet this is exactly what is currently suggested with Intuit’s desire to have customers use the online edition.

It may be a great solution for now, but what’s the next step up from there?  Is it QuickBooks Enterprise on the desktop?  Kind of a weird message, don’t you think?  Let’s have customers adopt an anytime, anywhere subscription solution model, and then migrate them back to the desktop where the management and maintenance of the solution is higher due to number of users, and where there is no mobility, multi-location or remote access capability as there was with online.

The thought is that QuickBooks Online will eventually compete with the Netsuite and Intacct class of SaaS solutions, but right now it doesn’t and there are customers who must leave that product for something that handles their larger and deeper business needs (like the QuickBooks Premier and Enterprise solutions do).   There is a big gap between the entry level accounting products and those which are designed for the larger or midsize “small business”, and the QuickBooks desktop editions represent the only viable options in that very large space.  In fact, many businesses utilize line of business products that allow them to retain use of QuickBooks even as the enterprise scales far beyond the expectation that QuickBooks could handle the need.  But it often can, and it makes sense for businesses to leverage this ability if they are able.

The answer for these growing businesses  – the place they should go when they’ve outgrown the small business SaaS solution like QuickBooks Online (or Xero or Freshbooks or whatever) is to a hosted or remote-enabled QuickBooks model.  With the QuickBooks desktop editions hosted and managed by a cloud provider, businesses are able to retain the benefits of managed service, subscription pricing, and anytime/anywhere access while utilizing the products that are recognized as the industry standards for finance and accounting for growing businesses.

The hosted approach gives the businesses a clear path for the advancement of their systems in line with the growing needs of the business, and removes the need to shift working models from online to on-prem.  As needs increase and the complexity of systems grow through integration and scale, the service provider manages the platform and systems, enabling the business to not simply continue operating, but to grow and expand with the confidence that there is a plan to grow and expand the systems which support it.   The place to go is the cloud, and whether it is an entry-level SaaS solution or a hosted desktop and server approach, the service is there to handle the business.

jmbunnyfeetMake Sense?

J