RELATED IDEAS
Support multiple billing entities and invoices for the same account
What is the challenge? |
Consultants want to have a single Aha! account that they can use for their own work as well as specific client implementations, but they don't want to pay for all of them so they have to create multiple Aha! accounts instead. |
What is the impact? |
It's more complicated to manage multiple Aha! accounts. |
Describe your idea |
Support multiple billing entities for an account, with invoices sent to them corresponding to a defined group of seats in the account. |
© 2025 Aha! Labs Inc.•All rights reserved
Also, please note that without being able to demonstrate the value of Aha! Roadmaps with my own account, my clients would, in general, not entertain messing with Aha! at all, due to its expense and no view of tangible benefits. I sold Aha! Enterprise into a client by showing how we could get better supplier management of offshore software developers using it. I also sold the offshore developer on using it because it was a richer work handover than was achieved with docs, with their existing Trello system and even better than Aha! Roadmaps synced to Trello. We would have gotten nowhere without me being able to tangibly demonstrate the benefits. That would have hurt your sales.
It's not more complicated for THE USER to manage multiple Aha! accounts. Only for billing and access control. Those people are not your primary customers.
Migrating data from one workspace in one account, into an equivalent workspace in a client account took me over 8 hours, today, with lots of cutting and pasting. The spreadsheet export/import is useless, as it recreated cards in the kanban of Develop as product features, which these were not. I also got a duplicate feature for each requirement IN a feature. This export/import circus is not fit for purpose.