SAAS bloody weekend

"I wanted to take a quick dip in the pool but ended up drowning instead in the middle of an ocean." =(

That's what I told my mom when she came to the room a moment ago asking what's going on with me. I haven't showered, haven't gone out for 2 days now. I've just been here in front of my laptop staring at this giant spreadsheet full of numbers. A whole world of numbers and percentages. I'm mesmerized, intrigued by all this information but at the same time overwhelmed. You can drill down on almost every aspect and get confronted with all sorts of details. And there's just no end to it. 

My deadline for this report is later tonight, but I am nowhere near completion. 
I am more pressured now because I've promised that by hook or by crook we're gonna deploy by July. But this Numbers file is key to that, and here I am hopelessly stuck. 

TBH, designing the product was much easier. It's the love of my life. I dream about it even when I sleep. I can visualize every report it generates, every use case, every lingering bug.  I've memorized all the remaining features prior to phase 1.5 and beta launch. 

But creating a financial model for it is another thing altogether. 
The other night I spoke to my friend/colleague T and he reminded me about my MBA -  with that background things should have been easier, shouldn't it? 

But uhm, we didn't learn about churn, about MRR, about tactics for user conversion for SAAS products in MBA class. When forecasting traffic and how much of this will lead to signups -- which figure do you start with? Should you reverse calculate and start with bottomline? 

I'll write about this soon, perhaps when I've reached the final point. I'll share more about this experience. Who knows this will be successful? I'll go back to this post and talk about perseverance and staying sane through it all. Meanwhile, brb.