(public).sospep.systems ~ view step ~ 010-founder

<h1 style="text-align: center;">STEP - 010</h1>
<ol>
<li>] ANSWER:</li>
<ol>
<li>[ a long time ago ] spending more then I earned, built a personal financial management system with spreadsheets(my first tech love)] </li>
<ol>
<li>] PROBLEM: keep in mind, this was when lotus 123 was still the king of the spreadsheet and I don't think Quicken even existed yet.&nbsp; It was easy to create a "budget" on paper (which is what i had,&nbsp;but tracking your expenses was a bit of bear), then i discovered personal computers and spreadsheet software.</li>
<li>] SOLUTION: from a&nbsp; monthly budget on a&nbsp;sheet of paper to a real time, budget forecasting, expense tracking, variance reporting, income tax calculating personal money management behemoth of a workbook.</li>
<li>] the monthly sheets soon fed into an annual sheet where i could ...</li>
<li>] the annual sheet then fed into the Tax Return sheet which calculated the amount of tax refund | tax due&nbsp;based on the income earned/taxes paid to date, as well as the optimal amount of RRSP(CDN retirement plan) contribution</li>
<li>] URL: no,&nbsp;( i *could dig up the files, find a copy of Lotus 123, a pc that would still run lotus 123, ... )</li>
</ol>
<li>[ more recently ] - Worked as a customer support agent - built a support case documentation tool for the team</li>
<ol>
<li>] PROBLEM:&nbsp;the CRM tool that the team used to document support calls/cases just used&nbsp;an open text feild&nbsp;for capturing an&nbsp;agents "case notes". The "case notes" that support agents entered were highly inconsistent and varied from the "line of text" guys/gals, example "cust called with problem on 635 model, assisted and fixed problem" which provided almost no useful information to the "wall of text" guys/gals where&nbsp;all ... many of the important details may be&nbsp;included in&nbsp;the notes, but the time to parse them out of the "wall of text" could become be problematic, time consuming</li>
<li>] SOLUTION: I&nbsp;built an html (app) that agents could use to gather and document all of the case details (&nbsp;issue, product info, product model details, related products,&nbsp;troubleshooting steps and resolution). All support agents were now able to gather the same details and the details were formatted in a consistent&nbsp; manner. The app was not integrated with the CRM tool, so it exported the output to a text file which the agent could then post into the open text field of the CRM tool</li>
<li>] URL: no, but i have this on disk and can demo* it, (*it requires internet explorer and uses active x&nbsp;)</li>
</ol>
<li>[ lately ] &nbsp;</li>
<ol>
<li>]</li>
</ol>
<li>[point - why I chose these 2 examples]</li>
<ol>
<li>] both systems were fairly complex, both had&nbsp; a good deal of functionality, both took a fair amount of my time to build and I built them both because&nbsp;I wanted/needed them. Neither were built with any intention of making money,</li>
</ol></ol></ol>

~ view step ~ Procedure] 001-application-questions-ycombinator FROM [ App] project-accelorator-application IN [ servers] prj-022-sospep