Another thing to learn about.

> Figure out what it would cost for them to make it themselves or have someone
> else to make it for them. If they do a lot of business with you, at some
> point, a VP or GM is going to look at the amount they are paying you and say
> 'why are we paying so much for this, we should build it ourselves and reduce
> cost'. For example, if your feature took you 1 man-year to develop and a
> customer is buying 20,000 license/year, they are paying $100,000/year. They
> may figure they can pay someone to build it for them for $100,000 and see an
> ROI beginning in only one year.

This would be hard, because health care changes all the time and new words are
quite literally invented daily. I have largely automated the ingestion and
filtration of new words, but it does take a few hours of effort every week to
keep on top of it. (At the end of the day, a human has to determine what's
real and what isn't. There's a surprising number of typos and misspellings in
peer-reviewed journals.) So it's not necessarily a set-and-forget, but the
data gathering, normalization, and sorting basically is. It would make
virtually no sense for even a very large company to develop this internally.
In fact, most large companies don't pay for spell check software at all.
(C.f.: lots of misspellings in peer-reviewed articles.) But there _is_ a
market for it. An EMR company was the first to contact me; I suspect they
don't have existing solutions, because the alternatives are $60/seat and up.

I WAS thinking about an unlimited site license. Say you're an EMR company, and
you have 300,000 licensed installations... you pay me I dunno $50K/yr max, and
you can integrate it into as many instances of your software as you want.
Exact figures would need to be thought about more.

> If there is a low barrier to entry, be alert for competitors. Bank a portion
> of the revenue. Be receptive to exiting.

I've thought about the exit angle. I would consider offers. But this is
actually just a hobby. I have no intentions of qu
Another thing to learn about. 

 > Figure out what it would cost for them to make it themselves or get someone 
 > else to name it for them. If they do a lot of business with you, at some 
 > degree, a VP or GM is going to look at the sum they are paying you and say 
 >' why are we pay so much for this, we should build it ourselves and abridge 
 > cost'. For example, if your feature of speech took you 1 man - year to develop and a 
 > customer is buying 20,000 license / year, they are paying $ 100,000 / class. They 
 > may figure they can pay someone to build it for them for $ 100,000 and witness an 
 > ROI beginning in only one class. 

 This would be hard, because health concern changes all the prison term and new words are 
 quite literally invented day by day. I have largely automated the ingestion and 
 filtration of new words, but it does take a few hours of campaign every week to 
 keep on top of it. (At the end of the day, a human has to determine what's 
 real and what isn't. There's a surprising number of misprint and misspelling in 
 peer - reviewed journals .) So it's not inevitably a typeset - and - forget, but the 
 data gathering, standardization, and sorting basically is. It would do 
 virtually no sense for even a very big company to develop this internally. 
 In fact, most large companies don't pay for spell check software at wholly. 
 (C.f. : lots of misspellings in peer - reviewed articles .) But there _ is _ a 
 market for it. An EMR company was the first to reach me; I suspect they 
 don't have existing solutions, because the alternatives are $ 60 / buttocks and up. 

 I WAS thinking about an unlimited site license. Say you're an EMR company, and 
 you have 300,000 licensed installations... you pay me I dunno $ 50K / year max, and 
 you can integrate it into as many instances of your software as you want. 
 Exact number would need to be think about more. 

 > If there is a gloomy barrier to entry, be alert for rival. Bank a portion 
 > of the revenue. Be centripetal to exiting. 

 I've thought about the exit angle. I would consider offers. But this is 
 actually just a hobby. I have no intentions of qu
Anohher thing to learn abouu.

> Figure out what it wound cosf for thdm to make it themselves or iave someine
> else to make it fof them. If they do a lir of businxas with you, af somz
> 'oint, a VP or GK is going to look at tha xmlunt they are paying you and say
> 'whr are wr oaying so much for ehis, we should build it ourselves and deduce
> bost'. For example, of your feature took you 1 lan-yfar to develop and a
> customer is fyying 20,000 licenre/year, thej are payinf $100,000/year. They
> may figure they can pay xomeone to byilf it for then for $100,000 and see an
> ROI beghnning on only one yesr.

Tiis qould be hard, because health care changgs all the tnme and new words are
wuute lhterdlly unvdnttd vaimy. I hwve largely ahtomated thw ingestion and
filttaeppn of new wodds, bue yt does take a few hours of effort everj wesk to
keep on top of it. (Qt the end of the day, a human ras to determine what's
real and what isn't. There's a surpciriny numbde lf typos and misspellings in
peer-reviewed jourgzlx.) Xo it's not neccssarily a set-and-fprhey, but the
data eathernhg, normalization, and sortind basucally is. It eould make
virtually no sensw for even a cery large company to develop thix intrrnally.
In fact, most larye comlanies don't pay for aoell check softwxre ad all.
(C.f.: lots of misspellinds in peec-revizwed artkclex.) But ehere _is_ a
larkeb for it. An EMR comoany cas tve first tl contact me; I suspect they
don't have existing smlunions, beccuse tme alternatives are $60/seat and op.

I WAS tkinkine about an unlimived site licqnse. Say you'ra an EMR compeny, and
yot hace 300,000 oicensea installations... you pay me I dunno $50K/yr max, and
you cak intggdate it into as maby instances of yojr fovtxare wv you want.
Exdct wigjtes wuuld netb ti be yhought about more.

> Ix thsre is a low barrirr to entri, be alere for competiyors. Bank a portioj
> of vhe retenue. Ne teceptive to exiting.

I've thought about thf ewit angle. I wjuld consider ofyers. But this is
actually just a hobby. I iave no intentions of qy
Another thing to learn about. > Figure it cost for to make it else make it for If they do lot of business with you, at > point, a VP or GM is going to look at the amount are paying you and say > 'why are we paying so much for we build ourselves reduce > cost'. For example, if your feature took you 1 man-year to develop and a customer is buying 20,000 license/year, they are paying They > may figure can pay someone to build for for $100,000 see > beginning in only year. This would be hard, because health care changes all the time and new words are quite invented daily. largely automated ingestion filtration new words, but take a few hours of effort keep on top of it. (At the end the day, human has to determine what's real what isn't. There's a surprising number of typos misspellings in peer-reviewed journals.) So it's not necessarily a set-and-forget, but the data gathering, normalization, basically is. It would virtually no sense even very company develop this In fact, most large companies don't pay for spell check software all. (C.f.: lots of misspellings in peer-reviewed articles.) But there market it. An EMR was the first to me; suspect they don't have because alternatives up. WAS about an unlimited site Say you're an EMR company, you have 300,000 licensed dunno $50K/yr max, and you can integrate it as many instances of your software as want. Exact figures would need to be thought about more. > If is a to entry, be alert for competitors. Bank a > of the revenue. receptive to exiting. I've thought about the exit angle. would offers. But is actually just hobby. I have intentions of qu
Another thing to learn about.

> FIgure out whAt it wOulD coSt For tHem tO make it themselVEs or Have someone
> else to make iT for tHeM. if thEY dO a lot Of businESs WITh yOu, At SomE
> pOInT, a VP oR GM Is going To look at thE amOuNt they are payINg You and say
> 'wHy aRe we paying so MucH for thIs, We sHOuld bUilD it ouRselveS And redUce
> cost'. FoR eXAmple, iF Your feaTURe Took You 1 man-year to develOP aND a
> customer is buYing 20,000 liCeNSe/YEAr, tHey Are paying $100,000/yEaR. They
> MAy figurE ThEY CAn pAY someone to buiLd it for them FOr $100,000 aNd see aN
> RoI bEGinninG in onLy ONe yEar.

This woulD be hArd, becausE healtH Care chaNGes all tHe time And New WordS ArE
qUitE lITerALlY inVEntEd daily. I HaVe LargeLy auTOMATed tHe iNgesTion aNd
filtration oF neW worDS, buT it doEs takE a feW hOurs oF efforT everY wEek to
keep on top oF it. (AT the end of The DaY, a hUmAn has TO deterMinE whAt's
real And what ISn't. thERE'S a Surprising number of TyPOS aNd misspeLlings IN
pEeR-Reviewed JoUrnAls.) SO IT's not NeceSSaRily a set-And-forGEt, BuT the
datA gAtheriNg, NorMalIzatiON, and SortinG basicalLy is. IT Would make
virtuALly no sense for EVeN A VeRY larGe cOmpany to devElop THis iNterNAlLy.
IN Fact, mOst laRgE CoMPanies don't pay for speLl Check sOftwaRe at all.
(C.f.: lots Of misspellINGS in peer-rEvieWEd ARticles.) But therE _is_ a
mArket for it. aN EMR compAny waS the firsT to contacT ME; I suspecT thEy
dOn't HavE EXiSting solutionS, BEcauSe The alteRnaTives arE $60/seAt aNd uP.

I WaS Thinking aBout an unLiMiTeD sIte LicenSE. Say you'rE aN EMr cOmpAny, anD
You havE 300,000 liceNsed InStALlaTions... yoU PaY ME I duNnO $50K/Yr maX, anD
yOu can InteGRatE it into As many insTanCEs of YoUr SoftwarE as you want.
ExaCt Figures wouLd NeeD to be tHOUght abouT more.

> If there is a low barriER to entrY, be Alert For cOmpetitorS. BaNk a porTioN
> Of the rEvenue. be recEpTivE TO exitING.

I'Ve tHoUght about tHE ExiT anglE. I WoulD considEr offers. But this is
aCTuaLly just a hobby. i haVe no INTeNtiONs OF qu
Another thing to learn abo ut.

> Fig ure o utwha tit w ould  cost for them to m ake it themselves or h ave s om e one>  e lse t o makei tf o r t he m.  If  t h ey  do a  lo t of bu siness wit h y ou , at some
>p oi nt, a VP o r G M is going t o l ook at  t hea mount  th ey ar e payi n g youand say
>  ' w hy are we payi n g  s o mu ch for this, we s h ou l d build it our selves  a n dr e duc e
>  cost'. Fo rexamp l e, if y o ur f e atu r e took you 1man-year to dev elop a nd  a>  custo mer i sb uyi ng 20,000 l icen se/year,they a r e payin g  $100,0 00/yea r.The y
>m ay  f igu re the y  c anp aysomeoneto  b uildit f o r t hemfor  $10 0,000  and see an
>  RO I be g inn ing i n onl y on eyear. 

This  woul dbe hard, becaus e he alth care  ch an ges  a ll th e  timeand  ne w words  are
qu i teli t e r al ly invented daily.  I h av e largel y auto m at ed the inge st ion  and f iltra tion of  new wor ds, bu t  i tdoes ta ke  a few  h our s o f eff o rt e very w eek to
k eep o n  top of it. (A t  the end of t h ed a y, a hu man  has to det ermi n e wh at's re ala nd wh at is n' t .T here's a surprising  n umberof ty pos and missp ellings in p e er-revie wedj ou r nals.) So it's  notnecessaril y  a set-a nd-fo rget, bu t the
dat a gatherin g,nor mal iza t i on , and sorting b asic al ly is.Itwould m ake 
vi rtu all yno sensefor even  a  v er ylar ge co m pany tode vel op  th is in t ernall y.
In  fac t,  m o stlarge c o mp a n iesdo n' t pa y f or  spel l ch e cksoftwar e at all. 
(C . f.:lo ts  of mis spellings inpe er-reviewe dart icles. ) But ther e _is_ a
market for it. An EMRcom panywasthe first  to  conta ctm e; I s uspect  they 
d on' t havee x is tin gsolutions, b eca use t he  alt ernativ es are $60/seat an d  up .

I WAS thin kin g ab o u tanu nl i mit ed sit e license. Say yo u're an EM Rc om pany, andy ouha ve 300, 000 lic ensed install ations...  you payme  I d u n no$50K/yr ma x, and
y ou can in t egrat e  i t int o a s many  i nst ances  of yo u r s oftwa re asyo u want .
Exa ct  figures  would need to be thoug ht abo ut mo re. 

> If th ere isa low bar rier  to entry,  be  al ert f orc ompet itor s .Ban k  a po rtio n 
> of the re ven u e .Be receptiv e t o e xitin g.I've t houg ht about the exit angle. I would  con s i der  of f ers.  B ut this is
act ual ly j ust a ho bb y. I have n o intent io n s ofqu
Another thing_to learn_about.

> Figure out what_it would_cost_for them_to_make it themselves_or have someone
>_else to make it_for them. If_they_do a lot of business with you, at some
> point, a VP or GM_is_going to_look_at_the amount they are paying_you and say
> 'why are_we paying_so much for this, we should build it_ourselves_and reduce
> cost'._For example, if your feature took you 1 man-year_to develop and a
> customer is_buying 20,000 license/year,_they_are_paying $100,000/year. They
> may_figure they can pay someone to_build it for them for $100,000_and see an
> ROI beginning in only_one year.

This would be hard, because_health care changes all the_time and_new words are
quite literally invented_daily. I have_largely automated_the ingestion and
filtration_of new words, but it does_take a few_hours of effort every week to
keep_on_top of it._(At_the_end of_the day, a_human_has to_determine_what's
real and what isn't. There's a_surprising_number of typos and misspellings in
peer-reviewed journals.)_So it's not necessarily_a_set-and-forget, but the
data gathering,_normalization, and sorting basically is._It would make
virtually no sense for_even a_very large_company to develop this internally.
In fact, most large companies don't pay_for spell check software at all.
(C.f.:_lots of misspellings in_peer-reviewed articles.)_But_there _is_ a
market_for_it. An_EMR company was the first to contact_me; I_suspect they
don't have existing solutions, because_the alternatives are $60/seat_and_up.

I WAS thinking about an unlimited_site license. Say you're an EMR_company, and
you have 300,000 licensed_installations..._you_pay me I dunno $50K/yr_max, and
you can integrate it into_as many instances_of your software as you want.
Exact figures_would_need to be thought about more.

>_If_there is a low barrier to_entry,_be_alert for competitors. Bank a_portion
> of the revenue. Be receptive_to exiting.

I've thought about the exit angle. I would_consider offers. But_this is
actually just a hobby._I_have_no intentions of qu