Share the work with a team of professionals, instead of staffing a projects with resources.
StarterSquad works primarily for startups, and because we keep the same team together for multiple MVP's we don't waste time sandboxing over and over again.
Getting a team to work well together is a tough job that takes time and dedication. We have already done that job for you. Having skilled professionals in the team is half the job. Knowing each others strengths and weaknesses is the other half. Have a look at our profiles and feel free to connect.
Hiring developers is hard and risky. If you sign with someone that doesn't fit the team you risk losing a years salary on the bad decision. StarterSquad sells capacity to clients on a week by week basis: you never risk losing more than one week of budget. You have more room to experiment and learn before committing to your own staff.
Getting a team up to speed takes time and effort, which you'll be paying for along the way. StarterSquad teams have been working together for longer periods before you buy their capacity, so they will hit the ground running. This means you can get something done quickly, and then reserve budget until you're ready for your next experiment.
We work for startups only, keeping the team together for multiple engagements. We believe in openness, collaboration and learning. We're a stable team, at high velocity. Add your work to our TODO list and we'll crunch through it like a well oiled machine. You can share work with a team of professionals, instead of staffing projects with resources every time. Your organisation stays lean, while we stay agile.
By doing many small, cutting edge projects in short succession we are forcing ourselves to adapt to change every day. This keeps the team agile and up-to-date.
We’re spread all over the world, we work from our homes or inspiring locations of our choosing. Dragging a ball and chain to the office is so last century.
We believe that your best work happens when it happens. This might be Sunday morning at 6 when you’re running in the woods, or while having a long afternoon tea. Or at your desk around 10 on wednesday morning. You know this better than anyone else.
A project we take on as a team should be rewarding to work on. Life is too short to configure WebSphere, no matter what the pay.
The Technical Feasibility Scan is a perfect tool for startups in a (seed capital) funding round.
Together with the trackrecord of Iwein and the Startersquad team it convinced our investors that our IT roadmap is feasible within planning and budget.
A week ago I stumbled on an interesting article by Petri Kainulainen about estimations. It argues that because estimations are invariably going to be wrong, you should stop doing them. In fact they can be counterproductive because they trigger gaming instead of adding value. I believe this is true to some extent, although I also believe you can do valuable estimations of risk and effort, as long as you don’t let them interfere with your goals by letting them cause gaming.
The thing that Petri didn’t mention, but is all important in my opinion, is that development cost are only a marginal part of the equation. In other words, we’re estimating only a small part of the costs.