It’s been a few years since I posted in this thread. Re:
Currently I have two businesses that are about to merge with a larger company that specializes in REIT's and TIMO's. One company is TU, which is currently getting a facelift and should have a new design in two weeks. The other is LL, which should be out by the time the good Lord returns, because my programmer (php) has over committed himself.
TU addresses the issue of helping educate landowners in proper timber management and sustainability, while also connected them with reputable timber companies (also an issue in the industry), while Logger Log is a smartphone app that tracks timber from the landowners property to the mill and updates all of the essential data in real-time.
TU is in it's infant stage, so any advice/help in the SEO department would be greatly appreciated. LL should sell itself and with the connections I'm getting with the larger company, I'm not really worried about getting the word out.
I'm at the beginning of this journey, as these are my 2nd and 3rd ventures. My first was
www.realcreate.com, but that burst with the real estate bubble. Timing as they say, is everything.
tl;dr - This year we’ve done $147,000 in sales and if nothing changes (meaning even if we don’t add a single customer) we’ll do a little over $350,000 in sales next year. And we’re currently in talks with another company that wants to test it with one of their crews, which would push our sales to over $1,000,000 next year.
PART 1
To give some context, LL is enterprise software for the timber industry and at this point we’ve spent over 4 years pursuing it. We spent the first 3 years with one guy and pushed out a web app and two android apps, which eventually sputtered, and 1.5 more years going back to the drawing board, raising startup capital, and doing things “the right way”.
In the quoted post I mentioned that our developer for LoggerLog had overcommitted himself and was moving slowly. This trend continued and really never remedied itself. I think this occurred because of two major issues that I’m sure most startups make:
- We hired poorly
- Our developer already had an app on the market that was bringing him cashflow, so he didn’t need our app to be successful. He was already content and that’s bad.
- We traded him equity up front in exchange for his time, which created a huge issue six months into development, where he was less-and-less motivated to work. He was already vested and wasn’t getting paid, so it’s understandable. Giving up leverage up front is bad. Don’t reward people for doing nothing, reward them for doing good somethings.
- He was a back-end-only guy, who tried to wear the designer hat, didn’t ask for help when he needed it, and made way too many executive decisions. He was sort of a loner who didn’t work/communicate well with others. He was a super nice guy, but lacked process.
- He didn’t develop on a framework, which bit us on the ass over-and-over again. Spaghetti code is bad.
- We didn’t spend enough time planning
- I took our developers word on a lot of stuff and chose to be lazy instead of being diligent and checking up on him and his work. This was exacerbated by his lack of willingness to communicate and propensity to get red-faced if he was questioned.
- We didn’t integrate the design/development process until later in the dev process, which should’ve been done up front. It also tangled up in our hire, where our developer refused any changes and took any suggestions as a direct insult.Which, ultimately left us with an interface of Frankenstein proportions.
- Scope creep. When you don’t have a design and someone’s building software based on assumptions and what you tell him, you’re going to have scope creep. You’re going to have some much mf’ing scope creep you’ll think it’ll never end. It won’t.
The first mistake lended itself to the second mistake. I still remember the day we met with our developer for the first time, presented our site-map and a simple user-flow, asked if he had any questions, and he responded, “Nope. I got it! I’ll get started right away.” I still remember being shocked and confused by the response. “Really? You don’t have a single question? This is pretty extensive software…” I do, however, remember my dad being impressed and excited by the response, which I think was due to his lack of knowledge around software design/dev more than anything.
This sort of shoot-from-the-hip attitude quickly became the norm and about a year later we were trying and failing to onboard our first customer. I think it was around the Summer of 2014. My dad and our developer went to meet the customer in person and get him started. Everyone was excited and I was waiting to get a phone call talking about a successful launch. To make a long story short, our developer couldn’t even get him signed up. To this day I cannot comprehend how this even happens, but I’ll point again to #2 on the “major issues” docket.
About 6 months prior to this we’d totally redesigned the site and hired a front-end guy to come in a put the UI together. Before this, the software was a total clusterf*^$ and nearly impossible to navigate, so it was a necessity. I spent a lot of time with a designer getting everything right and then again with the front end guy to get it translated. Once we got it into the hands of our developer, he totally half-assed the integration. I was pissed.
When I called him on it he was legitimately shocked. I couldn’t believe it. He insisted that he’d done his best, wasn’t a designer, wasn’t a front end guy, and had been left holding the bag to get everything done and out the door. Mind you he never asked for help or direction during the integration, did it all in one foul swoop, and then cried foul when I got pissed. It was at this moment that I knew we were fucked. I guess what I felt is the same thing people feel when they realize they’re in a shitty relationship for the first time.
If I questioned his design choices, he’d get mad and say he wasn’t a designer. When I presented him with designs, he’d half-bake them into the software no-questions-asked and then get mad when I questioned them. The weirdest one was the whole design thing, because he would insist he wasn’t a designer or a front end guy and then lose his mind if I was critical of design choices or front end dev. Anyways, I realized that this was a bad cycle that was only going to repeat itself.
After the failed launch, I upped my cries for parting ways with the developer, which had only been subtle suggestions up until this point. It probably took 3-4 months for my dad to get onboard with the idea. You see he’d been the one going to the developers house everyday to motivate him to work, make sure things were getting done and hold him accountable. I’m not shitting you. My dad went to his house everyday, because if he didn’t, nothing would get done. Work only got done when my dad was there.
My dad didn’t want to split with the developer, because he felt like we’d come so far and actually and had something going. I mean we had an MVP of sorts and people wanted to use it. It kinda drove him crazy that it was always so close to being finished, yet so far due to design flaws in the system. I told my dad, as many times as it took, “Look, I get it. We’ve come a long way and we kind of have a system here, but we tried to launch it with someone and he couldn’t even get them signed up! What’s going to happen the next time? Why would we expect things to go differently when nothing is going to change? If we don’t do something different we’re going to hurt our reputation.”
My dad’s fear did have a point. The longer you take to release something, the more opportunity there to lose that opportunity. But, the risk to move forward with our developer was too great. So, we split ways and started looking for funding. For what it’s worth, on top of the total shitshow that our dev cycle was, our developer was going through a divorce, so I’m sure that added to his woes and created issues that wouldn’t have otherwise existed.
When it was all-said-and-done I think we were out $20k over a couple of years, which isn’t bad. And we also had a really good idea of what we needed to do. We’d built a couple of mobile apps based on field tests and they were really good prototypes. We’d also attended a couple of big industry meetings in 2013/2014 to get a feel for demand and there was definitely a growing need for what we were building.