Oh Crap I Need an App: The Adventures of a Non-Geek Entrepreneur Trying to Get an Application to Make Her Web-Based Business Idea a Reality by Casey Burke Bunn

Author:Casey Burke Bunn
Language: eng
Format: mobi
Published: 2014-03-27T00:00:00+00:00

21 Yet another Setback

With the Weaslette threat swept under the rug, I moved on to the excitement of a TV appearance. Because I had helped the TV station with their events, they offered me a segment on their morning show a month before my wedding. I had an opportunity to go on and talk about the website and functionality, and tell the whole world that I could use it for my own wedding.

I was a guinea pig for my own product, and used the service for the engagement party, the rehearsal dinner, and the wedding.

While the show went great, it did not drive a ton of traffic to the site. I was actually grateful for this because we were shaky and very manual, not yet a product in which I had confidence. I was, however, happy with my interview and with the video the station provided, which I believed would someday help build credibility for a product that actually worked.

Time rolled on and still Twit was not done.

Surprised?

My insider told me about the staff meetings where the president of the company was complaining about the work to get my project done. The designer, we will call him Gabe because he was like an angel, once took a vacation to New York during my project. He was my only hope when something went wrong. A client would call me desperate for a fix, and because I was not technical there was nothing I could do except panic and pray I could get hold of Gabe to save me.

Gabe helped me on his vacation, late into the night, trying to figure out issues and fix things himself. He cared about the application and he was my saving grace. When the bugs were still rampant Gabe helped me set up my wedding pages too. Without him, I would not have been able to use my site for my own wedding!

I documented all of the emails from Twit saying it would be done in two weeks, and in two more weeks, and that it would be done in two weeks, and in another two weeks…

I began to think it would never be done.

My board was getting antsy too. We had a meeting to test the user interface. It did not go well, so they asked me to have a technical review of the code done. The review came back that the code was “spaghetti” which basically means poorly written and not scalable.

Oh woe is me!

In early October, after nine plus months of working with Twit, I fired him too!

I took a board member with me to do this, along with all of my documentation, which filled an entire binder. I spent 12 hours before this meeting, highlighting items and printing off emails, progress promises and documentation on conversations. I wrote a letter so that I would not forget anything that I needed to say to Twit. It helped me to be concise and speak with less emotion. It caught him totally off guard.

We were sitting at the same round table in the cozy green room where it all started, just the three of us.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.