Reduced Layers
To control costs and increase likelihood of project success we put software stakeholders
in direct contact with actual engineers. Rather it is via email, ticket tracking
system, or instant messenger, keeping the developer close to the end software
user is considered very important to us.
RFPs
We don't respond to RFPs. These are giant time drains on client and vendors. The
only people we have seen that win RFPs are the people that drafted the RFP or
big companies with $175 hourly rates that can afford to pay people all day
responding to these things. If you would like an estimate on your project,
we would be excited to provide it, we only request that you meet us face to
face. If you put the effort into coming to our office, we will help estimate
your project.
But I want it fixed cost.
I will explain why you don't really want this. No one, including me, Micajah staff, you, your brother really know
what your software project is going to cost. There are too many unknowns and variables on any project to really know. We can
get decently close and get some reasonable range in place. If you demand a fixed cost bid, which Micajah will not provide, there
is only one real thing the vendor can do, which is, pad the hell out of it. Out of the gate, there are three scenarios: a.) the vendor
makes a windfall profit b.) the vendor looses money c.) the vendor guessed very very well (unlikely).
On day one your project starts. On that very day, the instant you signed development documents, you and the
developer are pitted against each other. You now have a locked in price and want to get in as many "must have" features
as possible and the developer is trying to do a little work as possible and collect their check. Maybe a few of these
type deals have worked out, the majority do not work out well for one or both parties.
Okay, if not fixed how do I protect myself?
There are two primary ways you can protect yourself here...
Cut the features to the core, then cut them again. Any idiot can sit around and think of a new feature, or say "we need this thing
like facebook has". A genius is able to sit in the room and say "what is absolutely critical to deploy this app on day 1", (like Steve Job genius)
If you want to be the smartest guy/gall in the room, go work for Goldman Sachs. If banking is not your gig and you find yourself
on a software project, then cut the development features to the absolute smallest minimum function that will do a real unit of work.
Don't be that tard that sits in the room and say "it would be cool if..."
the other option ...
Break into Chunks.Take your project and break it into small deliverable chunks. When the developer finishes that chunk, pay up, and move to the next
chunk. Say you have a development range of 100-150k, maybe break into 10K chunks. Two weeks of work is another good way to divide. This method keeps your and the developer's interest
aligned. The developer needs you to be happy to keep authorizing more chunks. You need the developer to be happy so he answers the phone when you call.
If a person or company can write software at any level, chances are they are not starving. Withholding payments or strong arm tactics are very
rarely going to get you where you want to be, unless the other guy is going to loose their house and kids if they don't comply
It has to be Win-Win. I know the phrase is played out. Clients and
vendors really need to figure out ways to structure agreements in which both
parties interest are aligned in the deal. Fixed costs projects will have you pitted against each other no
later than immediately as you sign the
docs.