Two weeks. Two people. That’s all we had to finish our first major project. It was our first shot as a new company. Talk about jumping in the deep end. To make matters worse, we were making a day trading bot platform. The stars were aligned for our failure. Even I was skeptical of our success at the beginning of that fortnight of hell. But to everyone’s surprise, including my own, we made it.
This mad pace? This mad rush? This is how we handle every project. It doesn’t matter if we have two months or two years for a contract. We always compress the bulk of the work into a super short timeframe. Why? Because mindset.
Traditionally, tech people take things slow. Software can be made quickly, but few do it this quickly. Because if we left engineers to their own devices, the Model T would never have come off the assembly line. We technical folk love tweaking, optimizing, and analyzing. Which has its place, but that’s not all that matters.
Early on, we realized the importance of agility. Because we had no idea what we were doing. So we were bound to get into sticky situations. And everyone who’s ever been stuck in one of those knows this well: When something’s not working, you need to jump off the ship as soon as possible. But if it’s working, you should also be able to add fuel to the fire. It’s all about flexibility. Nimbleness. This would be our top advantage. Google can’t do that. They have thousands of engineers to manage. But we can chase opportunities as soon as we see them. Quick feedback loops, short build cycles, and a lineup of decent ideas? That’s a recipe for success.
How do you increase success? Increase delivery. Take more clients. Build more products. Deliver better features. It’s all about delivering. And that’s why we decided to move fast from day one. In my tech company, we optimize for speed and completion, not perfection or performance. In fact, refinement is almost always attacked and rejected. Because if your product is refined, and it’s a new product — which is almost always the case for us — that means you’re releasing too late.
That’s how we move fast even when making something as complex as trading bots. Sounds sketchy, but we just focus on getting the job done rather than doing it well. Just get it done, and worry about it later. Sure, some things aren’t optimized. And maybe a minor bug finds its way to a customer, once in a while. But I think of it this way: If it weren’t for you, your customers wouldn’t have a product to use at all. Isn’t buggy better than nonexistent?
P.S. Interested in what we’re building? I’d link a landing page, but we just started making it today. Give us a minute.