Temperature-Controller-Software-Scripted-Driver: Difference between revisions

From *** My Personal Wiki ***
Jump to navigation Jump to search
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Business Model ==
== Business Model ==


* include "Buy support time" in menus. User gets nominal value with purchase of software. Thereafter must pay. Menu directs to webpage that they fill in and pay via PayPal.
* Software spreads to cover full controller market
* Software spreads to cover full controller market
** Acts as a roving software commercial
** Community - helps generate awareness of the software and "capture effect"
* include "Buy software support time" in menus. User gets nominal value with purchase of software. Thereafter must pay. Menu directs to webpage that they fill in and pay via PayPal.
* Sell system design and consultation
* Sell driver script development service to temperature controller manufactures - put in a menu
* Sell driver script development service to temperature controller manufactures - put in a menu


Business model works best when there is a desire to connect. All components should be designed keeping this in mind.


== Infrastructure Tasks ==
== Infrastructure Tasks ==
Line 20: Line 23:
By form name:
By form name:


* [[NagScreen]] - use to coerce user into connecting to network to allow updates / decommissioning
* [[RunProfile]]
* [[RunProfile]]
* [[ChannelManagement]]
* [[ChannelManagement]]
Line 32: Line 36:
* [[GraphicTemperatureDisplay]] - with drag tags that superimpose on top of a photo/graphic
* [[GraphicTemperatureDisplay]] - with drag tags that superimpose on top of a photo/graphic
* [[ProfileUpLoader]]
* [[ProfileUpLoader]]
* [[DeviceServer]]
* [[DeviceServer]] - device server & client
* [[RemoteMonitoringAndControl]]
* [[RemoteMonitoringAndControl]]
== Development Sequence Strategy ==
* What is the most rapid sequence to generating revenue stream?
** Modify SKC to use scripted drivers and sell with existing controller stock?

Latest revision as of 17:33, 16 January 2011

Business Model[edit]

  • Software spreads to cover full controller market
    • Acts as a roving software commercial
    • Community - helps generate awareness of the software and "capture effect"
  • include "Buy software support time" in menus. User gets nominal value with purchase of software. Thereafter must pay. Menu directs to webpage that they fill in and pay via PayPal.
  • Sell system design and consultation
  • Sell driver script development service to temperature controller manufactures - put in a menu

Business model works best when there is a desire to connect. All components should be designed keeping this in mind.

Infrastructure Tasks[edit]

  • Registration database
  • User Forums - Profit from the user synergies
  • Downloads
    • Language packs
    • Updates
  • Controller Scripts

Software Tasks[edit]

By form name:


Development Sequence Strategy[edit]

  • What is the most rapid sequence to generating revenue stream?
    • Modify SKC to use scripted drivers and sell with existing controller stock?