Avaya, NEC, Toshiba Proposal Content Added to SalesDoc Architect
We’ve just made it even easier for clients to implement and maintain the SalesDoc Architect document library by making proposal content for Avaya, NEC and Toshiba solutions available to our clients (see our news release). Rather than having clients manually add that proposal content to their document library – document section by document section – we are able to provide that content to them en masse, and maintain it for them on an ongoing basis.
The question that we’re asked most frequently by prospective clients is: how long does it take to implement SalesDoc Architect? My answer is: not very long, especially if you’re willing to start out with a good but less-than-perfect solution. It’s still a big improvement over what’s been done in the past, and the initial solution can be perfected and improved over time. Unlike other enterprise software solutions that require a huge project to “get everything right” for the initial implementation, with SalesDoc Architect you can start small and grow from there.
Over the past year or so, we’ve added lots of new features and processes that make it easier to implement SalesDoc Architect, because we know that TIME is everyone’s most precious resource. We’ve added mass-import features that enable administrators to mass import document sections, part/pricing data, part/document associations (which enable document sections to be automatically included in outputs when specific part numbers are configured in the solution) and other data. We’ve also created a QuickStart program and process to speed up implementation.
But we’re not going to stop there. We are working on a program to co-op with some of our clients to create and maintain some of the engineering data – like implementation hours and peripheral product requirements – for solutions from several vendors. We are also in the process of setting up several vehicles to share best practices amongst our clients, including an online forum.
By the way, for those who want to know how the content updates work from a (somewhat) technical perspective, the document content provided by us is added to client databases (where clients can add their own document and other content) through a database merge function. Subsequent updates to the proposal content are merged into client databases in the same way, usually on a monthly basis.