Re: (ET) Elec-Trak co-op/partnership??

[Tim Chapin <tchapin umich edu>]

I am willing to handle/help handle the distribution/warehousing..so on.  It
would be at the home business level.  At this point, I havn't a clue the
size inventory we are talking about here or the start up monies needed to
purchase the inventory.  I am just willing to see if I alone with someone
else could set this up.  
Again this would be operated at the home business level, using ups and the
such for delivery.  At the onset it would not handle credit card operations
or other freals.

I through out my location just because I am more centrally located that say
someone on either coast.

I am not a business man or an electrical person, but I do beleave that
electric is the way to go for lawn care and beleave we have a viable
business here until someone else starts developing an affordable electric
tractor.  I feel with the right marketing, we could pull a huge number of
people in from the west coast that are looking for just this kind of thing.

>Return-Path: <owner-elec-trak cosmos5 phy tufts edu>
>X-Authentication-Warning: cosmos5.phy.tufts.edu: majordom set sender to
owner-elec-trak cosmos5 phy tufts edu using -f
>X-Sender: krowharr mail bcpl net
>Date: Mon, 09 Oct 2000 13:43:42 -0400
>To: Elec-Trak cosmos5 phy tufts edu
>From: Brenda Harrison & Tim Krokowski <krowharr bcpl net>
>Subject: Re: (ET) Elec-Trak co-op/partnership??
>Sender: owner-elec-trak cosmos5 phy tufts edu
>
>Hi Tim,
>       Distribution for a reasonable price is my biggest problem to 
> overcome.
>Are you including warehousing of spares, tracking current inventory, et
>cetera?  I'm not picking on you, I'm curious how it would be done.  I have
>troubleshooting experience with electronics and electromechanical
>components but not on the Elec-trak's.  I would think with the manual from
>Tech Services "we" could handle at least 75% of most problems.  There are
>some real guru's amongst the list.  Bill Gunn already has most of the
>infrastructure in place.  I need to talk to him to see how a transfer 
>would
>work.
>
>Tim Krokowski
>
>At 01:12 PM 10/9/00 -0400, you wrote:
>>I have no expertese in elec traks and know little about electronics, but 
>>I
>>would be interested in a partnership.  I'm not stupid (some may differ) 
>>so
>>with time, I could build up an expertise.  Also it would depend on the
>>inital startup costs (of course). 
>> My back ground is in computer programming and would be willing to setup 
>> a
>>website for parts ordering and could handle distrubition (I am located in
>>lower Michigan (Ann Arbor area)), I just couldn't handle the trouble
>>shooting end.
>>
>>Any others out there willing to do a partership?
>>
>>>Return-Path: <owner-elec-trak cosmos5 phy tufts edu>
>>>X-Authentication-Warning: cosmos5.phy.tufts.edu: majordom set sender to
>>owner-elec-trak cosmos5 phy tufts edu using -f
>>>X-Sender: krowharr mail bcpl net
>>>Date: Mon, 09 Oct 2000 11:53:30 -0400
>>>To: Elec-Trak cosmos5 phy tufts edu
>>>From: Brenda Harrison & Tim Krokowski <krowharr bcpl net>
>>>Subject: (ET) Elec-Trak co-op to continue Bill Gunn's business?
>>>Sender: owner-elec-trak cosmos5 phy tufts edu
>>>
>>>Greetings list members,
>>>
>>>     I don't know how hard it would be to do but if there isn't one 
>>> individual
>>>interested in taking on the Elec-Trak portion of Bill's business maybe 
>>>the
>>>list as a whole could take it over.  Create a corporation and sell 
>>>shares
>>>to raise capital.  Or pay in advance "X" amount of money on account for
>>>future parts you would purchase and use that money to buy Bill's old
>>>inventory.
>>>
>>>     I know this is probably silly of me to propose but without parts 
>>> and
>>>support Elec- traks are dead.  It's just a matter of time.
>>>
>>>     Can anyone give Tech services phone # (again)?  I can't find it in 
>>> past
>>>emails and my manuals not here and I want to see how much Bill wants to
>>>take over the business.
>>>
>>>Tim Krokowski
>>>Maryland
>>>E-20
>>>cordless pushmower
>>>waterwheels & hydroelectric
>>>active/passive solar house
>>>
>>
>>
>>
>