Warning about MTX accounting!

[chrisk]

I am a Microsoft Solution Provider who works extensively in Access and
FoxPro, designing databases and accounting systems for businesses.
Although I had no previous experience with MTX, last July I had a
client, with whom I had been working already, to whom I proposed
using the MTX accounting system and interfacing it with other Access
systems I was developing for him.

We bought the MTX package (demo version), but the client wanted
references from other companies who were running the package to see
if they were experiencing any problems with MTX.

Instead of doing that, MTX referred the client to a developer in
their own dealer network, who misrepresented my cost of the MTX
package to the client, and stole the account. Now the client has
the MTX package installed, the other developer has a new account, and
I am out at least $10,000 in development business which was lost
because of MTX's indiscretion.

More disturbing was that when I confronted MTX with the facts of the matter
in several conversations with their president and sales manager,
I was told that MTX had done nothing illegal, and that they 'would
handle it the same way as we did in August [were a similar situation
to occur]'. In fact, MTX has indicated that they are unwilling to do
anything whatever to redress their unfair steering of the business
I brought them into their own business channels.

I am posting this note in an effort to warn other developers and
Solution Providers what is likely to happen if they choose to deal
with MTX International.

Chris Kemp <chr...@paladn.com>

[ste...@ibm.net]

In <3io3ob$u...@jupiter.planet.net>, chrisk <chr...@paladn.com> writes:
>
>We bought the MTX package (demo version), but the client wanted
>references from other companies who were running the package to see
>if they were experiencing any problems with MTX.
>
>Instead of doing that, MTX referred the client to a developer in
>their own dealer network, who misrepresented my cost of the MTX
>package to the client, and stole the account. Now the client has
>the MTX package installed, the other developer has a new account, and
>I am out at least $10,000 in development business which was lost
>because of MTX's indiscretion.
>

What do you mean "misrepresented my cost of the MTX package to the client"?
If this developer lied to your client about your cost, couldn't you speak to
your client and present them with the appropriate documentation?
Even though I think MTX mishandled the situation, and thanks to you,
we all are warned of their business practices, I do question how firmly
you had this client, and/or how good was such a client.

I have found that many software firms, do not treat consultants properly,
especially when you bring them the potential sale. We have recommended
a PC based portfolio system that costs $14,000 to $20,000, to clients,
of which five or so have purchased the product based on our
recommendation. Not only have we received no signs of appreciation
from the vendor - no leads, no discounts, zip - they require our clients
to pay them a couple thousand dollars a year for support, and they
market their consulting services directly to such clients. We have asked
that we obtain technical support from the vendor, and our clients funnel
their questions through us. No such deal.

The problems that we are talking about (cross-channel conflicts) is very
much present in the software market, and we all need to be careful.

Steven R. Zuch
Cogent Management Inc.