Vibrant, if this is going to be "the single app" for business users, then it must, absolutely must have CRM capabilities, must have timesheets, and should have invoicing and something ERPish - at least later.

Integration with accounting packages would be nice, but not vital - there are few enough people involved in that side of the business that having the ability to extract, prepare reports, etc., will be sufficient.

I'm a partner in a small consulting firm. We're just over a dozen, and we are already struggling with "keeping everything in one place". We need shared calendars and shared contacts, we need a way of easily keeping track of all interactions with clients (the CRM bits), we need a way of getting useful reports on employee/contractor activity (I really like the idea of iDoneThis, but unless timesheets can be derived from the digests, then it is duplication of effort, since we need those - the timesheets - first and foremost).

We live and die by our billing, and our billing depends on time tracking. And we work through a mix of direct contracts, middlemen, etc., like pretty much everybody in this business. And in many, many other businesses.

I've rejected business apps because they use a "timesheet per client" model, instead of the more intuitive and useful (for my staff) timesheet per worker model: I want one place for my worker to enter everything they did, and I want the system, the computer that is supposed to be good at drudge work, to extract which bits go to which clients. If an admin needs to tweak that (based on rates, discounts, and the thousand other things at play), so be it. But my employees DO NOT decide how much of their time gets billed, I do; they tell me what they worked, I make sense of it.

If time reporting is still a thing on the side, this isn't everything in one place.

If CRM is still a thing on the side, this isn't everything in one place.

Other things that would be useful: Document collaboration with built-in version control, like Quip. Kanban boards like Trello.

Maybe also Zapier integration: Write a few zaps to allow your users to integrate with their existing tools.

Integration with existing is more useful and powerful than you may credit: Most of your potential users are already in business, suffering their tools, but making do. You will convert them if you make it easy for them to adopt your tools step-by-step.

Businesses that spring up "post-Dynado" and move immediately to Dynado will be rare, so don't assume an "all in" mentality or assume "clear fields".

You will need Android and iOS apps, you may want to have a BB app. The web interface may be cool, but what about when I am on a long flight without Internet access? How will I get anything done?

Quip has an offline mode for its mobile apps, but if I am working offline for a long time, I want a real keyboard and screen, which means my Air, which means a native OSX application.

And if you have integrated document collaboration, you will need import and export. My customers want Office formats, so I need them. Can't live without 'em.

Fundamentally, business is about managing revenue and cost and keeping the customers coming back. All of the other stuff - single inbox, simpler project management, etc., etc. - are all just polish and veneer, shuffling deck chairs on the Titanic, if they do not contribute to increasing revenue and lowering cost.

So customer contact management (from shared contacts to CRM) and time management (from project management to time tracking to timesheet management) are fundamental.

(Edited to add a few missing words, correct a few typos.)